Inkscape Wiki - User contributions [en]

Extension requirements

2006-09-15T04:39:26Z

Craig9: Fixed mac link, warning about win link (can't find correct page)

<b>Setting Up Effects in Inkscape</b><br>
<i>For effects to work you need to be using inkscape .42 or later.</i><br>
<i>For info about what effects can do, screenshots, and how to make your own go to [http://www.ekips.org/comp/inkscape/ Aarons Site]</i><br>
<i>See also [[GettingExtensionsWorking]].</i><br>

<b>Unhide the Effects menu</b><Br>
- On the "Misc" tab of the "Inkscape Preferences" dialog check the box labeled "Enable script effects" (0.41+CVS onwards only)
- Close and reopen Inkscape

<b>Python Effects</b><Br>
<i>on Debian GNU / Linux</i>
- apt-get install python python-xml

<i>on Microsoft Windows</i>
- [http://www.inkscape.org/cgi-bin/wiki.pl?GettingEffectsWorking/Windows Tutorial on Getting Effects to work on Windows] (broken link)

<i>on Mac os X</i>
- See [http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX Mac OS X compiling page] (at the bottom)

<b>Perl Effects</b><br>
<i>on Debian GNU / Linux</i>
- apt-get install perl libxml-xql-perl

<i>on Gentoo GNU / Linux</i>
- emerge -a XML-XQL

<i>on Microsoft Windows</i>
- install [http://www.activestate.com/Products/Download/Download.plex?id=ActivePerl [[ActivePerl]]]
- install XML::XQL::DOM (perhaps like this?)
1: install prereqs with ppm:
install xml-dom
install parse-yapp
install datemanip
2: download xml-xql from:
http://www.cpan.org/authors/id/T/TJ/TJMATHER/XML-XQL-0.68.tar.gz
3: open command prompt and locate perl"s lib directory with:
perl -e "print qq(@INC)" (mine was C:[[/Perl/site/lib]])
4: unpack xml-xql archive
5: copy contents of XML-XQL-*\lib\XML into C:\Perl\site\lib\XML
6: copy XML-XQL-*\XQLParser\Parser.pm to C:\Perl\site\lib\XML\XQL

<b>Plugin Effects</b><br>
- I have absolutely no idea. Please record your success here. :)

<b>What if it doesn't work?</b><br>
- Run Inkscape from the console
- Use the error messges printed to the console to diagnose the problem (very often missing dependencies)
- On Windows you will have to redirect output to a text file like this: "inkscape > output.txt"

Translation information

2006-09-01T17:31:43Z

Craig9: /* Community based, user oriented */

== Introduction ==
=== Community based, user oriented ===
The translations of the various documents focusing on Inkscape rely on the work of volunteers.
Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes.
It is very important not to forget that Inkscape is an open source, community based and user oriented project, which implies that software developers/contributors are generally users. It also implies that the translation efforts are user oriented, with a strong focus on interface, user documentation and website.

=== Guidelines/workflow ===

# '''Contact to a local translation group, to get support and help on your language'''. Rather than working alone, you should work with an experienced translation team for your language. Thus you will benefit from their knowledge, as well as being able to communicate with them on your own mother tongue. Moreover, translation teams use to have style guidelines and a standarized vocabulary for technical terms that you should be aware of. There may be many communities working on translations for your own language, but a good starting point is subscribing to your local [http://developer.gnome.org/projects/gtp/teams.html GNOME translation team] or [http://l10n.kde.org/teams/ KDE translation team].
# '''Subscribe to''' [https://lists.sourceforge.net/lists/listinfo/inkscape-translator Inkscape translator mailing list]. By subscribing on Inkscape's translator list you will be able to ask for help on some questions more related to Inkscape issues to other Inkscape translators, as well as the mantainers.
# '''Get files for your language'''. If you only want to translate the interface messages, you can get the files from [http://svn.sourceforge.net/viewcvs.cgi/inkscape/ Inkscape's svn repository web interface]. Besides getting files from web interface, you can obtain the full repository; instructions on how to do this are found [http://inkscape.org/svn.php here]. See section [[#Translatable_content]] for which files you have to modify to translate each part of Inkscape.
# '''Submit finished work to patch tracker'''. Finished translations must be sent to patch tracker and/or mailing list in order to be integrated into the trunk. You will need a Sourceforge.net account to commit patches to [http://sourceforge.net/tracker/?group_id=93438&atid=604308 Inkscape's patch tracker]. Before sending a file, remember to check that the file(s) you are submitting doesn't have syntax errors that would break the building process.
# '''Send a mail on the translator mailing list'''. Your contribution will be reviewed/commited as soon as possible.

=== Best practices ===

* Best case for a good translation: translate from English to your mother tongue.
* Test the behavior of the interface before starting translation.
* Several small updates are more efficient than only a big one.
* If you're new to Inkscape, or to vector software, taking a look at [http://wiki.inkscape.org/wiki/index.php/InkscapeTerminology Inkscape Terminology page] can be a good idea. It is a work in progress, but can give some clues on basic vocabulary of Inkscape.
* Some good explanations of the behavior of Inkscape, also using some reference terminology can be found here: [http://tavmjong.free.fr/INKSCAPE/MANUAL/html/index.php A Guide to Inkscape] and [http://wiki.inkscape.org/wiki/index.php/UserManual User manual].
* Always keep in mind consistency of terminology; a simple, precise & explicit vocabulary/style will result in an efficient and thus good translation.
* Don't hesitate to ask others (developers/translators/users) if you don't understand a word/sentence or if you think an original string is not good (too complex, not precise enough, etc.).

=== Polishing Translations - Microtypography ===
Here are some things to note in order to achieve good microtypography (typography at the word or character level).
* use the proper quotes (e.g. »foo«)
* use the proper kind of dashes (with the proper amount of whitespace around them) - EN DASH (U+2013): "–", MINUS (U+2212): "−"
* use non-breakable space where appropriate (e.g. before units; some countries use a halfspace here) - NO-BREAK SPACE (U+00A0): " "
* use halfspace where appropriate (example: "z. B.") NARROW No-BREAK SPACE U+202F: " "
* use "24×24", not "24x24"
* use "90°", not "90 degrees" where appropriate
* use the proper Unicode codepoint for "..." - "…". In German at least, a space comes before this ellipsis.

==== Links ====
* http://de.wikipedia.org/wiki/Typografie (German)
* [http://www.dante.de/dante/DTK/dtk96_4/Text/dtk96_4_neubauer_feinheiten.pdf Marion Neubauer: ''Feinheiten bei wissenschaftlichen Publikationen – Mikrotypographie-Regeln, Teil I''] (PDF, German)
* [http://www.dante.de/dante/DTK/dtk97_1/Text/dtk97_1_neubauer_feinheiten.pdf Marion Neubauer: ''Feinheiten bei wissenschaftlichen Publikationen – Mikrotypographie-Regeln, Teil II''] (PDF, German)
* [http://www.zvisionwelt.de/typokurz.pdf Christoph Bier: ''typokurz – Einige wichtige typograﬁsche Regeln''] (PDF, German)

== Translatable content ==

Inkscape's translation effort covers many areas, from aplication UI itself to web pages and tutorials. This is a summary of all those areas, sorted by priority.

These tasks, rather than being for hackers only, can be achieved by most software enthusiasts, whether they have a technological background or were just plain users. The main requirement is the wish to provide support for Inkscape on your language: the technology required for you to do that has been developed in a simple approach, and it involves mainly text files and applications used to verify its syntax. Supporting applications were existing to make these tasks much easier.

=== User interface ===

PO files contain the strings for the Inkscape user interface (main software and extentions). A PO file is a text file which contains the original English message and its translation. That's why it is obviously the translation to start with.

See [[InterfaceTranslation#Interface_Translation|InterfaceTranslation]] page for detailed information on the PO files.

=== Tutorials ===

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.
It is even a good opportunity for '''you''' to become more acquainted with Inkscape.

See [[DocumentationTranslation#Tutorial_Translation|Documentation Translation]] page for detailed information on tutorial translation.

=== Keyboard and mouse shortcuts ===

Inkscape is proud for having keyboard and mouse shortcuts for almost all of its functionality. Those shortcuts can help you increase your drawing productivity/efficiency. The map of the default shortcuts is embedded in the interface (help menu) next to the tutorials, and can also be accessed from the web site.

See [[DocumentationTranslation#Keyboard_and_mouse_translation|Documentation Translation]] page for detailed information on translating shortcuts.

=== Windows installer ===

High value for users, even if the installation process of Inkscape is quite simple, translating the Windows installer helps potential users a lot to get a good feeling when they use Inkscape.

See [[InterfaceTranslation#Windows_installer_translation|Interface Translation]] page for detailed information for Windows installer translation.

=== Templates ===

The default template of the Inkscape document can be localized to make the localization consistent. Localized can be the (size?) of the default document and also the name of the default layer.

See [[InterfaceTranslation#Default_template_translation|Interface Translation]] page for detailed information on default document's template.

=== Man pages ===
The man pages consist of a standard user documentation, available from the command line. On Unixbased systems simply type "man inkscape" from the prompt of a command window.

Some distributions also generate a browsable (html) man page, accessible from a dedicated help shortcut.

The man page of Inkscape provides some insightful information about the software, especially focused on operations that do not require GUI (example: export to png from the command line, or extract one object from a svg file).

See [[DocumentationTranslation#Man_pages|Documentation Translation]] page for detailed information for man page translation.

=== Release notes ===
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps the "normal user" to get a lot of insight into the capabilities of Inkscape.

* gives a general overview of the possibilities of the software to potential users
* can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

See [[WebSiteTranslation#Release_notes|WebSite Translation]] page for detailed information on translating release notes.

=== User manual ===
Some members of the Inkscape community are also focusing on an [[UserManual]]. This document can be read as a reference document for advanced users and as a good introduction to the functionalities of Inkscape by everyone.

See [[DocumentationTranslation#User_Manual|Documentation Translation]] page for detailed information on translating the user manual.

=== Web pages, News and Wiki ===
English is generaly the exchange-tongue of developers, and developer/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

You can take a look at the [[WebSiteTranslation|WebSite Translation]] page for detailed information about how to translate the web content of Inkscape

See the [[Main_Page|main wiki page of Inkscape]] to get some examples (Spanish and German) of the translation of this wiki.

=== Others ===
Text files found in the inkscape directory
...

== Status ==
See this [[TranslationStatus|dedicated page]].

User manual information

2006-06-26T14:33:57Z

Craig9: /* Where can I find the latest update? */

This is mainly a scratchpad to begin working out the [[UserManual]]. We can post ideas and fragments of text up here, but the real deal will be in CVS so that it can be checked out and worked on.

Other manuals and tutorials are [http://inkscape.org/cgi-bin/wiki.pl?OtherProjects#outsidetut listed here]

: Why not write the manual here? Use wiki as a versioning & collaboration tool -- that's what it's for :) You can then use a script to turn raw wiki pages into whatever format you need for the distribution

Currently in CVS there is a manual (or beginnings of a manual) that was written in French for SodiPodi. Has anyone looked at it? What are your thoughts?

* [[VectorAndBitmap]]
* [[IllustratorUsers|Inkscape for Illustrator Converts]]
* [[TricksAndTips]]
* [[KeyboardShortcuts]]
* [[InkscapeColor]]

We need to work now on an update of this Manual and have a specific version for Inkscape.

* Queries about Manual can be added here or sent to cedric@le-radar.com

== Inkscape tutorial paginated for printing ==

In SVG, each page is a layer. Make one page visible and others invisible. (The Wiki would not accept the PDF because the files are too big.)

These tutorials were adapted from Inkscape 0.41.

* upload:inkscape-tutorial-basic.svgz
* upload:inkscape-tutorial-shapes.svgz

== Where can I find the latest update? ==
* If you want to contribute, download the USER_MANUAL part of SVN
* If you just want to browse to find a subject, you can go to http://www.le-radar.com/?mm/inkscape_inkscape.rss and choose your language. It is the most up2date.
* An alternative, in-progress, unofficial version can be found at http://www.angelfire.com/mi/kevincharles/inkscape/

== How to Help ==

* Adding new information to the manual : write your files in docbook or in plain text that we'll convert (please follow [[Manualguidelines.html|guidelines]])
* translating pages
* contact a contributor or add your name in the follow list and have a look at the [[Manualwip.Html|WIP]]

* If you want to contribute, download the USER_MANUAL part of SVN
* To view actual state in html, type "make your_language" (notice that xsltproc is needed). If nothing is generated, it is that your language is actually not added to the manual. Thanks to begin one, ad become responsible for this part ;)
* edit the trunk/xml/inkscapeUTF.xml file. All languages are inside.
* Just read the file, choose the language reference you want to use (en, fr...) and translate by duplicating the node and changing lang attribute to yours.
* For pictures, you may use the "images/sshot_yourlanguage" directory or create it if necessary".
* when finishing editing, if necessary edit the Makefile and add your language to the Makefile. In every case test your file with some tools (xmllint...) or just type again "make your_language" : syntax errors will be displayed : please correct them.
* svn commit

== FAQ ==
'''Why is there only one xml file?'''
Because some experience show it is much easier to follow : the translator reads the text in the same time it is editing. But the day many languages will be added, it will be a need to produce a trunked manual file.

'''I try to validate the manual file and i get some errors corresponding the the language attributes.'''
Normal, some tags are not allowed to be repeated in the DTD (sect1 title for example), but having all language in one file makes it necessary. In this case, validate with the given Makefile that take this difference in consideration.

'''How can i produce HTML files from the XML one?'''
Type "make your_language" to have truncated html file (one file per sect1), or "make singleYour_language" to have all the manual in one html file.

'''Can i export to PDF?'''
yep. make a single html file (read above) and "make pdfYour_language". Dependancy to htmldoc. If anyone wants to work on a different XSL stylesheet that produce language specific XML file and use db2pdf, it is welcome.

== People ==
'''Cedric''' - main contributor - ''cedric at le-radar.com''

'''John''' - Author and French/British translation

'''Ernesto''' - Spanish translation - ''celise at prodigy.net.mx''

'''Antonio''' - Italian translation - ''antonio.angelo at poste.it''

'''Bryce''' - English translation/editing - ''bryce at bryceharrington.com''

'''Kevin''' - English translation/editing - ''inkscape.docs at wixsonit.com''

[[Category:User Documentation]]
[[Category:Needs Work]]

Output format requirements

2006-06-26T10:21:07Z

Craig9: which versions of illustrator store files as pdf

= Tips for getting Extensions to work =
Inkscape's extensions allow for importing and exporting non-SVG file types and direct editing of the current SVG document. For more information about the Extensions that appear in the Effects menu read [[GettingEffectsWorking]].

=== Open *.TXT ===
- install perl
- install SVG perl module

=== Open *.AI ===
- install perl and optionally Image::Magick
- Only handles Illustrator versions prior to version 9 (version 9 onwards stores files as PDF according to https://createpdf.adobe.com/cgi-feeder.pl/formats?BP=&LOC=en_US)

=== Save *.AI ===
- requires pstoedit with the ps2ai filter
- uses Inkscapes internal ps output extension

=== Open *.PS ===
- requires skconvert python script from sketch =>> install sketch

=== Open *.WMF ===
- requires wmf2svg, part of libwmf (http://wvware.sourceforge.net/libwmf.html)

=== Save *.PDF (Win32) ===
<pre>
- install [[GhostScript]] http://www.cs.wisc.edu/~ghost/doc/AFPL/get851.htm
- create ps2pdf.cmd in %instdir%/share/extensions/

REM BEGIN
@echo off
REM edit %GSDIR% to match the ghostscript installation directory
set GSDIR=%PROGRAMFILES%\gs\gs8.51\
set GSBINDIR=%GSDIR%bin
set GSLIBDIR=%GSDIR%lib
set PATH=%GSBINDIR%;%GSLIBDIR%;%PATH%
ps2pdf.bat %1 -
REM END

- edit pdf_output.inx

<inkscape-extension>
<name>PDF Output</name>
<id>org.inkscape.output.pdf</id>
<dependency type="extension">org.inkscape.output.ps</dependency>
<dependency type="executable" location="extensions">ps2pdf.cmd</dependency>

<output>
<extension>.pdf</extension>
<mimetype>image/x-portable-document-format</mimetype>
<filetypename>Adobe PDF (*.pdf)</filetypename>
<filetypetooltip>Adobe Portable Document Format</filetypetooltip>
</output>
<script>
<command reldir="extensions">ps2pdf.cmd</command>
<helper_extension>org.inkscape.output.ps</helper_extension>
</script>
</inkscape-extension>
</pre>

Roadmap

2006-06-26T09:54:57Z

Craig9: Tried to improve list formatting

== Inkscape Development Roadmap ==

NOTE: This is a working document showing specific near-term tasks needed for achieving milestones. The number in front of the version is in reference to the milestone.

''Milestones 0-9 have been completed since the start of the Inkscape Project. See [[OldRoadmap]]''

=== Milestone 10 - RFE's & Extensions Implementation - Inkscape 0.44 ===

New/Changed Dependencies
* (DONE) Add libcroco

Internals

* Implement extension API
* Implement extension registry
* Complete Extension preferences dialog
* (DONE) Reduce open/total RFE ratio to 55%
* masks/clippaths
** (DONE)Implement creation
** on-canvas editing
* Create an SPObject API for tracking references and avoiding id clashes on import and interdocument copy/paste. What we need are a void SPDocument::importCopies([set of SPObjects]), and an [set of SPObjects] SPObject::dependencies() method.
* Implement gradient UI "release" handler to deal with gradient garbage collection (see bug 984854)
* improvement of svg patterns UI - make it similar to gradient-drag, instead of piggybacking knotholder

RFE's
* [http://sourceforge.net/tracker/index.php?func=detail&aid=893812&group_id=93438&atid=604309 hyperlinking]
*(DONE, in .43?) tools: add/remove points on path, bezier drag

Maintenance
* Learn and use autoscan and autoreconf to find out which configure tests are still needed.
* Clean up configure.in
* (PARTIALLY DONE) [http://inkscape.org/cgi-bin/wiki.pl?DirectoryReorgProposal Directory Reorganization] (rejon)
* When run without installing, make it look for icon image file(s) locally so we don't get garbage icons

Testing
* (DONE) Implement tests of Inkscape against the [[W3C]] test suite [rick beton, bryce]
* Include some rendering tests in `make check'.

=== Milestone 11 - Import[[/Export]] Feature Enhancements - Inkscape 0.45 ===

* integrate [[Googles_Summer_Of_Code]] 2006 work, i.e. [[Filter_Effects|SVG Filters]] and [[User:Daleharvey|formalising the protocol for inkboard communication]]
* Make printing work more efficiently and reliably
* Enhance file manager
* PDF Export
* Investigate ps2ai, pstoedit and ai2svg conversion options (potential EPS support?)
* Import of native Adobe Illustrator files
* Other RFE's related to Import[[/Export]]
* Add extension for use of [[VDX2SVG]] (http://vdxtosvg.sourceforge.net/)
* Add extension for use of [[PDF2SVG]] (http://www.solidcode.net/pdf2svg/ - this doesn't actually link to a useful page)
* [[WebDAV/FTP]] support via GNOME-VFS, Neon, or the like

=== Milestone 12 - Style Refactoring - Inkscape 0.46 ===

* Eliminate use of the style.h types in as much of codebase as possible, particularly display/*.
* Change to use of GQuarks instead of #defines where feasible
* Editable toolbars (libegg)

=== Milestone 13 - Bug Hunt & RFE's - Inkscape 0.47 ===

* Reduce open/total RFE ratio to 40%
* Reduce open/total bug ratio to 5%

=== Milestone 14 - Drawing Feature Enhancements - Inkscape 0.48 ===

* Object-to-object snapping
* (DONE) Markers
* Enhanced grid system
* Inter-application cut-and-paste
* Inter-application drag-and-drop
* Clipart manager GUI
* Hyperlinking (Dupe? This is in milestone 10, too)
* (DONE) Load-from-URL

=== Milestone 15 - Style Rewrite & libcroco - Inkscape 0.49 ===

* Replace style.cpp entirely, with a clearer and cleaner version.
* (DONE) Integrate use of libcroco for handling Cascading Style Sheets.

* Palettes

(suggestion: having custom palletes, like from Gnome )
(suggestion: accuraced palettes from colour norms, like Pantone, Trumatch, Focoltone, Toyo, etc. (since lots of people uses it, specially professionally) - problem: some are patented/copyrighted, which seems each norm company like this must be contacted for authorization (?) - as well, is also an open-source colour norm standard welcome? (which works on both video/printing outputs, like Pantone seems to be?) )

=== Milestone 16 - Cairoification - Inkscape 0.50 ===

* Prereq: Is renderer immune to the same kinds of numerical problems we see with our new renderer, libnr, or libart?
* Create a Cairo-based SVG Canvas library

=== Milestone 17 - Animation Conceptualization - Inkscape 0.51 ===

* Prereq: We need a conceptualization of how it should work
* Currently, part of the concept discussion is at [[Animation-(Timeline)|here]]

=== Milestone 18 - Fonts Revisited - Inkscape 0.52 ===

* Reenable fuzzy font matching [bb]
* (DONE) Bidirectional text in Pango needs attention
* (DONE) [[MakeVertical]] in Pango needs attention

=== Milestone 19 - Palettes - Inkscape 0.53 ===

* Implement [[LittleCMS]] as color management system
* (DONE) Create a swatches dialog

=== Milestone 20 - Full Animation Support - Inkscape 0.54 ===

=== Milestone 21 - RFE's - Inkscape 0.55 ===

* Reduce open/total RFE ratio to 30%

=== Milestone [Future] ===
* Investigate performance measurement testing for Inkscape
* Convert all tabs into spaces (convert tabs to 4 spaces)
* Rename all '[[SPFooBar]]' routines to '[[FooBar]]' and put into namespaces
** (DONE) dialogs folder
* Investigate SVG docs where SVG is not the default namespace used at the root -- e.g. <svg:svg xmlns:svg="http://...etc"><svg:rect.../><blah></svg:svg> -- <blah> would end up getting shoehorned into the svg namespace
* Write an Internal DTD subset describing the custom Inkscape XML elements, for validation against SVG DTD
* Ensure Inkscape does not throw away the internal DTD subsets of documents it reads
* Start thinking about 1.0 when major functionality gaps are closed
** (BASICALLY DONE) layers
** (DONE) color palette
** (DONE) gradient tool
** mask tool
** (DONE) patterns
** (DONE) text on path and in shape
** (DONE) text selection
** perspective transforms
** SVG filters
** scripting
** path editing
** shaped strokes
* Implement preliminary support for iso & hex grid [njh]
* Implement perspective transformations via [[PerspectiveObject]]
* Improve freehand curve smoothness [pjrm, paraprax]
* Review X1-1GUITest on SF
* Review usability links at http://openusability.org/docman/?group_id=52
* Review usability links at http://openusability.org/docman/?group_id=57

[[Category:Developer Documentation]]

Roadmap

2006-06-26T09:47:26Z

Craig9: /* Milestone 11 - Import/Export Feature Enhancements - Inkscape 0.45 */

== Inkscape Development Roadmap ==

NOTE: This is a working document showing specific near-term tasks needed for achieving milestones. The number in front of the version is in reference to the milestone.

''Milestones 0-9 have been completed since the start of the Inkscape Project. See [[OldRoadmap]]''

=== Milestone 10 - RFE's & Extensions Implementation - Inkscape 0.44 ===

New/Changed Dependencies
* (DONE) Add libcroco

Internals

* Implement extension API
* Implement extension registry
* Complete Extension preferences dialog
* (DONE) Reduce open/total RFE ratio to 55%
* masks/clippaths
** (DONE)Implement creation
** on-canvas editing
* Create an SPObject API for tracking references and avoiding id clashes on import and interdocument copy/paste. What we need are a void SPDocument::importCopies([set of SPObjects]), and an [set of SPObjects] SPObject::dependencies() method.
* Implement gradient UI "release" handler to deal with gradient garbage collection (see bug 984854)
* improvement of svg patterns UI - make it similar to gradient-drag, instead of piggybacking knotholder

RFE's
* [http://sourceforge.net/tracker/index.php?func=detail&aid=893812&group_id=93438&atid=604309 hyperlinking]
*(DONE, in .43?) tools: add/remove points on path, bezier drag

Maintenance
* Learn and use autoscan and autoreconf to find out which configure tests are still needed.
* Clean up configure.in
* (PARTIALLY DONE) [http://inkscape.org/cgi-bin/wiki.pl?DirectoryReorgProposal Directory Reorganization] (rejon)
* When run without installing, make it look for icon image file(s) locally so we don't get garbage icons

Testing
* (DONE) Implement tests of Inkscape against the [[W3C]] test suite [rick beton, bryce]
* Include some rendering tests in `make check'.

=== Milestone 11 - Import[[/Export]] Feature Enhancements - Inkscape 0.45 ===

* integrate [[Googles_Summer_Of_Code]] 2006 work, i.e. [[Filter_Effects|SVG Filters]] and [[User:Daleharvey|formalising the protocol for inkboard communication]]
* Make printing work more efficiently and reliably
* Enhance file manager
* PDF Export
* Investigate ps2ai, pstoedit and ai2svg conversion options (potential EPS support?)
* Import of native Adobe Illustrator files
* Other RFE's related to Import[[/Export]]
* Add extension for use of [[VDX2SVG]] (http://vdxtosvg.sourceforge.net/)
* Add extension for use of [[PDF2SVG]] (http://www.solidcode.net/pdf2svg/ - this doesn't actually link to a useful page)
* [[WebDAV/FTP]] support via GNOME-VFS, Neon, or the like

=== Milestone 12 - Style Refactoring - Inkscape 0.46 ===

* Eliminate use of the style.h types in as much of codebase as possible, particularly display/*.
* Change to use of GQuarks instead of #defines where feasible
* Editable toolbars (libegg)

=== Milestone 13 - Bug Hunt & RFE's - Inkscape 0.47 ===

* Reduce open/total RFE ratio to 40%
* Reduce open/total bug ratio to 5%

=== Milestone 14 - Drawing Feature Enhancements - Inkscape 0.48 ===

* Object-to-object snapping
* (DONE) Markers
* Enhanced grid system
* Inter-application cut-and-paste
* Inter-application drag-and-drop
* Clipart manager GUI
* Hyperlinking (Dupe? This is in milestone 10, too)
* (DONE) Load-from-URL

=== Milestone 15 - Style Rewrite & libcroco - Inkscape 0.49 ===

* Replace style.cpp entirely, with a clearer and cleaner version.
* (DONE) Integrate use of libcroco for handling Cascading Style Sheets.

* Palettes

(suggestion: having custom palletes, like from Gnome )
(suggestion: accuraced palettes from colour norms, like Pantone, Trumatch, Focoltone, Toyo, etc. (since lots of people uses it, specially professionally) - problem: some are patented/copyrighted, which seems each norm company like this must be contacted for authorization (?) - as well, is also an open-source colour norm standard welcome? (which works on both video/printing outputs, like Pantone seems to be?) )

=== Milestone 16 - Cairoification - Inkscape 0.50 ===

* Prereq: Is renderer immune to the same kinds of numerical problems we see with our new renderer, libnr, or libart?
* Create a Cairo-based SVG Canvas library

=== Milestone 17 - Animation Conceptualization - Inkscape 0.51 ===

* Prereq: We need a conceptualization of how it should work
* Currently, part of the concept discussion is at [[Animation-(Timeline)|here]]

=== Milestone 18 - Fonts Revisited - Inkscape 0.52 ===

* Reenable fuzzy font matching [bb]
* (DONE) Bidirectional text in Pango needs attention
* (DONE) [[MakeVertical]] in Pango needs attention

=== Milestone 19 - Palettes - Inkscape 0.53 ===

* Implement [[LittleCMS]] as color management system
* (DONE) Create a swatches dialog

=== Milestone 20 - Full Animation Support - Inkscape 0.54 ===

=== Milestone 21 - RFE's - Inkscape 0.55 ===

* Reduce open/total RFE ratio to 30%

=== Milestone [Future] ===
* Investigate performance measurement testing for Inkscape
* Convert all tabs into spaces (convert tabs to 4 spaces)
* Rename all '[[SPFooBar]]' routines to '[[FooBar]]' and put into namespaces
** (DONE) dialogs folder
* Investigate SVG docs where SVG is not the default namespace used at the root -- e.g. <svg:svg xmlns:svg="http://...etc"><svg:rect.../><blah></svg:svg> -- <blah> would end up getting shoehorned into the svg namespace
* Write an Internal DTD subset describing the custom Inkscape XML elements, for validation against SVG DTD
* Ensure Inkscape does not throw away the internal DTD subsets of documents it reads
* Start thinking about 1.0 when major functionality gaps are closed ((BASICALLY DONE) layers, (DONE) color palette, (DONE) gradient tool, mask tool, (DONE) patterns, (DONE) text on path and in shape, (DONE) text selection, perspective transforms, SVG filters, scripting, path editing, shaped strokes)
* Implement preliminary support for iso & hex grid [njh]
* Implement perspective transformations via [[PerspectiveObject]]
* Improve freehand curve smoothness [pjrm, paraprax]
* Review X1-1GUITest on SF
* Review usability links at http://openusability.org/docman/?group_id=52
* Review usability links at http://openusability.org/docman/?group_id=57

[[Category:Developer Documentation]]

Roadmap

2006-06-26T09:46:13Z

Craig9: Duplicate milestone item

== Inkscape Development Roadmap ==

NOTE: This is a working document showing specific near-term tasks needed for achieving milestones. The number in front of the version is in reference to the milestone.

''Milestones 0-9 have been completed since the start of the Inkscape Project. See [[OldRoadmap]]''

=== Milestone 10 - RFE's & Extensions Implementation - Inkscape 0.44 ===

New/Changed Dependencies
* (DONE) Add libcroco

Internals

* Implement extension API
* Implement extension registry
* Complete Extension preferences dialog
* (DONE) Reduce open/total RFE ratio to 55%
* masks/clippaths
** (DONE)Implement creation
** on-canvas editing
* Create an SPObject API for tracking references and avoiding id clashes on import and interdocument copy/paste. What we need are a void SPDocument::importCopies([set of SPObjects]), and an [set of SPObjects] SPObject::dependencies() method.
* Implement gradient UI "release" handler to deal with gradient garbage collection (see bug 984854)
* improvement of svg patterns UI - make it similar to gradient-drag, instead of piggybacking knotholder

RFE's
* [http://sourceforge.net/tracker/index.php?func=detail&aid=893812&group_id=93438&atid=604309 hyperlinking]
*(DONE, in .43?) tools: add/remove points on path, bezier drag

Maintenance
* Learn and use autoscan and autoreconf to find out which configure tests are still needed.
* Clean up configure.in
* (PARTIALLY DONE) [http://inkscape.org/cgi-bin/wiki.pl?DirectoryReorgProposal Directory Reorganization] (rejon)
* When run without installing, make it look for icon image file(s) locally so we don't get garbage icons

Testing
* (DONE) Implement tests of Inkscape against the [[W3C]] test suite [rick beton, bryce]
* Include some rendering tests in `make check'.

=== Milestone 11 - Import[[/Export]] Feature Enhancements - Inkscape 0.45 ===

* integrate [[Googles_Summer_Of_Code]] 2006 work, i.e. [[Filter_Effects|SVG Filters]] and [[User:Daleharvey|formalising the protocol for inkboard communication]]
* Make printing work more efficiently and reliably
* Enhance file manager
* PDF Export
* Investigate ps2ai, pstoedit and ai2svg conversion options (potential EPS support?)
* Import of native Adobe Illustrator files
* Other RFE's related to Import[[/Export]]
* Add extension for use of [[VDX2SVG]] (http://vdxtosvg.sourceforge.net/)
* Add extension for use of [[PDF2SVG]] (http://www.solidcode.net/pdf2svg/)
* [[WebDAV/FTP]] support via GNOME-VFS, Neon, or the like

=== Milestone 12 - Style Refactoring - Inkscape 0.46 ===

* Eliminate use of the style.h types in as much of codebase as possible, particularly display/*.
* Change to use of GQuarks instead of #defines where feasible
* Editable toolbars (libegg)

=== Milestone 13 - Bug Hunt & RFE's - Inkscape 0.47 ===

* Reduce open/total RFE ratio to 40%
* Reduce open/total bug ratio to 5%

=== Milestone 14 - Drawing Feature Enhancements - Inkscape 0.48 ===

* Object-to-object snapping
* (DONE) Markers
* Enhanced grid system
* Inter-application cut-and-paste
* Inter-application drag-and-drop
* Clipart manager GUI
* Hyperlinking (Dupe? This is in milestone 10, too)
* (DONE) Load-from-URL

=== Milestone 15 - Style Rewrite & libcroco - Inkscape 0.49 ===

* Replace style.cpp entirely, with a clearer and cleaner version.
* (DONE) Integrate use of libcroco for handling Cascading Style Sheets.

* Palettes

(suggestion: having custom palletes, like from Gnome )
(suggestion: accuraced palettes from colour norms, like Pantone, Trumatch, Focoltone, Toyo, etc. (since lots of people uses it, specially professionally) - problem: some are patented/copyrighted, which seems each norm company like this must be contacted for authorization (?) - as well, is also an open-source colour norm standard welcome? (which works on both video/printing outputs, like Pantone seems to be?) )

=== Milestone 16 - Cairoification - Inkscape 0.50 ===

* Prereq: Is renderer immune to the same kinds of numerical problems we see with our new renderer, libnr, or libart?
* Create a Cairo-based SVG Canvas library

=== Milestone 17 - Animation Conceptualization - Inkscape 0.51 ===

* Prereq: We need a conceptualization of how it should work
* Currently, part of the concept discussion is at [[Animation-(Timeline)|here]]

=== Milestone 18 - Fonts Revisited - Inkscape 0.52 ===

* Reenable fuzzy font matching [bb]
* (DONE) Bidirectional text in Pango needs attention
* (DONE) [[MakeVertical]] in Pango needs attention

=== Milestone 19 - Palettes - Inkscape 0.53 ===

* Implement [[LittleCMS]] as color management system
* (DONE) Create a swatches dialog

=== Milestone 20 - Full Animation Support - Inkscape 0.54 ===

=== Milestone 21 - RFE's - Inkscape 0.55 ===

* Reduce open/total RFE ratio to 30%

=== Milestone [Future] ===
* Investigate performance measurement testing for Inkscape
* Convert all tabs into spaces (convert tabs to 4 spaces)
* Rename all '[[SPFooBar]]' routines to '[[FooBar]]' and put into namespaces
** (DONE) dialogs folder
* Investigate SVG docs where SVG is not the default namespace used at the root -- e.g. <svg:svg xmlns:svg="http://...etc"><svg:rect.../><blah></svg:svg> -- <blah> would end up getting shoehorned into the svg namespace
* Write an Internal DTD subset describing the custom Inkscape XML elements, for validation against SVG DTD
* Ensure Inkscape does not throw away the internal DTD subsets of documents it reads
* Start thinking about 1.0 when major functionality gaps are closed ((BASICALLY DONE) layers, (DONE) color palette, (DONE) gradient tool, mask tool, (DONE) patterns, (DONE) text on path and in shape, (DONE) text selection, perspective transforms, SVG filters, scripting, path editing, shaped strokes)
* Implement preliminary support for iso & hex grid [njh]
* Implement perspective transformations via [[PerspectiveObject]]
* Improve freehand curve smoothness [pjrm, paraprax]
* Review X1-1GUITest on SF
* Review usability links at http://openusability.org/docman/?group_id=52
* Review usability links at http://openusability.org/docman/?group_id=57

[[Category:Developer Documentation]]