https://wiki.inkscape.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=XavicondeInkscape Wiki - User contributions [en]2026-05-25T02:34:42ZUser contributionsMediaWiki 1.36.1https://wiki.inkscape.org/wiki/index.php?title=Translation_information&diff=17089Translation information2007-12-03T16:39:01Z<p>Xaviconde: /* Guidelines/workflow */</p>
<hr />
<div>== Introduction ==<br />
=== Community based, user oriented ===<br />
The translations of the various documents focusing on Inkscape rely on the work of volunteers.<br />
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.<br />
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.<br />
<br />
=== Guidelines/workflow ===<br />
<br />
# '''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].<br />
# '''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.<br />
# '''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.<br />
# '''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 Launchpad account to commit patches to [http://bugs.launchpad.net/inkscape 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.<br />
# '''Send a mail on the translator mailing list'''. Your contribution will be reviewed/commited as soon as possible.<br />
<br />
=== Best practices ===<br />
<br />
* Best case for a good translation: translate from English to your mother tongue.<br />
* Test the behavior of the interface before starting translation.<br />
* Several small updates are more efficient than only a big one.<br />
* 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.<br />
* 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].<br />
* Always keep in mind consistency of terminology; a simple, precise & explicit vocabulary/style will result in an efficient and thus good translation.<br />
* 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.).<br />
<br />
=== Polishing Translations - Microtypography ===<br />
Here are some things to note in order to achieve good microtypography (typography at the word or character level).<br />
* use the proper quotes (e.g. »foo« or «foo» or “foo”, depending on your local rules)<br />
* use the proper kind of dashes (with the proper amount of whitespace around them) - EN DASH (U+2013): "–", MINUS (U+2212): "−"<br />
* use non-breakable space where appropriate (e.g. before units; some countries use a halfspace here) - NO-BREAK SPACE (U+00A0): " "<br />
* use halfspace where appropriate (example: "z. B.") NARROW No-BREAK SPACE U+202F: " "<br />
* use "24×24", not "24x24"<br />
* use "90°", not "90 degrees" where appropriate<br />
* use the proper Unicode codepoint for "..." - "…". In German at least, a space comes before this ellipsis.<br />
* see http://www.cs.tut.fi/~jkorpela/chars/si.html for information on the use of SI units in Unicode<br />
* write numbers correctly - either with a decimal comma or a decimal point (see http://en.wikipedia.org/wiki/Decimal_separator#Dot_countries)<br />
* see http://translate.sourceforge.net/wiki/toolkit/pofilter<br />
<br />
==== Links ====<br />
* http://de.wikipedia.org/wiki/Typografie (German)<br />
* [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)<br />
* [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)<br />
* [http://www.zvisionwelt.de/typokurz.pdf Christoph Bier: ''typokurz – Einige wichtige typografische Regeln''] (PDF, German)<br />
* http://www.cs.tut.fi/~jkorpela/html/french.html (in English, for French)<br />
<br />
== Translatable content ==<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== User interface ===<br />
<br />
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.<br />
<br />
See [[InterfaceTranslation#Interface_Translation|InterfaceTranslation]] page for detailed information on the PO files.<br />
<br />
=== Tutorials ===<br />
<br />
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.<br />
It is even a good opportunity for '''you''' to become more acquainted with Inkscape.<br />
<br />
See [[DocumentationTranslation#Tutorial_Translation|Documentation Translation]] page for detailed information on tutorial translation.<br />
<br />
=== Keyboard and mouse shortcuts ===<br />
<br />
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.<br />
<br />
See [[DocumentationTranslation#Keyboard_and_mouse_translation|Documentation Translation]] page for detailed information on translating shortcuts.<br />
<br />
=== Windows installer ===<br />
<br />
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. <br />
<br />
<br />
See [[InterfaceTranslation#Windows_installer_translation|Interface Translation]] page for detailed information for Windows installer translation.<br />
<br />
=== Templates ===<br />
<br />
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. <br />
<br />
See [[InterfaceTranslation#Default_template_translation|Interface Translation]] page for detailed information on default document's template.<br />
<br />
=== Man pages ===<br />
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. <br />
<br />
Some distributions also generate a browsable (html) man page, accessible from a dedicated help shortcut.<br />
<br />
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).<br />
<br />
<br />
See [[DocumentationTranslation#Man_pages|Documentation Translation]] page for detailed information for man page translation.<br />
<br />
=== Release notes ===<br />
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.<br />
<br />
* gives a general overview of the possibilities of the software to potential users<br />
* can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)<br />
<br />
See [[WebSiteTranslation#Release_notes|WebSite Translation]] page for detailed information on translating release notes.<br />
<br />
=== User manual ===<br />
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.<br />
<br />
See [[DocumentationTranslation#User_Manual|Documentation Translation]] page for detailed information on translating the user manual.<br />
<br />
=== Web pages, News and Wiki ===<br />
English is generaly the exchange-tongue of developers, and developer/user documentation is mainly written in English. <br />
<br />
Translation efforts should be first oriented on user documentation.<br />
<br />
You can take a look at the [[WebSiteTranslation|WebSite Translation]] page for detailed information about how to translate the web content of Inkscape<br />
<br />
See the [[Main_Page|main wiki page of Inkscape]] to get some examples (Spanish and German) of the translation of this wiki.<br />
<br />
=== Others ===<br />
Text files found in the inkscape directory<br />
...<br />
<br />
== Status ==<br />
See this [[TranslationStatus|dedicated page]].</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=NotaAlliberament045&diff=13118NotaAlliberament0452007-02-04T12:38:46Z<p>Xaviconde: </p>
<hr />
<div>== L'Inkscape presenta la seva versió 0.45 :: http://www.inkscape.org :: Dibuixeu amb llibertat ==<br />
<br />
La comunitat de l'Inkscape presenta avui la versió més recent del seu programari de dibuix de gràfics vectorials. L'Inkscape 0.45 presenta un filtre de difuminat gaussià SVG, desenvolupat durant el programa Summer of Code de Google, que permet aplicar un difuminat suau i natural sobre qualsevol objecte de l'Inkscape, incloent formes, textos i imatges. Això permet un gran conjunt d'efectes fotorealístics: llums i ombres de formes arbitràries, profunditat de camp, ombres, lluentors, etc. També, els objectes difuminats es poden emprar com a màscares per a altres objectes.<br />
<br />
S'inclouen moltes altres noves característiques, millores a les eines existents i correccions d'errors: <br />
<br />
* Un diàleg d'historial, que us permet navegar per la història de canvis.<br />
* S'han afegit molts efectes i extensions, incloent un patró que segueix un camí i efectes de color.<br />
* Millores en la velocitat de renderització, de l'ordre d'un 2-3% en general i entre 5 i 10% per a dibuixos que fan servir molts efectes de transparència i/o degradats radials.<br />
* S'ha millorat la qualitat de les imatges composades, gràcies a l'eliminació de l'efecte de bandes als degradats.<br />
<br />
<br />
=== Descàrrega ===<br />
<br />
Descarregueu els paquets per a Windows, Linux i Mac OS X:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
Per a més detalls, consulteu les notes completes de la versió 0.45:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
Captures de pantalla dels usuaris de la comunitat:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
<br />
===Quant a l'Inkscape ===<br />
<br />
L'Inkscape és una eina de dibuix de codi obert que fa servir el format de gràfics de vectors escalable SVG del World Wide Web Consortium ([[W3C]]). Algunes de les característiques suportades inclouen formes bàsiques, camins, textos, marcadors, clons, transparències, transformacions, degradats i agrupació. A més, l'Inkscape suporta metadades de Creative Commons, edició de nodes, capes, operacions de camins complexes, text sobre camí, text dins de formes i edició XML de l'SVG. També importa múltiples formats com EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP i TIFF, i exporta a PNG, PS, PDF i altres formats basats en vectors.<br />
<br />
La principal motivació per a l'Inkscape és proporcionar a la comunitat del codi obert una eina de dibuix que suporti completament XML, SVG i CSS2 del [[W3C]]. D'altres feines addicionals inclouen convertir el codi base de <nowiki>C/GTK+</nowiki> a <nowiki>C++/GTKmm</nowiki>, posant èmfasi en un nucli lleuger amb potents característiques afegides mitjançant un mecanisme d'extensions, i la creació d'un procés de desenvolupament obert, amicable i orientat a la comunitat.</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=NotaAlliberament045&diff=13112NotaAlliberament0452007-02-04T12:33:59Z<p>Xaviconde: </p>
<hr />
<div>== L'Inkscape presenta la seva versió 0.45 :: http://www.inkscape.org :: Dibuixeu amb llibertat ==<br />
<br />
<<-- The Inkscape community today announces the newest version of its vector graphic drawing software. Inkscape 0.45 features a new Gaussian Blur SVG filter. Sponsored by Google's Summer of Code program, Gaussian Blur allows you to softly and naturally blur any Inkscape objects, including shapes, text, and images. This enables a wide range of photorealistic effects: arbitrarily shaped shades and lights, depth of field, drop shadows, glows, etc. Also, blurred objects can be used as masks for other objects to achieve the "feathered mask" effect. -->><br />
<br />
La comunitat de l'Inkscape presenta avui la versió més recent del seu programari de dibuix de gràfics vectorials. L'Inkscape 0.45 presenta un filtre de difuminat gaussià SVG, desenvolupat durant el programa Summer of Code de Google, que permet aplicar un difuminat suau i natural sobre qualsevol objecte de l'Inkscape, incloent formes, textos i imatges. Això permet un gran conjunt d'efectes fotorealístics: llums i ombres de formes arbitràries, profunditat de camp, ombres, lluentors, etc. També, els objectes difuminats es poden emprar com a màscares per a altres objectes.<br />
<br />
<<-- Numerous other new features, enhancements to existing features, and bug fixes have been included. A history dialog allows you to browse your change history. Many new extension effects are added including Pattern along Path and Color Effects. There have been performance improvements to rendering speed, on the order of 2-3% in general, and up to 5-10% for drawings using heavy transparency and/or radial gradients. Compositing quality is also improved through the removal of banding seen in gradients.-->><br />
<br />
S'inclouen moltes altres noves característiques, millores a les eines existents i correccions d'errors: <br />
<br />
* Un diàleg d'historial, que us permet navegar per la història de canvis.<br />
* S'han afegit molts efectes i extensions, incloent un patró que segueix un camí i efectes de color.<br />
* Millores en la velocitat de renderització, de l'ordre d'un 2-3% en general i entre 5 i 10% per a dibuixos que fan servir molts efectes de transparència i/o degradats radials.<br />
* S'ha millorat la qualitat de les imatges composades, gràcies a l'eliminació de l'efecte de bandes als degradats.<br />
<br />
<br />
=== Descàrrega ===<br />
<br />
<<-- Download Linux, Windows, and Mac OS X packages:-->><br />
<br />
Descarregueu els paquets per a Windows, Linux i Mac OS X:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
<<-- For many more details, see the complete Release Notes for 0.45:-->><br />
<br />
Per a més detalls, consulteu les notes completes de la versió 0.45:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
<<-- Community submitted screenshots: -->><br />
<br />
Captures de pantalla dels usuaris de la comunitat:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
<br />
===Quant a l'Inkscape ===<br />
<br />
<<-- Inkscape is an open source drawing tool that uses the World Wide Web Consortium's ([[W3C]]) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, <nowiki>PostScript</nowiki>, and most bitmap formats, and exports PNG, PS, PDF and various vector formats. -->><br />
<br />
L'Inkscape és una eina de dibuix de codi obert que fa servir el format de gràfics de vectors escalable SVG del World Wide Web Consortium ([[W3C]]). Algunes de les característiques suportades inclouen formes bàsiques, camins, textos, marcadors, clons, transparències, transformacions, degradats i agrupació. A més, l'Inkscape suporta metadades de Creative Commons, edició de nodes, capes, operacions de camins complexes, text sobre camí, text dins de formes i edició XML de l'SVG. També importa múltiples formats com EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP i TIFF, i exporta a PNG, PS, PDF i altres formats basats en vectors.<br />
<br />
<<-- Inkscape's main motivation is to provide the Open Source community with a fully [[W3C]] compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from <nowiki>C/Gtk</nowiki> to <nowiki>C++/Gtkmm</nowiki>, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process. -->><br />
<br />
La principal motivació per a l'Inkscape és proporcionar a la comunitat del codi obert una eina de dibuix que suporti completament XML, SVG i CSS2 del [[W3C]]. D'altres feines addicionals inclouen convertir el codi base de <nowiki>C/GTK+</nowiki> a <nowiki>C++/GTKmm</nowiki>, posant èmfasi en un nucli lleuger amb potents característiques afegides mitjançant un mecanisme d'extensions, i la creació d'un procés de desenvolupament obert, amicable i orientat a la comunitat.</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=NotaAlliberament045&diff=13110NotaAlliberament0452007-02-04T12:28:37Z<p>Xaviconde: </p>
<hr />
<div>== L'Inkscape presenta la seva versió 0.45 :: http://www.inkscape.org :: Dibuixeu amb llibertat ==<br />
<br />
<<-- The Inkscape community today announces the newest version of its vector graphic drawing software. Inkscape 0.45 features a new Gaussian Blur SVG filter. Sponsored by Google's Summer of Code program, Gaussian Blur allows you to softly and naturally blur any Inkscape objects, including shapes, text, and images. This enables a wide range of photorealistic effects: arbitrarily shaped shades and lights, depth of field, drop shadows, glows, etc. Also, blurred objects can be used as masks for other objects to achieve the "feathered mask" effect. -->><br />
<br />
La comunitat de l'Inkscape presenta avui la versió més recent del seu programari de dibuix de gràfics vectorials. L'Inkscape 0.45 presenta un filtre de difuminat gaussià SVG, desenvolupat durant el programa Summer of Code de Google, que permet aplicar un difuminat suau i natural sobre qualsevol objecte de l'Inkscape, incloent formes, textos i imatges. Això permet un gran conjunt d'efectes fotorealístics: llums i ombres de formes arbitràries, profunditat de camp, ombres, lluentors, etc. També, els objectes difuminats es poden emprar com a màscares per a altres objectes.<br />
<br />
<<-- Numerous other new features, enhancements to existing features, and bug fixes have been included. A history dialog allows you to browse your change history. Many new extension effects are added including Pattern along Path and Color Effects. There have been performance improvements to rendering speed, on the order of 2-3% in general, and up to 5-10% for drawings using heavy transparency and/or radial gradients. Compositing quality is also improved through the removal of banding seen in gradients.-->><br />
<br />
S'inclouen moltes altres noves característiques, millores a les eines existents i correccions d'errors: <br />
<br />
* Un diàleg d'historial, que us permet navegar per la història de canvis. Molts efectes.<br />
<br />
* S'han afegit molts efectes i extensions, incloent un patró que segueix un camí, i efectes de color.<br />
<br />
* Millores en la velocitat de renderització, de l'ordre d'un 5 a un 10% per a dibuixos que fan servir molts efectes de transparència i/o degradats radials.<br />
<br />
* S'ha millorat la qualitat de les imatges composades, gràcies a l'eliminació de l'efecte de bandes als degradats.<br />
<br />
<br />
=== Descàrrega ===<br />
<br />
<<-- Download Linux, Windows, and Mac OS X packages:-->><br />
<br />
Descarregueu els paquets per a Windows, Linux i Mac OS X:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
<<-- For many more details, see the complete Release Notes for 0.45:-->><br />
<br />
Per a més detalls, consulteu les notes completes de la versió 0.45:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
<<-- Community submitted screenshots: -->><br />
<br />
Captures de pantalla dels usuaris de la comunitat:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
<br />
===Quant a l'Inkscape ===<br />
<br />
<<-- Inkscape is an open source drawing tool that uses the World Wide Web Consortium's ([[W3C]]) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, <nowiki>PostScript</nowiki>, and most bitmap formats, and exports PNG, PS, PDF and various vector formats. -->><br />
<br />
L'Inkscape és una eina de dibuix de codi obert que fa servir el format de gràfics de vectors escalable SVG del World Wide Web Consortium ([[W3C]]). Algunes de les característiques suportades inclouen formes bàsiques, camins, textos, marcadors, clons, transparències, transformacions, degradats i agrupació. A més, l'Inkscape suporta metadades de Creative Commons, edició de nodes, capes, operacions de camins complexes, text a camí, text a formes i edició XML de l'SVG. També importa múltiples formats com EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP i TIFF i exporta PNG així com múltiples formats basats en vectors.<br />
<br />
<<-- Inkscape's main motivation is to provide the Open Source community with a fully [[W3C]] compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from <nowiki>C/Gtk</nowiki> to <nowiki>C++/Gtkmm</nowiki>, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process. -->><br />
<br />
La principal motivació per a l'Inkscape és proporcionar a la comunitat del codi obert una eina de dibuix que suporti completament XML, SVG i CSS2 del [[W3C]]. D'altres feines addicionals inclouen convertir el codi base de <nowiki>C/GTK+</nowiki> a <nowiki>C++/GTKmm</nowiki>, posant èmfasi en un nucli lleuger amb potents característiques afegides mitjançant un mecanisme d'extensions, i la creació d'un procés de desenvolupament obert, amicable i orientat a la comunitat.</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=NotaAlliberament045&diff=13108NotaAlliberament0452007-02-04T12:26:11Z<p>Xaviconde: </p>
<hr />
<div>== L'Inkscape presenta la seva versió 0.45 :: http://www.inkscape.org :: Dibuixeu amb llibertat ==<br />
<br />
<<-- The Inkscape community today announces the newest version of its vector graphic drawing software. Inkscape 0.45 features a new Gaussian Blur SVG filter. Sponsored by Google's Summer of Code program, Gaussian Blur allows you to softly and naturally blur any Inkscape objects, including shapes, text, and images. This enables a wide range of photorealistic effects: arbitrarily shaped shades and lights, depth of field, drop shadows, glows, etc. Also, blurred objects can be used as masks for other objects to achieve the "feathered mask" effect. -->><br />
<br />
La comunitat de l'Inkscape presenta avui la versió més recent del seu programari de dibuix de gràfics vectorials. L'Inkscape 0.45 presenta un filtre de difuminat gaussià SVG, desenvolupat durant el programa Summer of Code de Google, que permet aplicar un difuminat suau i natural sobre qualsevol objecte de l'Inkscape, incloent formes, textos i imatges. Això permet un gran conjunt d'efectes fotorealístics: llums i ombres de formes arbitràries, profunditat de camp, ombres, lluentors, etc. També, els objectes difuminats es poden emprar com a màscares per a altres objectes.<br />
<br />
<<-- Numerous other new features, enhancements to existing features, and bug fixes have been included. A history dialog allows you to browse your change history. Many new extension effects are added including Pattern along Path and Color Effects. There have been performance improvements to rendering speed, on the order of 2-3% in general, and up to 5-10% for drawings using heavy transparency and/or radial gradients. Compositing quality is also improved through the removal of banding seen in gradients.-->><br />
<br />
S'inclouen moltes altres noves característiques, millores a les eines existents i correccions d'errors: <br />
<br />
* Un diàleg d'historial, que us permet navegar per la història de canvis. Molts efectes.<br />
<br />
* S'han afegit molts efectes i extensions, incloent un patró que segueix un camí, i efectes de color.<br />
<br />
* Millores en la velocitat de renderització, de l'ordre d'un 5 a un 10% per a dibuixos que fan servir molts efectes de transparència i/o degradats radials.<br />
<br />
* S'ha millorat la qualitat de les imatges composades, gràcies a l'eliminació de l'efecte de bandes als degradats.<br />
<br />
<br />
=== Descàrrega ===<br />
<br />
<<-- Download Linux, Windows, and Mac OS X packages:-->><br />
<br />
Descarregueu els paquets per a Windows, Linux i Mac OS X:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
<<-- For many more details, see the complete Release Notes for 0.45:-->><br />
<br />
Per a més detalls, consulteu les notes completes de la versió 0.45:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
<<-- Community submitted screenshots: -->><br />
<br />
Captures de pantalla dels usuaris de la comunitat:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
<br />
===Quant a l'Inkscape ===<br />
<br />
Inkscape is an open source drawing tool that uses the World Wide Web Consortium's ([[W3C]]) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, <nowiki>PostScript</nowiki>, and most bitmap formats, and exports PNG, PS, PDF and various vector formats.<br />
<br />
Inkscape's main motivation is to provide the Open Source community with a fully [[W3C]] compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from <nowiki>C/Gtk</nowiki> to <nowiki>C++/Gtkmm</nowiki>, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=NotaAlliberament045&diff=13106NotaAlliberament0452007-02-04T12:25:01Z<p>Xaviconde: </p>
<hr />
<div>== L'Inkscape presenta la seva versió 0.45 :: http://www.inkscape.org :: Dibuixeu amb llibertat ==<br />
<br />
<<-- The Inkscape community today announces the newest version of its vector graphic drawing software. Inkscape 0.45 features a new Gaussian Blur SVG filter. Sponsored by Google's Summer of Code program, Gaussian Blur allows you to softly and naturally blur any Inkscape objects, including shapes, text, and images. This enables a wide range of photorealistic effects: arbitrarily shaped shades and lights, depth of field, drop shadows, glows, etc. Also, blurred objects can be used as masks for other objects to achieve the "feathered mask" effect. -->><br />
<br />
La comunitat de l'Inkscape presenta avui la versió més recent del seu programari de dibuix de gràfics vectorials. L'Inkscape 0.45 presenta un filtre de difuminat gaussià SVG, desenvolupat durant el programa Summer of Code de Google, que permet aplicar un difuminat suau i natural sobre qualsevol objecte de l'Inkscape, incloent formes, textos i imatges. Això permet un gran conjunt d'efectes fotorealístics: llums i ombres de formes arbitràries, profunditat de camp, ombres, lluentors, etc. També, els objectes difuminats es poden emprar com a màscares per a altres objectes.<br />
<br />
<<-- Numerous other new features, enhancements to existing features, and bug fixes have been included. A history dialog allows you to browse your change history. Many new extension effects are added including Pattern along Path and Color Effects. There have been performance improvements to rendering speed, on the order of 2-3% in general, and up to 5-10% for drawings using heavy transparency and/or radial gradients. Compositing quality is also improved through the removal of banding seen in gradients.-->><br />
<br />
S'inclouen moltes altres noves característiques, millores a les eines existents i correccions d'errors: <br />
<br />
* Un diàleg d'historial, que us permet navegar per la història de canvis. Molts efectes.<br />
<br />
* S'han afegit molts efectes i extensions, incloent un patró que segueix un camí, i efectes de color.<br />
<br />
* Millores en la velocitat de renderització, de l'ordre d'un 5 a un 10% per a dibuixos que fan servir molts efectes de transparència i/o degradats radials.<br />
<br />
* S'ha millorat la qualitat de les imatges composades, gràcies a l'eliminació de l'efecte de bandes als degradats.<br />
<br />
<<-- Download Linux, Windows, and Mac OS X packages:-->><br />
<br />
Descarregueu els paquets per a Windows, Linux i Mac OS X:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
<<-- For many more details, see the complete Release Notes for 0.45:-->><br />
<br />
Per a més detalls, consulteu les notes completes de la versió 0.45:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
<<-- Community submitted screenshots: -->><br />
<br />
Captures de pantalla dels usuaris de la comunitat:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
===Quant a l'Inkscape ===<br />
<br />
Inkscape is an open source drawing tool that uses the World Wide Web Consortium's ([[W3C]]) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, <nowiki>PostScript</nowiki>, and most bitmap formats, and exports PNG, PS, PDF and various vector formats.<br />
<br />
Inkscape's main motivation is to provide the Open Source community with a fully [[W3C]] compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from <nowiki>C/Gtk</nowiki> to <nowiki>C++/Gtkmm</nowiki>, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=NotaAlliberament045&diff=13104NotaAlliberament0452007-02-04T12:23:44Z<p>Xaviconde: </p>
<hr />
<div>== L'Inkscape presenta la seva versió 0.45 :: http://www.inkscape.org :: Dibuixeu amb llibertat ==<br />
<br />
<<-- The Inkscape community today announces the newest version of its vector graphic drawing software. Inkscape 0.45 features a new Gaussian Blur SVG filter. Sponsored by Google's Summer of Code program, Gaussian Blur allows you to softly and naturally blur any Inkscape objects, including shapes, text, and images. This enables a wide range of photorealistic effects: arbitrarily shaped shades and lights, depth of field, drop shadows, glows, etc. Also, blurred objects can be used as masks for other objects to achieve the "feathered mask" effect. -->><br />
<br />
La comunitat de l'Inkscape presenta avui la versió més recent del seu programari de dibuix de gràfics vectorials. L'Inkscape 0.45 presenta un filtre de difuminat gaussià SVG, desenvolupat durant el programa Summer of Code de Google, que permet aplicar un difuminat suau i natural sobre qualsevol objecte de l'Inkscape, incloent formes, textos i imatges. Això permet un gran conjunt d'efectes fotorealístics: llums i ombres de formes arbitràries, profunditat de camp, ombres, lluentors, etc. També, els objectes difuminats es poden emprar com a màscares per a altres objectes.<br />
<br />
<<-- Numerous other new features, enhancements to existing features, and bug fixes have been included. A history dialog allows you to browse your change history. Many new extension effects are added including Pattern along Path and Color Effects. There have been performance improvements to rendering speed, on the order of 2-3% in general, and up to 5-10% for drawings using heavy transparency and/or radial gradients. Compositing quality is also improved through the removal of banding seen in gradients.-->><br />
<br />
S'inclouen moltes altres noves característiques, millores a les eines existents i correccions d'errors: <br />
<br />
* Un diàleg d'historial, que us permet navegar per la història de canvis. Molts efectes.<br />
<br />
* S'han afegit molts efectes i extensions, incloent un patró que segueix un camí, i efectes de color.<br />
<br />
* Millores en la velocitat de renderització, de l'ordre d'un 5 a un 10% per a dibuixos que fan servir molts efectes de transparència i/o degradats radials.<br />
<br />
* S'ha millorat la qualitat de les imatges composades, gràcies a l'eliminació de l'efecte de bandes als degradats.<br />
<br />
<<-- Download Linux, Windows, and Mac OS X packages:-->><br />
<br />
Descarregueu els paquets per a Windows, Linux i Mac OS X:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
<<-- For many more details, see the complete Release Notes for 0.45:-->><br />
<br />
Per <br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
Community submitted screenshots:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
===About Inkscape===<br />
<br />
Inkscape is an open source drawing tool that uses the World Wide Web Consortium's ([[W3C]]) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, <nowiki>PostScript</nowiki>, and most bitmap formats, and exports PNG, PS, PDF and various vector formats.<br />
<br />
Inkscape's main motivation is to provide the Open Source community with a fully [[W3C]] compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from <nowiki>C/Gtk</nowiki> to <nowiki>C++/Gtkmm</nowiki>, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=NotaAlliberament045&diff=13100NotaAlliberament0452007-02-04T12:15:16Z<p>Xaviconde: </p>
<hr />
<div><br />
== L'Inkscape presenta la seva versió 0.45 :: http://www.inkscape.org :: Dibuixeu amb llibertat ==<br />
<br />
-- The Inkscape community today announces the newest version of its vector graphic drawing software. Inkscape 0.45 features a new Gaussian Blur SVG filter. Sponsored by Google's Summer of Code program, Gaussian Blur allows you to softly and naturally blur any Inkscape objects, including shapes, text, and images. This enables a wide range of photorealistic effects: arbitrarily shaped shades and lights, depth of field, drop shadows, glows, etc. Also, blurred objects can be used as masks for other objects to achieve the "feathered mask" effect. <br />
<br />
La comunitat de l'Inkscape presenta avui la versió més recent del seu programari de dibuix de gràfics vectorials. L'Inkscape 0.45 presenta un filtre de difuminat gaussià SVG, desenvolupat durant el programa Summer of Code de Google, que permet aplicar un difuminat suau i natural sobre qualsevol objecte de l'Inkscape, incloent formes, textos i imatges. Això permet un gran conjunt d'efectes fotorealístics: llums i ombres de formes arbitràries, profunditat de camp, ombres, lluentors, etc. També, els objectes difuminats es poden emprar com a màscares per a altres objectes.<br />
<br />
Numerous other new features, enhancements to existing features, and bug fixes have been included. A history dialog allows you to browse your change history. Many new extension effects are added including Pattern along Path and Color Effects. There have been performance improvements to rendering speed, on the order of 2-3% in general, and up to 5-10% for drawings using heavy transparency and/or radial gradients. Compositing quality is also improved through the removal of banding seen in gradients.<br />
<br />
Download Linux, Windows, and Mac OS X packages:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
For many more details, see the complete Release Notes for 0.45:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
Community submitted screenshots:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
===About Inkscape===<br />
<br />
Inkscape is an open source drawing tool that uses the World Wide Web Consortium's ([[W3C]]) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, <nowiki>PostScript</nowiki>, and most bitmap formats, and exports PNG, PS, PDF and various vector formats.<br />
<br />
Inkscape's main motivation is to provide the Open Source community with a fully [[W3C]] compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from <nowiki>C/Gtk</nowiki> to <nowiki>C++/Gtkmm</nowiki>, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=ReleaseAnnounce045&diff=13098ReleaseAnnounce0452007-02-04T12:10:00Z<p>Xaviconde: Updated catalan link</p>
<hr />
<div>This is concept of the Release Announcement for the 0.45 version.<br />
<br />
== Inkscape Announces 0.45 Release :: http://www.inkscape.org :: Draw Freely ==<br />
<br />
The Inkscape community today announces the newest version of its vector graphic drawing software. Inkscape 0.45 features a new Gaussian Blur SVG filter. Sponsored by Google's Summer of Code program, Gaussian Blur allows you to softly and naturally blur any Inkscape objects, including shapes, text, and images. This enables a wide range of photorealistic effects: arbitrarily shaped shades and lights, depth of field, drop shadows, glows, etc. Also, blurred objects can be used as masks for other objects to achieve the "feathered mask" effect. <br />
<br />
Numerous other new features, enhancements to existing features, and bug fixes have been included. A history dialog allows you to browse your change history. Many new extension effects are added including Pattern along Path and Color Effects. There have been performance improvements to rendering speed, on the order of 2-3% in general, and up to 5-10% for drawings using heavy transparency and/or radial gradients. Compositing quality is also improved through the removal of banding seen in gradients.<br />
<br />
Download Linux, Windows, and Mac OS X packages:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
For many more details, see the complete Release Notes for 0.45:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
Community submitted screenshots:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
===About Inkscape===<br />
<br />
Inkscape is an open source drawing tool that uses the World Wide Web Consortium's ([[W3C]]) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, <nowiki>PostScript</nowiki>, and most bitmap formats, and exports PNG, PS, PDF and various vector formats.<br />
<br />
Inkscape's main motivation is to provide the Open Source community with a fully [[W3C]] compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from <nowiki>C/Gtk</nowiki> to <nowiki>C++/Gtkmm</nowiki>, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.<br />
<br />
== Release announce translations ==<br />
<br />
Catalan: http://wiki.inkscape.org/wiki/index.php/NotaAlliberament045<br />
<br />
Czech: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-cs<br />
<br />
Deutsch: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-de<br />
<br />
French: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-fr<br />
<br />
Italian: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-it<br />
<br />
Japanese: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-ja<br />
<br />
Portuguese: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-ptBR<br />
<br />
Vietnamese: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-vi<br />
[[Category:Marketing]]</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=AnunciAlliberament044&diff=8420AnunciAlliberament0442006-09-30T14:09:56Z<p>Xaviconde: /* Inkscape anuncia la versió 0.44 :: http://www.inkscape.org :: Dibueixeu en llibertat */</p>
<hr />
<div>Traducció de http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce044<br />
<br />
== Inkscape anuncia la versió 0.44 :: http://www.inkscape.org :: Dibuixeu en llibertat ==<br />
<br />
La comunitat de l'Inkscape ha alliberat oficialment avui la darrera versió del seu programari de dibuix d'imatges vectorials. L'Inkscape 0.44 satisfà una gran quantitat de peticions d'usuaris, suporta un gran nombre de característiques d'SVG, està traduït en més idiomes i afegeix molta velocitat i simplicitat.<br />
<br />
Dels molts canvis notables en la interfície d'usuari s'inclouen un diàleg de capes, selector de color adjuntat, un diàleg de preferències redissenyat, una barra d'eines de text i noves icones. D'altres canvis més profunds inclouen centres de rotació persistents, indicació d'estil interactiva en la barra d'eines, dreceres de teclat configurables, millores en el retolador cal·ligràfic i la nova característiques per "escolpir nodes". I la exportació en PDF suporta transparències.<br />
<br />
En alliberaments anteriors, es proporcionava un sistema experimental de connectors d'"Efectes", però sempre ha estat inhabilitat per defecte. Amb aquesta versió, l'equip pensa que ja està prou avançat, així que s'ha habilitat per defecte.<br />
<br />
Per a dibuixos molt complexos, l'Inkscape ara proporciona un mode contorn, que millora el rendiment. El nostre suport a SVG s'ha incrementat més encara amb la implementació de l'etiqueta <switch>. S'ha implementat els perfils de color ICC per a les imatges. I centenars d'altres característiques i correccions d'errors.<br />
<br />
També volem agrair Google per l'esponsorització de cinc estudiants per treballar en diferents àrees de desenvolupament de l'Inkscape: filtres SVG, especificació del protocol de pisarra compartida Inkboard, exportació a PDF amb Cairo i optimitzacions de la memòria.<br />
<br />
Descarregueu els paquets per a Linux, Windows i Mac OS X:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
Per a més detalls, veieu les completes notes de la versió 0.44:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
I captures de pantalla enviades per la comunitat:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
<br />
<br />
===Quant a l'Inkscape===<br />
<br />
L'Inkscape és una eina de dibuix de codi obert que fa servir el format de gràfics de vectors escalable SVG del World Wide Web Consortium ([[W3C]]). Algunes de les característiques suportades inclouen formes bàsiques, camins, textos, marcadors, clons, transparències, transformacions, degradats i agrupació. A més, l'Inkscape suporta metadades de Creative Commons, edició de nodes, capes, operacions de camins complexes, text a camí, text a formes i edició XML de l'SVG. També importa múltiples formats com EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP i TIFF i exporta PNG així com múltiples formats basats en vectors.<br />
<br />
La principal motivació per a l'Inkscape és proporcionar a la comunitat del codi obert una eina de dibuix que suporti completament XML, SVG i CSS2 del [[W3C]]. D'altres feines addicionals inclouen convertir el codi base de <nowiki>C/GTK+</nowiki> a <nowiki>C++/GTKmm</nowiki>, posant èmfasi en un nucli lleuger amb potents característiques afegides mitjançant un mecanisme d'extensions, i la creació d'un procés de desenvolupament obert, amicable i orientat a la comunitat.</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=AnunciAlliberament044&diff=8418AnunciAlliberament0442006-09-30T14:09:25Z<p>Xaviconde: /* Quant a l'Inkscape */</p>
<hr />
<div>Traducció de http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce044<br />
<br />
== Inkscape anuncia la versió 0.44 :: http://www.inkscape.org :: Dibueixeu en llibertat ==<br />
<br />
La comunitat de l'Inkscape ha alliberat oficialment avui la darrera versió del seu programari de dibuix d'imatges vectorials. L'Inkscape 0.44 satisfà una gran quantitat de peticions d'usuaris, suporta un gran nombre de característiques d'SVG, està traduït en més idiomes i afegeix molta velocitat i simplicitat.<br />
<br />
Dels molts canvis notables en la interfície d'usuari s'inclouen un diàleg de capes, selector de color adjuntat, un diàleg de preferències redissenyat, una barra d'eines de text i noves icones. D'altres canvis més profunds inclouen centres de rotació persistents, indicació d'estil interactiva en la barra d'eines, dreceres de teclat configurables, millores en el retolador cal·ligràfic i la nova característiques per "escolpir nodes". I la exportació en PDF suporta transparències.<br />
<br />
En alliberaments anteriors, es proporcionava un sistema experimental de connectors d'"Efectes", però sempre ha estat inhabilitat per defecte. Amb aquesta versió, l'equip pensa que ja està prou avançat, així que s'ha habilitat per defecte.<br />
<br />
Per a dibuixos molt complexos, l'Inkscape ara proporciona un mode contorn, que millora el rendiment. El nostre suport a SVG s'ha incrementat més encara amb la implementació de l'etiqueta <switch>. S'ha implementat els perfils de color ICC per a les imatges. I centenars d'altres característiques i correccions d'errors.<br />
<br />
També volem agrair Google per l'esponsorització de cinc estudiants per treballar en diferents àrees de desenvolupament de l'Inkscape: filtres SVG, especificació del protocol de pisarra compartida Inkboard, exportació a PDF amb Cairo i optimitzacions de la memòria.<br />
<br />
Descarregueu els paquets per a Linux, Windows i Mac OS X:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
Per a més detalls, veieu les completes notes de la versió 0.44:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
I captures de pantalla enviades per la comunitat:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
<br />
<br />
===Quant a l'Inkscape===<br />
<br />
L'Inkscape és una eina de dibuix de codi obert que fa servir el format de gràfics de vectors escalable SVG del World Wide Web Consortium ([[W3C]]). Algunes de les característiques suportades inclouen formes bàsiques, camins, textos, marcadors, clons, transparències, transformacions, degradats i agrupació. A més, l'Inkscape suporta metadades de Creative Commons, edició de nodes, capes, operacions de camins complexes, text a camí, text a formes i edició XML de l'SVG. També importa múltiples formats com EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP i TIFF i exporta PNG així com múltiples formats basats en vectors.<br />
<br />
La principal motivació per a l'Inkscape és proporcionar a la comunitat del codi obert una eina de dibuix que suporti completament XML, SVG i CSS2 del [[W3C]]. D'altres feines addicionals inclouen convertir el codi base de <nowiki>C/GTK+</nowiki> a <nowiki>C++/GTKmm</nowiki>, posant èmfasi en un nucli lleuger amb potents característiques afegides mitjançant un mecanisme d'extensions, i la creació d'un procés de desenvolupament obert, amicable i orientat a la comunitat.</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=AnunciAlliberament044&diff=6690AnunciAlliberament0442006-06-07T13:55:23Z<p>Xaviconde: </p>
<hr />
<div>Traducció de http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce044<br />
<br />
== Inkscape anuncia la versió 0.44 :: http://www.inkscape.org :: Dibueixeu en llibertat ==<br />
<br />
La comunitat de l'Inkscape ha alliberat oficialment avui la darrera versió del seu programari de dibuix d'imatges vectorials. L'Inkscape 0.44 satisfà una gran quantitat de peticions d'usuaris, suporta un gran nombre de característiques d'SVG, està traduït en més idiomes i afegeix molta velocitat i simplicitat.<br />
<br />
Dels molts canvis notables en la interfície d'usuari s'inclouen un diàleg de capes, selector de color adjuntat, un diàleg de preferències redissenyat, una barra d'eines de text i noves icones. D'altres canvis més profunds inclouen centres de rotació persistents, indicació d'estil interactiva en la barra d'eines, dreceres de teclat configurables, millores en el retolador cal·ligràfic i la nova característiques per "escolpir nodes". I la exportació en PDF suporta transparències.<br />
<br />
En alliberaments anteriors, es proporcionava un sistema experimental de connectors d'"Efectes", però sempre ha estat inhabilitat per defecte. Amb aquesta versió, l'equip pensa que ja està prou avançat, així que s'ha habilitat per defecte.<br />
<br />
Per a dibuixos molt complexos, l'Inkscape ara proporciona un mode contorn, que millora el rendiment. El nostre suport a SVG s'ha incrementat més encara amb la implementació de l'etiqueta <switch>. S'ha implementat els perfils de color ICC per a les imatges. I centenars d'altres característiques i correccions d'errors.<br />
<br />
També volem agrair Google per l'esponsorització de cinc estudiants per treballar en diferents àrees de desenvolupament de l'Inkscape: filtres SVG, especificació del protocol de pisarra compartida Inkboard, exportació a PDF amb Cairo i optimitzacions de la memòria.<br />
<br />
Descarregueu els paquets per a Linux, Windows i Mac OS X:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
Per a més detalls, veieu les completes notes de la versió 0.44:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
I captures de pantalla enviades per la comunitat:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
<br />
<br />
===Quant a l'Inkscape===<br />
<br />
L'Inkscape és una eina de dibuix de codi obert que fa servir el format de gràfics de vectors escalable SVG del World Wide Web Consortium ([[W3C]]). Algunes de les característiques suportades inclouen formes bàsiques, camins, textos, marcadors, clons, transparències, transformacions, degradats i agrupació. A més, l'Inkscape suporta metadades de Creative Commons, edició de nodes, capes, operacions de camins complexes, text a camí, text a formes i edició XML de l'SVG. També importa múltiples formats com EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP i TIFF i exporta PNG així com múltiples formats basats en vectors.<br />
<br />
La principal motivació per a l'Inkscape és proporcionar a la comunitat del codi obert una eina de dibuix que suporti completament XML, SVG i CSS2 del [[W3C]]. D'altres feines addicionals inclouen convertir el codi base de <nowiki>C/GTK+</nowiki> a <nowiki>C++/GTKmm</nowiki>, posant èmfasi en un nucli lleuger amb potents característiques afegides mitjançant un mecanisme d'extensions, i la creació d'un procés de desenvolupament obert, amicable i orientat a la comunitat.</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=ReleaseAnnounce044&diff=6689ReleaseAnnounce0442006-06-07T13:46:26Z<p>Xaviconde: </p>
<hr />
<div>This is concept of the Release Announcement for the 0.44 version.<br />
<br />
== Inkscape Announces 0.44 Release :: http://www.inkscape.org :: Draw Freely ==<br />
<br />
The Inkscape community today officially released the latest version of its vector graphic drawing software. Inkscape 0.44 adds many new features, is faster and more usable, better supports SVG, is translated into more languages, and adds a lot of speed and polish.<br />
<br />
Major new features include Layers dialog, support for clipping and masking, improved PDF export with transparency, configurable keyboard shortcuts, innovative "node sculpting" capability in Node tool, and the Outline mode. Significant gains are achieved in performance, especially in screen rendering and Node tool.<br />
<br />
Noticeable user interface changes include docked color swatches, interactive style indicator in the statusbar, a redesigned preferences dialog, a text toolbar, and new icons. Our SVG compliance has also taken a step forward, with the added support for the <switch> tag and ICC color profiles for images. This release also includes hundreds of smaller features, usability enhancements and bug fixes. <br />
<br />
For several releases, a collection of extension effects was shipped with Inkscape, but the Effects menu to access them was turned off by default. With this release, it has become mature enough, with effects working out of the box on all platforms, so this menu is enabled. <br />
<br />
We'd like to thank Google for their sponsorship of five students to work on several Inkscape development efforts: SVG Filters, Inkboard protocol, PDF export with Cairo, and memory optimization.<br />
<br />
Download Linux, Windows, and Mac OS X packages:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
For many more details, see the complete Release Notes for 0.44:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
Community submitted screenshots:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
===About Inkscape===<br />
<br />
Inkscape is an open source drawing tool that uses the World Wide Web Consortium's ([[W3C]]) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It also imports several formats like EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP, and TIFF and exports PNG as well as multiple vector-based formats.<br />
<br />
Inkscape's main motivation is to provide the Open Source community with a fully [[W3C]] compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from <nowiki>C/Gtk</nowiki> to <nowiki>C++/Gtkmm</nowiki>, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.<br />
<br />
== Release announce translations ==<br />
<br />
Catalan: http://wiki.inkscape.org/wiki/index.php/AnunciAlliberament044<br />
<br />
Czech: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce044-cs<br />
<br />
French: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce044-fr<br />
<br />
Italian: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce044-it</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=AnunciAlliberament044&diff=6687AnunciAlliberament0442006-06-07T13:28:14Z<p>Xaviconde: </p>
<hr />
<div>== Inkscape anuncia la versió 0.44 :: http://www.inkscape.org :: Dibueixeu en llibertat ==<br />
<br />
La comunitat de l'Inkscape ha alliberat oficialment avui la darrera versió del seu programari de dibuix d'imatges vectorials. L'Inkscape 0.44 satisfà una gran quantitat de peticions d'usuaris, suporta un gran nombre de característiques d'SVG, està traduït en més idiomes i afegeix molta velocitat i simplicitat.<br />
<br />
Dels molts canvis notables en la interfície d'usuari s'inclouen un diàleg de capes, selector de color adjuntat, un diàleg de preferències redissenyat, una barra d'eines de text i noves icones. D'altres canvis més profunds inclouen centres de rotació persistents, indicació d'estil interactiva en la barra d'eines, dreceres de teclat configurables, millores en el retolador cal·ligràfic i la nova característiques per "escolpir nodes". I la exportació en PDF suporta transparències.<br />
<br />
Durant molts alliberaments, es proporcionava un sistema experimental de connectors d'"Efectes", però sempre ha estat inhabilitat per defecte. Amb aquesta versió, l'equip pensa que ja està prou avançat, així que s'ha habilitat per defecte.<br />
<br />
Per a dibuixos molt complexos, l'Inkscape ara proporciona un mode contorn, que millora el rendiment. El nostre suport a SVG s'ha incrementat més encara amb la implementació de l'etiqueta <switch>. S'ha implementat els perfils de color ICC per a les imatges. I centenars d'altres característiques i correccions d'errors.<br />
<br />
També volem agrair Google per l'esponsorització de cinc estudiants per treballar en diferents àrees de desenvolupament de l'Inkscape: filtres SVG, especificació del protocol de pisarra compartida Inkboard, exportació a PDF amb Cairo i optimitzacions de la memòria.<br />
<br />
Descarregueu els paquets per a Linux, Windows i Mac OS X:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
Per a més detalls, veieu les completes notes de la versió 0.44:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
I captures de pantalla enviades per la comunitat:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
<br />
<br />
Quant a l'Inkscape<br />
<br />
L'Inkscape és una eina de dibuix de codi obert que fa servir el format de gràfics de vectors escalable SVG del World Wide Web Consortium ([[W3C]]). Algunes de les característiques suportades inclouen formes bàsiques, camins, textos, marcadors, clons, transparències, transformacions, degradats i agrupació. A més, l'Inkscape suporta metadades de Creative Commons, edició de nodes, capes, operacions de camins complexes, text a camí, text a formes i edició XML de l'SVG. També importa múltiples formats com EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP i TIFF i exporta PNG així com múltiples formats basats en vectors.<br />
<br />
La principal motivació per a l'Inkscape és proporcionar a la comunitat del codi obert una eina de dibuix que suporti completament XML, SVG i CSS2 del [[W3C]]. D'altres feines addicionals inclouen convertir el codi base de <nowiki>C/GTK+</nowiki> a <nowiki>C++/GTKmm</nowiki>, posant èmfasi en un nucli lleuger amb potents característiques afegides mitjançant un mecanisme d'extensions, i la creació d'un procés de desenvolupament obert, amicable i orientat a la comunitat.</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=ReleaseAnnounce044&diff=6685ReleaseAnnounce0442006-06-07T13:08:09Z<p>Xaviconde: /* Inkscape Announces 0.44 Release :: http://www.inkscape.org :: Draw Freely */</p>
<hr />
<div>This is concept of the Release Announcement for the 0.44 version.<br />
<br />
== Inkscape Announces 0.44 Release :: http://www.inkscape.org :: Draw Freely ==<br />
<br />
The Inkscape community today officially released the latest version of its vector graphic drawing software. Inkscape 0.44 adds many new features, is faster and more usable, better supports SVG, is translated into more languages, and adds a lot of speed and polish.<br />
<br />
Major new features include Layers dialog, support for clipping and masking, improved PDF export with transparency, configurable keyboard shortcuts, innovative "node sculpting" capability in Node tool, and the Outline mode. Significant gains are achieved in performance, especially in screen rendering and Node tool.<br />
<br />
Noticeable user interface changes include docked color swatches, interactive style indicator in the statusbar, a redesigned preferences dialog, a text toolbar, and new icons. Our SVG compliance has also taken a step forward, with the added support for the <switch> tag and ICC color profiles for images. This release also includes hundreds of smaller features, usability enhancements and bug fixes. <br />
<br />
For several releases, a collection of extension effects was shipped with Inkscape, but the Effects menu to access them was turned off by default. With this release, it has become mature enough, with effects working out of the box on all platforms, so this menu is enabled. <br />
<br />
We'd like to thank Google for their sponsorship of five students to work on several Inkscape development efforts: SVG Filters, Inkboard protocol, PDF export with Cairo, and memory optimization.<br />
<br />
Download Linux, Windows, and Mac OS X packages:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
For many more details, see the complete Release Notes for 0.44:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
Community submitted screenshots:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
===About Inkscape===<br />
<br />
Inkscape is an open source drawing tool that uses the World Wide Web Consortium's ([[W3C]]) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It also imports several formats like EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP, and TIFF and exports PNG as well as multiple vector-based formats.<br />
<br />
Inkscape's main motivation is to provide the Open Source community with a fully [[W3C]] compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from <nowiki>C/Gtk</nowiki> to <nowiki>C++/Gtkmm</nowiki>, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=AnunciAlliberament044&diff=6660AnunciAlliberament0442006-06-06T11:42:39Z<p>Xaviconde: </p>
<hr />
<div>== Inkscape Announces 0.44 Release :: http://www.inkscape.org :: Draw Freely ==<br />
<br />
The Inkscape community today officially released the latest version of its vector graphic drawing software. Inkscape 0.44 fulfils a number of user requests, supports a larger number of SVG features, is translated into more languages, and adds a lot of spit and polish.<br />
<br />
Several noticeable changes in the user interface include a layer dialog, docked swatches, a redesigned preferences dialog, a text toolbar, and new icons. Deeper interface changes include persistent rotation centers, interactive style indication in the toolbar, configurable keyboard shortcuts, improvements in calligraphic pen, and the exciting new "node sculpting" functionality. PDF export now supports transparency.<br />
<br />
For several releases an experimental 'Effects' plug-in system has been provided, but this has always been turned off by default. With this release, the team feels this is mature enough, so it has been changed to be on by default.<br />
<br />
For highly complex drawings, inkscape now provides an outline mode that will improve performance. Our SVG compliance has also taken a step forward, with the implementation of the <switch> tag. ICC color profiles are implemented for images. And hundreds of other features and bug fixes.<br />
<br />
We'd also like to thank Google for their sponsorship of five students to work on several Inkscape development efforts: SVG Filters, Inkboard protocol spec, PDF export with Cairo, and Memory Optimizations.<br />
<br />
<br />
Download Linux, Windows, and Mac OS X packages:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
For many more details, see the complete Release Notes for 0.44:<br />
<br />
http://wiki.inkscape.org/wiki/index.php/Release_Notes<br />
<br />
Community submitted screenshots:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
<br />
<br />
About Inkscape<br />
<br />
Inkscape is an open source drawing tool that uses the World Wide Web Consortium's ([[W3C]]) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It also imports several formats like EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP, and TIFF and exports PNG as well as multiple vector-based formats.<br />
<br />
Inkscape's main motivation is to provide the Open Source community with a fully [[W3C]] compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from <nowiki>C/Gtk</nowiki> to <nowiki>C++/Gtkmm</nowiki>, emphasizing a lightweight core with powerful features added through an extension mechanism, and the establishment of a friendly, open, community-oriented development process.</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=Notes_Alliberament&diff=6651Notes Alliberament2006-06-05T17:37:15Z<p>Xaviconde: /* Velocitat */</p>
<hr />
<div>== Inkscape 0.44: resum ==<br />
<br />
L'Inkscape 0.44 és més gran i millor que mai! Alguns dels aspectes destacats són:<br />
<br />
* Diàleg de capes<br />
<br />
* Mode contorn, amb millores del rendiment<br />
<br />
* Exportació nadiva en PDF amb transparència<br />
<br />
* Clipping and masking support<br />
<br />
* Dreceres de teclat configurables, incloent emulació de Xara <br />
<br />
* Paleta de color adjuntada en la finestra d'edició de la paleta de colors<br />
<br />
* Indicador interactiu de l'estil de la selecció a la barra d'estat<br />
<br />
* Un innovador "esculptor de nodes" i altres millores a l'eina de nodes<br />
<br />
* Ara les extensions estan habilitades per defecte i funcionen tant a Linux com a Windows<br />
<br />
* Millor suport d'SVG: element <switch>, perfils de color ICC per a les imatges<br />
<br />
* Centres de rotació persistents, ordre per enganxar la mida<br />
<br />
* S'ha redissenyat el diàleg de preferències, noves icones, menús reordenats, moltes millores cosmètiques<br />
<br />
* Centenars de correccions d'errors i petites millores<br />
<br />
* Encara que no està relacionat directament amb l'Inkscape, val la pena notar que des de la darrera versió, ara [http://www.mozilla.com/firefox/ Firefox 1.5] suporta per defecte el format SVG. Això significa que podeu veure qualsevol document SVG en la vostra finestra del Firefox sense convertir entre formats o instal·lant connectors addicionals.<br />
<br />
= Rendiment =<br />
<br />
== Mode contorn ==<br />
<br />
S'ha implementat el mode de visualització de contorn ("cablejat"). Useu <i>Visualització > Mode de visualització > Contorn</i> per activar-lo. En aquest mode:<br />
<br />
* tots els camins i formes es dibuixen com a <b>contorns invertits</b> (negre sobre fons clar i viceversa) de mida constant (1 píxeld de pantalla, independentment de l'ampliació), i sense emplenat,<br />
<br />
* el text és pinta amb emplenat invers, sense contorn,<br />
<br />
* els mapes de bits es mostren tal qual,<br />
<br />
* s'ignora l'opacitat i els desgradats.<br />
<br />
En general, el mode contorn no és dràsticament més ràpid que el mode regular (normalment entre un 10% i un 50%), i en alguns casos especials pot ser fins i tot més lent. Tanmateix, el valor del mode de contorn rau no només en la seva velocitat; també és una bona manera de fer-se una idea de l'estructura i els objectes d'un document, i és convenient per a editar nodes amb precisió i per trobar objectes "perduts".<br />
<br />
== Velocitat ==<br />
<br />
A més del mode contorn, que fa més senzill treballar amb dibuixos complexos, aquesta versió de l'Inkscape també proporciona millores significants en la velocitat en moltes àrees.<br />
<br />
* Gràcies a les <b>optimitzacions en el representador</b>, el redibuix a la pantalla de l'Inkscape és <b>almenys un 10% més ràpid</b>, i en alguns casos (com en camins puntejats en ampliacions altes) <b>fins a tres vegades superior</b>.<br />
<br />
* <b>Optimitzacions en l'eina de nodes</b> fan que es guanyi en velocitat notablement en editar nodes. Per tant, alternar entre l'eina de nodes (amb un camí seleccionat), i seleccionar nodes en l'eina és ara <b>almenys deu vegades més ràpid</b> que abans. Altres operaciones, incloent arrossegament de corbes i de nodes i operacions per moure/escalar/girar en múltiples nodes seleccionats és molt més ràpid també. Això és especialment important quan es treballa amb camins complexos; amb aquestes optimitzacions, els camins que contenen milers de nodes, encara que segueixen sent lents, són més usables que abans.<br />
<br />
* Una optimització en el mètode d'assignació d'atributs fa que les operacions com ara moure múltiples objectes mitjançant tecles de fletxa sigui <b>almenys un 30% més ràpid</b> comparat amb 0.43. Això és especialment notable quan esteu movent clons seleccionats conjuntament amb el seu original (p.e. mosaic de clon): en aquest cas Inkscape treballa de <b>dos a tres cops més ràpid</b>.<br />
<br />
* Les <b>icones de la interfície</b> ara es dibuixen en segon pla (des de la font SVG a <code>share/icons/icons.svg</code>) quan l'Inkscape no fa res, en comptes d'esperar que es dibuixin totes les icones en un menú la primera vegada que el mostreu. Això elimina el molest retard en obrir menús el primer cop.<br />
<br />
* Anteriorment, en ampliar per veure una pertita porció d'un camí (especialment en camins grans i complexos) havia un retard notable i un increment de la memòria massa gran. S'ha optimitzat el representador per a dibuixar <b>només la part visible del camí</b>, i com a resultat la velocitat de representació és gairebé la mateixa a qualsevol nivell d'ampliació, millorant entre 10 i 40 vegades la velocitat en comparació amb la versió anterior (com més gran l'ampliació més gran el guany).<br />
<br />
* L'ordre <b>Cami > Trenca en parts</b> és ara dotzenes de vegades (fins a 100x) vegades més ràpid per a camins complexos amb milers de subcamins.<br />
<br />
= Interface =<br />
<br />
== Layers dialog ==<br />
<br />
* Ctrl+Shift+L [joncruz, mental]<br />
<br />
== Selected style indicator ==<br />
<br />
A new control in the left end of the statusbar lets you quickly view and change the <b>fill and stroke of the selected objects</b>. When you have a text selection in Text tool or a gradient handle selected in the Gradient tool, this indicator displays and changes the style of the text fragment or gradient stop, instead of the entire object (it's the same behavior as the Fill&amp;Stroke dialog.)<br />
<br />
* The two indicators, labelled <b>F:</b> (top) and <b>S:</b> (bottom), display fill and stroke of the selected object(s) correspondingly. (For gradient handles, they always display the same style.)<br />
<br />
* Each fill/stroke indicator can display either a <b>color+opacity swatch</b> (the opacity shown here is the fill opacity or stroke opacity, not the master opacity) or a text label specifying <b>N/A</b> (nothing selected), <b>None</b> (no fill/stroke), <b>Unset</b> (unset fill/stroke), <b>L Gradient</b>, <b>R Gradient</b>, <b>Pattern</b> (corresponding fill/stroke types), or <b>Different</b> (selected objects have different fill/stroke types).<br />
<br />
* Additionally, each indicator may be accompanied by one of two flags, <b>m</b> ("multiple", meaning there are two or more objects all with the same fill/stroke) or <b>a</b> ("averaged", meaning there are two or more objects with different flat colors in fill/stroke, and the indicator shows the average of these colors).<br />
<br />
* <b>Left-click</b> on an indicator opens or activates the Fill&Stroke dialog with the corresponding tab (Fill or Stroke) active.<br />
<br />
* <b>Right-click</b> on an indicator opens a popup menu with the following items:<br />
** <b>Edit fill/stroke...</b>: Opens or activates the Fill&Stroke dialog with the corresponding tab selected. (Same as left-click.)<br />
** <b>Last set color</b>: Applies to the selected objects the fill/stroke color that was last applied to anythig.<br />
** <b>Last selected color</b>: Applies to the selected objects the fill/stroke color that was last displayed in this indicator. (Allows you to easily copy fill/stroke color between objects: select source, select destination, apply "last selected color".)<br />
** <b>Invert</b>: Sets the fill or stroke to the inverse of the current color (does not affect opacity).<br />
** <b>White</b>, <b>Black</b>: Sets the fill or stroke to the corresponding color (fully opaque).<br />
** <b>Copy color</b>, <b>Paste color</b>: Copies or pastes the fill or stroke color (when it's color) to/from the system clipboard, as text in the <code>#rrggbb</code> hex format.<br />
** <b>Swap fill and stroke</b>: Exchanges fill and stroke (both their types and colors, if any). <br />
** <b>Make fill/stroke opaque</b>: Removes fill or stroke transparency (not master transparency!).<br />
** <b>Unset fill/stroke</b>: Unsets fill or stroke from selected objects.<br />
** <b>Remove fill/stroke</b>: Removes fill or stroke from the selected objects.<br />
<br />
* <b>Middle-click</b> on a fill/stroke indicator removes fill/stroke from selected objects; if it is already removed (i.e. if the indicator displays "None"), it does the same as the "Last set color" command from the popup menu.<br />
<br />
* <b>Drag and Drop</b> of colors onto a fil/stroke indicator sets the fill and stroke of the selected object(s) correspondingly.<br />
<br />
* The Stroke indicator also displays the <b>stroke width</b> of selection (averaged if there are multiple objects selected with different stroke widths), located to the right of the stroke color/transparency swatch. Left-clicking on it opens the Fill&Stroke dialog with the Stroke Style tab selected. Right-clicking on it opens a popup menu which allows you to choose the units for displaying the stroke width, as well as choose one of the presets to assign to selection.<br />
<br />
* To the right of the fill/stroke indicators, the <b>Opacity</b> numeric field (labelled "O:") shows and allows you to change the master opacity of the selected object (or the averaged opacity of several selected objects). <b>Right-clicking </b> the numeric field opens a popup menu with preset opacity levels. <b>Middle-clicking</b> on the "O:" label cycles the opacity through the values of 0 (transparent), 0.5, and 1 (opaque).<br />
<br />
The zoom field and the cursor coordinates indicator have been rearranged for compactness and moved to the right end of the statusbar. There's also a window resize handle added at the very end of the statusbar.<br />
<br />
== Eina d'indicador d'estil ==<br />
<br />
Per a cada eina per crear objectes (formes, Bolígraf/Llapis, Cal·ligràfic, Text), la barra de control (al damunt) inclou ara un <b>indicador d'estil</b> a la dreta. Aquest indicador mostra quin estil tindrà l'objecte nou. L'indicador mostra correctament qualsevol estil que l'eina pot utilitzar - el "darrer" estil o l'estil fix d'aquella eina. Per exemple, fent clic a un paleta (fins i tot sense seleccionar res) canvia el "darrer" color posat i, si està configurada per utilitzar l'últim conjunt de color, el seu indicador s'actualitza, donant-li una idea del seu "pinzell" abans que comenci a dibuixar.<br />
<br />
== Controls bar for the Text tool ==<br />
<br />
* This version adds the beginnings of a Controls Bar for the Text tool (previously empty). Now you can select the <b>font family</b>, <b>size</b>, apply <b>bold</b> and <i>italic</i> styles, change <b>alignment</b> and <b>text orientation</b> without opening the Text and Font dialog. <br />
<br />
* All controls are <b>instant-apply</b> and work on the entire text object (if nothing selected) or text selection. They can also apply to multiple text objects (though you would need to switch to Selector to select multiple text objects, then switch back to Text tool for its controls). <br />
<br />
* The font-family drop-down contains names and <b>previews</b> of all fonts; unlike other programs, we didn't apply each font to its name, but added a separate preview string displayed with gray color after each font's name. This design ensures readability of font family names and provides maximum useful information in a limited space.<br />
<br />
* We will be adding more controls (including spacing and kerning) to this bar for the next versions.<br />
<br />
== Docked color palette ==<br />
<br />
* Previously, color swatches could only be used from a floating palette (Ctrl+Shift+W). Now the color swatches palette is embedded in the main UI, at the bottom of the window between the canvas and the statusbar. It is enabled by default; use <i>View > Show/Hide > Palette</i> to enable or disable it. The docked palette has the same functionality as the floating one; use a button in the top right corner to access the swatches menu.<br />
<br />
* The <b>Wrap</b> option (off by default) in the swatches menu converts the palette from a single row into a frame 2 or 3 rows high, for better access to colors in large palettes.<br />
<br />
* <b>Drag and Drop</b> of <b>colors</b> has been enabled.<br />
** Dragging colors from a palette shows a live swatch of the color being dragged under cursor.<br />
** Drag and Drop of colors onto the selected style indicator in the statusbar sets the fill or stroke of the selected object(s).<br />
** Colors can be <b>dropped</b> directly on to objects on canvas to set their <b>fill</b>, or <b>shift+dropped</b> to set their <b>stroke</b>. This affects only the object you drop the color on, regardless of whether that object is selected or not.<br />
** Colors can be dragged to and from other applications.<br />
<br />
* The new <b>Inkscape default</b> color palette was added. It contains a range of grays, standard HTML named colors, and a full range of colors sorted by their HSL values (475 colors overall). It is generated by a Python script which is available from Inkscape SVN in share/palettes.<br />
<br />
* Several <b>specialized color palettes</b>, useful in color-coordinated projects, were created or borrowed from GIMP: Grays, Reds, Greens, Blues, Gold, Royal, Khaki, Hilite, and Topographic.<br />
<br />
* All standard sizes of the swatches (Tiny, Small, Medium, Large, Huge) are made <b>smaller</b> overall.<br />
<br />
== Inkscape Preferences dialog ==<br />
<br />
Not only was the Inkscape Preferences dialog completely rewritten and redesigned, it is now also <b>fully GNOME-HIG compliant</b>. Numerous <b>bugs</b> were taken care of with the rewrite. As a new feature, the <b>Simplify threshold</b> can now be set with more precision.<br />
<br />
== Document Properties / Metadata dialogs ==<br />
<br />
* The Document Preferences dialog is now named <b>Document Properties</b>, and it was split in two: metadata were extracted into the <b>Document Metadata</b> dialog; metadata widgets are now also spread over two pages.<br />
<br />
* A button was added to <b>fit the canvas to the current selection</b> or, if there's no selection, to the entire drawing. The button resizes the canvas and, if necessary, moves the drawing into place. It is now very easy to size the canvas to an illustration after it is ready.<br />
<br />
* <b>New controls</b>: the new object snapping features required their own property widgets, and you can set the snapping sensitivity with a slider, or let it snap regardless of distance (grid only).<br />
<br />
* Rearrangements within <b>Document Properties</b>: everything snapping-related was collected on one page; Grid and Guide widgets are on their own, the same page. For better HIG compliance, all widgets were categorized; especially the widgets on the Page page were completely rearranged in the General/Format/Border categories.<br />
<br />
* <b>Bug fixes</b>: grayed out license URI had too low contrast, so it's no longer grayed out; the proprietary license didn't clean the license URI; spinbuttons had no tooltips, and minor grid quirks were removed; data was not updated when a new file replaced another in the same window.<br />
<br />
* <b>HIG compliance</b>: much work went into that, and now only a few details are missing from full Gnome-HIG compliance.<br />
<br />
* <b>Updated Creative Commons Licenses</b>: Updated CC licenses to the latest 2.5 versions by default in the license tab of the metadata dialog.<br />
<br />
== Menus ==<br />
<br />
* <b>Zoom</b> commands in the View menu are moved to a submenu; the <i>Zoom In</i> and <i>Zoom Out</i> commands are added to that submenu.<br />
<br />
* <b>Clone</b> commands are moved into a submenu in Edit menu and given more descriptive names and tips.<br />
<br />
* <b>Pattern</b> commands (<i>Objects to Pattern</i> and <i>Pattern to Objects</i>) are moved into a submenu in Object menu, under the new Clip and Mask submenus.<br />
<br />
* The contents of the <b>Effects menu</b> are categorized into submenus, and several effects are renamed to use more intuitive names. <br />
<br />
== Statusbar ==<br />
<br />
* In Selector, for multiple selected objects, the statusbar now reports their types. For example, if 5 groups are selected, it displays<br />
<br />
::<b>5</b> objects of type <b>Group</b> in layer <b>LayerName</b>.<br />
<br />
:instead of just "5 objects selected" as before. If there are up to 3 types in the selection, they will be listed, for example:<br />
<br />
::<b>5</b> objects of types <b>Group</b>, <b>Path</b>, <b>Rectangle</b> in layer <b>LayerName</b>.<br />
<br />
:The order of the list will correspond to the order in which the objects were added to selection. If there are 4 or more types in selection, only the number of types is reported, for example:<br />
<br />
::<b>5</b> objects of <b>4</b> types in layer <b>LayerName</b>.<br />
<br />
* In Selector, objects selected in groups are now identified as such, and the group ID is given, for example:<br />
<br />
::<b>Rectangle</b> in group <i>g212</i> (layer <b>content</b>)<br />
<br />
:If selected objects have different parents within one layer (for example, if one is selected in a group and another outside it), the number of parents is reported:<br />
<br />
::<b>2</b> objects of types <b>Rectangle</b>, <b>Path</b> in <b>2</b> parents (layer <b>content</b>)<br />
<br />
:If objects are in different layers, only the number of layers is reported since this also implies different parents:<br />
<br />
::<b>2</b> objects of types <b>Rectangle</b>, <b>Path</b> in <b>2</b> layers<br />
<br />
* In Node tool, if your node selection includes nodes from different subpaths, statusbar reports the number of subpaths with selection and the total number of subpaths, for example:<br />
<br />
::<b>2</b> of <b>195</b> nodes selected in <b>2</b> of <b>36</b> subpaths.<br />
<br />
* The contents of the statusbar message are now duplicated as a <b>tooltip</b> that is shown when you hover the mouse over the statusbar. [TODO: need to strip markup from the tooltips.] <br />
<br />
* The statusbar text is now no longer just cut off if there is insufficient room, but an ellipsis (...) is inserted at the end to show there's more (only with Gtk 2.6 and newer).<br />
<br />
== Theme ==<br />
<br />
* Inkscape has a <b>new default icon set</b> titled "Crispy" provided by Andre Sousa. The new icons are intended to add a more professional and cohesive look to our application, as well as to make the functions the icons represent more self-evident.<br />
<br />
= Clipping and masking =<br />
<br />
Inkscape now provides some UI for using <b>clipping paths and masks</b>. <br />
<br />
* Any object can be non-destructively intersected with a path (called a <i>clipping path</i>) so that only the intersected portion of the object is visible. <br />
** <b>To apply clipping</b>, select the objects to be clipped and the clipping path object, make sure the clipping path is above the other objects in z-order, and do <i>Object > Clip > Set</i>.<br />
** You can <b>transform, edit, or style</b> the clipped objects as usual. The clipping remains applied and transforms together with each clipped object.<br />
** To <b>remove the clipping</b>, do <i>Object > Clip > Release</i>. The clipping path is returned to the drawing as a regular object; it is inserted on top of the unclipped object in z-order. <br />
<br />
* Any object can be non-destructively masked by another object (called <i>mask</i>) so that: the mask's black or transparent areas become fully transparent in the masked object; mask's opaque white areas become fully opaque; and all intermediate colors translate into intermediate levels of opacity in the masked object. This allows you to apply, for example, arbitrary transparency gradients to objects.<br />
** To <b>apply a mask</b>, select the objects to be masked and the mask object, make sure the mask is above the other objects in z-order, and do <i>Object > Mask > Set</i>.<br />
** You can <b>transform, edit, or style</b> the masked objects as usual. The mask remains applied and transforms together with each masked object.<br />
** To <b>remove the masking</b>, do <i>Object > Mask > Release</i>. The mask is returned to the drawing as a regular object; it is inserted on top of the unmasked object in z-order. <br />
<br />
* Objects with clippath show their bounding box intersected with the bounding box of the clippath, instead of the original unclipped bbox as before. (However, this does not apply to objects without clippath of their own which are clipped by being inside a clipped group.)<br />
<br />
* Clipped or masked objects display "<i>clipped</i>" or "<i>masked</i>", correspondingly, in their statusbar descriptions.<br />
<br />
* Although Inkscape had render-only support for clipping paths and masks for quite some time, in this release we fixed a number of bugs which may affect the display of your documents using clippaths or masks.<br />
** Clippaths and masks with objectBoundingBox units are now shown correctly upon loading of the document.<br />
** Clippaths without fill didn't work, this is now fixed.<br />
** Objects with clippaths or masks are correctly copied/pasted between documents.<br />
<br />
= SVG conformance =<br />
<br />
== Color profile support ==<br />
<br />
Inkscape now includes base ICC profile functionality. If compiled with LittleCMS support (if you run <code>configure</code> with <code>--enable-lcms</code> switch), Inkscape passes the [http://www.w3.org/Graphics/SVG/Test/20030813/htmlframe/full-color-prof-01-f.html ICC color profile test] by W3C. The &lt;color-profile&gt; element has been implemented along with the "color-profile" attribute for &lt;image&gt; elements.<br />
<br />
== &lt;switch&gt; support ==<br />
<br />
Rendering support for SVG 1.1's '''Conditional Processing Module''' has been implemented, including ''switch'' element, ''requiredFeatures'', ''requiredExtensions'', ''systemLanguage'' attributes. Inkscape passes the Conditional processing tests ([http://www.w3.org/Graphics/SVG/Test/20030813/htmlframe/full-struct-cond-01-t.html] and [http://www.w3.org/Graphics/SVG/Test/20030813/htmlframe/full-struct-cond-02-t.html]) by W3C.<br />
<br />
== SVG output ==<br />
<br />
* In Inkscape's SVG documents, <b>colors</b> are now expressed by name (‘white’) or three-digit form (‘<tt>#f3c</tt>’) when possible.<br />
<br />
* The numeric values in <code>transform</code> attributes are written without insignificant trailing zeros, and anything less than that 1e-8 by absolute value (usually caused by rounding errors) is written as 0 to reduce clutter.<br />
<br />
= Transformations =<br />
<br />
== Transform dialog ==<br />
<br />
Fixes and improvements in the Transform dialog (Ctrl+Shift+M):<br />
<br />
* The <b>Apply to each object separately</b> checkbox is added, allowing you to scale/rotate/skew each selected object by the same amount, around that object's center. When off (by default), the selection is transformed as a whole. The status of this checkbox is remembered across sessions. (It has no effect on Move and Matrix tabs).<br />
<br />
* The <b>Clear</b> button resets the values on the current tab to defaults.<br />
<br />
* The <b>Scale</b> tab now allows you to specify horizontal or vertical size increments in percentage or absolute units. Also, there's a <b>Scale proportionally</b> checkbox which ensures that scaling preserves the width/height ratio. (If you are scaling several objects proportionally with "Apply to each object separately", you can only use the % unit to specify the scaling; otherwise each object's scale increments will have the width/height ratio of the entire selection, not of that specific object.)<br />
<br />
* The <b>Skew</b> tab can now specify the skew as an <b>absolute displacement</b> (e.g. for horizontal skewing of a rectangle, that means the shift of the top rectangle side relative to the bottom), as <b>percentage displacement</b> (e.g. a 1% horizontal skew of a rectangle means shifting the top side by 1% of the rectangle height), or as an <b>angle</b> (e.g. horizontal skew by 15 degrees results in the sides of a rectangle being rotated to that angle, while the top and bottom remain horizontal).<br />
<br />
* The <b>Matrix</b> tab (previously called "Transform") can either edit the current <code>transform=</code> matrix of an object, or post-multiply the <code>transform=</code> with the matrix you specify, depending on the <b>Edit current matrix</b> checkbox. (As it is now redundant, the transformation matrix in the Object Properties dialog is removed.)<br />
<br />
* The dialog now correctly <b>watches selection changes</b> in the active document window and updates its values accordingly.<br />
<br />
* The layout of the dialog is simplified, tooltips and mnemonics added for better usability.<br />
<br />
* Many bugs are fixed, especially in value conversions between units.<br />
<br />
== Persistent rotation centers ==<br />
<br />
* The position of the center (axis) of rotation and skewing used by Selector is now <b>remembered</b> for all objects and restored when you select those objects again (even after saving and reopening the document). When you move or scale an object, its rotation center is moved or scaled too, so its position relative to the object always remains the same unless you move it explicitly.<br />
<br />
* When you have several objects selected, they use the rotation center of the <b>first selected object</b>. If the first object does not have center set (i.e. if it's in a default central position), then several objects will rotate around the geometric center of their common bounding box (as before).<br />
<br />
* <b>Shift+click</b> on the rotation center resets it back to the center of the object's box.<br />
<br />
* Consequently, dragging the rotation center is now <b>an undoable action</b>; you can press Ctrl+Z to undo the drag.<br />
<br />
* <b>Keyboard rotation</b> by [, ] keys with various modifiers, as well as the Rotate tab in the <b>Transform dialog</b>, work around the selected object's rotation center (for multi-object selection, the rotation center of the first selected object).<br />
<br />
* Rotation centers are <b>preserved</b> when duplicating, cloning (including clone tiler), grouping/ungrouping, and converting to path.<br />
<br />
[TODO: <br />
- make it work smartly for groups: if a group has center not set, return the center of the first object inside group with the center set<br />
<br />
- a separate tab in the Transform dialog, with 9 buttons in the square grid (for setting it to object's corners, sides, and center) as well as x/y fields for setting center to any position<br />
<br />
- make center snap to grid/guides/objects and to other centers<br />
<br />
- make objects snap with their center to grid/guides/objects]<br />
<br />
== Pasting size ==<br />
<br />
A number of commands are added to easily scale selected objects to match the size of the object(s) previously copied to the clipboard. They are all in the Paste Size submenu in Edit menu:<br />
<br />
* <b>Paste Size</b> scales the whole selection to match the overall size of the clipboard object(s).<br />
<br />
* <b>Paste Width</b>/<b>Paste Height</b> scale the whole selection horizontally/vertically so that it matches the width/height of the clipboard object(s). These commands honor the scale ratio lock on the Selector controls bar (between W and H fields), so that when that lock is pressed, the other dimension of the selected object is scaled in the same proportion; otherwise the other dimension is unchanged.<br />
<br />
* <b>Paste Size Separately</b>, <b>Paste Width Separately</b> and <b>Paste Height Separately</b> work similarly to the above described commands, except that they scale <i>each selected object</i> separately to make it match the size/width/height of the clipboard object(s).<br />
<br />
= Tools =<br />
<br />
== Node tool ==<br />
<br />
=== Node sculpting ===<br />
<br />
An entirely new way of manipulating paths in Node tool is added in this version: Node sculpting. Normally, when you have several nodes selected and you drag one of them, all selected nodes move by the same amount. Now, if you <b>Alt-drag</b> one of the selected nodes, only that node is fully displaced; other selected nodes are moved less than the full amount, so that those farthest from the drag point remain stationary. This is similar to "proportional editing" or "soft selection" in 3D editors such as Blender.<br />
<br />
So, for example, if you select several nodes on a straight line and Alt+drag the middle selected node, the path will bend into a <b>smooth bell-like curve</b>. Nodes' handles are also adjusted correspondingly to keep the overall shape smooth and natural. (If you don't have enough nodes on a path fragment that you want to reshape in this way, just select the end nodes of that fragment and press <b>Ins</b> a few times to populate it with nodes.)<br />
<br />
Moreover, node sculpting is <b>sensitive to pressure</b> of your tablet pen. If you press slightly, your curve will have a narrow sharp tip (i.e. the nearest neighbors of your dragged node will move only a bit); if you press hard, the curve's tip will be wide and blunt (i.e. the nearest neighbors will move almost as much as the dragged node). (Hint: to stop dragging without losing your shape, first release Alt and then lift the tip of the pen.)<br />
<br />
There are many possible applications of the sculpting technique. To take a simple example, selecting all nodes of an ellipse-like shape and Alt+dragging one of them will smoothly and naturally stretch and skew the entire shape in any direction. Doing the same to a complex path, such as star or spiral, will twist and punch it without destroying its intricate structure - this is the way to get squashed or self-intersecting stars, eccentric spirals and other shapes not easily doable before. Selecting only part of all nodes allows you to smoothly reshape parts of the figure without disturbing the rest.<br />
<br />
When applied to text converted to path, node sculpting is a fun and easy way to twist, bend and distort it, achieving effects similar to "perspective envelope" or "curvilinear envelope" in other programs - but in a more powerful and flexible way. For example, by selecting all or part of the text's nodes and Alt-dragging, you can not only make a wavy banner out of a paragraph of text, but also apply a "magnifying lens"-like effect to any word in the middle. <br />
<br />
Especially useful node sculpting is for complex natural paths, such as calligraphic strokes or bitmap traces, where you often want to do large-scale pushes and bends without destroying the small-scale features. Things like making a calligraphic stroke narrower in one place and wider in another, or changing the proportions, extending the ear or flattening the nose of a head - all this is now much faster and more natural to do using sculpting. It is also a new way to <i>create</i> new paths, too - starting from en ellipse with added nodes, it takes just a few Alt+drags to tweak it into a silhouette of a head, or a map of Australia, or an Inkscape logo!<br />
<br />
Some examples are shown on the screenshot: [[http://www.inkscape.org/screenshots/gallery/inkscape-0.44-nodesculpting.png]].<br />
<br />
=== "Show handles" toggle ===<br />
<br />
The Controls bar for the Nodes tool now includes a toggle button which controls whether Bezier handles are shown on selected nodes (on by default). Selecting and dragging nodes on node-dense paths in zoom-out (e.g. for node sculpting) may be extremely difficult without hiding the handles, as it's hard to pick a node and not a handle when handles are shown.<br />
<br />
=== New deletion behavior ===<br />
<br />
* In Node tool, <b>deleting node(s)</b> by Del/Backspace keys or by Ctrl+Alt+clicking a node now <b>tries to preserve, as much as possible, the current shape of the path</b>. This means that the nodes adjacent to those being deleted have their handles adjusted to approximate the form that the path had before deletion. For example, if you Ctrl+Alt+click a path twice, once to add a new node and then to delete it, the path will not change at all (or change very slightly). The old deletion behavior without adjusting handles is still available via <b>Ctrl+Del</b> or <b>Ctrl+Backspace</b>.<br />
<br />
=== Preserving positions of nodes and handles ===<br />
<br />
* When you <b>switch the type</b> of the selected node to Smooth or Symmetric by pressing Shift+S/Shift+Y, you can now <b>preserve the position</b> of one of the two handles by hovering your mouse over it, so that only the other handle is rotated/scaled to match.<br />
<br />
* Similarly, when you <b>join endnodes</b> by pressing Shift+J, you can <b>preserve the position</b> of one of the two nodes by hovering your mouse over it, so that only the other node is moved. <br />
<br />
=== Miscellaneous ===<br />
<br />
* The <b>!</b> key <b>inverts node selection</b> in the current subpath(s) (i.e. subpaths with at least one selected node); <b>Alt+!</b> inverts in the entire path. (This is similar to how these keys work in Selector, with current subpath(s) instead of the current layer.)<br />
<br />
* The keyboard shortcut for "Make selected segments curves" in Node tool is changed from Shift+K to <b>Shift+U</b> for better mnemonics.<br />
<br />
== Calligraphic pen ==<br />
<br />
* Even when using a graphics tablet with pressure sensitivity, the Calligraphy pen's strokes often look too smooth and artificial. To enable a more natural look, the new <b>Tremor</b> parameter is added to the Calligraphy tool in this version. Adjustable in the Controls bar from 0.0 to 1.0, it will affect your strokes producing anything from slight unevenness to wild blotches and splotches. This significantly expands the creative range of the tool.<br />
<br />
* In all previous versions, pen width depended on zoom in such a way that the strokes <i>appeared</i> the same visible width at any zoom, but were in fact narrower at zoom-in and wider at zoom-out. This behavior makes sense if you want to keep the same "feel" of the pen regardless of zoom; for example, if you zoomed in to make a small fix to your drawing, it's natural that your pen becomes physically smaller but feels the same to you. So, this behavior is kept as the default, but now we also added an alternative mode where your <b>pen width is constant in absolute units</b> regardless of zoom. To switch to this mode, use the checkbox on the tool's Preferences page (you can open it by double-clicking the tool button).<br />
<br />
* The <b>Width</b> field in the tool's controls bar now changes <b>from 1 to 100</b>, which corresponds to the range from 0.01 to 1.0 in the previous version. If the "width in absolute units" mode is turned on, the value in this fields gives the width of the stroke in px units. In the default mode, the value of 100 gives 100px wide strokes only at 100% zoom, and strokes are correspondingly narrower or wider at other zoom levels.<br />
<br />
* A new preferences option for the Calligraphic tool, <b>Keep selected</b>, controls whether the newly created object remains selected after you finish drawing it. If you turn it off (by default it's on) and set the tool to using Last Set color, you can easily choose a new color by clicking on the palette without having to worry if this will change the color of the stroke you just created. (Watch the tool style indicator at the right end of the Controls bar for the style of the next stroke you will draw.)<br />
<br />
* <b>Esc</b> deselects selected objects in Calligraphic, as in most other tools.<br />
<br />
* The stroke you're drawing is now shown, while you're drawing it, with the correct color and opacity that it will eventually have, instead of always black as before.<br />
<br />
* On a new Inkscape installation, this tool now uses the last set style by default instead of the fixed black as before (this is changeable in the Inkscape Preferences for the tool).<br />
<br />
== Pen tool ==<br />
<br />
* While drawing a path, you can now <b>move the last node you created</b> by the same keys as in Node tool - that is, arrows, with Shift (for 10x displacement) or Alt (screen pixel displacement) modifiers. <br />
<br />
* Also, you can switch the not-yet-finalized (red) segment of the path being drawn from curve to line (<b>Shift+L</b>) or back to curve (<b>Shift+U</b>), again the same shortcuts as in the Node tool.<br />
<br />
* By popular demand, if a new path is being drawn but not yet finished, <b>Ctrl+Z cancels</b> that unfinished path (i.e. does the same as Esc), instead of undoing the previous action.<br />
<br />
* In Pen tool, <b>Del</b> works the same as Backspace to delete the last created point on the unfinished path.<br />
<br />
= Connectors and automatic layout =<br />
<br />
* There have been numerous bugfixes and several improvements to the behaviour of <b>connectors</b> and the <b>connector tool</b>:<br />
** Connectors moved as part of a selection will now stay attached to other objects in the selection, rather than becoming detached from them.<br />
** By default, the Connector tool will not attach connectors to text objects. There is a new checkbox in the connector preferences to control this setting.<br />
** The <b>margins around avoided shapes</b> (used for autorouting connectors) can now be adjusted via the "Spacing" control on the controls bar.<br />
<br />
* Automatic Diagram Layout - A new button is available in the alignment and distribution dialogue that performs automatic layout of diagrams involving a network of shapes and connectors. Layout is accomplished using force-directed graph layout based on the Kamada-Kawai algorithm. This algorithm treats edges as if they are springs such that the distance between nodes will be proportional to the path length---number of connectors---between them. Disconnected components (where not every shape is connected) will be arranged around the circumference of a circle.<br />
<br />
* There is a new <b>Remove Overlaps</b> button to move the selected objects enough that they don't overlap each other. A minimum spacing between the boundaries of objects can be specifiedTogether with the automatic layout tool, described above, this should be a significant addition to Inkscape's usability for diagramming. [Consider expanding this, comparing with existing Unclump and Distribute edge-to-edge buttons. - pjrm]<br />
<br />
= Selective tracing with SIOX =<br />
<br />
[ishmal]<br />
<br />
<br />
= Snapping =<br />
<br />
* [object snap - carl]<br />
<br />
* [highlight - mtou]<br />
<br />
* [only to visible gridlines - mtou]<br />
<br />
* <b>Guidelines</b> are made easier to pick: now you don't need to position mouse <i>exactly</i> over a guideline to activate it, instead there's a small position tolerance (1 screen pixel on each side of the guideline).<br />
<br />
= Sublayers =<br />
<br />
Previously, it was only possible to make a group a temporary sublayer by entering that group. Now Inkscape supports creating and using true persistent sublayers within a layer.<br />
<br />
* The <b>Add layer</b> dialog allows you to place the new layer above, below, or inside the current layer.<br />
<br />
* In Preferences (Selecting tab), options are added allowing the "Select All" command and Tab key selection to work either in the current layer only or in the current layer and its sublayers.<br />
<br />
= Extensions =<br />
<br />
* The <b>Effects menu is now always on</b>, it's no longer an "experimental feature". The preference setting to enable the menu has been removed.<br />
<br />
* Python extensions (which includes almost all currently available extensions) <b>work on Windows out of the box</b>, using a copy of Python shipping with Inkscape. The only minor inconvenience is that when an effect is launched, you get an empty console window that stays on while the effect is doing its work. (Don't close that window, it will disappear by itself when the effect is finished.)<br />
<br />
* A new Python effect, <b>Render > LaTeX formula</b>, allows you to type in any LaTeX formula and get a vector object with the TeX rendition of this formula inserted into your document. You need to have <b>latex</b>, <b>dvips</b>, and <b>pstoedit</b> installed and in PATH for this to work.<br />
<br />
* A new Python effect, <b>Flatten Path</b>, flattens paths in the current selection, approximating each path with a polyline whose segments meet the specified criteria for flatness.<br />
<br />
* A new Python effect, <b>Measure Path</b>, attaches a text label to each path in the selection giving the length of that path (in px units).<br />
<br />
* The <b>Radius Randomize</b> effect has a new parameter which enables <b>normal distribution</b> of random displacements instead of uniform as before, which gives a more natural feel to the randomized path.<br />
<br />
* The <b>Render > L-system</b> (formerly "Fractal (Lindenmayer)") effect is improved in this version. Now you can specify different angle values for turning left and right, which makes it possible to smoothly bend some L-systems sideways. Also, you can separately randomize the step length and the angles by a given percent for more natural look (this works especially well with plant-like branching shapes). This effect can be used to create Penrose tiling, Sierpinsky triangle, Dragon curve and other famous mathematical artefacts, as well as various meanders, friezes, patterns, and trees. Some examples can be seen on this [http://inkscape.org/screenshots/gallery/inkscape-0.44-lindenmayer.png screenshot] as well as in the new example file <code>share/examples/l-systems.svg</code>.<br />
<br />
* The <b>Interpolate Path</b>, <b>Random Tree</b>, and <b>L-system</b> effects are fixed to place their result on the current layer instead of document root and in the center of the (last-saved) document view instead of 0,0 as before.<br />
<br />
* INX files now have the ability to hold more information. This includes tooltips and descriptions of the extensions. These are all also translatable.<br />
<br />
* Thanks to keyboard configurability, it is now possible to assign keyboard shortcuts to those effects you use most often, so you can activate them without going into the menu.<br />
<br />
= Formats =<br />
<br />
* Inkscape's <b>PDF export</b> is now native (i.e. does not require any external applications) and <b>supports transparency</b>, including gradients with transparency. This replaced the old export extension that required Ghostscript and worked via Postscript, losing any transparency. The new PDF export is still immature; in particular it does not handle text, so you should check "Convert text to path" on the export options dialog. Other things not yet supported include: gradients on stroke; eccentric elliptic gradients; patterns, masks, and clipping paths; embedded images.<br />
<br />
* You can now <b>Save as Compressed Inkscape SVG with media</b>.This save option collects the svg file and all linked images into a zip archive for distribution. Although you cannot open the resulting archive directly with inkscape, the media is linked such that after unzipping you can open the SVG file immediately.<br />
<br />
* An output format for <b>desktop cutting plotters</b>, such as the Wishblade and Craftrobo, was added. This format is a very minimalist DXF file with appropriate scaling and translation applied. This output format should not be expected to operate as a generalized DXF output.<br />
<br />
* [xfig]<br />
<br />
* [odg - ishmal]<br />
<br />
* The new <b>XCF output extension</b> exports all top-level elements (i.e. layers and objects directly under root) as PNGs and assembles them into an XCF for procesing in the Gimp. Requires Python, PyXML and Gimp. Gimp 2.2.x or above must be in the path and be named <code>gimp</code>. A version of Inkscape 0.44 or above must be accessible from the path. Does not function in Windows.<br />
<br />
= Configurable keyboard =<br />
<br />
Inkscape's <b>keyboard shortcuts are now configurable!</b> <br />
<br />
At this time, not all Inkscape actions can have their shortcuts customized. However, the majority of actions, including everything you see in the menus, are already configurable, and we're working on making more actions configurable. <br />
<br />
On startup, Inkscape reads its keyboard shortcuts from <code>share/keys/default.xml</code>. That file is a copy of <code>inkscape.xml</code> in the same directory, which also contains keyboard emulation profiles for other vector editors:<br />
<br />
*<code>xara.xml</code>: Xara X/Xara Xtreme/Xara LX keys<br />
<br />
You can copy any of these over default.xml to use that profile. In all profiles, those keys which are not used by the corresponding program still have their Inkscape bindings. If you can contribute a profile for some vector editor that we don't yet have, we will appreciate that. The files have a simple XML-based format described in <code>inkscape.xml</code>.<br />
<br />
You can also <b>customize some of your keybindings</b> without overwriting the main <code>default.xml</code>. If your profile directory (<code>~/.inkscape</code> on Linux) contains a <code>keys</code> subdirectory with a <code>default.xml</code> file, the keybindings from that file will overlay (i.e. add to, and override in case of a conflict) the default bindings. The format of your own <code>default.xml</code> is the same as that of the main <code>default.xml</code>.<br />
<br />
= Miscellaneous shortcuts =<br />
<br />
* Now you can use <b>Shift+middle button drag</b>, in any tool, to zoom into an area. This works the same as simple drag in Zoom tool, but is faster because it does not require switching away from your current tool. Together with <b>middle button drag</b> (panning), <b>middle button click</b> (zoom in) and <b>Shift+middle button click</b> (zoom out), this completes the set of canvas navigation shortcuts available in any tool or context.<br />
<br />
* In Gradient tool, <b>Shift+R reverses the gradient definition</b> (i.e. mirrors the stop positions) without moving the gradient handles. For example, an elliptic gradient with blue center and red periphery becomes red in the center and blue in the periphery. This works on the gradient(s) of the currently selected gradient handle or, if no handle is selected, on all selected objects' gradients. (Compare with the Node tool where Shift+R reverses the direction of the selected path.) This is especially convenient for elliptic gradients which, unlike linear, you cannot simply rotate by 180 degrees for the same result.<br />
<br />
* In Selector, <b>Ctrl+Enter</b> enters the selected group (making it a temporary layer). <b>Ctrl+Backspace</b> leaves the current layer and goes one layer up in the hierarchy (but not to root).<br />
<br />
= Miscellaneous improvements =<br />
<br />
* <b>Document templates</b> (listed in <i>File &gt; New</i>) are now first searched in the <code>templates</code> subdirectory of the user's profile directory (on Linux it's <code>~/.inkscape/templates</code>), then in the system-wide Inkscape templates directory. This allows you to add your own templates on top of the list of standard templates, as well as override the default template with your own one (the <code>default.svg</code> in the profile directory has priority over the system-wide one).<br />
<br />
* <b>Converting stroke to path</b> now correctly processes dashed strokes. For paths with markers, this command now creates a group containing the stroke converted to path and all its markers as independent objects (i.e. they are not markers anymore, but instead you can easily transform them or paint them any color, as a workaround for the "markers don't take the color of the stroke" bug).<br />
<br />
* When toggling one of the "transform with object" buttons (for stroke width, rounded rectangle corners, gradients, or patterns), a <b>message</b> is displayed in the statusbar explaining what has changed in the program's behavior. Hopefully this will reduce the number of complaints from users who had accidentally toggled one of these and were surprised by the result.<br />
<br />
* Whole thousands above 2000 in the rulers are now displayed as <b>2k, 3k, 4k</b> etc.<br />
<br />
* In the Document Preferences dialog, the new object style for each tool is now shown as a <b>style swatch</b> (displaying fill/stroke colors and opacity, stroke width, and master opacity), similar in design to the selected style indicator in the statusbar.<br />
<br />
* In the Grid Arrange dialog, row/column spacing can now be negative. <br />
<br />
* The installation default is now to scale the <b>rounded rectangle corners</b> with the rectangles themselves (the previous default mode, still available as an option, was to keep rounding radii unchanged when scaling rectangles). <br />
<br />
* Added a new <code>--export-area-canvas</code> command line parameter that causes the exported PNG to contain the full canvas. This option as well as <code>--export-area-drawing</code> and <code>--export-area</code> can now be used along with <code>--export-id</code> and <code>--export-id-only</code> for greater flexibility.<br />
<br />
* The <code>--query-*</code> command line parameters now return the true SVG bounding box of the object instead of the Inkscape coordinate system bbox (with inverted Y axis). The new behavior makes more sense for scripting use of Inkscape.<br />
<br />
* The <b>dpi</b> value in the Export dialog has had its range extended; now possible values are from 0.01 to 100000. <br />
<br />
* Individual <b>&lt;tspan&gt;s</b> within text objects (including line tspans) can now be selected via the XML editor to view their bounding boxes (though per SVG, you cannot transform them). Also, you can use the <code>--query-*</code> command line parameters to find out the bounding boxes of tspans from a script. (Individual strings within or between tspans are still not selectable, and they cannot have an ID for querying anyway.)<br />
<br />
* The placeholder image which is shown when a bitmap file was no longer accessible reads now "<b>Linked image not found</b>" instead of the confusing "Broken image".<br />
<br />
* <b>Cloning multiple selected objects</b> now works as expected (i.e. each selected object is cloned separately, similar to the Duplicate command). Previously you could only clone a single selected object. <br />
<br />
* The separate "license" and "contributors" dialogs have been merged into tabs on the About dialog. The about dialog now correctly sizes itself to fit the size of the splash SVG (while remaining resizable), and the rendering area is now cropped to the correct aspect ratio when the dialog is resized. The dialog also now displays the build information in the upper right corner.<br />
<br />
* [new cursors - scislac]<br />
<br />
* In the Transform dialog / Rotate tab, the icon was flipped horizontally to be in line with the direction of positive rotation; the change was applied to the default (now crispy) and legacy icon sets.<br />
<br />
* The <b>scale ratio lock button</b> on the Selector controls bar shows a closed lock when pressed and open lock otherwise (same as the layer lock in the statusbar).<br />
<br />
* The <b>Browse</b> button on Export dialog now opens the new file chooser, same as those used by Open and Save.<br />
<br />
* A new <b>RazorWire</b> path marker was added. By applying it as a mid-marker you can get a good approximation of a razor wire.<br />
<br />
= Miscellaneous bugfixes =<br />
<br />
* Reading a document with an <b>incorrect namespace URI</b> not only did not cause Inkscape to complain, but could also "pollute" Inkscape's internal namespace table, resulting in an "infection" of subsequently saved documents by the incorrect namespace. This is now fixed, but as a result, documents with incorrect namespace URIs will no longer load. You will have to edit them in a text editor to fix the namespaces. <br />
<br />
* With newer versions of GTK, <b>dragging with graphics tablet pen</b> did not work in some tools and contexts (in particular, in Node and Rectangle tools). This is fixed.<br />
<br />
* <b>Scaling of objects with stroke</b> in Selector used to cause undesired shifts of the scaled object, as well as scaling it in the dimension which was intended to remain untouched (e.g. slight change in width when you scale only height). All these problems are now fixed, both for interactive scaling by mouse and for numeric scaling via the Controls bar, and for both values of the "Scale stroke with objects" option. Among other things, this means that stroked objects no longer lose snapping on scale, and that the "Default scale origin" option in the Selector tool preferences finally works as designed. Caveat: There may still be problems if you scale a selection that contains objects with different stroke widths.<br />
<br />
* Scaling of stroke now works for objects that didn't specify stroke-width; before, they always ended up with the default 1px stroke.<br />
<br />
* The bounding box for text and flowed text objects did not include stroke width. This has been fixed.<br />
<br />
* Stroke miterlimit on text objects was misinterpreted in absolute units instead of multiplies of stroke width (resulting in miter joins rendered as bevel). <br />
<br />
* The unfinished path in Pen tool is now cancelled, not finalized, when you switch away from the Pen tool. Apart from being more intuitively correct, this also fixes a crash when you quit Inkscape with the unfinished path in Pen tool.<br />
<br />
* Fonts on Win32 now use the native font mapper, meaning that Inkscape's font list is the same as other Windows programs, and the (potentially) very long delay experienced when using fonts for the first time in each session is gone.<br />
<br />
* Setting dash pattern was broken for transformed objects, and copy/paste of style with dash pattern did not apply correctly to objects with transforms.<br />
<br />
* An error caused a complete extra screen redraw after each zoom operation. That is, after you press "+" in a complex drawing, Inkscape redraws, but for some time after that it remains still unresponsive because it does that second redraw (invisibly for you, i.e. nothing changes on the screen). This is fixed.<br />
<br />
* Gradient rendering was off by one pixel, which often resulted in visibly wrong gradient rendering for small objects or in zoom-out. <br />
<br />
* The SVG path parser could not handle fractional numbers with the initial dot. <br />
<br />
* Several pattern rendering bugs are fixed, discovered by working with SVG files exported from Adobe Illustrator.<br />
<br />
* Inkscape on Mac OS X will now notice fonts in your ~/Library/Fonts directory, in addition to the other standard places.<br />
<br />
* Inkscape couldn't be compiled with libxml versions <= 2.6.9, and we now bumped the requirements from 2.6.0 up to <b>libxml >= 2.6.11</b>, which is the earliest you can get officially, anyway.<br />
<br />
* Inkscape no longer crashes when presented with a defective inx file for extensions.<br />
<br />
* More document memory is now freed when documents are closed.<br />
<br />
* EPS output now correctly includes an %%EOF footer.<br />
<br />
* There was a regression in 0.43 that caused several minor, though annoying bugs; knots and handles remained highlighted after the mouse was released, and the rubberband selection rectangle stayed visible if the selection was ended over a node while in the node tool. This regression has been fixed. <br />
<br />
* The connector routing code would previously sometimes confuse objects between multiple documents resulting in strange routing behaviour. This has been fixed.<br />
<br />
* There existed a bug in 0.43's Inkboard code that allowed a malicious outsider to very easily disrupt an Inkboard session. This has been fixed.<br />
<br />
* There existed a bug in 0.43's Inkboard code that would cause deadlocks in the case that two users attempted to invite each other at the same time (see bug #[https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1352522&group_id=93438 1352522] for further details). This should be fixed, although the fix has not been widely tested.<br />
<br />
* There existed a bug in 0.43's Inkboard code that would cause session invitations to not appear on the invitee's screen. This was the result of a mistake in handling GDK modifier flags, and has been fixed.<br />
<br />
= Translations =<br />
<br />
* INX files (containing the UI of the external effects) now allow the user visible strings to be translated. This means that effect dialogs, file type selections, and extension names can all be translated by translators.<br />
<br />
= Internal =<br />
<br />
* The Document Properties Dialog code was completely gtkmmified, which lead to dramatic reduction of code size due to usage of widget objects. The used widget objects should be reusable by other dialogs, too, and the code is much more readable.<br />
<br />
* Work on optimizing includes in all cpp files started, using the purgeincludes tool specifically written for that purpose, and ended with 40% of include lines removed!<br />
<br />
= Known problems =<br />
=== Problems with libgc-6.7 ===<br />
* Inkscape will hang or even crash when linked with this (newest) version of the Boehm garbage collection library. Make sure you use libgc-6.5 or 6.6 until this is sorted out.<br />
<br />
=== Namespaces may need fixing ===<br />
<br />
* Previous versions of inkscape sometimes silently saved documents with <b>wrong namespace URIs</b>. This has been fixed, but such corrupted documents will no longer load successfully. Such documents may require their namespace declarations to be fixed by hand.<br />
<br />
=== Beware of defective themes on Linux ===<br />
<br />
* Inkscape and other Gtk programs can crash on any Linux, when the <b>gtk2-engines-smooth / libsmooth</b> package is installed. We have filed a bug against libsmooth which is now in gtk-engine and part of gnome. Removing the package resolves the problem, however, but it would be nice if you as affected user would inform the gtk-engines maintainers of the problem. See especially http://bugzilla.gnome.org/show_bug.cgi?id=312115 (thanks to Thomas Wood)<br />
* A similar crash happens if the <b>KDE Baghira</b> theme or the package <b>gtk_qt_engine</b> are installed. If you experience Inkscape crashes on KDE, please try to install a different theme from Baghira, or uninstall the gtk_qt_engine package from your system. Both problems also affect older versions of Inkscape.<br />
<br />
=== Make sure to remove menus.xml if you have it ===<br />
<br />
* If you were using certain CVS/SVN builds from autumn of 2005, you may have the file <code>menus.xml</code> hanging around in your profile directory (e.g. <code>~/.inkscape</code> on Linux). In that case you will see many errors about verbs that cannot be found, and some commands in menus will be disabled. Make sure to delete <code>menus.xml</code> to fix this.<br />
<br />
= Previous releases =<br />
<br />
* ReleaseNotes043 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes043)<br />
* ReleaseNotes042 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes042)<br />
* ReleaseNotes041 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes041)<br />
* ReleaseNotes040 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes040)<br />
* ReleaseNotes039 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes039)<br />
* ReleaseNotes038 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes038)<br />
* ReleaseNotes037 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes037)<br />
* ReleaseNotes036 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes036)<br />
* ReleaseNotes035 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes035)</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=Notes_Alliberament&diff=6649Notes Alliberament2006-06-05T13:44:28Z<p>Xaviconde: /* Performance */</p>
<hr />
<div>== Inkscape 0.44: resum ==<br />
<br />
L'Inkscape 0.44 és més gran i millor que mai! Alguns dels aspectes destacats són:<br />
<br />
* Diàleg de capes<br />
<br />
* Mode contorn, amb millores del rendiment<br />
<br />
* Exportació nadiva en PDF amb transparència<br />
<br />
* Clipping and masking support<br />
<br />
* Dreceres de teclat configurables, incloent emulació de Xara <br />
<br />
* Paleta de color adjuntada en la finestra d'edició de la paleta de colors<br />
<br />
* Indicador interactiu de l'estil de la selecció a la barra d'estat<br />
<br />
* Un innovador "esculptor de nodes" i altres millores a l'eina de nodes<br />
<br />
* Ara les extensions estan habilitades per defecte i funcionen tant a Linux com a Windows<br />
<br />
* Millor suport d'SVG: element <switch>, perfils de color ICC per a les imatges<br />
<br />
* Centres de rotació persistents, ordre per enganxar la mida<br />
<br />
* S'ha redissenyat el diàleg de preferències, noves icones, menús reordenats, moltes millores cosmètiques<br />
<br />
* Centenars de correccions d'errors i petites millores<br />
<br />
* Encara que no està relacionat directament amb l'Inkscape, val la pena notar que des de la darrera versió, ara [http://www.mozilla.com/firefox/ Firefox 1.5] suporta per defecte el format SVG. Això significa que podeu veure qualsevol document SVG en la vostra finestra del Firefox sense convertir entre formats o instal·lant connectors addicionals.<br />
<br />
= Rendiment =<br />
<br />
== Mode contorn ==<br />
<br />
S'ha implementat el mode de visualització de contorn ("cablejat"). Useu <i>Visualització > Mode de visualització > Contorn</i> per activar-lo. En aquest mode:<br />
<br />
* tots els camins i formes es dibuixen com a <b>contorns invertits</b> (negre sobre fons clar i viceversa) de mida constant (1 píxeld de pantalla, independentment de l'ampliació), i sense emplenat,<br />
<br />
* el text és pinta amb emplenat invers, sense contorn,<br />
<br />
* els mapes de bits es mostren tal qual,<br />
<br />
* s'ignora l'opacitat i els desgradats.<br />
<br />
En general, el mode contorn no és dràsticament més ràpid que el mode regular (normalment entre un 10% i un 50%), i en alguns casos especials pot ser fins i tot més lent. Tanmateix, el valor del mode de contorn rau no només en la seva velocitat; també és una bona manera de fer-se una idea de l'estructura i els objectes d'un document, i és convenient per a editar nodes amb precisió i per trobar objectes "perduts".<br />
<br />
== Velocitat ==<br />
<br />
A més del mode contorn, que fa més senzill treballar amb dibuixos complexos, aquesta versió de l'Inkscape també proporciona millores significants en la velocitat en moltes àrees.<br />
<br />
* Gràcies a les <b>optimitzacions en el representador</b>, el redibuix a la pantalla de l'Inkscape és <b>almenys un 10% més ràpid</b>, i en alguns casos (com en camins puntejats en ampliacions altes) <b>fins a tres vegades superior</b>.<br />
<br />
* <b>Optimizations in the Node tool</b> resulted in noticeable speed gains for node editing. Thus, switching to and from the Node tool (with a path selected), as well as selecting nodes in that tool, are now <b>at least ten times faster</b> than before. Other operations, including curve and node dragging and move/scale/rotate operations on multiple selected nodes, are much faster as well. This is especially important when working with complex paths; with these optimizations, paths containing several thousand nodes, though still slow, are much more usable.<br />
<br />
* An optimization in the attribute setting method made operations such as moving multiple objects with arrow keys at least <b>30% faster</b> compared to 0.43. This is especially noticeable when you are moving clones selected together with their original (e.g. a clone tiling), in which case Inkscape now works <b>three to four times faster</b>.<br />
<br />
* <b>Interface icons</b> are now rendered in the background (from SVG source in <code>share/icons/icons.svg</code>) when Inkscape is idle, rather than waiting for all the icons in a menu to render the first time you pull it up. This eliminates the annoying delay when opening menus for the first time.<br />
<br />
* Previously, zooming in to view a small portion of a path (especially big and complex path), there was a very noticeable slowdown and memory use increased dramatically. We optimized the renderer to <b>only process the visible part of a path</b>, and as a result the rendering speed is now almost the same at any zoom up to the maximum, providing up to 10-40 times speedup compared to the previous version (the closer is the zoom, the greater is the gain).<br />
<br />
* The <b>Path > Break Apart</b> command is now dozens of times (up to 100x) faster for complex paths with thousands of subpaths.<br />
<br />
= Interface =<br />
<br />
== Layers dialog ==<br />
<br />
* Ctrl+Shift+L [joncruz, mental]<br />
<br />
== Selected style indicator ==<br />
<br />
A new control in the left end of the statusbar lets you quickly view and change the <b>fill and stroke of the selected objects</b>. When you have a text selection in Text tool or a gradient handle selected in the Gradient tool, this indicator displays and changes the style of the text fragment or gradient stop, instead of the entire object (it's the same behavior as the Fill&amp;Stroke dialog.)<br />
<br />
* The two indicators, labelled <b>F:</b> (top) and <b>S:</b> (bottom), display fill and stroke of the selected object(s) correspondingly. (For gradient handles, they always display the same style.)<br />
<br />
* Each fill/stroke indicator can display either a <b>color+opacity swatch</b> (the opacity shown here is the fill opacity or stroke opacity, not the master opacity) or a text label specifying <b>N/A</b> (nothing selected), <b>None</b> (no fill/stroke), <b>Unset</b> (unset fill/stroke), <b>L Gradient</b>, <b>R Gradient</b>, <b>Pattern</b> (corresponding fill/stroke types), or <b>Different</b> (selected objects have different fill/stroke types).<br />
<br />
* Additionally, each indicator may be accompanied by one of two flags, <b>m</b> ("multiple", meaning there are two or more objects all with the same fill/stroke) or <b>a</b> ("averaged", meaning there are two or more objects with different flat colors in fill/stroke, and the indicator shows the average of these colors).<br />
<br />
* <b>Left-click</b> on an indicator opens or activates the Fill&Stroke dialog with the corresponding tab (Fill or Stroke) active.<br />
<br />
* <b>Right-click</b> on an indicator opens a popup menu with the following items:<br />
** <b>Edit fill/stroke...</b>: Opens or activates the Fill&Stroke dialog with the corresponding tab selected. (Same as left-click.)<br />
** <b>Last set color</b>: Applies to the selected objects the fill/stroke color that was last applied to anythig.<br />
** <b>Last selected color</b>: Applies to the selected objects the fill/stroke color that was last displayed in this indicator. (Allows you to easily copy fill/stroke color between objects: select source, select destination, apply "last selected color".)<br />
** <b>Invert</b>: Sets the fill or stroke to the inverse of the current color (does not affect opacity).<br />
** <b>White</b>, <b>Black</b>: Sets the fill or stroke to the corresponding color (fully opaque).<br />
** <b>Copy color</b>, <b>Paste color</b>: Copies or pastes the fill or stroke color (when it's color) to/from the system clipboard, as text in the <code>#rrggbb</code> hex format.<br />
** <b>Swap fill and stroke</b>: Exchanges fill and stroke (both their types and colors, if any). <br />
** <b>Make fill/stroke opaque</b>: Removes fill or stroke transparency (not master transparency!).<br />
** <b>Unset fill/stroke</b>: Unsets fill or stroke from selected objects.<br />
** <b>Remove fill/stroke</b>: Removes fill or stroke from the selected objects.<br />
<br />
* <b>Middle-click</b> on a fill/stroke indicator removes fill/stroke from selected objects; if it is already removed (i.e. if the indicator displays "None"), it does the same as the "Last set color" command from the popup menu.<br />
<br />
* <b>Drag and Drop</b> of colors onto a fil/stroke indicator sets the fill and stroke of the selected object(s) correspondingly.<br />
<br />
* The Stroke indicator also displays the <b>stroke width</b> of selection (averaged if there are multiple objects selected with different stroke widths), located to the right of the stroke color/transparency swatch. Left-clicking on it opens the Fill&Stroke dialog with the Stroke Style tab selected. Right-clicking on it opens a popup menu which allows you to choose the units for displaying the stroke width, as well as choose one of the presets to assign to selection.<br />
<br />
* To the right of the fill/stroke indicators, the <b>Opacity</b> numeric field (labelled "O:") shows and allows you to change the master opacity of the selected object (or the averaged opacity of several selected objects). <b>Right-clicking </b> the numeric field opens a popup menu with preset opacity levels. <b>Middle-clicking</b> on the "O:" label cycles the opacity through the values of 0 (transparent), 0.5, and 1 (opaque).<br />
<br />
The zoom field and the cursor coordinates indicator have been rearranged for compactness and moved to the right end of the statusbar. There's also a window resize handle added at the very end of the statusbar.<br />
<br />
== Eina d'indicador d'estil ==<br />
<br />
Per a cada eina per crear objectes (formes, Bolígraf/Llapis, Cal·ligràfic, Text), la barra de control (al damunt) inclou ara un <b>indicador d'estil</b> a la dreta. Aquest indicador mostra quin estil tindrà l'objecte nou. L'indicador mostra correctament qualsevol estil que l'eina pot utilitzar - el "darrer" estil o l'estil fix d'aquella eina. Per exemple, fent clic a un paleta (fins i tot sense seleccionar res) canvia el "darrer" color posat i, si està configurada per utilitzar l'últim conjunt de color, el seu indicador s'actualitza, donant-li una idea del seu "pinzell" abans que comenci a dibuixar.<br />
<br />
== Controls bar for the Text tool ==<br />
<br />
* This version adds the beginnings of a Controls Bar for the Text tool (previously empty). Now you can select the <b>font family</b>, <b>size</b>, apply <b>bold</b> and <i>italic</i> styles, change <b>alignment</b> and <b>text orientation</b> without opening the Text and Font dialog. <br />
<br />
* All controls are <b>instant-apply</b> and work on the entire text object (if nothing selected) or text selection. They can also apply to multiple text objects (though you would need to switch to Selector to select multiple text objects, then switch back to Text tool for its controls). <br />
<br />
* The font-family drop-down contains names and <b>previews</b> of all fonts; unlike other programs, we didn't apply each font to its name, but added a separate preview string displayed with gray color after each font's name. This design ensures readability of font family names and provides maximum useful information in a limited space.<br />
<br />
* We will be adding more controls (including spacing and kerning) to this bar for the next versions.<br />
<br />
== Docked color palette ==<br />
<br />
* Previously, color swatches could only be used from a floating palette (Ctrl+Shift+W). Now the color swatches palette is embedded in the main UI, at the bottom of the window between the canvas and the statusbar. It is enabled by default; use <i>View > Show/Hide > Palette</i> to enable or disable it. The docked palette has the same functionality as the floating one; use a button in the top right corner to access the swatches menu.<br />
<br />
* The <b>Wrap</b> option (off by default) in the swatches menu converts the palette from a single row into a frame 2 or 3 rows high, for better access to colors in large palettes.<br />
<br />
* <b>Drag and Drop</b> of <b>colors</b> has been enabled.<br />
** Dragging colors from a palette shows a live swatch of the color being dragged under cursor.<br />
** Drag and Drop of colors onto the selected style indicator in the statusbar sets the fill or stroke of the selected object(s).<br />
** Colors can be <b>dropped</b> directly on to objects on canvas to set their <b>fill</b>, or <b>shift+dropped</b> to set their <b>stroke</b>. This affects only the object you drop the color on, regardless of whether that object is selected or not.<br />
** Colors can be dragged to and from other applications.<br />
<br />
* The new <b>Inkscape default</b> color palette was added. It contains a range of grays, standard HTML named colors, and a full range of colors sorted by their HSL values (475 colors overall). It is generated by a Python script which is available from Inkscape SVN in share/palettes.<br />
<br />
* Several <b>specialized color palettes</b>, useful in color-coordinated projects, were created or borrowed from GIMP: Grays, Reds, Greens, Blues, Gold, Royal, Khaki, Hilite, and Topographic.<br />
<br />
* All standard sizes of the swatches (Tiny, Small, Medium, Large, Huge) are made <b>smaller</b> overall.<br />
<br />
== Inkscape Preferences dialog ==<br />
<br />
Not only was the Inkscape Preferences dialog completely rewritten and redesigned, it is now also <b>fully GNOME-HIG compliant</b>. Numerous <b>bugs</b> were taken care of with the rewrite. As a new feature, the <b>Simplify threshold</b> can now be set with more precision.<br />
<br />
== Document Properties / Metadata dialogs ==<br />
<br />
* The Document Preferences dialog is now named <b>Document Properties</b>, and it was split in two: metadata were extracted into the <b>Document Metadata</b> dialog; metadata widgets are now also spread over two pages.<br />
<br />
* A button was added to <b>fit the canvas to the current selection</b> or, if there's no selection, to the entire drawing. The button resizes the canvas and, if necessary, moves the drawing into place. It is now very easy to size the canvas to an illustration after it is ready.<br />
<br />
* <b>New controls</b>: the new object snapping features required their own property widgets, and you can set the snapping sensitivity with a slider, or let it snap regardless of distance (grid only).<br />
<br />
* Rearrangements within <b>Document Properties</b>: everything snapping-related was collected on one page; Grid and Guide widgets are on their own, the same page. For better HIG compliance, all widgets were categorized; especially the widgets on the Page page were completely rearranged in the General/Format/Border categories.<br />
<br />
* <b>Bug fixes</b>: grayed out license URI had too low contrast, so it's no longer grayed out; the proprietary license didn't clean the license URI; spinbuttons had no tooltips, and minor grid quirks were removed; data was not updated when a new file replaced another in the same window.<br />
<br />
* <b>HIG compliance</b>: much work went into that, and now only a few details are missing from full Gnome-HIG compliance.<br />
<br />
* <b>Updated Creative Commons Licenses</b>: Updated CC licenses to the latest 2.5 versions by default in the license tab of the metadata dialog.<br />
<br />
== Menus ==<br />
<br />
* <b>Zoom</b> commands in the View menu are moved to a submenu; the <i>Zoom In</i> and <i>Zoom Out</i> commands are added to that submenu.<br />
<br />
* <b>Clone</b> commands are moved into a submenu in Edit menu and given more descriptive names and tips.<br />
<br />
* <b>Pattern</b> commands (<i>Objects to Pattern</i> and <i>Pattern to Objects</i>) are moved into a submenu in Object menu, under the new Clip and Mask submenus.<br />
<br />
* The contents of the <b>Effects menu</b> are categorized into submenus, and several effects are renamed to use more intuitive names. <br />
<br />
== Statusbar ==<br />
<br />
* In Selector, for multiple selected objects, the statusbar now reports their types. For example, if 5 groups are selected, it displays<br />
<br />
::<b>5</b> objects of type <b>Group</b> in layer <b>LayerName</b>.<br />
<br />
:instead of just "5 objects selected" as before. If there are up to 3 types in the selection, they will be listed, for example:<br />
<br />
::<b>5</b> objects of types <b>Group</b>, <b>Path</b>, <b>Rectangle</b> in layer <b>LayerName</b>.<br />
<br />
:The order of the list will correspond to the order in which the objects were added to selection. If there are 4 or more types in selection, only the number of types is reported, for example:<br />
<br />
::<b>5</b> objects of <b>4</b> types in layer <b>LayerName</b>.<br />
<br />
* In Selector, objects selected in groups are now identified as such, and the group ID is given, for example:<br />
<br />
::<b>Rectangle</b> in group <i>g212</i> (layer <b>content</b>)<br />
<br />
:If selected objects have different parents within one layer (for example, if one is selected in a group and another outside it), the number of parents is reported:<br />
<br />
::<b>2</b> objects of types <b>Rectangle</b>, <b>Path</b> in <b>2</b> parents (layer <b>content</b>)<br />
<br />
:If objects are in different layers, only the number of layers is reported since this also implies different parents:<br />
<br />
::<b>2</b> objects of types <b>Rectangle</b>, <b>Path</b> in <b>2</b> layers<br />
<br />
* In Node tool, if your node selection includes nodes from different subpaths, statusbar reports the number of subpaths with selection and the total number of subpaths, for example:<br />
<br />
::<b>2</b> of <b>195</b> nodes selected in <b>2</b> of <b>36</b> subpaths.<br />
<br />
* The contents of the statusbar message are now duplicated as a <b>tooltip</b> that is shown when you hover the mouse over the statusbar. [TODO: need to strip markup from the tooltips.] <br />
<br />
* The statusbar text is now no longer just cut off if there is insufficient room, but an ellipsis (...) is inserted at the end to show there's more (only with Gtk 2.6 and newer).<br />
<br />
== Theme ==<br />
<br />
* Inkscape has a <b>new default icon set</b> titled "Crispy" provided by Andre Sousa. The new icons are intended to add a more professional and cohesive look to our application, as well as to make the functions the icons represent more self-evident.<br />
<br />
= Clipping and masking =<br />
<br />
Inkscape now provides some UI for using <b>clipping paths and masks</b>. <br />
<br />
* Any object can be non-destructively intersected with a path (called a <i>clipping path</i>) so that only the intersected portion of the object is visible. <br />
** <b>To apply clipping</b>, select the objects to be clipped and the clipping path object, make sure the clipping path is above the other objects in z-order, and do <i>Object > Clip > Set</i>.<br />
** You can <b>transform, edit, or style</b> the clipped objects as usual. The clipping remains applied and transforms together with each clipped object.<br />
** To <b>remove the clipping</b>, do <i>Object > Clip > Release</i>. The clipping path is returned to the drawing as a regular object; it is inserted on top of the unclipped object in z-order. <br />
<br />
* Any object can be non-destructively masked by another object (called <i>mask</i>) so that: the mask's black or transparent areas become fully transparent in the masked object; mask's opaque white areas become fully opaque; and all intermediate colors translate into intermediate levels of opacity in the masked object. This allows you to apply, for example, arbitrary transparency gradients to objects.<br />
** To <b>apply a mask</b>, select the objects to be masked and the mask object, make sure the mask is above the other objects in z-order, and do <i>Object > Mask > Set</i>.<br />
** You can <b>transform, edit, or style</b> the masked objects as usual. The mask remains applied and transforms together with each masked object.<br />
** To <b>remove the masking</b>, do <i>Object > Mask > Release</i>. The mask is returned to the drawing as a regular object; it is inserted on top of the unmasked object in z-order. <br />
<br />
* Objects with clippath show their bounding box intersected with the bounding box of the clippath, instead of the original unclipped bbox as before. (However, this does not apply to objects without clippath of their own which are clipped by being inside a clipped group.)<br />
<br />
* Clipped or masked objects display "<i>clipped</i>" or "<i>masked</i>", correspondingly, in their statusbar descriptions.<br />
<br />
* Although Inkscape had render-only support for clipping paths and masks for quite some time, in this release we fixed a number of bugs which may affect the display of your documents using clippaths or masks.<br />
** Clippaths and masks with objectBoundingBox units are now shown correctly upon loading of the document.<br />
** Clippaths without fill didn't work, this is now fixed.<br />
** Objects with clippaths or masks are correctly copied/pasted between documents.<br />
<br />
= SVG conformance =<br />
<br />
== Color profile support ==<br />
<br />
Inkscape now includes base ICC profile functionality. If compiled with LittleCMS support (if you run <code>configure</code> with <code>--enable-lcms</code> switch), Inkscape passes the [http://www.w3.org/Graphics/SVG/Test/20030813/htmlframe/full-color-prof-01-f.html ICC color profile test] by W3C. The &lt;color-profile&gt; element has been implemented along with the "color-profile" attribute for &lt;image&gt; elements.<br />
<br />
== &lt;switch&gt; support ==<br />
<br />
Rendering support for SVG 1.1's '''Conditional Processing Module''' has been implemented, including ''switch'' element, ''requiredFeatures'', ''requiredExtensions'', ''systemLanguage'' attributes. Inkscape passes the Conditional processing tests ([http://www.w3.org/Graphics/SVG/Test/20030813/htmlframe/full-struct-cond-01-t.html] and [http://www.w3.org/Graphics/SVG/Test/20030813/htmlframe/full-struct-cond-02-t.html]) by W3C.<br />
<br />
== SVG output ==<br />
<br />
* In Inkscape's SVG documents, <b>colors</b> are now expressed by name (‘white’) or three-digit form (‘<tt>#f3c</tt>’) when possible.<br />
<br />
* The numeric values in <code>transform</code> attributes are written without insignificant trailing zeros, and anything less than that 1e-8 by absolute value (usually caused by rounding errors) is written as 0 to reduce clutter.<br />
<br />
= Transformations =<br />
<br />
== Transform dialog ==<br />
<br />
Fixes and improvements in the Transform dialog (Ctrl+Shift+M):<br />
<br />
* The <b>Apply to each object separately</b> checkbox is added, allowing you to scale/rotate/skew each selected object by the same amount, around that object's center. When off (by default), the selection is transformed as a whole. The status of this checkbox is remembered across sessions. (It has no effect on Move and Matrix tabs).<br />
<br />
* The <b>Clear</b> button resets the values on the current tab to defaults.<br />
<br />
* The <b>Scale</b> tab now allows you to specify horizontal or vertical size increments in percentage or absolute units. Also, there's a <b>Scale proportionally</b> checkbox which ensures that scaling preserves the width/height ratio. (If you are scaling several objects proportionally with "Apply to each object separately", you can only use the % unit to specify the scaling; otherwise each object's scale increments will have the width/height ratio of the entire selection, not of that specific object.)<br />
<br />
* The <b>Skew</b> tab can now specify the skew as an <b>absolute displacement</b> (e.g. for horizontal skewing of a rectangle, that means the shift of the top rectangle side relative to the bottom), as <b>percentage displacement</b> (e.g. a 1% horizontal skew of a rectangle means shifting the top side by 1% of the rectangle height), or as an <b>angle</b> (e.g. horizontal skew by 15 degrees results in the sides of a rectangle being rotated to that angle, while the top and bottom remain horizontal).<br />
<br />
* The <b>Matrix</b> tab (previously called "Transform") can either edit the current <code>transform=</code> matrix of an object, or post-multiply the <code>transform=</code> with the matrix you specify, depending on the <b>Edit current matrix</b> checkbox. (As it is now redundant, the transformation matrix in the Object Properties dialog is removed.)<br />
<br />
* The dialog now correctly <b>watches selection changes</b> in the active document window and updates its values accordingly.<br />
<br />
* The layout of the dialog is simplified, tooltips and mnemonics added for better usability.<br />
<br />
* Many bugs are fixed, especially in value conversions between units.<br />
<br />
== Persistent rotation centers ==<br />
<br />
* The position of the center (axis) of rotation and skewing used by Selector is now <b>remembered</b> for all objects and restored when you select those objects again (even after saving and reopening the document). When you move or scale an object, its rotation center is moved or scaled too, so its position relative to the object always remains the same unless you move it explicitly.<br />
<br />
* When you have several objects selected, they use the rotation center of the <b>first selected object</b>. If the first object does not have center set (i.e. if it's in a default central position), then several objects will rotate around the geometric center of their common bounding box (as before).<br />
<br />
* <b>Shift+click</b> on the rotation center resets it back to the center of the object's box.<br />
<br />
* Consequently, dragging the rotation center is now <b>an undoable action</b>; you can press Ctrl+Z to undo the drag.<br />
<br />
* <b>Keyboard rotation</b> by [, ] keys with various modifiers, as well as the Rotate tab in the <b>Transform dialog</b>, work around the selected object's rotation center (for multi-object selection, the rotation center of the first selected object).<br />
<br />
* Rotation centers are <b>preserved</b> when duplicating, cloning (including clone tiler), grouping/ungrouping, and converting to path.<br />
<br />
[TODO: <br />
- make it work smartly for groups: if a group has center not set, return the center of the first object inside group with the center set<br />
<br />
- a separate tab in the Transform dialog, with 9 buttons in the square grid (for setting it to object's corners, sides, and center) as well as x/y fields for setting center to any position<br />
<br />
- make center snap to grid/guides/objects and to other centers<br />
<br />
- make objects snap with their center to grid/guides/objects]<br />
<br />
== Pasting size ==<br />
<br />
A number of commands are added to easily scale selected objects to match the size of the object(s) previously copied to the clipboard. They are all in the Paste Size submenu in Edit menu:<br />
<br />
* <b>Paste Size</b> scales the whole selection to match the overall size of the clipboard object(s).<br />
<br />
* <b>Paste Width</b>/<b>Paste Height</b> scale the whole selection horizontally/vertically so that it matches the width/height of the clipboard object(s). These commands honor the scale ratio lock on the Selector controls bar (between W and H fields), so that when that lock is pressed, the other dimension of the selected object is scaled in the same proportion; otherwise the other dimension is unchanged.<br />
<br />
* <b>Paste Size Separately</b>, <b>Paste Width Separately</b> and <b>Paste Height Separately</b> work similarly to the above described commands, except that they scale <i>each selected object</i> separately to make it match the size/width/height of the clipboard object(s).<br />
<br />
= Tools =<br />
<br />
== Node tool ==<br />
<br />
=== Node sculpting ===<br />
<br />
An entirely new way of manipulating paths in Node tool is added in this version: Node sculpting. Normally, when you have several nodes selected and you drag one of them, all selected nodes move by the same amount. Now, if you <b>Alt-drag</b> one of the selected nodes, only that node is fully displaced; other selected nodes are moved less than the full amount, so that those farthest from the drag point remain stationary. This is similar to "proportional editing" or "soft selection" in 3D editors such as Blender.<br />
<br />
So, for example, if you select several nodes on a straight line and Alt+drag the middle selected node, the path will bend into a <b>smooth bell-like curve</b>. Nodes' handles are also adjusted correspondingly to keep the overall shape smooth and natural. (If you don't have enough nodes on a path fragment that you want to reshape in this way, just select the end nodes of that fragment and press <b>Ins</b> a few times to populate it with nodes.)<br />
<br />
Moreover, node sculpting is <b>sensitive to pressure</b> of your tablet pen. If you press slightly, your curve will have a narrow sharp tip (i.e. the nearest neighbors of your dragged node will move only a bit); if you press hard, the curve's tip will be wide and blunt (i.e. the nearest neighbors will move almost as much as the dragged node). (Hint: to stop dragging without losing your shape, first release Alt and then lift the tip of the pen.)<br />
<br />
There are many possible applications of the sculpting technique. To take a simple example, selecting all nodes of an ellipse-like shape and Alt+dragging one of them will smoothly and naturally stretch and skew the entire shape in any direction. Doing the same to a complex path, such as star or spiral, will twist and punch it without destroying its intricate structure - this is the way to get squashed or self-intersecting stars, eccentric spirals and other shapes not easily doable before. Selecting only part of all nodes allows you to smoothly reshape parts of the figure without disturbing the rest.<br />
<br />
When applied to text converted to path, node sculpting is a fun and easy way to twist, bend and distort it, achieving effects similar to "perspective envelope" or "curvilinear envelope" in other programs - but in a more powerful and flexible way. For example, by selecting all or part of the text's nodes and Alt-dragging, you can not only make a wavy banner out of a paragraph of text, but also apply a "magnifying lens"-like effect to any word in the middle. <br />
<br />
Especially useful node sculpting is for complex natural paths, such as calligraphic strokes or bitmap traces, where you often want to do large-scale pushes and bends without destroying the small-scale features. Things like making a calligraphic stroke narrower in one place and wider in another, or changing the proportions, extending the ear or flattening the nose of a head - all this is now much faster and more natural to do using sculpting. It is also a new way to <i>create</i> new paths, too - starting from en ellipse with added nodes, it takes just a few Alt+drags to tweak it into a silhouette of a head, or a map of Australia, or an Inkscape logo!<br />
<br />
Some examples are shown on the screenshot: [[http://www.inkscape.org/screenshots/gallery/inkscape-0.44-nodesculpting.png]].<br />
<br />
=== "Show handles" toggle ===<br />
<br />
The Controls bar for the Nodes tool now includes a toggle button which controls whether Bezier handles are shown on selected nodes (on by default). Selecting and dragging nodes on node-dense paths in zoom-out (e.g. for node sculpting) may be extremely difficult without hiding the handles, as it's hard to pick a node and not a handle when handles are shown.<br />
<br />
=== New deletion behavior ===<br />
<br />
* In Node tool, <b>deleting node(s)</b> by Del/Backspace keys or by Ctrl+Alt+clicking a node now <b>tries to preserve, as much as possible, the current shape of the path</b>. This means that the nodes adjacent to those being deleted have their handles adjusted to approximate the form that the path had before deletion. For example, if you Ctrl+Alt+click a path twice, once to add a new node and then to delete it, the path will not change at all (or change very slightly). The old deletion behavior without adjusting handles is still available via <b>Ctrl+Del</b> or <b>Ctrl+Backspace</b>.<br />
<br />
=== Preserving positions of nodes and handles ===<br />
<br />
* When you <b>switch the type</b> of the selected node to Smooth or Symmetric by pressing Shift+S/Shift+Y, you can now <b>preserve the position</b> of one of the two handles by hovering your mouse over it, so that only the other handle is rotated/scaled to match.<br />
<br />
* Similarly, when you <b>join endnodes</b> by pressing Shift+J, you can <b>preserve the position</b> of one of the two nodes by hovering your mouse over it, so that only the other node is moved. <br />
<br />
=== Miscellaneous ===<br />
<br />
* The <b>!</b> key <b>inverts node selection</b> in the current subpath(s) (i.e. subpaths with at least one selected node); <b>Alt+!</b> inverts in the entire path. (This is similar to how these keys work in Selector, with current subpath(s) instead of the current layer.)<br />
<br />
* The keyboard shortcut for "Make selected segments curves" in Node tool is changed from Shift+K to <b>Shift+U</b> for better mnemonics.<br />
<br />
== Calligraphic pen ==<br />
<br />
* Even when using a graphics tablet with pressure sensitivity, the Calligraphy pen's strokes often look too smooth and artificial. To enable a more natural look, the new <b>Tremor</b> parameter is added to the Calligraphy tool in this version. Adjustable in the Controls bar from 0.0 to 1.0, it will affect your strokes producing anything from slight unevenness to wild blotches and splotches. This significantly expands the creative range of the tool.<br />
<br />
* In all previous versions, pen width depended on zoom in such a way that the strokes <i>appeared</i> the same visible width at any zoom, but were in fact narrower at zoom-in and wider at zoom-out. This behavior makes sense if you want to keep the same "feel" of the pen regardless of zoom; for example, if you zoomed in to make a small fix to your drawing, it's natural that your pen becomes physically smaller but feels the same to you. So, this behavior is kept as the default, but now we also added an alternative mode where your <b>pen width is constant in absolute units</b> regardless of zoom. To switch to this mode, use the checkbox on the tool's Preferences page (you can open it by double-clicking the tool button).<br />
<br />
* The <b>Width</b> field in the tool's controls bar now changes <b>from 1 to 100</b>, which corresponds to the range from 0.01 to 1.0 in the previous version. If the "width in absolute units" mode is turned on, the value in this fields gives the width of the stroke in px units. In the default mode, the value of 100 gives 100px wide strokes only at 100% zoom, and strokes are correspondingly narrower or wider at other zoom levels.<br />
<br />
* A new preferences option for the Calligraphic tool, <b>Keep selected</b>, controls whether the newly created object remains selected after you finish drawing it. If you turn it off (by default it's on) and set the tool to using Last Set color, you can easily choose a new color by clicking on the palette without having to worry if this will change the color of the stroke you just created. (Watch the tool style indicator at the right end of the Controls bar for the style of the next stroke you will draw.)<br />
<br />
* <b>Esc</b> deselects selected objects in Calligraphic, as in most other tools.<br />
<br />
* The stroke you're drawing is now shown, while you're drawing it, with the correct color and opacity that it will eventually have, instead of always black as before.<br />
<br />
* On a new Inkscape installation, this tool now uses the last set style by default instead of the fixed black as before (this is changeable in the Inkscape Preferences for the tool).<br />
<br />
== Pen tool ==<br />
<br />
* While drawing a path, you can now <b>move the last node you created</b> by the same keys as in Node tool - that is, arrows, with Shift (for 10x displacement) or Alt (screen pixel displacement) modifiers. <br />
<br />
* Also, you can switch the not-yet-finalized (red) segment of the path being drawn from curve to line (<b>Shift+L</b>) or back to curve (<b>Shift+U</b>), again the same shortcuts as in the Node tool.<br />
<br />
* By popular demand, if a new path is being drawn but not yet finished, <b>Ctrl+Z cancels</b> that unfinished path (i.e. does the same as Esc), instead of undoing the previous action.<br />
<br />
* In Pen tool, <b>Del</b> works the same as Backspace to delete the last created point on the unfinished path.<br />
<br />
= Connectors and automatic layout =<br />
<br />
* There have been numerous bugfixes and several improvements to the behaviour of <b>connectors</b> and the <b>connector tool</b>:<br />
** Connectors moved as part of a selection will now stay attached to other objects in the selection, rather than becoming detached from them.<br />
** By default, the Connector tool will not attach connectors to text objects. There is a new checkbox in the connector preferences to control this setting.<br />
** The <b>margins around avoided shapes</b> (used for autorouting connectors) can now be adjusted via the "Spacing" control on the controls bar.<br />
<br />
* Automatic Diagram Layout - A new button is available in the alignment and distribution dialogue that performs automatic layout of diagrams involving a network of shapes and connectors. Layout is accomplished using force-directed graph layout based on the Kamada-Kawai algorithm. This algorithm treats edges as if they are springs such that the distance between nodes will be proportional to the path length---number of connectors---between them. Disconnected components (where not every shape is connected) will be arranged around the circumference of a circle.<br />
<br />
* There is a new <b>Remove Overlaps</b> button to move the selected objects enough that they don't overlap each other. A minimum spacing between the boundaries of objects can be specifiedTogether with the automatic layout tool, described above, this should be a significant addition to Inkscape's usability for diagramming. [Consider expanding this, comparing with existing Unclump and Distribute edge-to-edge buttons. - pjrm]<br />
<br />
= Selective tracing with SIOX =<br />
<br />
[ishmal]<br />
<br />
<br />
= Snapping =<br />
<br />
* [object snap - carl]<br />
<br />
* [highlight - mtou]<br />
<br />
* [only to visible gridlines - mtou]<br />
<br />
* <b>Guidelines</b> are made easier to pick: now you don't need to position mouse <i>exactly</i> over a guideline to activate it, instead there's a small position tolerance (1 screen pixel on each side of the guideline).<br />
<br />
= Sublayers =<br />
<br />
Previously, it was only possible to make a group a temporary sublayer by entering that group. Now Inkscape supports creating and using true persistent sublayers within a layer.<br />
<br />
* The <b>Add layer</b> dialog allows you to place the new layer above, below, or inside the current layer.<br />
<br />
* In Preferences (Selecting tab), options are added allowing the "Select All" command and Tab key selection to work either in the current layer only or in the current layer and its sublayers.<br />
<br />
= Extensions =<br />
<br />
* The <b>Effects menu is now always on</b>, it's no longer an "experimental feature". The preference setting to enable the menu has been removed.<br />
<br />
* Python extensions (which includes almost all currently available extensions) <b>work on Windows out of the box</b>, using a copy of Python shipping with Inkscape. The only minor inconvenience is that when an effect is launched, you get an empty console window that stays on while the effect is doing its work. (Don't close that window, it will disappear by itself when the effect is finished.)<br />
<br />
* A new Python effect, <b>Render > LaTeX formula</b>, allows you to type in any LaTeX formula and get a vector object with the TeX rendition of this formula inserted into your document. You need to have <b>latex</b>, <b>dvips</b>, and <b>pstoedit</b> installed and in PATH for this to work.<br />
<br />
* A new Python effect, <b>Flatten Path</b>, flattens paths in the current selection, approximating each path with a polyline whose segments meet the specified criteria for flatness.<br />
<br />
* A new Python effect, <b>Measure Path</b>, attaches a text label to each path in the selection giving the length of that path (in px units).<br />
<br />
* The <b>Radius Randomize</b> effect has a new parameter which enables <b>normal distribution</b> of random displacements instead of uniform as before, which gives a more natural feel to the randomized path.<br />
<br />
* The <b>Render > L-system</b> (formerly "Fractal (Lindenmayer)") effect is improved in this version. Now you can specify different angle values for turning left and right, which makes it possible to smoothly bend some L-systems sideways. Also, you can separately randomize the step length and the angles by a given percent for more natural look (this works especially well with plant-like branching shapes). This effect can be used to create Penrose tiling, Sierpinsky triangle, Dragon curve and other famous mathematical artefacts, as well as various meanders, friezes, patterns, and trees. Some examples can be seen on this [http://inkscape.org/screenshots/gallery/inkscape-0.44-lindenmayer.png screenshot] as well as in the new example file <code>share/examples/l-systems.svg</code>.<br />
<br />
* The <b>Interpolate Path</b>, <b>Random Tree</b>, and <b>L-system</b> effects are fixed to place their result on the current layer instead of document root and in the center of the (last-saved) document view instead of 0,0 as before.<br />
<br />
* INX files now have the ability to hold more information. This includes tooltips and descriptions of the extensions. These are all also translatable.<br />
<br />
* Thanks to keyboard configurability, it is now possible to assign keyboard shortcuts to those effects you use most often, so you can activate them without going into the menu.<br />
<br />
= Formats =<br />
<br />
* Inkscape's <b>PDF export</b> is now native (i.e. does not require any external applications) and <b>supports transparency</b>, including gradients with transparency. This replaced the old export extension that required Ghostscript and worked via Postscript, losing any transparency. The new PDF export is still immature; in particular it does not handle text, so you should check "Convert text to path" on the export options dialog. Other things not yet supported include: gradients on stroke; eccentric elliptic gradients; patterns, masks, and clipping paths; embedded images.<br />
<br />
* You can now <b>Save as Compressed Inkscape SVG with media</b>.This save option collects the svg file and all linked images into a zip archive for distribution. Although you cannot open the resulting archive directly with inkscape, the media is linked such that after unzipping you can open the SVG file immediately.<br />
<br />
* An output format for <b>desktop cutting plotters</b>, such as the Wishblade and Craftrobo, was added. This format is a very minimalist DXF file with appropriate scaling and translation applied. This output format should not be expected to operate as a generalized DXF output.<br />
<br />
* [xfig]<br />
<br />
* [odg - ishmal]<br />
<br />
* The new <b>XCF output extension</b> exports all top-level elements (i.e. layers and objects directly under root) as PNGs and assembles them into an XCF for procesing in the Gimp. Requires Python, PyXML and Gimp. Gimp 2.2.x or above must be in the path and be named <code>gimp</code>. A version of Inkscape 0.44 or above must be accessible from the path. Does not function in Windows.<br />
<br />
= Configurable keyboard =<br />
<br />
Inkscape's <b>keyboard shortcuts are now configurable!</b> <br />
<br />
At this time, not all Inkscape actions can have their shortcuts customized. However, the majority of actions, including everything you see in the menus, are already configurable, and we're working on making more actions configurable. <br />
<br />
On startup, Inkscape reads its keyboard shortcuts from <code>share/keys/default.xml</code>. That file is a copy of <code>inkscape.xml</code> in the same directory, which also contains keyboard emulation profiles for other vector editors:<br />
<br />
*<code>xara.xml</code>: Xara X/Xara Xtreme/Xara LX keys<br />
<br />
You can copy any of these over default.xml to use that profile. In all profiles, those keys which are not used by the corresponding program still have their Inkscape bindings. If you can contribute a profile for some vector editor that we don't yet have, we will appreciate that. The files have a simple XML-based format described in <code>inkscape.xml</code>.<br />
<br />
You can also <b>customize some of your keybindings</b> without overwriting the main <code>default.xml</code>. If your profile directory (<code>~/.inkscape</code> on Linux) contains a <code>keys</code> subdirectory with a <code>default.xml</code> file, the keybindings from that file will overlay (i.e. add to, and override in case of a conflict) the default bindings. The format of your own <code>default.xml</code> is the same as that of the main <code>default.xml</code>.<br />
<br />
= Miscellaneous shortcuts =<br />
<br />
* Now you can use <b>Shift+middle button drag</b>, in any tool, to zoom into an area. This works the same as simple drag in Zoom tool, but is faster because it does not require switching away from your current tool. Together with <b>middle button drag</b> (panning), <b>middle button click</b> (zoom in) and <b>Shift+middle button click</b> (zoom out), this completes the set of canvas navigation shortcuts available in any tool or context.<br />
<br />
* In Gradient tool, <b>Shift+R reverses the gradient definition</b> (i.e. mirrors the stop positions) without moving the gradient handles. For example, an elliptic gradient with blue center and red periphery becomes red in the center and blue in the periphery. This works on the gradient(s) of the currently selected gradient handle or, if no handle is selected, on all selected objects' gradients. (Compare with the Node tool where Shift+R reverses the direction of the selected path.) This is especially convenient for elliptic gradients which, unlike linear, you cannot simply rotate by 180 degrees for the same result.<br />
<br />
* In Selector, <b>Ctrl+Enter</b> enters the selected group (making it a temporary layer). <b>Ctrl+Backspace</b> leaves the current layer and goes one layer up in the hierarchy (but not to root).<br />
<br />
= Miscellaneous improvements =<br />
<br />
* <b>Document templates</b> (listed in <i>File &gt; New</i>) are now first searched in the <code>templates</code> subdirectory of the user's profile directory (on Linux it's <code>~/.inkscape/templates</code>), then in the system-wide Inkscape templates directory. This allows you to add your own templates on top of the list of standard templates, as well as override the default template with your own one (the <code>default.svg</code> in the profile directory has priority over the system-wide one).<br />
<br />
* <b>Converting stroke to path</b> now correctly processes dashed strokes. For paths with markers, this command now creates a group containing the stroke converted to path and all its markers as independent objects (i.e. they are not markers anymore, but instead you can easily transform them or paint them any color, as a workaround for the "markers don't take the color of the stroke" bug).<br />
<br />
* When toggling one of the "transform with object" buttons (for stroke width, rounded rectangle corners, gradients, or patterns), a <b>message</b> is displayed in the statusbar explaining what has changed in the program's behavior. Hopefully this will reduce the number of complaints from users who had accidentally toggled one of these and were surprised by the result.<br />
<br />
* Whole thousands above 2000 in the rulers are now displayed as <b>2k, 3k, 4k</b> etc.<br />
<br />
* In the Document Preferences dialog, the new object style for each tool is now shown as a <b>style swatch</b> (displaying fill/stroke colors and opacity, stroke width, and master opacity), similar in design to the selected style indicator in the statusbar.<br />
<br />
* In the Grid Arrange dialog, row/column spacing can now be negative. <br />
<br />
* The installation default is now to scale the <b>rounded rectangle corners</b> with the rectangles themselves (the previous default mode, still available as an option, was to keep rounding radii unchanged when scaling rectangles). <br />
<br />
* Added a new <code>--export-area-canvas</code> command line parameter that causes the exported PNG to contain the full canvas. This option as well as <code>--export-area-drawing</code> and <code>--export-area</code> can now be used along with <code>--export-id</code> and <code>--export-id-only</code> for greater flexibility.<br />
<br />
* The <code>--query-*</code> command line parameters now return the true SVG bounding box of the object instead of the Inkscape coordinate system bbox (with inverted Y axis). The new behavior makes more sense for scripting use of Inkscape.<br />
<br />
* The <b>dpi</b> value in the Export dialog has had its range extended; now possible values are from 0.01 to 100000. <br />
<br />
* Individual <b>&lt;tspan&gt;s</b> within text objects (including line tspans) can now be selected via the XML editor to view their bounding boxes (though per SVG, you cannot transform them). Also, you can use the <code>--query-*</code> command line parameters to find out the bounding boxes of tspans from a script. (Individual strings within or between tspans are still not selectable, and they cannot have an ID for querying anyway.)<br />
<br />
* The placeholder image which is shown when a bitmap file was no longer accessible reads now "<b>Linked image not found</b>" instead of the confusing "Broken image".<br />
<br />
* <b>Cloning multiple selected objects</b> now works as expected (i.e. each selected object is cloned separately, similar to the Duplicate command). Previously you could only clone a single selected object. <br />
<br />
* The separate "license" and "contributors" dialogs have been merged into tabs on the About dialog. The about dialog now correctly sizes itself to fit the size of the splash SVG (while remaining resizable), and the rendering area is now cropped to the correct aspect ratio when the dialog is resized. The dialog also now displays the build information in the upper right corner.<br />
<br />
* [new cursors - scislac]<br />
<br />
* In the Transform dialog / Rotate tab, the icon was flipped horizontally to be in line with the direction of positive rotation; the change was applied to the default (now crispy) and legacy icon sets.<br />
<br />
* The <b>scale ratio lock button</b> on the Selector controls bar shows a closed lock when pressed and open lock otherwise (same as the layer lock in the statusbar).<br />
<br />
* The <b>Browse</b> button on Export dialog now opens the new file chooser, same as those used by Open and Save.<br />
<br />
* A new <b>RazorWire</b> path marker was added. By applying it as a mid-marker you can get a good approximation of a razor wire.<br />
<br />
= Miscellaneous bugfixes =<br />
<br />
* Reading a document with an <b>incorrect namespace URI</b> not only did not cause Inkscape to complain, but could also "pollute" Inkscape's internal namespace table, resulting in an "infection" of subsequently saved documents by the incorrect namespace. This is now fixed, but as a result, documents with incorrect namespace URIs will no longer load. You will have to edit them in a text editor to fix the namespaces. <br />
<br />
* With newer versions of GTK, <b>dragging with graphics tablet pen</b> did not work in some tools and contexts (in particular, in Node and Rectangle tools). This is fixed.<br />
<br />
* <b>Scaling of objects with stroke</b> in Selector used to cause undesired shifts of the scaled object, as well as scaling it in the dimension which was intended to remain untouched (e.g. slight change in width when you scale only height). All these problems are now fixed, both for interactive scaling by mouse and for numeric scaling via the Controls bar, and for both values of the "Scale stroke with objects" option. Among other things, this means that stroked objects no longer lose snapping on scale, and that the "Default scale origin" option in the Selector tool preferences finally works as designed. Caveat: There may still be problems if you scale a selection that contains objects with different stroke widths.<br />
<br />
* Scaling of stroke now works for objects that didn't specify stroke-width; before, they always ended up with the default 1px stroke.<br />
<br />
* The bounding box for text and flowed text objects did not include stroke width. This has been fixed.<br />
<br />
* Stroke miterlimit on text objects was misinterpreted in absolute units instead of multiplies of stroke width (resulting in miter joins rendered as bevel). <br />
<br />
* The unfinished path in Pen tool is now cancelled, not finalized, when you switch away from the Pen tool. Apart from being more intuitively correct, this also fixes a crash when you quit Inkscape with the unfinished path in Pen tool.<br />
<br />
* Fonts on Win32 now use the native font mapper, meaning that Inkscape's font list is the same as other Windows programs, and the (potentially) very long delay experienced when using fonts for the first time in each session is gone.<br />
<br />
* Setting dash pattern was broken for transformed objects, and copy/paste of style with dash pattern did not apply correctly to objects with transforms.<br />
<br />
* An error caused a complete extra screen redraw after each zoom operation. That is, after you press "+" in a complex drawing, Inkscape redraws, but for some time after that it remains still unresponsive because it does that second redraw (invisibly for you, i.e. nothing changes on the screen). This is fixed.<br />
<br />
* Gradient rendering was off by one pixel, which often resulted in visibly wrong gradient rendering for small objects or in zoom-out. <br />
<br />
* The SVG path parser could not handle fractional numbers with the initial dot. <br />
<br />
* Several pattern rendering bugs are fixed, discovered by working with SVG files exported from Adobe Illustrator.<br />
<br />
* Inkscape on Mac OS X will now notice fonts in your ~/Library/Fonts directory, in addition to the other standard places.<br />
<br />
* Inkscape couldn't be compiled with libxml versions <= 2.6.9, and we now bumped the requirements from 2.6.0 up to <b>libxml >= 2.6.11</b>, which is the earliest you can get officially, anyway.<br />
<br />
* Inkscape no longer crashes when presented with a defective inx file for extensions.<br />
<br />
* More document memory is now freed when documents are closed.<br />
<br />
* EPS output now correctly includes an %%EOF footer.<br />
<br />
* There was a regression in 0.43 that caused several minor, though annoying bugs; knots and handles remained highlighted after the mouse was released, and the rubberband selection rectangle stayed visible if the selection was ended over a node while in the node tool. This regression has been fixed. <br />
<br />
* The connector routing code would previously sometimes confuse objects between multiple documents resulting in strange routing behaviour. This has been fixed.<br />
<br />
* There existed a bug in 0.43's Inkboard code that allowed a malicious outsider to very easily disrupt an Inkboard session. This has been fixed.<br />
<br />
* There existed a bug in 0.43's Inkboard code that would cause deadlocks in the case that two users attempted to invite each other at the same time (see bug #[https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1352522&group_id=93438 1352522] for further details). This should be fixed, although the fix has not been widely tested.<br />
<br />
* There existed a bug in 0.43's Inkboard code that would cause session invitations to not appear on the invitee's screen. This was the result of a mistake in handling GDK modifier flags, and has been fixed.<br />
<br />
= Translations =<br />
<br />
* INX files (containing the UI of the external effects) now allow the user visible strings to be translated. This means that effect dialogs, file type selections, and extension names can all be translated by translators.<br />
<br />
= Internal =<br />
<br />
* The Document Properties Dialog code was completely gtkmmified, which lead to dramatic reduction of code size due to usage of widget objects. The used widget objects should be reusable by other dialogs, too, and the code is much more readable.<br />
<br />
* Work on optimizing includes in all cpp files started, using the purgeincludes tool specifically written for that purpose, and ended with 40% of include lines removed!<br />
<br />
= Known problems =<br />
=== Problems with libgc-6.7 ===<br />
* Inkscape will hang or even crash when linked with this (newest) version of the Boehm garbage collection library. Make sure you use libgc-6.5 or 6.6 until this is sorted out.<br />
<br />
=== Namespaces may need fixing ===<br />
<br />
* Previous versions of inkscape sometimes silently saved documents with <b>wrong namespace URIs</b>. This has been fixed, but such corrupted documents will no longer load successfully. Such documents may require their namespace declarations to be fixed by hand.<br />
<br />
=== Beware of defective themes on Linux ===<br />
<br />
* Inkscape and other Gtk programs can crash on any Linux, when the <b>gtk2-engines-smooth / libsmooth</b> package is installed. We have filed a bug against libsmooth which is now in gtk-engine and part of gnome. Removing the package resolves the problem, however, but it would be nice if you as affected user would inform the gtk-engines maintainers of the problem. See especially http://bugzilla.gnome.org/show_bug.cgi?id=312115 (thanks to Thomas Wood)<br />
* A similar crash happens if the <b>KDE Baghira</b> theme or the package <b>gtk_qt_engine</b> are installed. If you experience Inkscape crashes on KDE, please try to install a different theme from Baghira, or uninstall the gtk_qt_engine package from your system. Both problems also affect older versions of Inkscape.<br />
<br />
=== Make sure to remove menus.xml if you have it ===<br />
<br />
* If you were using certain CVS/SVN builds from autumn of 2005, you may have the file <code>menus.xml</code> hanging around in your profile directory (e.g. <code>~/.inkscape</code> on Linux). In that case you will see many errors about verbs that cannot be found, and some commands in menus will be disabled. Make sure to delete <code>menus.xml</code> to fix this.<br />
<br />
= Previous releases =<br />
<br />
* ReleaseNotes043 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes043)<br />
* ReleaseNotes042 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes042)<br />
* ReleaseNotes041 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes041)<br />
* ReleaseNotes040 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes040)<br />
* ReleaseNotes039 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes039)<br />
* ReleaseNotes038 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes038)<br />
* ReleaseNotes037 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes037)<br />
* ReleaseNotes036 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes036)<br />
* ReleaseNotes035 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes035)</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=Notes_Alliberament&diff=6625Notes Alliberament2006-06-05T10:03:34Z<p>Xaviconde: /* Inkscape 0.44: overview */</p>
<hr />
<div>== Inkscape 0.44: resum ==<br />
<br />
L'Inkscape 0.44 és més gran i millor que mai! Alguns dels aspectes destacats són:<br />
<br />
* Diàleg de capes<br />
<br />
* Mode contorn, amb millores del rendiment<br />
<br />
* Exportació nadiva en PDF amb transparència<br />
<br />
* Clipping and masking support<br />
<br />
* Dreceres de teclat configurables, incloent emulació de Xara <br />
<br />
* Paleta de color adjuntada en la finestra d'edició de la paleta de colors<br />
<br />
* Indicador interactiu de l'estil de la selecció a la barra d'estat<br />
<br />
* Un innovador "esculptor de nodes" i altres millores a l'eina de nodes<br />
<br />
* Ara les extensions estan habilitades per defecte i funcionen tant a Linux com a Windows<br />
<br />
* Millor suport d'SVG: element <switch>, perfils de color ICC per a les imatges<br />
<br />
* Centres de rotació persistents, ordre per enganxar la mida<br />
<br />
* S'ha redissenyat el diàleg de preferències, noves icones, menús reordenats, moltes millores cosmètiques<br />
<br />
* Centenars de correccions d'errors i petites millores<br />
<br />
* Encara que no està relacionat directament amb l'Inkscape, val la pena notar que des de la darrera versió, ara [http://www.mozilla.com/firefox/ Firefox 1.5] suporta per defecte el format SVG. Això significa que podeu veure qualsevol document SVG en la vostra finestra del Firefox sense convertir entre formats o instal·lant connectors addicionals.<br />
<br />
= Performance =<br />
<br />
== Outline mode ==<br />
<br />
An Outline ("wireframe") display mode is implemented. Use the <i>View > Display Mode > Outline</i> to activate it. In this mode:<br />
<br />
* all paths and shapes are rendered as <b>inverse</b> (black on light background and vice versa) <b>outlines</b> of constant width (1 screen pixel regardless of zoom), without fill;<br />
<br />
* text is painted by inverse fill, without stroke; <br />
<br />
* bitmaps are shown as is;<br />
<br />
* any opacity and gradients are ignored.<br />
<br />
The outline mode is usually not drastically faster than regular mode (usually 10% to 50% faster), and in some special cases it may even be slower. However, the value of the outline mode is not only in its speed; it is a good way to get an idea of the structure and objects of your document, and it is convenient for precision node editing and for finding "stray objects". <br />
<br />
== Speed ==<br />
<br />
In addition to the Outline mode which makes it much easier to work with complex drawings, this version of Inkscape also provides significant speed improvements in many areas.<br />
<br />
* Thanks to <b>optimizations in the renderer</b>, Inkscape's screen redraw is <b>faster by at least 10%</b>, and in some cases (such as complex stroked/dashed paths at high zooms) <b>up to three times faster</b>. <br />
<br />
* <b>Optimizations in the Node tool</b> resulted in noticeable speed gains for node editing. Thus, switching to and from the Node tool (with a path selected), as well as selecting nodes in that tool, are now <b>at least ten times faster</b> than before. Other operations, including curve and node dragging and move/scale/rotate operations on multiple selected nodes, are much faster as well. This is especially important when working with complex paths; with these optimizations, paths containing several thousand nodes, though still slow, are much more usable.<br />
<br />
* An optimization in the attribute setting method made operations such as moving multiple objects with arrow keys at least <b>30% faster</b> compared to 0.43. This is especially noticeable when you are moving clones selected together with their original (e.g. a clone tiling), in which case Inkscape now works <b>three to four times faster</b>.<br />
<br />
* <b>Interface icons</b> are now rendered in the background (from SVG source in <code>share/icons/icons.svg</code>) when Inkscape is idle, rather than waiting for all the icons in a menu to render the first time you pull it up. This eliminates the annoying delay when opening menus for the first time.<br />
<br />
* Previously, zooming in to view a small portion of a path (especially big and complex path), there was a very noticeable slowdown and memory use increased dramatically. We optimized the renderer to <b>only process the visible part of a path</b>, and as a result the rendering speed is now almost the same at any zoom up to the maximum, providing up to 10-40 times speedup compared to the previous version (the closer is the zoom, the greater is the gain).<br />
<br />
* The <b>Path > Break Apart</b> command is now dozens of times (up to 100x) faster for complex paths with thousands of subpaths.<br />
<br />
= Interface =<br />
<br />
== Layers dialog ==<br />
<br />
* Ctrl+Shift+L [joncruz, mental]<br />
<br />
== Selected style indicator ==<br />
<br />
A new control in the left end of the statusbar lets you quickly view and change the <b>fill and stroke of the selected objects</b>. When you have a text selection in Text tool or a gradient handle selected in the Gradient tool, this indicator displays and changes the style of the text fragment or gradient stop, instead of the entire object (it's the same behavior as the Fill&amp;Stroke dialog.)<br />
<br />
* The two indicators, labelled <b>F:</b> (top) and <b>S:</b> (bottom), display fill and stroke of the selected object(s) correspondingly. (For gradient handles, they always display the same style.)<br />
<br />
* Each fill/stroke indicator can display either a <b>color+opacity swatch</b> (the opacity shown here is the fill opacity or stroke opacity, not the master opacity) or a text label specifying <b>N/A</b> (nothing selected), <b>None</b> (no fill/stroke), <b>Unset</b> (unset fill/stroke), <b>L Gradient</b>, <b>R Gradient</b>, <b>Pattern</b> (corresponding fill/stroke types), or <b>Different</b> (selected objects have different fill/stroke types).<br />
<br />
* Additionally, each indicator may be accompanied by one of two flags, <b>m</b> ("multiple", meaning there are two or more objects all with the same fill/stroke) or <b>a</b> ("averaged", meaning there are two or more objects with different flat colors in fill/stroke, and the indicator shows the average of these colors).<br />
<br />
* <b>Left-click</b> on an indicator opens or activates the Fill&Stroke dialog with the corresponding tab (Fill or Stroke) active.<br />
<br />
* <b>Right-click</b> on an indicator opens a popup menu with the following items:<br />
** <b>Edit fill/stroke...</b>: Opens or activates the Fill&Stroke dialog with the corresponding tab selected. (Same as left-click.)<br />
** <b>Last set color</b>: Applies to the selected objects the fill/stroke color that was last applied to anythig.<br />
** <b>Last selected color</b>: Applies to the selected objects the fill/stroke color that was last displayed in this indicator. (Allows you to easily copy fill/stroke color between objects: select source, select destination, apply "last selected color".)<br />
** <b>Invert</b>: Sets the fill or stroke to the inverse of the current color (does not affect opacity).<br />
** <b>White</b>, <b>Black</b>: Sets the fill or stroke to the corresponding color (fully opaque).<br />
** <b>Copy color</b>, <b>Paste color</b>: Copies or pastes the fill or stroke color (when it's color) to/from the system clipboard, as text in the <code>#rrggbb</code> hex format.<br />
** <b>Swap fill and stroke</b>: Exchanges fill and stroke (both their types and colors, if any). <br />
** <b>Make fill/stroke opaque</b>: Removes fill or stroke transparency (not master transparency!).<br />
** <b>Unset fill/stroke</b>: Unsets fill or stroke from selected objects.<br />
** <b>Remove fill/stroke</b>: Removes fill or stroke from the selected objects.<br />
<br />
* <b>Middle-click</b> on a fill/stroke indicator removes fill/stroke from selected objects; if it is already removed (i.e. if the indicator displays "None"), it does the same as the "Last set color" command from the popup menu.<br />
<br />
* <b>Drag and Drop</b> of colors onto a fil/stroke indicator sets the fill and stroke of the selected object(s) correspondingly.<br />
<br />
* The Stroke indicator also displays the <b>stroke width</b> of selection (averaged if there are multiple objects selected with different stroke widths), located to the right of the stroke color/transparency swatch. Left-clicking on it opens the Fill&Stroke dialog with the Stroke Style tab selected. Right-clicking on it opens a popup menu which allows you to choose the units for displaying the stroke width, as well as choose one of the presets to assign to selection.<br />
<br />
* To the right of the fill/stroke indicators, the <b>Opacity</b> numeric field (labelled "O:") shows and allows you to change the master opacity of the selected object (or the averaged opacity of several selected objects). <b>Right-clicking </b> the numeric field opens a popup menu with preset opacity levels. <b>Middle-clicking</b> on the "O:" label cycles the opacity through the values of 0 (transparent), 0.5, and 1 (opaque).<br />
<br />
The zoom field and the cursor coordinates indicator have been rearranged for compactness and moved to the right end of the statusbar. There's also a window resize handle added at the very end of the statusbar.<br />
<br />
== Eina d'indicador d'estil ==<br />
<br />
Per a cada eina per crear objectes (formes, Bolígraf/Llapis, Cal·ligràfic, Text), la barra de control (al damunt) inclou ara un <b>indicador d'estil</b> a la dreta. Aquest indicador mostra quin estil tindrà l'objecte nou. L'indicador mostra correctament qualsevol estil que l'eina pot utilitzar - el "darrer" estil o l'estil fix d'aquella eina. Per exemple, fent clic a un paleta (fins i tot sense seleccionar res) canvia el "darrer" color posat i, si està configurada per utilitzar l'últim conjunt de color, el seu indicador s'actualitza, donant-li una idea del seu "pinzell" abans que comenci a dibuixar.<br />
<br />
== Controls bar for the Text tool ==<br />
<br />
* This version adds the beginnings of a Controls Bar for the Text tool (previously empty). Now you can select the <b>font family</b>, <b>size</b>, apply <b>bold</b> and <i>italic</i> styles, change <b>alignment</b> and <b>text orientation</b> without opening the Text and Font dialog. <br />
<br />
* All controls are <b>instant-apply</b> and work on the entire text object (if nothing selected) or text selection. They can also apply to multiple text objects (though you would need to switch to Selector to select multiple text objects, then switch back to Text tool for its controls). <br />
<br />
* The font-family drop-down contains names and <b>previews</b> of all fonts; unlike other programs, we didn't apply each font to its name, but added a separate preview string displayed with gray color after each font's name. This design ensures readability of font family names and provides maximum useful information in a limited space.<br />
<br />
* We will be adding more controls (including spacing and kerning) to this bar for the next versions.<br />
<br />
== Docked color palette ==<br />
<br />
* Previously, color swatches could only be used from a floating palette (Ctrl+Shift+W). Now the color swatches palette is embedded in the main UI, at the bottom of the window between the canvas and the statusbar. It is enabled by default; use <i>View > Show/Hide > Palette</i> to enable or disable it. The docked palette has the same functionality as the floating one; use a button in the top right corner to access the swatches menu.<br />
<br />
* The <b>Wrap</b> option (off by default) in the swatches menu converts the palette from a single row into a frame 2 or 3 rows high, for better access to colors in large palettes.<br />
<br />
* <b>Drag and Drop</b> of <b>colors</b> has been enabled.<br />
** Dragging colors from a palette shows a live swatch of the color being dragged under cursor.<br />
** Drag and Drop of colors onto the selected style indicator in the statusbar sets the fill or stroke of the selected object(s).<br />
** Colors can be <b>dropped</b> directly on to objects on canvas to set their <b>fill</b>, or <b>shift+dropped</b> to set their <b>stroke</b>. This affects only the object you drop the color on, regardless of whether that object is selected or not.<br />
** Colors can be dragged to and from other applications.<br />
<br />
* The new <b>Inkscape default</b> color palette was added. It contains a range of grays, standard HTML named colors, and a full range of colors sorted by their HSL values (475 colors overall). It is generated by a Python script which is available from Inkscape SVN in share/palettes.<br />
<br />
* Several <b>specialized color palettes</b>, useful in color-coordinated projects, were created or borrowed from GIMP: Grays, Reds, Greens, Blues, Gold, Royal, Khaki, Hilite, and Topographic.<br />
<br />
* All standard sizes of the swatches (Tiny, Small, Medium, Large, Huge) are made <b>smaller</b> overall.<br />
<br />
== Inkscape Preferences dialog ==<br />
<br />
Not only was the Inkscape Preferences dialog completely rewritten and redesigned, it is now also <b>fully GNOME-HIG compliant</b>. Numerous <b>bugs</b> were taken care of with the rewrite. As a new feature, the <b>Simplify threshold</b> can now be set with more precision.<br />
<br />
== Document Properties / Metadata dialogs ==<br />
<br />
* The Document Preferences dialog is now named <b>Document Properties</b>, and it was split in two: metadata were extracted into the <b>Document Metadata</b> dialog; metadata widgets are now also spread over two pages.<br />
<br />
* A button was added to <b>fit the canvas to the current selection</b> or, if there's no selection, to the entire drawing. The button resizes the canvas and, if necessary, moves the drawing into place. It is now very easy to size the canvas to an illustration after it is ready.<br />
<br />
* <b>New controls</b>: the new object snapping features required their own property widgets, and you can set the snapping sensitivity with a slider, or let it snap regardless of distance (grid only).<br />
<br />
* Rearrangements within <b>Document Properties</b>: everything snapping-related was collected on one page; Grid and Guide widgets are on their own, the same page. For better HIG compliance, all widgets were categorized; especially the widgets on the Page page were completely rearranged in the General/Format/Border categories.<br />
<br />
* <b>Bug fixes</b>: grayed out license URI had too low contrast, so it's no longer grayed out; the proprietary license didn't clean the license URI; spinbuttons had no tooltips, and minor grid quirks were removed; data was not updated when a new file replaced another in the same window.<br />
<br />
* <b>HIG compliance</b>: much work went into that, and now only a few details are missing from full Gnome-HIG compliance.<br />
<br />
* <b>Updated Creative Commons Licenses</b>: Updated CC licenses to the latest 2.5 versions by default in the license tab of the metadata dialog.<br />
<br />
== Menus ==<br />
<br />
* <b>Zoom</b> commands in the View menu are moved to a submenu; the <i>Zoom In</i> and <i>Zoom Out</i> commands are added to that submenu.<br />
<br />
* <b>Clone</b> commands are moved into a submenu in Edit menu and given more descriptive names and tips.<br />
<br />
* <b>Pattern</b> commands (<i>Objects to Pattern</i> and <i>Pattern to Objects</i>) are moved into a submenu in Object menu, under the new Clip and Mask submenus.<br />
<br />
* The contents of the <b>Effects menu</b> are categorized into submenus, and several effects are renamed to use more intuitive names. <br />
<br />
== Statusbar ==<br />
<br />
* In Selector, for multiple selected objects, the statusbar now reports their types. For example, if 5 groups are selected, it displays<br />
<br />
::<b>5</b> objects of type <b>Group</b> in layer <b>LayerName</b>.<br />
<br />
:instead of just "5 objects selected" as before. If there are up to 3 types in the selection, they will be listed, for example:<br />
<br />
::<b>5</b> objects of types <b>Group</b>, <b>Path</b>, <b>Rectangle</b> in layer <b>LayerName</b>.<br />
<br />
:The order of the list will correspond to the order in which the objects were added to selection. If there are 4 or more types in selection, only the number of types is reported, for example:<br />
<br />
::<b>5</b> objects of <b>4</b> types in layer <b>LayerName</b>.<br />
<br />
* In Selector, objects selected in groups are now identified as such, and the group ID is given, for example:<br />
<br />
::<b>Rectangle</b> in group <i>g212</i> (layer <b>content</b>)<br />
<br />
:If selected objects have different parents within one layer (for example, if one is selected in a group and another outside it), the number of parents is reported:<br />
<br />
::<b>2</b> objects of types <b>Rectangle</b>, <b>Path</b> in <b>2</b> parents (layer <b>content</b>)<br />
<br />
:If objects are in different layers, only the number of layers is reported since this also implies different parents:<br />
<br />
::<b>2</b> objects of types <b>Rectangle</b>, <b>Path</b> in <b>2</b> layers<br />
<br />
* In Node tool, if your node selection includes nodes from different subpaths, statusbar reports the number of subpaths with selection and the total number of subpaths, for example:<br />
<br />
::<b>2</b> of <b>195</b> nodes selected in <b>2</b> of <b>36</b> subpaths.<br />
<br />
* The contents of the statusbar message are now duplicated as a <b>tooltip</b> that is shown when you hover the mouse over the statusbar. [TODO: need to strip markup from the tooltips.] <br />
<br />
* The statusbar text is now no longer just cut off if there is insufficient room, but an ellipsis (...) is inserted at the end to show there's more (only with Gtk 2.6 and newer).<br />
<br />
== Theme ==<br />
<br />
* Inkscape has a <b>new default icon set</b> titled "Crispy" provided by Andre Sousa. The new icons are intended to add a more professional and cohesive look to our application, as well as to make the functions the icons represent more self-evident.<br />
<br />
= Clipping and masking =<br />
<br />
Inkscape now provides some UI for using <b>clipping paths and masks</b>. <br />
<br />
* Any object can be non-destructively intersected with a path (called a <i>clipping path</i>) so that only the intersected portion of the object is visible. <br />
** <b>To apply clipping</b>, select the objects to be clipped and the clipping path object, make sure the clipping path is above the other objects in z-order, and do <i>Object > Clip > Set</i>.<br />
** You can <b>transform, edit, or style</b> the clipped objects as usual. The clipping remains applied and transforms together with each clipped object.<br />
** To <b>remove the clipping</b>, do <i>Object > Clip > Release</i>. The clipping path is returned to the drawing as a regular object; it is inserted on top of the unclipped object in z-order. <br />
<br />
* Any object can be non-destructively masked by another object (called <i>mask</i>) so that: the mask's black or transparent areas become fully transparent in the masked object; mask's opaque white areas become fully opaque; and all intermediate colors translate into intermediate levels of opacity in the masked object. This allows you to apply, for example, arbitrary transparency gradients to objects.<br />
** To <b>apply a mask</b>, select the objects to be masked and the mask object, make sure the mask is above the other objects in z-order, and do <i>Object > Mask > Set</i>.<br />
** You can <b>transform, edit, or style</b> the masked objects as usual. The mask remains applied and transforms together with each masked object.<br />
** To <b>remove the masking</b>, do <i>Object > Mask > Release</i>. The mask is returned to the drawing as a regular object; it is inserted on top of the unmasked object in z-order. <br />
<br />
* Objects with clippath show their bounding box intersected with the bounding box of the clippath, instead of the original unclipped bbox as before. (However, this does not apply to objects without clippath of their own which are clipped by being inside a clipped group.)<br />
<br />
* Clipped or masked objects display "<i>clipped</i>" or "<i>masked</i>", correspondingly, in their statusbar descriptions.<br />
<br />
* Although Inkscape had render-only support for clipping paths and masks for quite some time, in this release we fixed a number of bugs which may affect the display of your documents using clippaths or masks.<br />
** Clippaths and masks with objectBoundingBox units are now shown correctly upon loading of the document.<br />
** Clippaths without fill didn't work, this is now fixed.<br />
** Objects with clippaths or masks are correctly copied/pasted between documents.<br />
<br />
= SVG conformance =<br />
<br />
== Color profile support ==<br />
<br />
Inkscape now includes base ICC profile functionality. If compiled with LittleCMS support (if you run <code>configure</code> with <code>--enable-lcms</code> switch), Inkscape passes the [http://www.w3.org/Graphics/SVG/Test/20030813/htmlframe/full-color-prof-01-f.html ICC color profile test] by W3C. The &lt;color-profile&gt; element has been implemented along with the "color-profile" attribute for &lt;image&gt; elements.<br />
<br />
== &lt;switch&gt; support ==<br />
<br />
Rendering support for SVG 1.1's '''Conditional Processing Module''' has been implemented, including ''switch'' element, ''requiredFeatures'', ''requiredExtensions'', ''systemLanguage'' attributes. Inkscape passes the Conditional processing tests ([http://www.w3.org/Graphics/SVG/Test/20030813/htmlframe/full-struct-cond-01-t.html] and [http://www.w3.org/Graphics/SVG/Test/20030813/htmlframe/full-struct-cond-02-t.html]) by W3C.<br />
<br />
== SVG output ==<br />
<br />
* In Inkscape's SVG documents, <b>colors</b> are now expressed by name (‘white’) or three-digit form (‘<tt>#f3c</tt>’) when possible.<br />
<br />
* The numeric values in <code>transform</code> attributes are written without insignificant trailing zeros, and anything less than that 1e-8 by absolute value (usually caused by rounding errors) is written as 0 to reduce clutter.<br />
<br />
= Transformations =<br />
<br />
== Transform dialog ==<br />
<br />
Fixes and improvements in the Transform dialog (Ctrl+Shift+M):<br />
<br />
* The <b>Apply to each object separately</b> checkbox is added, allowing you to scale/rotate/skew each selected object by the same amount, around that object's center. When off (by default), the selection is transformed as a whole. The status of this checkbox is remembered across sessions. (It has no effect on Move and Matrix tabs).<br />
<br />
* The <b>Clear</b> button resets the values on the current tab to defaults.<br />
<br />
* The <b>Scale</b> tab now allows you to specify horizontal or vertical size increments in percentage or absolute units. Also, there's a <b>Scale proportionally</b> checkbox which ensures that scaling preserves the width/height ratio. (If you are scaling several objects proportionally with "Apply to each object separately", you can only use the % unit to specify the scaling; otherwise each object's scale increments will have the width/height ratio of the entire selection, not of that specific object.)<br />
<br />
* The <b>Skew</b> tab can now specify the skew as an <b>absolute displacement</b> (e.g. for horizontal skewing of a rectangle, that means the shift of the top rectangle side relative to the bottom), as <b>percentage displacement</b> (e.g. a 1% horizontal skew of a rectangle means shifting the top side by 1% of the rectangle height), or as an <b>angle</b> (e.g. horizontal skew by 15 degrees results in the sides of a rectangle being rotated to that angle, while the top and bottom remain horizontal).<br />
<br />
* The <b>Matrix</b> tab (previously called "Transform") can either edit the current <code>transform=</code> matrix of an object, or post-multiply the <code>transform=</code> with the matrix you specify, depending on the <b>Edit current matrix</b> checkbox. (As it is now redundant, the transformation matrix in the Object Properties dialog is removed.)<br />
<br />
* The dialog now correctly <b>watches selection changes</b> in the active document window and updates its values accordingly.<br />
<br />
* The layout of the dialog is simplified, tooltips and mnemonics added for better usability.<br />
<br />
* Many bugs are fixed, especially in value conversions between units.<br />
<br />
== Persistent rotation centers ==<br />
<br />
* The position of the center (axis) of rotation and skewing used by Selector is now <b>remembered</b> for all objects and restored when you select those objects again (even after saving and reopening the document). When you move or scale an object, its rotation center is moved or scaled too, so its position relative to the object always remains the same unless you move it explicitly.<br />
<br />
* When you have several objects selected, they use the rotation center of the <b>first selected object</b>. If the first object does not have center set (i.e. if it's in a default central position), then several objects will rotate around the geometric center of their common bounding box (as before).<br />
<br />
* <b>Shift+click</b> on the rotation center resets it back to the center of the object's box.<br />
<br />
* Consequently, dragging the rotation center is now <b>an undoable action</b>; you can press Ctrl+Z to undo the drag.<br />
<br />
* <b>Keyboard rotation</b> by [, ] keys with various modifiers, as well as the Rotate tab in the <b>Transform dialog</b>, work around the selected object's rotation center (for multi-object selection, the rotation center of the first selected object).<br />
<br />
* Rotation centers are <b>preserved</b> when duplicating, cloning (including clone tiler), grouping/ungrouping, and converting to path.<br />
<br />
[TODO: <br />
- make it work smartly for groups: if a group has center not set, return the center of the first object inside group with the center set<br />
<br />
- a separate tab in the Transform dialog, with 9 buttons in the square grid (for setting it to object's corners, sides, and center) as well as x/y fields for setting center to any position<br />
<br />
- make center snap to grid/guides/objects and to other centers<br />
<br />
- make objects snap with their center to grid/guides/objects]<br />
<br />
== Pasting size ==<br />
<br />
A number of commands are added to easily scale selected objects to match the size of the object(s) previously copied to the clipboard. They are all in the Paste Size submenu in Edit menu:<br />
<br />
* <b>Paste Size</b> scales the whole selection to match the overall size of the clipboard object(s).<br />
<br />
* <b>Paste Width</b>/<b>Paste Height</b> scale the whole selection horizontally/vertically so that it matches the width/height of the clipboard object(s). These commands honor the scale ratio lock on the Selector controls bar (between W and H fields), so that when that lock is pressed, the other dimension of the selected object is scaled in the same proportion; otherwise the other dimension is unchanged.<br />
<br />
* <b>Paste Size Separately</b>, <b>Paste Width Separately</b> and <b>Paste Height Separately</b> work similarly to the above described commands, except that they scale <i>each selected object</i> separately to make it match the size/width/height of the clipboard object(s).<br />
<br />
= Tools =<br />
<br />
== Node tool ==<br />
<br />
=== Node sculpting ===<br />
<br />
An entirely new way of manipulating paths in Node tool is added in this version: Node sculpting. Normally, when you have several nodes selected and you drag one of them, all selected nodes move by the same amount. Now, if you <b>Alt-drag</b> one of the selected nodes, only that node is fully displaced; other selected nodes are moved less than the full amount, so that those farthest from the drag point remain stationary. This is similar to "proportional editing" or "soft selection" in 3D editors such as Blender.<br />
<br />
So, for example, if you select several nodes on a straight line and Alt+drag the middle selected node, the path will bend into a <b>smooth bell-like curve</b>. Nodes' handles are also adjusted correspondingly to keep the overall shape smooth and natural. (If you don't have enough nodes on a path fragment that you want to reshape in this way, just select the end nodes of that fragment and press <b>Ins</b> a few times to populate it with nodes.)<br />
<br />
Moreover, node sculpting is <b>sensitive to pressure</b> of your tablet pen. If you press slightly, your curve will have a narrow sharp tip (i.e. the nearest neighbors of your dragged node will move only a bit); if you press hard, the curve's tip will be wide and blunt (i.e. the nearest neighbors will move almost as much as the dragged node). (Hint: to stop dragging without losing your shape, first release Alt and then lift the tip of the pen.)<br />
<br />
There are many possible applications of the sculpting technique. To take a simple example, selecting all nodes of an ellipse-like shape and Alt+dragging one of them will smoothly and naturally stretch and skew the entire shape in any direction. Doing the same to a complex path, such as star or spiral, will twist and punch it without destroying its intricate structure - this is the way to get squashed or self-intersecting stars, eccentric spirals and other shapes not easily doable before. Selecting only part of all nodes allows you to smoothly reshape parts of the figure without disturbing the rest.<br />
<br />
When applied to text converted to path, node sculpting is a fun and easy way to twist, bend and distort it, achieving effects similar to "perspective envelope" or "curvilinear envelope" in other programs - but in a more powerful and flexible way. For example, by selecting all or part of the text's nodes and Alt-dragging, you can not only make a wavy banner out of a paragraph of text, but also apply a "magnifying lens"-like effect to any word in the middle. <br />
<br />
Especially useful node sculpting is for complex natural paths, such as calligraphic strokes or bitmap traces, where you often want to do large-scale pushes and bends without destroying the small-scale features. Things like making a calligraphic stroke narrower in one place and wider in another, or changing the proportions, extending the ear or flattening the nose of a head - all this is now much faster and more natural to do using sculpting. It is also a new way to <i>create</i> new paths, too - starting from en ellipse with added nodes, it takes just a few Alt+drags to tweak it into a silhouette of a head, or a map of Australia, or an Inkscape logo!<br />
<br />
Some examples are shown on the screenshot: [[http://www.inkscape.org/screenshots/gallery/inkscape-0.44-nodesculpting.png]].<br />
<br />
=== "Show handles" toggle ===<br />
<br />
The Controls bar for the Nodes tool now includes a toggle button which controls whether Bezier handles are shown on selected nodes (on by default). Selecting and dragging nodes on node-dense paths in zoom-out (e.g. for node sculpting) may be extremely difficult without hiding the handles, as it's hard to pick a node and not a handle when handles are shown.<br />
<br />
=== New deletion behavior ===<br />
<br />
* In Node tool, <b>deleting node(s)</b> by Del/Backspace keys or by Ctrl+Alt+clicking a node now <b>tries to preserve, as much as possible, the current shape of the path</b>. This means that the nodes adjacent to those being deleted have their handles adjusted to approximate the form that the path had before deletion. For example, if you Ctrl+Alt+click a path twice, once to add a new node and then to delete it, the path will not change at all (or change very slightly). The old deletion behavior without adjusting handles is still available via <b>Ctrl+Del</b> or <b>Ctrl+Backspace</b>.<br />
<br />
=== Preserving positions of nodes and handles ===<br />
<br />
* When you <b>switch the type</b> of the selected node to Smooth or Symmetric by pressing Shift+S/Shift+Y, you can now <b>preserve the position</b> of one of the two handles by hovering your mouse over it, so that only the other handle is rotated/scaled to match.<br />
<br />
* Similarly, when you <b>join endnodes</b> by pressing Shift+J, you can <b>preserve the position</b> of one of the two nodes by hovering your mouse over it, so that only the other node is moved. <br />
<br />
=== Miscellaneous ===<br />
<br />
* The <b>!</b> key <b>inverts node selection</b> in the current subpath(s) (i.e. subpaths with at least one selected node); <b>Alt+!</b> inverts in the entire path. (This is similar to how these keys work in Selector, with current subpath(s) instead of the current layer.)<br />
<br />
* The keyboard shortcut for "Make selected segments curves" in Node tool is changed from Shift+K to <b>Shift+U</b> for better mnemonics.<br />
<br />
== Calligraphic pen ==<br />
<br />
* Even when using a graphics tablet with pressure sensitivity, the Calligraphy pen's strokes often look too smooth and artificial. To enable a more natural look, the new <b>Tremor</b> parameter is added to the Calligraphy tool in this version. Adjustable in the Controls bar from 0.0 to 1.0, it will affect your strokes producing anything from slight unevenness to wild blotches and splotches. This significantly expands the creative range of the tool.<br />
<br />
* In all previous versions, pen width depended on zoom in such a way that the strokes <i>appeared</i> the same visible width at any zoom, but were in fact narrower at zoom-in and wider at zoom-out. This behavior makes sense if you want to keep the same "feel" of the pen regardless of zoom; for example, if you zoomed in to make a small fix to your drawing, it's natural that your pen becomes physically smaller but feels the same to you. So, this behavior is kept as the default, but now we also added an alternative mode where your <b>pen width is constant in absolute units</b> regardless of zoom. To switch to this mode, use the checkbox on the tool's Preferences page (you can open it by double-clicking the tool button).<br />
<br />
* The <b>Width</b> field in the tool's controls bar now changes <b>from 1 to 100</b>, which corresponds to the range from 0.01 to 1.0 in the previous version. If the "width in absolute units" mode is turned on, the value in this fields gives the width of the stroke in px units. In the default mode, the value of 100 gives 100px wide strokes only at 100% zoom, and strokes are correspondingly narrower or wider at other zoom levels.<br />
<br />
* A new preferences option for the Calligraphic tool, <b>Keep selected</b>, controls whether the newly created object remains selected after you finish drawing it. If you turn it off (by default it's on) and set the tool to using Last Set color, you can easily choose a new color by clicking on the palette without having to worry if this will change the color of the stroke you just created. (Watch the tool style indicator at the right end of the Controls bar for the style of the next stroke you will draw.)<br />
<br />
* <b>Esc</b> deselects selected objects in Calligraphic, as in most other tools.<br />
<br />
* The stroke you're drawing is now shown, while you're drawing it, with the correct color and opacity that it will eventually have, instead of always black as before.<br />
<br />
* On a new Inkscape installation, this tool now uses the last set style by default instead of the fixed black as before (this is changeable in the Inkscape Preferences for the tool).<br />
<br />
== Pen tool ==<br />
<br />
* While drawing a path, you can now <b>move the last node you created</b> by the same keys as in Node tool - that is, arrows, with Shift (for 10x displacement) or Alt (screen pixel displacement) modifiers. <br />
<br />
* Also, you can switch the not-yet-finalized (red) segment of the path being drawn from curve to line (<b>Shift+L</b>) or back to curve (<b>Shift+U</b>), again the same shortcuts as in the Node tool.<br />
<br />
* By popular demand, if a new path is being drawn but not yet finished, <b>Ctrl+Z cancels</b> that unfinished path (i.e. does the same as Esc), instead of undoing the previous action.<br />
<br />
* In Pen tool, <b>Del</b> works the same as Backspace to delete the last created point on the unfinished path.<br />
<br />
= Connectors and automatic layout =<br />
<br />
* There have been numerous bugfixes and several improvements to the behaviour of <b>connectors</b> and the <b>connector tool</b>:<br />
** Connectors moved as part of a selection will now stay attached to other objects in the selection, rather than becoming detached from them.<br />
** By default, the Connector tool will not attach connectors to text objects. There is a new checkbox in the connector preferences to control this setting.<br />
** The <b>margins around avoided shapes</b> (used for autorouting connectors) can now be adjusted via the "Spacing" control on the controls bar.<br />
<br />
* Automatic Diagram Layout - A new button is available in the alignment and distribution dialogue that performs automatic layout of diagrams involving a network of shapes and connectors. Layout is accomplished using force-directed graph layout based on the Kamada-Kawai algorithm. This algorithm treats edges as if they are springs such that the distance between nodes will be proportional to the path length---number of connectors---between them. Disconnected components (where not every shape is connected) will be arranged around the circumference of a circle.<br />
<br />
* There is a new <b>Remove Overlaps</b> button to move the selected objects enough that they don't overlap each other. A minimum spacing between the boundaries of objects can be specifiedTogether with the automatic layout tool, described above, this should be a significant addition to Inkscape's usability for diagramming. [Consider expanding this, comparing with existing Unclump and Distribute edge-to-edge buttons. - pjrm]<br />
<br />
= Selective tracing with SIOX =<br />
<br />
[ishmal]<br />
<br />
<br />
= Snapping =<br />
<br />
* [object snap - carl]<br />
<br />
* [highlight - mtou]<br />
<br />
* [only to visible gridlines - mtou]<br />
<br />
* <b>Guidelines</b> are made easier to pick: now you don't need to position mouse <i>exactly</i> over a guideline to activate it, instead there's a small position tolerance (1 screen pixel on each side of the guideline).<br />
<br />
= Sublayers =<br />
<br />
Previously, it was only possible to make a group a temporary sublayer by entering that group. Now Inkscape supports creating and using true persistent sublayers within a layer.<br />
<br />
* The <b>Add layer</b> dialog allows you to place the new layer above, below, or inside the current layer.<br />
<br />
* In Preferences (Selecting tab), options are added allowing the "Select All" command and Tab key selection to work either in the current layer only or in the current layer and its sublayers.<br />
<br />
= Extensions =<br />
<br />
* The <b>Effects menu is now always on</b>, it's no longer an "experimental feature". The preference setting to enable the menu has been removed.<br />
<br />
* Python extensions (which includes almost all currently available extensions) <b>work on Windows out of the box</b>, using a copy of Python shipping with Inkscape. The only minor inconvenience is that when an effect is launched, you get an empty console window that stays on while the effect is doing its work. (Don't close that window, it will disappear by itself when the effect is finished.)<br />
<br />
* A new Python effect, <b>Render > LaTeX formula</b>, allows you to type in any LaTeX formula and get a vector object with the TeX rendition of this formula inserted into your document. You need to have <b>latex</b>, <b>dvips</b>, and <b>pstoedit</b> installed and in PATH for this to work.<br />
<br />
* A new Python effect, <b>Flatten Path</b>, flattens paths in the current selection, approximating each path with a polyline whose segments meet the specified criteria for flatness.<br />
<br />
* A new Python effect, <b>Measure Path</b>, attaches a text label to each path in the selection giving the length of that path (in px units).<br />
<br />
* The <b>Radius Randomize</b> effect has a new parameter which enables <b>normal distribution</b> of random displacements instead of uniform as before, which gives a more natural feel to the randomized path.<br />
<br />
* The <b>Render > L-system</b> (formerly "Fractal (Lindenmayer)") effect is improved in this version. Now you can specify different angle values for turning left and right, which makes it possible to smoothly bend some L-systems sideways. Also, you can separately randomize the step length and the angles by a given percent for more natural look (this works especially well with plant-like branching shapes). This effect can be used to create Penrose tiling, Sierpinsky triangle, Dragon curve and other famous mathematical artefacts, as well as various meanders, friezes, patterns, and trees. Some examples can be seen on this [http://inkscape.org/screenshots/gallery/inkscape-0.44-lindenmayer.png screenshot] as well as in the new example file <code>share/examples/l-systems.svg</code>.<br />
<br />
* The <b>Interpolate Path</b>, <b>Random Tree</b>, and <b>L-system</b> effects are fixed to place their result on the current layer instead of document root and in the center of the (last-saved) document view instead of 0,0 as before.<br />
<br />
* INX files now have the ability to hold more information. This includes tooltips and descriptions of the extensions. These are all also translatable.<br />
<br />
* Thanks to keyboard configurability, it is now possible to assign keyboard shortcuts to those effects you use most often, so you can activate them without going into the menu.<br />
<br />
= Formats =<br />
<br />
* Inkscape's <b>PDF export</b> is now native (i.e. does not require any external applications) and <b>supports transparency</b>, including gradients with transparency. This replaced the old export extension that required Ghostscript and worked via Postscript, losing any transparency. The new PDF export is still immature; in particular it does not handle text, so you should check "Convert text to path" on the export options dialog. Other things not yet supported include: gradients on stroke; eccentric elliptic gradients; patterns, masks, and clipping paths; embedded images.<br />
<br />
* You can now <b>Save as Compressed Inkscape SVG with media</b>.This save option collects the svg file and all linked images into a zip archive for distribution. Although you cannot open the resulting archive directly with inkscape, the media is linked such that after unzipping you can open the SVG file immediately.<br />
<br />
* An output format for <b>desktop cutting plotters</b>, such as the Wishblade and Craftrobo, was added. This format is a very minimalist DXF file with appropriate scaling and translation applied. This output format should not be expected to operate as a generalized DXF output.<br />
<br />
* [xfig]<br />
<br />
* [odg - ishmal]<br />
<br />
* The new <b>XCF output extension</b> exports all top-level elements (i.e. layers and objects directly under root) as PNGs and assembles them into an XCF for procesing in the Gimp. Requires Python, PyXML and Gimp. Gimp 2.2.x or above must be in the path and be named <code>gimp</code>. A version of Inkscape 0.44 or above must be accessible from the path. Does not function in Windows.<br />
<br />
= Configurable keyboard =<br />
<br />
Inkscape's <b>keyboard shortcuts are now configurable!</b> <br />
<br />
At this time, not all Inkscape actions can have their shortcuts customized. However, the majority of actions, including everything you see in the menus, are already configurable, and we're working on making more actions configurable. <br />
<br />
On startup, Inkscape reads its keyboard shortcuts from <code>share/keys/default.xml</code>. That file is a copy of <code>inkscape.xml</code> in the same directory, which also contains keyboard emulation profiles for other vector editors:<br />
<br />
*<code>xara.xml</code>: Xara X/Xara Xtreme/Xara LX keys<br />
<br />
You can copy any of these over default.xml to use that profile. In all profiles, those keys which are not used by the corresponding program still have their Inkscape bindings. If you can contribute a profile for some vector editor that we don't yet have, we will appreciate that. The files have a simple XML-based format described in <code>inkscape.xml</code>.<br />
<br />
You can also <b>customize some of your keybindings</b> without overwriting the main <code>default.xml</code>. If your profile directory (<code>~/.inkscape</code> on Linux) contains a <code>keys</code> subdirectory with a <code>default.xml</code> file, the keybindings from that file will overlay (i.e. add to, and override in case of a conflict) the default bindings. The format of your own <code>default.xml</code> is the same as that of the main <code>default.xml</code>.<br />
<br />
= Miscellaneous shortcuts =<br />
<br />
* Now you can use <b>Shift+middle button drag</b>, in any tool, to zoom into an area. This works the same as simple drag in Zoom tool, but is faster because it does not require switching away from your current tool. Together with <b>middle button drag</b> (panning), <b>middle button click</b> (zoom in) and <b>Shift+middle button click</b> (zoom out), this completes the set of canvas navigation shortcuts available in any tool or context.<br />
<br />
* In Gradient tool, <b>Shift+R reverses the gradient definition</b> (i.e. mirrors the stop positions) without moving the gradient handles. For example, an elliptic gradient with blue center and red periphery becomes red in the center and blue in the periphery. This works on the gradient(s) of the currently selected gradient handle or, if no handle is selected, on all selected objects' gradients. (Compare with the Node tool where Shift+R reverses the direction of the selected path.) This is especially convenient for elliptic gradients which, unlike linear, you cannot simply rotate by 180 degrees for the same result.<br />
<br />
* In Selector, <b>Ctrl+Enter</b> enters the selected group (making it a temporary layer). <b>Ctrl+Backspace</b> leaves the current layer and goes one layer up in the hierarchy (but not to root).<br />
<br />
= Miscellaneous improvements =<br />
<br />
* <b>Document templates</b> (listed in <i>File &gt; New</i>) are now first searched in the <code>templates</code> subdirectory of the user's profile directory (on Linux it's <code>~/.inkscape/templates</code>), then in the system-wide Inkscape templates directory. This allows you to add your own templates on top of the list of standard templates, as well as override the default template with your own one (the <code>default.svg</code> in the profile directory has priority over the system-wide one).<br />
<br />
* <b>Converting stroke to path</b> now correctly processes dashed strokes. For paths with markers, this command now creates a group containing the stroke converted to path and all its markers as independent objects (i.e. they are not markers anymore, but instead you can easily transform them or paint them any color, as a workaround for the "markers don't take the color of the stroke" bug).<br />
<br />
* When toggling one of the "transform with object" buttons (for stroke width, rounded rectangle corners, gradients, or patterns), a <b>message</b> is displayed in the statusbar explaining what has changed in the program's behavior. Hopefully this will reduce the number of complaints from users who had accidentally toggled one of these and were surprised by the result.<br />
<br />
* Whole thousands above 2000 in the rulers are now displayed as <b>2k, 3k, 4k</b> etc.<br />
<br />
* In the Document Preferences dialog, the new object style for each tool is now shown as a <b>style swatch</b> (displaying fill/stroke colors and opacity, stroke width, and master opacity), similar in design to the selected style indicator in the statusbar.<br />
<br />
* In the Grid Arrange dialog, row/column spacing can now be negative. <br />
<br />
* The installation default is now to scale the <b>rounded rectangle corners</b> with the rectangles themselves (the previous default mode, still available as an option, was to keep rounding radii unchanged when scaling rectangles). <br />
<br />
* Added a new <code>--export-area-canvas</code> command line parameter that causes the exported PNG to contain the full canvas. This option as well as <code>--export-area-drawing</code> and <code>--export-area</code> can now be used along with <code>--export-id</code> and <code>--export-id-only</code> for greater flexibility.<br />
<br />
* The <code>--query-*</code> command line parameters now return the true SVG bounding box of the object instead of the Inkscape coordinate system bbox (with inverted Y axis). The new behavior makes more sense for scripting use of Inkscape.<br />
<br />
* The <b>dpi</b> value in the Export dialog has had its range extended; now possible values are from 0.01 to 100000. <br />
<br />
* Individual <b>&lt;tspan&gt;s</b> within text objects (including line tspans) can now be selected via the XML editor to view their bounding boxes (though per SVG, you cannot transform them). Also, you can use the <code>--query-*</code> command line parameters to find out the bounding boxes of tspans from a script. (Individual strings within or between tspans are still not selectable, and they cannot have an ID for querying anyway.)<br />
<br />
* The placeholder image which is shown when a bitmap file was no longer accessible reads now "<b>Linked image not found</b>" instead of the confusing "Broken image".<br />
<br />
* <b>Cloning multiple selected objects</b> now works as expected (i.e. each selected object is cloned separately, similar to the Duplicate command). Previously you could only clone a single selected object. <br />
<br />
* The separate "license" and "contributors" dialogs have been merged into tabs on the About dialog. The about dialog now correctly sizes itself to fit the size of the splash SVG (while remaining resizable), and the rendering area is now cropped to the correct aspect ratio when the dialog is resized. The dialog also now displays the build information in the upper right corner.<br />
<br />
* [new cursors - scislac]<br />
<br />
* In the Transform dialog / Rotate tab, the icon was flipped horizontally to be in line with the direction of positive rotation; the change was applied to the default (now crispy) and legacy icon sets.<br />
<br />
* The <b>scale ratio lock button</b> on the Selector controls bar shows a closed lock when pressed and open lock otherwise (same as the layer lock in the statusbar).<br />
<br />
* The <b>Browse</b> button on Export dialog now opens the new file chooser, same as those used by Open and Save.<br />
<br />
* A new <b>RazorWire</b> path marker was added. By applying it as a mid-marker you can get a good approximation of a razor wire.<br />
<br />
= Miscellaneous bugfixes =<br />
<br />
* Reading a document with an <b>incorrect namespace URI</b> not only did not cause Inkscape to complain, but could also "pollute" Inkscape's internal namespace table, resulting in an "infection" of subsequently saved documents by the incorrect namespace. This is now fixed, but as a result, documents with incorrect namespace URIs will no longer load. You will have to edit them in a text editor to fix the namespaces. <br />
<br />
* With newer versions of GTK, <b>dragging with graphics tablet pen</b> did not work in some tools and contexts (in particular, in Node and Rectangle tools). This is fixed.<br />
<br />
* <b>Scaling of objects with stroke</b> in Selector used to cause undesired shifts of the scaled object, as well as scaling it in the dimension which was intended to remain untouched (e.g. slight change in width when you scale only height). All these problems are now fixed, both for interactive scaling by mouse and for numeric scaling via the Controls bar, and for both values of the "Scale stroke with objects" option. Among other things, this means that stroked objects no longer lose snapping on scale, and that the "Default scale origin" option in the Selector tool preferences finally works as designed. Caveat: There may still be problems if you scale a selection that contains objects with different stroke widths.<br />
<br />
* Scaling of stroke now works for objects that didn't specify stroke-width; before, they always ended up with the default 1px stroke.<br />
<br />
* The bounding box for text and flowed text objects did not include stroke width. This has been fixed.<br />
<br />
* Stroke miterlimit on text objects was misinterpreted in absolute units instead of multiplies of stroke width (resulting in miter joins rendered as bevel). <br />
<br />
* The unfinished path in Pen tool is now cancelled, not finalized, when you switch away from the Pen tool. Apart from being more intuitively correct, this also fixes a crash when you quit Inkscape with the unfinished path in Pen tool.<br />
<br />
* Fonts on Win32 now use the native font mapper, meaning that Inkscape's font list is the same as other Windows programs, and the (potentially) very long delay experienced when using fonts for the first time in each session is gone.<br />
<br />
* Setting dash pattern was broken for transformed objects, and copy/paste of style with dash pattern did not apply correctly to objects with transforms.<br />
<br />
* An error caused a complete extra screen redraw after each zoom operation. That is, after you press "+" in a complex drawing, Inkscape redraws, but for some time after that it remains still unresponsive because it does that second redraw (invisibly for you, i.e. nothing changes on the screen). This is fixed.<br />
<br />
* Gradient rendering was off by one pixel, which often resulted in visibly wrong gradient rendering for small objects or in zoom-out. <br />
<br />
* The SVG path parser could not handle fractional numbers with the initial dot. <br />
<br />
* Several pattern rendering bugs are fixed, discovered by working with SVG files exported from Adobe Illustrator.<br />
<br />
* Inkscape on Mac OS X will now notice fonts in your ~/Library/Fonts directory, in addition to the other standard places.<br />
<br />
* Inkscape couldn't be compiled with libxml versions <= 2.6.9, and we now bumped the requirements from 2.6.0 up to <b>libxml >= 2.6.11</b>, which is the earliest you can get officially, anyway.<br />
<br />
* Inkscape no longer crashes when presented with a defective inx file for extensions.<br />
<br />
* More document memory is now freed when documents are closed.<br />
<br />
* EPS output now correctly includes an %%EOF footer.<br />
<br />
* There was a regression in 0.43 that caused several minor, though annoying bugs; knots and handles remained highlighted after the mouse was released, and the rubberband selection rectangle stayed visible if the selection was ended over a node while in the node tool. This regression has been fixed. <br />
<br />
* The connector routing code would previously sometimes confuse objects between multiple documents resulting in strange routing behaviour. This has been fixed.<br />
<br />
* There existed a bug in 0.43's Inkboard code that allowed a malicious outsider to very easily disrupt an Inkboard session. This has been fixed.<br />
<br />
* There existed a bug in 0.43's Inkboard code that would cause deadlocks in the case that two users attempted to invite each other at the same time (see bug #[https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1352522&group_id=93438 1352522] for further details). This should be fixed, although the fix has not been widely tested.<br />
<br />
* There existed a bug in 0.43's Inkboard code that would cause session invitations to not appear on the invitee's screen. This was the result of a mistake in handling GDK modifier flags, and has been fixed.<br />
<br />
= Translations =<br />
<br />
* INX files (containing the UI of the external effects) now allow the user visible strings to be translated. This means that effect dialogs, file type selections, and extension names can all be translated by translators.<br />
<br />
= Internal =<br />
<br />
* The Document Properties Dialog code was completely gtkmmified, which lead to dramatic reduction of code size due to usage of widget objects. The used widget objects should be reusable by other dialogs, too, and the code is much more readable.<br />
<br />
* Work on optimizing includes in all cpp files started, using the purgeincludes tool specifically written for that purpose, and ended with 40% of include lines removed!<br />
<br />
= Known problems =<br />
=== Problems with libgc-6.7 ===<br />
* Inkscape will hang or even crash when linked with this (newest) version of the Boehm garbage collection library. Make sure you use libgc-6.5 or 6.6 until this is sorted out.<br />
<br />
=== Namespaces may need fixing ===<br />
<br />
* Previous versions of inkscape sometimes silently saved documents with <b>wrong namespace URIs</b>. This has been fixed, but such corrupted documents will no longer load successfully. Such documents may require their namespace declarations to be fixed by hand.<br />
<br />
=== Beware of defective themes on Linux ===<br />
<br />
* Inkscape and other Gtk programs can crash on any Linux, when the <b>gtk2-engines-smooth / libsmooth</b> package is installed. We have filed a bug against libsmooth which is now in gtk-engine and part of gnome. Removing the package resolves the problem, however, but it would be nice if you as affected user would inform the gtk-engines maintainers of the problem. See especially http://bugzilla.gnome.org/show_bug.cgi?id=312115 (thanks to Thomas Wood)<br />
* A similar crash happens if the <b>KDE Baghira</b> theme or the package <b>gtk_qt_engine</b> are installed. If you experience Inkscape crashes on KDE, please try to install a different theme from Baghira, or uninstall the gtk_qt_engine package from your system. Both problems also affect older versions of Inkscape.<br />
<br />
=== Make sure to remove menus.xml if you have it ===<br />
<br />
* If you were using certain CVS/SVN builds from autumn of 2005, you may have the file <code>menus.xml</code> hanging around in your profile directory (e.g. <code>~/.inkscape</code> on Linux). In that case you will see many errors about verbs that cannot be found, and some commands in menus will be disabled. Make sure to delete <code>menus.xml</code> to fix this.<br />
<br />
= Previous releases =<br />
<br />
* ReleaseNotes043 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes043)<br />
* ReleaseNotes042 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes042)<br />
* ReleaseNotes041 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes041)<br />
* ReleaseNotes040 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes040)<br />
* ReleaseNotes039 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes039)<br />
* ReleaseNotes038 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes038)<br />
* ReleaseNotes037 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes037)<br />
* ReleaseNotes036 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes036)<br />
* ReleaseNotes035 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes035)</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=Notes_Alliberament&diff=6600Notes Alliberament2006-06-03T12:59:19Z<p>Xaviconde: </p>
<hr />
<div>== Inkscape 0.44: overview ==<br />
<br />
Inkscape 0.44 is bigger and better than ever. Some highlights:<br />
<br />
* Layers dialog<br />
<br />
* Outline mode, many performance improvements<br />
<br />
* Native PDF export with transparency<br />
<br />
* Clipping and masking support<br />
<br />
* Configurable keyboard shortcuts, including Xara X emulation<br />
<br />
* Docked color palette in the editing window<br />
<br />
* Interactive indicator of the style of selection in the statusbar<br />
<br />
* Innovative "node sculpting" and other improvements in Node tool<br />
<br />
* Extensions are enabled by default and work on both Linux and Windows<br />
<br />
* Better SVG support: <switch> element, ICC color profiles for images<br />
<br />
* Persistent rotation centers, Paste Size command<br />
<br />
* Redesigned preferences dialogs, new icons, rearranged menus, many cosmetic improvements<br />
<br />
* Hundreds of bugfixes and smaller features<br />
<br />
* Not directly related to Inkscape, but important nevertheless: since our last release, [http://www.mozilla.com/firefox/ Firefox 1.5] was released with SVG support enabled by default. This means that you can now view any Inkscape document right in your Firefox window without any format conversions or installing any plugins!<br />
<br />
= Performance =<br />
<br />
== Outline mode ==<br />
<br />
An Outline ("wireframe") display mode is implemented. Use the <i>View > Display Mode > Outline</i> to activate it. In this mode:<br />
<br />
* all paths and shapes are rendered as <b>inverse</b> (black on light background and vice versa) <b>outlines</b> of constant width (1 screen pixel regardless of zoom), without fill;<br />
<br />
* text is painted by inverse fill, without stroke; <br />
<br />
* bitmaps are shown as is;<br />
<br />
* any opacity and gradients are ignored.<br />
<br />
The outline mode is usually not drastically faster than regular mode (usually 10% to 50% faster), and in some special cases it may even be slower. However, the value of the outline mode is not only in its speed; it is a good way to get an idea of the structure and objects of your document, and it is convenient for precision node editing and for finding "stray objects". <br />
<br />
== Speed ==<br />
<br />
In addition to the Outline mode which makes it much easier to work with complex drawings, this version of Inkscape also provides significant speed improvements in many areas.<br />
<br />
* Thanks to <b>optimizations in the renderer</b>, Inkscape's screen redraw is <b>faster by at least 10%</b>, and in some cases (such as complex stroked/dashed paths at high zooms) <b>up to three times faster</b>. <br />
<br />
* <b>Optimizations in the Node tool</b> resulted in noticeable speed gains for node editing. Thus, switching to and from the Node tool (with a path selected), as well as selecting nodes in that tool, are now <b>at least ten times faster</b> than before. Other operations, including curve and node dragging and move/scale/rotate operations on multiple selected nodes, are much faster as well. This is especially important when working with complex paths; with these optimizations, paths containing several thousand nodes, though still slow, are much more usable.<br />
<br />
* An optimization in the attribute setting method made operations such as moving multiple objects with arrow keys at least <b>30% faster</b> compared to 0.43. This is especially noticeable when you are moving clones selected together with their original (e.g. a clone tiling), in which case Inkscape now works <b>three to four times faster</b>.<br />
<br />
* <b>Interface icons</b> are now rendered in the background (from SVG source in <code>share/icons/icons.svg</code>) when Inkscape is idle, rather than waiting for all the icons in a menu to render the first time you pull it up. This eliminates the annoying delay when opening menus for the first time.<br />
<br />
* Previously, zooming in to view a small portion of a path (especially big and complex path), there was a very noticeable slowdown and memory use increased dramatically. We optimized the renderer to <b>only process the visible part of a path</b>, and as a result the rendering speed is now almost the same at any zoom up to the maximum, providing up to 10-40 times speedup compared to the previous version (the closer is the zoom, the greater is the gain).<br />
<br />
* The <b>Path > Break Apart</b> command is now dozens of times (up to 100x) faster for complex paths with thousands of subpaths.<br />
<br />
= Interface =<br />
<br />
== Layers dialog ==<br />
<br />
* Ctrl+Shift+L [joncruz, mental]<br />
<br />
== Selected style indicator ==<br />
<br />
A new control in the left end of the statusbar lets you quickly view and change the <b>fill and stroke of the selected objects</b>. When you have a text selection in Text tool or a gradient handle selected in the Gradient tool, this indicator displays and changes the style of the text fragment or gradient stop, instead of the entire object (it's the same behavior as the Fill&amp;Stroke dialog.)<br />
<br />
* The two indicators, labelled <b>F:</b> (top) and <b>S:</b> (bottom), display fill and stroke of the selected object(s) correspondingly. (For gradient handles, they always display the same style.)<br />
<br />
* Each fill/stroke indicator can display either a <b>color+opacity swatch</b> (the opacity shown here is the fill opacity or stroke opacity, not the master opacity) or a text label specifying <b>N/A</b> (nothing selected), <b>None</b> (no fill/stroke), <b>Unset</b> (unset fill/stroke), <b>L Gradient</b>, <b>R Gradient</b>, <b>Pattern</b> (corresponding fill/stroke types), or <b>Different</b> (selected objects have different fill/stroke types).<br />
<br />
* Additionally, each indicator may be accompanied by one of two flags, <b>m</b> ("multiple", meaning there are two or more objects all with the same fill/stroke) or <b>a</b> ("averaged", meaning there are two or more objects with different flat colors in fill/stroke, and the indicator shows the average of these colors).<br />
<br />
* <b>Left-click</b> on an indicator opens or activates the Fill&Stroke dialog with the corresponding tab (Fill or Stroke) active.<br />
<br />
* <b>Right-click</b> on an indicator opens a popup menu with the following items:<br />
** <b>Edit fill/stroke...</b>: Opens or activates the Fill&Stroke dialog with the corresponding tab selected. (Same as left-click.)<br />
** <b>Last set color</b>: Applies to the selected objects the fill/stroke color that was last applied to anythig.<br />
** <b>Last selected color</b>: Applies to the selected objects the fill/stroke color that was last displayed in this indicator. (Allows you to easily copy fill/stroke color between objects: select source, select destination, apply "last selected color".)<br />
** <b>Invert</b>: Sets the fill or stroke to the inverse of the current color (does not affect opacity).<br />
** <b>White</b>, <b>Black</b>: Sets the fill or stroke to the corresponding color (fully opaque).<br />
** <b>Copy color</b>, <b>Paste color</b>: Copies or pastes the fill or stroke color (when it's color) to/from the system clipboard, as text in the <code>#rrggbb</code> hex format.<br />
** <b>Swap fill and stroke</b>: Exchanges fill and stroke (both their types and colors, if any). <br />
** <b>Make fill/stroke opaque</b>: Removes fill or stroke transparency (not master transparency!).<br />
** <b>Unset fill/stroke</b>: Unsets fill or stroke from selected objects.<br />
** <b>Remove fill/stroke</b>: Removes fill or stroke from the selected objects.<br />
<br />
* <b>Middle-click</b> on a fill/stroke indicator removes fill/stroke from selected objects; if it is already removed (i.e. if the indicator displays "None"), it does the same as the "Last set color" command from the popup menu.<br />
<br />
* <b>Drag and Drop</b> of colors onto a fil/stroke indicator sets the fill and stroke of the selected object(s) correspondingly.<br />
<br />
* The Stroke indicator also displays the <b>stroke width</b> of selection (averaged if there are multiple objects selected with different stroke widths), located to the right of the stroke color/transparency swatch. Left-clicking on it opens the Fill&Stroke dialog with the Stroke Style tab selected. Right-clicking on it opens a popup menu which allows you to choose the units for displaying the stroke width, as well as choose one of the presets to assign to selection.<br />
<br />
* To the right of the fill/stroke indicators, the <b>Opacity</b> numeric field (labelled "O:") shows and allows you to change the master opacity of the selected object (or the averaged opacity of several selected objects). <b>Right-clicking </b> the numeric field opens a popup menu with preset opacity levels. <b>Middle-clicking</b> on the "O:" label cycles the opacity through the values of 0 (transparent), 0.5, and 1 (opaque).<br />
<br />
The zoom field and the cursor coordinates indicator have been rearranged for compactness and moved to the right end of the statusbar. There's also a window resize handle added at the very end of the statusbar.<br />
<br />
== Tool style indicators ==<br />
<br />
For each object-creating tool (shapes, Pen/Pencil, Calligraphic, Text), the Controls bar (above the canvas) now includes a <b>style indicator</b> on the right. This indicator shows you which style the newly created object will have. The indicator correctly displays whichever style the tool is set to use - the global "last set" style or that tool's fixed style. For example, clicking on a palette swatch (even with nothing selected) changes the "last set" color and, if your tool is set to use the last set color, its indicator is updated, giving you an idea of your "brush" before you start to draw.<br />
<br />
== Controls bar for the Text tool ==<br />
<br />
* This version adds the beginnings of a Controls Bar for the Text tool (previously empty). Now you can select the <b>font family</b>, <b>size</b>, apply <b>bold</b> and <i>italic</i> styles, change <b>alignment</b> and <b>text orientation</b> without opening the Text and Font dialog. <br />
<br />
* All controls are <b>instant-apply</b> and work on the entire text object (if nothing selected) or text selection. They can also apply to multiple text objects (though you would need to switch to Selector to select multiple text objects, then switch back to Text tool for its controls). <br />
<br />
* The font-family drop-down contains names and <b>previews</b> of all fonts; unlike other programs, we didn't apply each font to its name, but added a separate preview string displayed with gray color after each font's name. This design ensures readability of font family names and provides maximum useful information in a limited space.<br />
<br />
* We will be adding more controls (including spacing and kerning) to this bar for the next versions.<br />
<br />
== Docked color palette ==<br />
<br />
* Previously, color swatches could only be used from a floating palette (Ctrl+Shift+W). Now the color swatches palette is embedded in the main UI, at the bottom of the window between the canvas and the statusbar. It is enabled by default; use <i>View > Show/Hide > Palette</i> to enable or disable it. The docked palette has the same functionality as the floating one; use a button in the top right corner to access the swatches menu.<br />
<br />
* The <b>Wrap</b> option (off by default) in the swatches menu converts the palette from a single row into a frame 2 or 3 rows high, for better access to colors in large palettes.<br />
<br />
* <b>Drag and Drop</b> of <b>colors</b> has been enabled.<br />
** Dragging colors from a palette shows a live swatch of the color being dragged under cursor.<br />
** Drag and Drop of colors onto the selected style indicator in the statusbar sets the fill or stroke of the selected object(s).<br />
** Colors can be <b>dropped</b> directly on to objects on canvas to set their <b>fill</b>, or <b>shift+dropped</b> to set their <b>stroke</b>. This affects only the object you drop the color on, regardless of whether that object is selected or not.<br />
** Colors can be dragged to and from other applications.<br />
<br />
* The new <b>Inkscape default</b> color palette was added. It contains a range of grays, standard HTML named colors, and a full range of colors sorted by their HSL values (475 colors overall). It is generated by a Python script which is available from Inkscape SVN in share/palettes.<br />
<br />
* Several <b>specialized color palettes</b>, useful in color-coordinated projects, were created or borrowed from GIMP: Grays, Reds, Greens, Blues, Gold, Royal, Khaki, Hilite, and Topographic.<br />
<br />
* All standard sizes of the swatches (Tiny, Small, Medium, Large, Huge) are made <b>smaller</b> overall.<br />
<br />
== Inkscape Preferences dialog ==<br />
<br />
Not only was the Inkscape Preferences dialog completely rewritten and redesigned, it is now also <b>fully GNOME-HIG compliant</b>. Numerous <b>bugs</b> were taken care of with the rewrite. As a new feature, the <b>Simplify threshold</b> can now be set with more precision.<br />
<br />
== Document Properties / Metadata dialogs ==<br />
<br />
* The Document Preferences dialog is now named <b>Document Properties</b>, and it was split in two: metadata were extracted into the <b>Document Metadata</b> dialog; metadata widgets are now also spread over two pages.<br />
<br />
* A button was added to <b>fit the canvas to the current selection</b> or, if there's no selection, to the entire drawing. The button resizes the canvas and, if necessary, moves the drawing into place. It is now very easy to size the canvas to an illustration after it is ready.<br />
<br />
* <b>New controls</b>: the new object snapping features required their own property widgets, and you can set the snapping sensitivity with a slider, or let it snap regardless of distance (grid only).<br />
<br />
* Rearrangements within <b>Document Properties</b>: everything snapping-related was collected on one page; Grid and Guide widgets are on their own, the same page. For better HIG compliance, all widgets were categorized; especially the widgets on the Page page were completely rearranged in the General/Format/Border categories.<br />
<br />
* <b>Bug fixes</b>: grayed out license URI had too low contrast, so it's no longer grayed out; the proprietary license didn't clean the license URI; spinbuttons had no tooltips, and minor grid quirks were removed; data was not updated when a new file replaced another in the same window.<br />
<br />
* <b>HIG compliance</b>: much work went into that, and now only a few details are missing from full Gnome-HIG compliance.<br />
<br />
* <b>Updated Creative Commons Licenses</b>: Updated CC licenses to the latest 2.5 versions by default in the license tab of the metadata dialog.<br />
<br />
== Menus ==<br />
<br />
* <b>Zoom</b> commands in the View menu are moved to a submenu; the <i>Zoom In</i> and <i>Zoom Out</i> commands are added to that submenu.<br />
<br />
* <b>Clone</b> commands are moved into a submenu in Edit menu and given more descriptive names and tips.<br />
<br />
* <b>Pattern</b> commands (<i>Objects to Pattern</i> and <i>Pattern to Objects</i>) are moved into a submenu in Object menu, under the new Clip and Mask submenus.<br />
<br />
* The contents of the <b>Effects menu</b> are categorized into submenus, and several effects are renamed to use more intuitive names. <br />
<br />
== Statusbar ==<br />
<br />
* In Selector, for multiple selected objects, the statusbar now reports their types. For example, if 5 groups are selected, it displays<br />
<br />
::<b>5</b> objects of type <b>Group</b> in layer <b>LayerName</b>.<br />
<br />
:instead of just "5 objects selected" as before. If there are up to 3 types in the selection, they will be listed, for example:<br />
<br />
::<b>5</b> objects of types <b>Group</b>, <b>Path</b>, <b>Rectangle</b> in layer <b>LayerName</b>.<br />
<br />
:The order of the list will correspond to the order in which the objects were added to selection. If there are 4 or more types in selection, only the number of types is reported, for example:<br />
<br />
::<b>5</b> objects of <b>4</b> types in layer <b>LayerName</b>.<br />
<br />
* In Selector, objects selected in groups are now identified as such, and the group ID is given, for example:<br />
<br />
::<b>Rectangle</b> in group <i>g212</i> (layer <b>content</b>)<br />
<br />
:If selected objects have different parents within one layer (for example, if one is selected in a group and another outside it), the number of parents is reported:<br />
<br />
::<b>2</b> objects of types <b>Rectangle</b>, <b>Path</b> in <b>2</b> parents (layer <b>content</b>)<br />
<br />
:If objects are in different layers, only the number of layers is reported since this also implies different parents:<br />
<br />
::<b>2</b> objects of types <b>Rectangle</b>, <b>Path</b> in <b>2</b> layers<br />
<br />
* In Node tool, if your node selection includes nodes from different subpaths, statusbar reports the number of subpaths with selection and the total number of subpaths, for example:<br />
<br />
::<b>2</b> of <b>195</b> nodes selected in <b>2</b> of <b>36</b> subpaths.<br />
<br />
* The contents of the statusbar message are now duplicated as a <b>tooltip</b> that is shown when you hover the mouse over the statusbar. [TODO: need to strip markup from the tooltips.] <br />
<br />
* The statusbar text is now no longer just cut off if there is insufficient room, but an ellipsis (...) is inserted at the end to show there's more (only with Gtk 2.6 and newer).<br />
<br />
== Theme ==<br />
<br />
* Inkscape has a <b>new default icon set</b> titled "Crispy" provided by Andre Sousa. The new icons are intended to add a more professional and cohesive look to our application, as well as to make the functions the icons represent more self-evident.<br />
<br />
= Clipping and masking =<br />
<br />
Inkscape now provides some UI for using <b>clipping paths and masks</b>. <br />
<br />
* Any object can be non-destructively intersected with a path (called a <i>clipping path</i>) so that only the intersected portion of the object is visible. <br />
** <b>To apply clipping</b>, select the objects to be clipped and the clipping path object, make sure the clipping path is above the other objects in z-order, and do <i>Object > Clip > Set</i>.<br />
** You can <b>transform, edit, or style</b> the clipped objects as usual. The clipping remains applied and transforms together with each clipped object.<br />
** To <b>remove the clipping</b>, do <i>Object > Clip > Release</i>. The clipping path is returned to the drawing as a regular object; it is inserted on top of the unclipped object in z-order. <br />
<br />
* Any object can be non-destructively masked by another object (called <i>mask</i>) so that: the mask's black or transparent areas become fully transparent in the masked object; mask's opaque white areas become fully opaque; and all intermediate colors translate into intermediate levels of opacity in the masked object. This allows you to apply, for example, arbitrary transparency gradients to objects.<br />
** To <b>apply a mask</b>, select the objects to be masked and the mask object, make sure the mask is above the other objects in z-order, and do <i>Object > Mask > Set</i>.<br />
** You can <b>transform, edit, or style</b> the masked objects as usual. The mask remains applied and transforms together with each masked object.<br />
** To <b>remove the masking</b>, do <i>Object > Mask > Release</i>. The mask is returned to the drawing as a regular object; it is inserted on top of the unmasked object in z-order. <br />
<br />
* Objects with clippath show their bounding box intersected with the bounding box of the clippath, instead of the original unclipped bbox as before. (However, this does not apply to objects without clippath of their own which are clipped by being inside a clipped group.)<br />
<br />
* Clipped or masked objects display "<i>clipped</i>" or "<i>masked</i>", correspondingly, in their statusbar descriptions.<br />
<br />
* Although Inkscape had render-only support for clipping paths and masks for quite some time, in this release we fixed a number of bugs which may affect the display of your documents using clippaths or masks.<br />
** Clippaths and masks with objectBoundingBox units are now shown correctly upon loading of the document.<br />
** Clippaths without fill didn't work, this is now fixed.<br />
** Objects with clippaths or masks are correctly copied/pasted between documents.<br />
<br />
= SVG conformance =<br />
<br />
== Color profile support ==<br />
<br />
Inkscape now includes base ICC profile functionality. If compiled with LittleCMS support (if you run <code>configure</code> with <code>--enable-lcms</code> switch), Inkscape passes the [http://www.w3.org/Graphics/SVG/Test/20030813/htmlframe/full-color-prof-01-f.html ICC color profile test] by W3C. The &lt;color-profile&gt; element has been implemented along with the "color-profile" attribute for &lt;image&gt; elements.<br />
<br />
== &lt;switch&gt; support ==<br />
<br />
Rendering support for SVG 1.1's '''Conditional Processing Module''' has been implemented, including ''switch'' element, ''requiredFeatures'', ''requiredExtensions'', ''systemLanguage'' attributes. Inkscape passes the Conditional processing tests ([http://www.w3.org/Graphics/SVG/Test/20030813/htmlframe/full-struct-cond-01-t.html] and [http://www.w3.org/Graphics/SVG/Test/20030813/htmlframe/full-struct-cond-02-t.html]) by W3C.<br />
<br />
== SVG output ==<br />
<br />
* In Inkscape's SVG documents, <b>colors</b> are now expressed by name (‘white’) or three-digit form (‘<tt>#f3c</tt>’) when possible.<br />
<br />
* The numeric values in <code>transform</code> attributes are written without insignificant trailing zeros, and anything less than that 1e-8 by absolute value (usually caused by rounding errors) is written as 0 to reduce clutter.<br />
<br />
= Transformations =<br />
<br />
== Transform dialog ==<br />
<br />
Fixes and improvements in the Transform dialog (Ctrl+Shift+M):<br />
<br />
* The <b>Apply to each object separately</b> checkbox is added, allowing you to scale/rotate/skew each selected object by the same amount, around that object's center. When off (by default), the selection is transformed as a whole. The status of this checkbox is remembered across sessions. (It has no effect on Move and Matrix tabs).<br />
<br />
* The <b>Clear</b> button resets the values on the current tab to defaults.<br />
<br />
* The <b>Scale</b> tab now allows you to specify horizontal or vertical size increments in percentage or absolute units. Also, there's a <b>Scale proportionally</b> checkbox which ensures that scaling preserves the width/height ratio. (If you are scaling several objects proportionally with "Apply to each object separately", you can only use the % unit to specify the scaling; otherwise each object's scale increments will have the width/height ratio of the entire selection, not of that specific object.)<br />
<br />
* The <b>Skew</b> tab can now specify the skew as an <b>absolute displacement</b> (e.g. for horizontal skewing of a rectangle, that means the shift of the top rectangle side relative to the bottom), as <b>percentage displacement</b> (e.g. a 1% horizontal skew of a rectangle means shifting the top side by 1% of the rectangle height), or as an <b>angle</b> (e.g. horizontal skew by 15 degrees results in the sides of a rectangle being rotated to that angle, while the top and bottom remain horizontal).<br />
<br />
* The <b>Matrix</b> tab (previously called "Transform") can either edit the current <code>transform=</code> matrix of an object, or post-multiply the <code>transform=</code> with the matrix you specify, depending on the <b>Edit current matrix</b> checkbox. (As it is now redundant, the transformation matrix in the Object Properties dialog is removed.)<br />
<br />
* The dialog now correctly <b>watches selection changes</b> in the active document window and updates its values accordingly.<br />
<br />
* The layout of the dialog is simplified, tooltips and mnemonics added for better usability.<br />
<br />
* Many bugs are fixed, especially in value conversions between units.<br />
<br />
== Persistent rotation centers ==<br />
<br />
* The position of the center (axis) of rotation and skewing used by Selector is now <b>remembered</b> for all objects and restored when you select those objects again (even after saving and reopening the document). When you move or scale an object, its rotation center is moved or scaled too, so its position relative to the object always remains the same unless you move it explicitly.<br />
<br />
* When you have several objects selected, they use the rotation center of the <b>first selected object</b>. If the first object does not have center set (i.e. if it's in a default central position), then several objects will rotate around the geometric center of their common bounding box (as before).<br />
<br />
* <b>Shift+click</b> on the rotation center resets it back to the center of the object's box.<br />
<br />
* Consequently, dragging the rotation center is now <b>an undoable action</b>; you can press Ctrl+Z to undo the drag.<br />
<br />
* <b>Keyboard rotation</b> by [, ] keys with various modifiers, as well as the Rotate tab in the <b>Transform dialog</b>, work around the selected object's rotation center (for multi-object selection, the rotation center of the first selected object).<br />
<br />
* Rotation centers are <b>preserved</b> when duplicating, cloning (including clone tiler), grouping/ungrouping, and converting to path.<br />
<br />
[TODO: <br />
- make it work smartly for groups: if a group has center not set, return the center of the first object inside group with the center set<br />
<br />
- a separate tab in the Transform dialog, with 9 buttons in the square grid (for setting it to object's corners, sides, and center) as well as x/y fields for setting center to any position<br />
<br />
- make center snap to grid/guides/objects and to other centers<br />
<br />
- make objects snap with their center to grid/guides/objects]<br />
<br />
== Pasting size ==<br />
<br />
A number of commands are added to easily scale selected objects to match the size of the object(s) previously copied to the clipboard. They are all in the Paste Size submenu in Edit menu:<br />
<br />
* <b>Paste Size</b> scales the whole selection to match the overall size of the clipboard object(s).<br />
<br />
* <b>Paste Width</b>/<b>Paste Height</b> scale the whole selection horizontally/vertically so that it matches the width/height of the clipboard object(s). These commands honor the scale ratio lock on the Selector controls bar (between W and H fields), so that when that lock is pressed, the other dimension of the selected object is scaled in the same proportion; otherwise the other dimension is unchanged.<br />
<br />
* <b>Paste Size Separately</b>, <b>Paste Width Separately</b> and <b>Paste Height Separately</b> work similarly to the above described commands, except that they scale <i>each selected object</i> separately to make it match the size/width/height of the clipboard object(s).<br />
<br />
= Tools =<br />
<br />
== Node tool ==<br />
<br />
=== Node sculpting ===<br />
<br />
An entirely new way of manipulating paths in Node tool is added in this version: Node sculpting. Normally, when you have several nodes selected and you drag one of them, all selected nodes move by the same amount. Now, if you <b>Alt-drag</b> one of the selected nodes, only that node is fully displaced; other selected nodes are moved less than the full amount, so that those farthest from the drag point remain stationary. This is similar to "proportional editing" or "soft selection" in 3D editors such as Blender.<br />
<br />
So, for example, if you select several nodes on a straight line and Alt+drag the middle selected node, the path will bend into a <b>smooth bell-like curve</b>. Nodes' handles are also adjusted correspondingly to keep the overall shape smooth and natural. (If you don't have enough nodes on a path fragment that you want to reshape in this way, just select the end nodes of that fragment and press <b>Ins</b> a few times to populate it with nodes.)<br />
<br />
Moreover, node sculpting is <b>sensitive to pressure</b> of your tablet pen. If you press slightly, your curve will have a narrow sharp tip (i.e. the nearest neighbors of your dragged node will move only a bit); if you press hard, the curve's tip will be wide and blunt (i.e. the nearest neighbors will move almost as much as the dragged node). (Hint: to stop dragging without losing your shape, first release Alt and then lift the tip of the pen.)<br />
<br />
There are many possible applications of the sculpting technique. To take a simple example, selecting all nodes of an ellipse-like shape and Alt+dragging one of them will smoothly and naturally stretch and skew the entire shape in any direction. Doing the same to a complex path, such as star or spiral, will twist and punch it without destroying its intricate structure - this is the way to get squashed or self-intersecting stars, eccentric spirals and other shapes not easily doable before. Selecting only part of all nodes allows you to smoothly reshape parts of the figure without disturbing the rest.<br />
<br />
When applied to text converted to path, node sculpting is a fun and easy way to twist, bend and distort it, achieving effects similar to "perspective envelope" or "curvilinear envelope" in other programs - but in a more powerful and flexible way. For example, by selecting all or part of the text's nodes and Alt-dragging, you can not only make a wavy banner out of a paragraph of text, but also apply a "magnifying lens"-like effect to any word in the middle. <br />
<br />
Especially useful node sculpting is for complex natural paths, such as calligraphic strokes or bitmap traces, where you often want to do large-scale pushes and bends without destroying the small-scale features. Things like making a calligraphic stroke narrower in one place and wider in another, or changing the proportions, extending the ear or flattening the nose of a head - all this is now much faster and more natural to do using sculpting. It is also a new way to <i>create</i> new paths, too - starting from en ellipse with added nodes, it takes just a few Alt+drags to tweak it into a silhouette of a head, or a map of Australia, or an Inkscape logo!<br />
<br />
Some examples are shown on the screenshot: [[http://www.inkscape.org/screenshots/gallery/inkscape-0.44-nodesculpting.png]].<br />
<br />
=== "Show handles" toggle ===<br />
<br />
The Controls bar for the Nodes tool now includes a toggle button which controls whether Bezier handles are shown on selected nodes (on by default). Selecting and dragging nodes on node-dense paths in zoom-out (e.g. for node sculpting) may be extremely difficult without hiding the handles, as it's hard to pick a node and not a handle when handles are shown.<br />
<br />
=== New deletion behavior ===<br />
<br />
* In Node tool, <b>deleting node(s)</b> by Del/Backspace keys or by Ctrl+Alt+clicking a node now <b>tries to preserve, as much as possible, the current shape of the path</b>. This means that the nodes adjacent to those being deleted have their handles adjusted to approximate the form that the path had before deletion. For example, if you Ctrl+Alt+click a path twice, once to add a new node and then to delete it, the path will not change at all (or change very slightly). The old deletion behavior without adjusting handles is still available via <b>Ctrl+Del</b> or <b>Ctrl+Backspace</b>.<br />
<br />
=== Preserving positions of nodes and handles ===<br />
<br />
* When you <b>switch the type</b> of the selected node to Smooth or Symmetric by pressing Shift+S/Shift+Y, you can now <b>preserve the position</b> of one of the two handles by hovering your mouse over it, so that only the other handle is rotated/scaled to match.<br />
<br />
* Similarly, when you <b>join endnodes</b> by pressing Shift+J, you can <b>preserve the position</b> of one of the two nodes by hovering your mouse over it, so that only the other node is moved. <br />
<br />
=== Miscellaneous ===<br />
<br />
* The <b>!</b> key <b>inverts node selection</b> in the current subpath(s) (i.e. subpaths with at least one selected node); <b>Alt+!</b> inverts in the entire path. (This is similar to how these keys work in Selector, with current subpath(s) instead of the current layer.)<br />
<br />
* The keyboard shortcut for "Make selected segments curves" in Node tool is changed from Shift+K to <b>Shift+U</b> for better mnemonics.<br />
<br />
== Calligraphic pen ==<br />
<br />
* Even when using a graphics tablet with pressure sensitivity, the Calligraphy pen's strokes often look too smooth and artificial. To enable a more natural look, the new <b>Tremor</b> parameter is added to the Calligraphy tool in this version. Adjustable in the Controls bar from 0.0 to 1.0, it will affect your strokes producing anything from slight unevenness to wild blotches and splotches. This significantly expands the creative range of the tool.<br />
<br />
* In all previous versions, pen width depended on zoom in such a way that the strokes <i>appeared</i> the same visible width at any zoom, but were in fact narrower at zoom-in and wider at zoom-out. This behavior makes sense if you want to keep the same "feel" of the pen regardless of zoom; for example, if you zoomed in to make a small fix to your drawing, it's natural that your pen becomes physically smaller but feels the same to you. So, this behavior is kept as the default, but now we also added an alternative mode where your <b>pen width is constant in absolute units</b> regardless of zoom. To switch to this mode, use the checkbox on the tool's Preferences page (you can open it by double-clicking the tool button).<br />
<br />
* The <b>Width</b> field in the tool's controls bar now changes <b>from 1 to 100</b>, which corresponds to the range from 0.01 to 1.0 in the previous version. If the "width in absolute units" mode is turned on, the value in this fields gives the width of the stroke in px units. In the default mode, the value of 100 gives 100px wide strokes only at 100% zoom, and strokes are correspondingly narrower or wider at other zoom levels.<br />
<br />
* A new preferences option for the Calligraphic tool, <b>Keep selected</b>, controls whether the newly created object remains selected after you finish drawing it. If you turn it off (by default it's on) and set the tool to using Last Set color, you can easily choose a new color by clicking on the palette without having to worry if this will change the color of the stroke you just created. (Watch the tool style indicator at the right end of the Controls bar for the style of the next stroke you will draw.)<br />
<br />
* <b>Esc</b> deselects selected objects in Calligraphic, as in most other tools.<br />
<br />
* The stroke you're drawing is now shown, while you're drawing it, with the correct color and opacity that it will eventually have, instead of always black as before.<br />
<br />
* On a new Inkscape installation, this tool now uses the last set style by default instead of the fixed black as before (this is changeable in the Inkscape Preferences for the tool).<br />
<br />
== Pen tool ==<br />
<br />
* While drawing a path, you can now <b>move the last node you created</b> by the same keys as in Node tool - that is, arrows, with Shift (for 10x displacement) or Alt (screen pixel displacement) modifiers. <br />
<br />
* Also, you can switch the not-yet-finalized (red) segment of the path being drawn from curve to line (<b>Shift+L</b>) or back to curve (<b>Shift+U</b>), again the same shortcuts as in the Node tool.<br />
<br />
* By popular demand, if a new path is being drawn but not yet finished, <b>Ctrl+Z cancels</b> that unfinished path (i.e. does the same as Esc), instead of undoing the previous action.<br />
<br />
* In Pen tool, <b>Del</b> works the same as Backspace to delete the last created point on the unfinished path.<br />
<br />
= Connectors and automatic layout =<br />
<br />
* There have been numerous bugfixes and several improvements to the behaviour of <b>connectors</b> and the <b>connector tool</b>:<br />
** Connectors moved as part of a selection will now stay attached to other objects in the selection, rather than becoming detached from them.<br />
** By default, the Connector tool will not attach connectors to text objects. There is a new checkbox in the connector preferences to control this setting.<br />
** The <b>margins around avoided shapes</b> (used for autorouting connectors) can now be adjusted via the "Spacing" control on the controls bar.<br />
<br />
* Automatic Diagram Layout - A new button is available in the alignment and distribution dialogue that performs automatic layout of diagrams involving a network of shapes and connectors. Layout is accomplished using force-directed graph layout based on the Kamada-Kawai algorithm. This algorithm treats edges as if they are springs such that the distance between nodes will be proportional to the path length---number of connectors---between them. Disconnected components (where not every shape is connected) will be arranged around the circumference of a circle.<br />
<br />
* There is a new <b>Remove Overlaps</b> button to move the selected objects enough that they don't overlap each other. A minimum spacing between the boundaries of objects can be specifiedTogether with the automatic layout tool, described above, this should be a significant addition to Inkscape's usability for diagramming. [Consider expanding this, comparing with existing Unclump and Distribute edge-to-edge buttons. - pjrm]<br />
<br />
= Selective tracing with SIOX =<br />
<br />
[ishmal]<br />
<br />
<br />
= Snapping =<br />
<br />
* [object snap - carl]<br />
<br />
* [highlight - mtou]<br />
<br />
* [only to visible gridlines - mtou]<br />
<br />
* <b>Guidelines</b> are made easier to pick: now you don't need to position mouse <i>exactly</i> over a guideline to activate it, instead there's a small position tolerance (1 screen pixel on each side of the guideline).<br />
<br />
= Sublayers =<br />
<br />
Previously, it was only possible to make a group a temporary sublayer by entering that group. Now Inkscape supports creating and using true persistent sublayers within a layer.<br />
<br />
* The <b>Add layer</b> dialog allows you to place the new layer above, below, or inside the current layer.<br />
<br />
* In Preferences (Selecting tab), options are added allowing the "Select All" command and Tab key selection to work either in the current layer only or in the current layer and its sublayers.<br />
<br />
= Extensions =<br />
<br />
* The <b>Effects menu is now always on</b>, it's no longer an "experimental feature". The preference setting to enable the menu has been removed.<br />
<br />
* Python extensions (which includes almost all currently available extensions) <b>work on Windows out of the box</b>, using a copy of Python shipping with Inkscape. The only minor inconvenience is that when an effect is launched, you get an empty console window that stays on while the effect is doing its work. (Don't close that window, it will disappear by itself when the effect is finished.)<br />
<br />
* A new Python effect, <b>Render > LaTeX formula</b>, allows you to type in any LaTeX formula and get a vector object with the TeX rendition of this formula inserted into your document. You need to have <b>latex</b>, <b>dvips</b>, and <b>pstoedit</b> installed and in PATH for this to work.<br />
<br />
* A new Python effect, <b>Flatten Path</b>, flattens paths in the current selection, approximating each path with a polyline whose segments meet the specified criteria for flatness.<br />
<br />
* A new Python effect, <b>Measure Path</b>, attaches a text label to each path in the selection giving the length of that path (in px units).<br />
<br />
* The <b>Radius Randomize</b> effect has a new parameter which enables <b>normal distribution</b> of random displacements instead of uniform as before, which gives a more natural feel to the randomized path.<br />
<br />
* The <b>Render > L-system</b> (formerly "Fractal (Lindenmayer)") effect is improved in this version. Now you can specify different angle values for turning left and right, which makes it possible to smoothly bend some L-systems sideways. Also, you can separately randomize the step length and the angles by a given percent for more natural look (this works especially well with plant-like branching shapes). This effect can be used to create Penrose tiling, Sierpinsky triangle, Dragon curve and other famous mathematical artefacts, as well as various meanders, friezes, patterns, and trees. Some examples can be seen on this [http://inkscape.org/screenshots/gallery/inkscape-0.44-lindenmayer.png screenshot] as well as in the new example file <code>share/examples/l-systems.svg</code>.<br />
<br />
* The <b>Interpolate Path</b>, <b>Random Tree</b>, and <b>L-system</b> effects are fixed to place their result on the current layer instead of document root and in the center of the (last-saved) document view instead of 0,0 as before.<br />
<br />
* INX files now have the ability to hold more information. This includes tooltips and descriptions of the extensions. These are all also translatable.<br />
<br />
* Thanks to keyboard configurability, it is now possible to assign keyboard shortcuts to those effects you use most often, so you can activate them without going into the menu.<br />
<br />
= Formats =<br />
<br />
* Inkscape's <b>PDF export</b> is now native (i.e. does not require any external applications) and <b>supports transparency</b>, including gradients with transparency. This replaced the old export extension that required Ghostscript and worked via Postscript, losing any transparency. The new PDF export is still immature; in particular it does not handle text, so you should check "Convert text to path" on the export options dialog. Other things not yet supported include: gradients on stroke; eccentric elliptic gradients; patterns, masks, and clipping paths; embedded images.<br />
<br />
* You can now <b>Save as Compressed Inkscape SVG with media</b>.This save option collects the svg file and all linked images into a zip archive for distribution. Although you cannot open the resulting archive directly with inkscape, the media is linked such that after unzipping you can open the SVG file immediately.<br />
<br />
* An output format for <b>desktop cutting plotters</b>, such as the Wishblade and Craftrobo, was added. This format is a very minimalist DXF file with appropriate scaling and translation applied. This output format should not be expected to operate as a generalized DXF output.<br />
<br />
* [xfig]<br />
<br />
* [odg - ishmal]<br />
<br />
* The new <b>XCF output extension</b> exports all top-level elements (i.e. layers and objects directly under root) as PNGs and assembles them into an XCF for procesing in the Gimp. Requires Python, PyXML and Gimp. Gimp 2.2.x or above must be in the path and be named <code>gimp</code>. A version of Inkscape 0.44 or above must be accessible from the path. Does not function in Windows.<br />
<br />
= Configurable keyboard =<br />
<br />
Inkscape's <b>keyboard shortcuts are now configurable!</b> <br />
<br />
At this time, not all Inkscape actions can have their shortcuts customized. However, the majority of actions, including everything you see in the menus, are already configurable, and we're working on making more actions configurable. <br />
<br />
On startup, Inkscape reads its keyboard shortcuts from <code>share/keys/default.xml</code>. That file is a copy of <code>inkscape.xml</code> in the same directory, which also contains keyboard emulation profiles for other vector editors:<br />
<br />
*<code>xara.xml</code>: Xara X/Xara Xtreme/Xara LX keys<br />
<br />
You can copy any of these over default.xml to use that profile. In all profiles, those keys which are not used by the corresponding program still have their Inkscape bindings. If you can contribute a profile for some vector editor that we don't yet have, we will appreciate that. The files have a simple XML-based format described in <code>inkscape.xml</code>.<br />
<br />
You can also <b>customize some of your keybindings</b> without overwriting the main <code>default.xml</code>. If your profile directory (<code>~/.inkscape</code> on Linux) contains a <code>keys</code> subdirectory with a <code>default.xml</code> file, the keybindings from that file will overlay (i.e. add to, and override in case of a conflict) the default bindings. The format of your own <code>default.xml</code> is the same as that of the main <code>default.xml</code>.<br />
<br />
= Miscellaneous shortcuts =<br />
<br />
* Now you can use <b>Shift+middle button drag</b>, in any tool, to zoom into an area. This works the same as simple drag in Zoom tool, but is faster because it does not require switching away from your current tool. Together with <b>middle button drag</b> (panning), <b>middle button click</b> (zoom in) and <b>Shift+middle button click</b> (zoom out), this completes the set of canvas navigation shortcuts available in any tool or context.<br />
<br />
* In Gradient tool, <b>Shift+R reverses the gradient definition</b> (i.e. mirrors the stop positions) without moving the gradient handles. For example, an elliptic gradient with blue center and red periphery becomes red in the center and blue in the periphery. This works on the gradient(s) of the currently selected gradient handle or, if no handle is selected, on all selected objects' gradients. (Compare with the Node tool where Shift+R reverses the direction of the selected path.) This is especially convenient for elliptic gradients which, unlike linear, you cannot simply rotate by 180 degrees for the same result.<br />
<br />
* In Selector, <b>Ctrl+Enter</b> enters the selected group (making it a temporary layer). <b>Ctrl+Backspace</b> leaves the current layer and goes one layer up in the hierarchy (but not to root).<br />
<br />
= Miscellaneous improvements =<br />
<br />
* <b>Document templates</b> (listed in <i>File &gt; New</i>) are now first searched in the <code>templates</code> subdirectory of the user's profile directory (on Linux it's <code>~/.inkscape/templates</code>), then in the system-wide Inkscape templates directory. This allows you to add your own templates on top of the list of standard templates, as well as override the default template with your own one (the <code>default.svg</code> in the profile directory has priority over the system-wide one).<br />
<br />
* <b>Converting stroke to path</b> now correctly processes dashed strokes. For paths with markers, this command now creates a group containing the stroke converted to path and all its markers as independent objects (i.e. they are not markers anymore, but instead you can easily transform them or paint them any color, as a workaround for the "markers don't take the color of the stroke" bug).<br />
<br />
* When toggling one of the "transform with object" buttons (for stroke width, rounded rectangle corners, gradients, or patterns), a <b>message</b> is displayed in the statusbar explaining what has changed in the program's behavior. Hopefully this will reduce the number of complaints from users who had accidentally toggled one of these and were surprised by the result.<br />
<br />
* Whole thousands above 2000 in the rulers are now displayed as <b>2k, 3k, 4k</b> etc.<br />
<br />
* In the Document Preferences dialog, the new object style for each tool is now shown as a <b>style swatch</b> (displaying fill/stroke colors and opacity, stroke width, and master opacity), similar in design to the selected style indicator in the statusbar.<br />
<br />
* In the Grid Arrange dialog, row/column spacing can now be negative. <br />
<br />
* The installation default is now to scale the <b>rounded rectangle corners</b> with the rectangles themselves (the previous default mode, still available as an option, was to keep rounding radii unchanged when scaling rectangles). <br />
<br />
* Added a new <code>--export-area-canvas</code> command line parameter that causes the exported PNG to contain the full canvas. This option as well as <code>--export-area-drawing</code> and <code>--export-area</code> can now be used along with <code>--export-id</code> and <code>--export-id-only</code> for greater flexibility.<br />
<br />
* The <code>--query-*</code> command line parameters now return the true SVG bounding box of the object instead of the Inkscape coordinate system bbox (with inverted Y axis). The new behavior makes more sense for scripting use of Inkscape.<br />
<br />
* The <b>dpi</b> value in the Export dialog has had its range extended; now possible values are from 0.01 to 100000. <br />
<br />
* Individual <b>&lt;tspan&gt;s</b> within text objects (including line tspans) can now be selected via the XML editor to view their bounding boxes (though per SVG, you cannot transform them). Also, you can use the <code>--query-*</code> command line parameters to find out the bounding boxes of tspans from a script. (Individual strings within or between tspans are still not selectable, and they cannot have an ID for querying anyway.)<br />
<br />
* The placeholder image which is shown when a bitmap file was no longer accessible reads now "<b>Linked image not found</b>" instead of the confusing "Broken image".<br />
<br />
* <b>Cloning multiple selected objects</b> now works as expected (i.e. each selected object is cloned separately, similar to the Duplicate command). Previously you could only clone a single selected object. <br />
<br />
* The separate "license" and "contributors" dialogs have been merged into tabs on the About dialog. The about dialog now correctly sizes itself to fit the size of the splash SVG (while remaining resizable), and the rendering area is now cropped to the correct aspect ratio when the dialog is resized. The dialog also now displays the build information in the upper right corner.<br />
<br />
* [new cursors - scislac]<br />
<br />
* In the Transform dialog / Rotate tab, the icon was flipped horizontally to be in line with the direction of positive rotation; the change was applied to the default (now crispy) and legacy icon sets.<br />
<br />
* The <b>scale ratio lock button</b> on the Selector controls bar shows a closed lock when pressed and open lock otherwise (same as the layer lock in the statusbar).<br />
<br />
* The <b>Browse</b> button on Export dialog now opens the new file chooser, same as those used by Open and Save.<br />
<br />
* A new <b>RazorWire</b> path marker was added. By applying it as a mid-marker you can get a good approximation of a razor wire.<br />
<br />
= Miscellaneous bugfixes =<br />
<br />
* Reading a document with an <b>incorrect namespace URI</b> not only did not cause Inkscape to complain, but could also "pollute" Inkscape's internal namespace table, resulting in an "infection" of subsequently saved documents by the incorrect namespace. This is now fixed, but as a result, documents with incorrect namespace URIs will no longer load. You will have to edit them in a text editor to fix the namespaces. <br />
<br />
* With newer versions of GTK, <b>dragging with graphics tablet pen</b> did not work in some tools and contexts (in particular, in Node and Rectangle tools). This is fixed.<br />
<br />
* <b>Scaling of objects with stroke</b> in Selector used to cause undesired shifts of the scaled object, as well as scaling it in the dimension which was intended to remain untouched (e.g. slight change in width when you scale only height). All these problems are now fixed, both for interactive scaling by mouse and for numeric scaling via the Controls bar, and for both values of the "Scale stroke with objects" option. Among other things, this means that stroked objects no longer lose snapping on scale, and that the "Default scale origin" option in the Selector tool preferences finally works as designed. Caveat: There may still be problems if you scale a selection that contains objects with different stroke widths.<br />
<br />
* Scaling of stroke now works for objects that didn't specify stroke-width; before, they always ended up with the default 1px stroke.<br />
<br />
* The bounding box for text and flowed text objects did not include stroke width. This has been fixed.<br />
<br />
* Stroke miterlimit on text objects was misinterpreted in absolute units instead of multiplies of stroke width (resulting in miter joins rendered as bevel). <br />
<br />
* The unfinished path in Pen tool is now cancelled, not finalized, when you switch away from the Pen tool. Apart from being more intuitively correct, this also fixes a crash when you quit Inkscape with the unfinished path in Pen tool.<br />
<br />
* Fonts on Win32 now use the native font mapper, meaning that Inkscape's font list is the same as other Windows programs, and the (potentially) very long delay experienced when using fonts for the first time in each session is gone.<br />
<br />
* Setting dash pattern was broken for transformed objects, and copy/paste of style with dash pattern did not apply correctly to objects with transforms.<br />
<br />
* An error caused a complete extra screen redraw after each zoom operation. That is, after you press "+" in a complex drawing, Inkscape redraws, but for some time after that it remains still unresponsive because it does that second redraw (invisibly for you, i.e. nothing changes on the screen). This is fixed.<br />
<br />
* Gradient rendering was off by one pixel, which often resulted in visibly wrong gradient rendering for small objects or in zoom-out. <br />
<br />
* The SVG path parser could not handle fractional numbers with the initial dot. <br />
<br />
* Several pattern rendering bugs are fixed, discovered by working with SVG files exported from Adobe Illustrator.<br />
<br />
* Inkscape on Mac OS X will now notice fonts in your ~/Library/Fonts directory, in addition to the other standard places.<br />
<br />
* Inkscape couldn't be compiled with libxml versions <= 2.6.9, and we now bumped the requirements from 2.6.0 up to <b>libxml >= 2.6.11</b>, which is the earliest you can get officially, anyway.<br />
<br />
* Inkscape no longer crashes when presented with a defective inx file for extensions.<br />
<br />
* More document memory is now freed when documents are closed.<br />
<br />
* EPS output now correctly includes an %%EOF footer.<br />
<br />
* There was a regression in 0.43 that caused several minor, though annoying bugs; knots and handles remained highlighted after the mouse was released, and the rubberband selection rectangle stayed visible if the selection was ended over a node while in the node tool. This regression has been fixed. <br />
<br />
* The connector routing code would previously sometimes confuse objects between multiple documents resulting in strange routing behaviour. This has been fixed.<br />
<br />
* There existed a bug in 0.43's Inkboard code that allowed a malicious outsider to very easily disrupt an Inkboard session. This has been fixed.<br />
<br />
* There existed a bug in 0.43's Inkboard code that would cause deadlocks in the case that two users attempted to invite each other at the same time (see bug #[https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1352522&group_id=93438 1352522] for further details). This should be fixed, although the fix has not been widely tested.<br />
<br />
* There existed a bug in 0.43's Inkboard code that would cause session invitations to not appear on the invitee's screen. This was the result of a mistake in handling GDK modifier flags, and has been fixed.<br />
<br />
= Translations =<br />
<br />
* INX files (containing the UI of the external effects) now allow the user visible strings to be translated. This means that effect dialogs, file type selections, and extension names can all be translated by translators.<br />
<br />
= Internal =<br />
<br />
* The Document Properties Dialog code was completely gtkmmified, which lead to dramatic reduction of code size due to usage of widget objects. The used widget objects should be reusable by other dialogs, too, and the code is much more readable.<br />
<br />
* Work on optimizing includes in all cpp files started, using the purgeincludes tool specifically written for that purpose, and ended with 40% of include lines removed!<br />
<br />
= Known problems =<br />
=== Problems with libgc-6.7 ===<br />
* Inkscape will hang or even crash when linked with this (newest) version of the Boehm garbage collection library. Make sure you use libgc-6.5 or 6.6 until this is sorted out.<br />
<br />
=== Namespaces may need fixing ===<br />
<br />
* Previous versions of inkscape sometimes silently saved documents with <b>wrong namespace URIs</b>. This has been fixed, but such corrupted documents will no longer load successfully. Such documents may require their namespace declarations to be fixed by hand.<br />
<br />
=== Beware of defective themes on Linux ===<br />
<br />
* Inkscape and other Gtk programs can crash on any Linux, when the <b>gtk2-engines-smooth / libsmooth</b> package is installed. We have filed a bug against libsmooth which is now in gtk-engine and part of gnome. Removing the package resolves the problem, however, but it would be nice if you as affected user would inform the gtk-engines maintainers of the problem. See especially http://bugzilla.gnome.org/show_bug.cgi?id=312115 (thanks to Thomas Wood)<br />
* A similar crash happens if the <b>KDE Baghira</b> theme or the package <b>gtk_qt_engine</b> are installed. If you experience Inkscape crashes on KDE, please try to install a different theme from Baghira, or uninstall the gtk_qt_engine package from your system. Both problems also affect older versions of Inkscape.<br />
<br />
=== Make sure to remove menus.xml if you have it ===<br />
<br />
* If you were using certain CVS/SVN builds from autumn of 2005, you may have the file <code>menus.xml</code> hanging around in your profile directory (e.g. <code>~/.inkscape</code> on Linux). In that case you will see many errors about verbs that cannot be found, and some commands in menus will be disabled. Make sure to delete <code>menus.xml</code> to fix this.<br />
<br />
= Previous releases =<br />
<br />
* ReleaseNotes043 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes043)<br />
* ReleaseNotes042 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes042)<br />
* ReleaseNotes041 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes041)<br />
* ReleaseNotes040 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes040)<br />
* ReleaseNotes039 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes039)<br />
* ReleaseNotes038 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes038)<br />
* ReleaseNotes037 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes037)<br />
* ReleaseNotes036 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes036)<br />
* ReleaseNotes035 (http://wiki.inkscape.org/wiki/index.php/ReleaseNotes035)</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=TestPage&diff=6599TestPage2006-06-03T12:55:21Z<p>Xaviconde: /* Templates */</p>
<hr />
<div>= Introduction =<br />
== Community based, user oriented ==<br />
The translations of the various documents focusing on Inkscape rely on the work of volunteers.<br />
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.<br />
It is very important not to forget that Inkscape is an open source, community based and user oriented software, which implies that software developpers/contributors are generaly users. It also implies that the translation efforts are also user oriented, with a strong focus on interface, user documentation and website.<br />
<br />
== Guidelines/workflow ==<br />
<br />
# '''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 start 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].<br />
# '''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.<br />
# '''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.<br />
# '''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 you are submitting doesn't have syntax errors that would break the building process.<br />
# '''Send a mail on the translator mailing list'''. Your contribution will be reviewed/commited as soon as possible.<br />
<br />
== Best practices ==<br />
<br />
Best case for a good translation : translate from English to your mother tongue.<br />
<br />
Test the behavior of the interface before starting translation<br />
<br />
= Translatable content =<br />
<br />
Inkscape's translation effort covers many areas, from aplication UI itself to web pages and tutorials. This is a summary of all those areas, ordered by priority.<br />
<br />
These tasks, rather than being for hackers only, can be achieved by most software enthusiasts, whether they have a technological background or just plain users. The main requirement is the wish to provide support for Inkscape on your language: the technology required for do that has been developed in a simple approach, and it involves mainly text files and applications used to verify its syntax. Supporting applications exists to make this tasks even easier.<br />
<br />
== User interface ==<br />
<br />
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.<br />
<br />
See section [[#Interface_Translation]] for information on PO files.<br />
<br />
== Tutorials ==<br />
<br />
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.<br />
<br />
See section [[#Tutorial_Translation]] for information on translating tutorials.<br />
<br />
== Windows installer ==<br />
<br />
High value for users, even if the installation process of Inkscape is quite simple, translating the Windows installer helps a lot potential users feeling good with Inkscape.<br />
<br />
== Templates ==<br />
<br />
The default template of Inkscape document can be localized to make the localization consistent. Localized can be size of the default document and also the name of default layer.<br />
* To translate default template, modify the default.svg file and save it as default.xx.svg where "xx" is ISO code of your language. The file can be found in ''/usr/share/inkscape/templates/'' directory on Linux, or ''C:\Program Files\Inkscape\share\templates\'' directory on MS Windows(tm). Also you can get it from [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape/trunk/share/templates/ SVN repository]. <br />
* You need to modify your PO translation as well to use your localized default template. Look up for a msgid "default.svg" on the PO file and translate it accordingly to the file name of the localized template.<br />
* To test it, save it to the proper location and restart Inkscape. Default document should be now based on your localized template. (This is valid if your system is properly set to your locales).<br />
* Upload default.xx.svg to the patch tracker.<br />
<br />
== Man pages ==<br />
A reminder for the moment. Will fill it later (matiphas)<br />
<br />
<br />
== Release notes ==<br />
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape<br />
<br />
- give a general overview of the possibilities of the software to potential users<br />
<br />
- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)<br />
<br />
== User manual ==<br />
Just a reminder for the moment. Will first take a look at user-manual process, get some info from cedric and then fill this section (matiphas).<br />
<br />
== News displayed on Inkscape web site ==<br />
<br />
== Web pages ==<br />
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English. <br />
<br />
Translation efforts should be first oriented on user documentation.<br />
<br />
See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.<br />
<br />
== Others ==<br />
Text files found in the inkscape directory<br />
...<br />
<br />
= Interface Translation =<br />
<br />
== Introduction to PO file format ==<br />
<br />
If you've never translated a PO file before, you will find its syntax very simple. The PO format is a really simple format, which probably at least partly explains its success and widespread use. The format is basically a hash list consisting of msgid and msgstr pairs, with the msgid being the original English string and key, and the msgstr being the translated value of it. Below is an example of a message.<br />
<br />
&#35;: gedit/dialogs/gedit-plugin-program-location-dialog.c:78<br />
&#35;: gedit/dialogs/program-location-dialog.glade2.h:2<br />
msgid "Set program location..."<br />
msgstr "Ställ in programplats..."<br />
<br />
In addition to the msgid and msgstr parts, a message usually also has lines starting with #: that tells what source files and what lines the string used as msgid was extracted from. These lines have no syntactic value. They are only there as a help for translators and developers to know where a message came from. <br />
<br />
A message in a PO file can be in one of essentially three different states. The message can be translated, fuzzy, or untranslated. A message counts as translated as soon as the msgstr part of it is non-empty. In a similar manner, an untranslated message is one where the msgstr is empty. The fuzzy state is special and essentially means that there is a translation in the msgstr part, but that this translation is most likely not entirely correct, and that it thus needs manual attention by a translator. A message can become fuzzy in one of two ways:<br />
<br />
* The original string that the msgid represents was changed in the source code. A typo in the string may have been fixed or the string altered in some other way. The translator needs to check that the msgstr is still valid and make changes if necessary.<br />
* A new string has been added to the source, and the string is very similar, but not identical, to the msgid of an already existing, translated message. Then the msgstr of that message will be automatically reused for the new message, but the new message will also at the same time be marked fuzzy so that the translator knows there is some difference that he or she needs to adapt the translation to match.<br />
<br />
There is always one special message in each valid PO file: the PO file header. It is encoded with the msgid for the empty string ("") as the key, and the actual header values are in the msgstr part. This unfortunately means that if you mark an empty string for translation, you will get the entire PO file header back as the "translation". In almost all cases this is probably not what you want. Hence, do not mark empty strings for translation.<br />
<br />
== Get the PO file for your language ==<br />
<br />
Download the .po file for your language from here:<br />
<br />
http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/<br />
<br />
If a .po file for your language does not yet exist, then you will have to get an empty template file to start a new translation. The most straightforward way to obtain the inkscape.pot template is from the SVN repository above. Alternatively, you can checkout the full SVN project repository and generate the project template. Information on how to get the source tree can be found [http://inkscape.org/svn.php here]. Then, you have to follow some steps in order to generate the template:<br />
<br />
1. "./autogen.sh"<br />
2. "./configure"<br />
3. enter the "po" directory: "cd po"<br />
4. generate the current PO template: "intltool-update --pot"<br />
<br />
To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough), <br />
<br />
1. update your local copy of Inkscape in the usual way: "svn update"<br />
2. merge your existing translations into the new POT file (inkscape.pot):<br />
<br />
"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"<br />
<br />
If you want to update ALL .po files in po/, cd there and run:<br />
<br />
make update-po<br />
<br />
Now that you have an empty PO template, you can start translating the messages. <br />
<br />
== Tools for translators ==<br />
<br />
You can edit PO files from any plain text editor, since they are simple text files. However, many useful tools have been developed to provide a simple experience translating PO files.<br />
<br />
* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)<br />
* kbabel (http://i18n.kde.org/tools/kbabel/)<br />
* gtranslator (http://gtranslator.sourceforge.net/)<br />
* poEdit (http://poedit.sourceforge.net/)<br />
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.<br />
<br />
And last but not least, [http://www.gnu.org/software/gettext/manual/ gettext] utils, which are installed on every linux distribution. You can see a complete reference too from installed info pages by running the command:<br />
<br />
info gettext<br />
<br />
== A few important things to remember ==<br />
<br />
* Some strings that can be ambiguous or having several meanings according to different contexts may have a context prefix : "Context|Amibiguous string". In this case, simply translate "Ambiguous string", the "Context|" string is just a not to translate indication.<br />
* After translating a fuzzy string (one that is marked with a ", fuzzy" comment), please remove its "fuzzy" tag -- otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated. KBabel can do this automatically (see KBabel settings).<br />
* Before publishing your work (after you have finished updating the PO file), please update the "PO-Revision-Date" and "Last-Translator" fields in the PO file header. KBabel can do this automatically.<br />
<br />
== Review ==<br />
<br />
This is the start of a list of places to get translation reviews done. So far:<br />
http://www.linux.it/tp/<br />
<br />
== Verification ==<br />
<br />
Before submitting your file in the patch tracker, please make sure it is valid:<br />
* Make sure the file is encoded in UTF-8 <br />
* Make sure it is a valid po file and obtain some statistics about it: simply run "msgfmt --statistics -cv translationFile.po" from a command window<br />
* Make sure it is correctly formatted: run "check-markup translationFile.po" from a command window and verify it doesn't output any error message. "check-markup" perl script can be found in the /po directory of Inkscape svn trunk<br />
<br />
== Locale Testing ==<br />
<br />
Before reporting that a locale doesn't work in Inkscape, you need to make sure that your system has that locale correctly set up. To do this, you need to generally find a way to run "locale-gen". (Under Debian/Ubuntu this is via "dpkg-reconfigure locales".) If you set both the LANG and LANGUAGE variables and check a regular tool, you should see the correct language for both the libc error (first line) and the tool error (second line):<br />
<br />
LANG=es_MX LANGUAGE=es_MX ls -z<br />
ls: opci&oacute;n inv&aacute;lida -- z<br />
Pruebe `ls --help' para m&aacute;s informaci&oacute;n.<br />
<br />
If it reports the regular C messages, your locale has not been correctly configured, and you'll need to find the right way to run "locale-gen" for your distribution:<br />
<br />
LANG=es_ES LANGUAGE=es_MX ls -z<br />
ls: invalid option -- z<br />
Try `ls --help' for more information.<br />
<br />
== Submit finished work ==<br />
<br />
Upload your work via the [[SourceForge]] patch tracker:<br />
<br />
http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308<br />
<br />
(Check the Upload checkbox and add your file or patch.)<br />
<br />
(Don't forget to compress your file before uploading it, as sourcefoge tracker doesn't accept large files.)<br />
<br />
Additionally, you may send a message to Inskcape's translators mailing list.<br />
<br />
== Programmers ==<br />
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.<br />
<br />
= Tutorial Translation =<br />
<br />
Inkscape tutorial sources are in [[DocBook]] format, with illustrations in SVG. If you want to translate one or more tutorials, first download the [[DocBook]] source here:<br />
<br />
http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/<br />
<br />
Each tutorial is in its own subdirectory. You need the *.xml file, for example basic/tutorial-basic.xml. Get it and simply replace all English text in it with the text in your language, preserving all XML markup. See README at that location for some notes on markup.<br />
<br />
* If there's already such a file in SVN, you can edit it instead :) If there's no xml file at the above location but there's a translation of this tutorial in SVG format (in share/tutorials in Inkscape distribution), you'll need to convert it to [[DocBook]] (and probably update). Conversion can be done simply by: select the text blocks of an SVG tutorial in Inkscape, Ctrl+C, and Ctrl+V in your text editor, then add the markup.<br />
<br />
* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish. <br />
<br />
* Do not use symbolic entities like &amp;aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &amp;#225; or simply write your text in UTF-8.<br />
<br />
* Most illustrations don't need translations, so you leave the references to them from English XML intact. If however an illustration has some text that you want to translate, open the illustration file in Inkscape (e.g. basic/basic-f12.svg), edit it as needed, and save under a different name (e.g. basic/basic-f12-es.svg). Then change the filename reference in the XML source appropriately.<br />
<br />
* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.<br />
<br />
* Send the file to Joshua Andler <scislac at users dot sf dot net>, and he'll convert it to SVG and HTML and upload it to SVN and the web site.<br />
<br />
* If after that you want to make any changes, download the file from the above location again, because it may have changed compared to the one you have.<br />
<br />
==Tools==<br />
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html<br />
* Transolution - http://transolution.python-hosting.com/<br />
<br />
===Transforming XML into PO files===<br />
One can also use xml2po to get PO files out of the XML sources, and also transform the PO files back to XML. After you have a PO file, follow the instructions for editing those files below.<br />
<br />
xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).<br />
<br />
Here are some command lines that were used to translate a German tutorial (the de-locale), please adapt accordingly until we nicely integrate this into our Makefiles.<br />
<br />
<pre><br />
## use this at the very beginning, when there is no translation at all:<br />
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml<br />
<br />
## use this when there is a *.de.xml, but you want a de.po:<br />
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml<br />
<br />
## xml2po is not happy when this directory doesn't exist:<br />
mkdir .tmp.basic<br />
<br />
## use this when the tutorial-basic.xml has been updated and you<br />
## want the new stuff in your de.po:<br />
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml<br />
<br />
## use this to create a tutorial-basic.de.xml from your de.po (ScislaC<br />
## will use this file to create the final tutorial SVG file)<br />
## WARNING: Unfortunately, this doesn't put localized screenshot <br />
## file names into the xml file!<br />
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml<br />
<br />
</pre><br />
<br />
= Keyboard and mouse translation =<br />
<br />
= Wiki and web site =<br />
== Translation of web site ==<br />
# There are two ways of getting files that you need to translate website:<br />
## Checkout actual svn version of inkscape_web module ([http://inkscape.org/svn.php Working with SVN]). To checkout the inkscape_web module use command: <pre>svn co https://svn.sourceforge.net/svnroot/inkscape/inkscape_web/trunk inkscape_web</pre> You need subversion client to do this.<br />
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.<br />
## Files you probably want to translate are:<br />
##* includes/localized.inc (file contains string to translate menu)<br />
##* index-en.inc (main page of inkscape.org)<br />
##* discussion-en.inc<br />
##* download-en.inc<br />
##* mailing-lists-en.inc<br />
##* report-bugs-en.inc<br />
##* submit2webmaster-en.inc<br />
##* submit2webmaster-en-form.inc<br />
##* svn-en.inc<br />
# Copy these files and replace "en" string in their name according to the ISO code of your language ("de" for german, "fr" for french, etc...).<br />
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.<br />
# If you have the file translated and really want to submit it, read it once more and correct errors ;)<br />
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.<br />
# Announce the translated file in the patch tracker in inkscape-translator(and optionally in inkscape-devel) mailing list. Persons responsible for updates of website will reply to you and/or submit the new "patch" directly.<br />
If the translation of website is new, the process of making new translation available can take a bit longer because of a need to create corresponding flag and check consistency of the translation.<br />
=== Translating news and status ===<br />
News and status information are available for translation too. News items are stored in the /news directory of inkscape_module in separate subdirectories named by language version. The structure of directory with news is:<br />
<pre><br />
/news<br />
- en<br />
\- 2005<br />
- 2006<br />
\- 04<br />
- 05<br />
\- 001.inc<br />
- 002.inc<br />
...<br />
- de<br />
- fr<br />
</pre><br />
To translate news into your language download/checkout 00x.inc file from "en" directory, translate and submit to the directory of your language(file has to be in UTF-8 encoding) or submit to the patch tracker and announce on the inkscape-translator list.<br />
If you want to translate status information, the structure of directories is like in the case of news, only the name of directory is different.<br />
<br />
= Status =<br />
See this [[http://wiki.inkscape.org/wiki/index.php/TranslationStatus dedicated page]]</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=TestPage&diff=6591TestPage2006-06-02T13:33:10Z<p>Xaviconde: /* Interface Translation */</p>
<hr />
<div>= Introduction =<br />
== Community based, user oriented ==<br />
The translations of the various documents focusing on Inkscape rely on the work of volunteers.<br />
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.<br />
It is very important not to forget that Inkscape is an open source, community based and user oriented software, which implies that software developpers/contributors are generaly users. It also implies that the translation efforts are also user oriented, with a strong focus on interface, user documentation and website.<br />
<br />
== Guidelines/workflow ==<br />
<br />
# '''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 start 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].<br />
# '''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.<br />
# '''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.<br />
# '''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 you are submitting doesn't have syntax errors that would break the building process.<br />
# '''Send a mail on the translator mailing list'''. Your contribution will be reviewed/commited as soon as possible.<br />
<br />
== Best practices ==<br />
<br />
Best case for a good translation : translate from English to your mother tongue.<br />
<br />
Test the behavior of the interface before starting translation<br />
<br />
= Translatable content =<br />
<br />
Inkscape's translation effort covers many areas, from aplication UI itself to web pages and tutorials. This is a summary of all those areas, ordered by priority.<br />
<br />
These tasks, rather than being for hackers only, can be achieved by most software enthusiasts, whether they have a technological background or just plain users. The main requirement is the wish to provide support for Inkscape on your language: the technology required for do that has been developed in a simple approach, and it involves mainly text files and applications used to verify its syntax. Supporting applications exists to make this tasks even easier.<br />
<br />
== User interface ==<br />
<br />
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.<br />
<br />
See section [[#Interface_Translation]] for information on PO files.<br />
<br />
== Tutorials ==<br />
<br />
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.<br />
<br />
See section [[#Tutorial_Translation]] for information on translating tutorials.<br />
<br />
== Windows installer ==<br />
<br />
High value for users, even if the installation process of Inkscape is quite simple, translating the Windows installer helps a lot potential users feeling good with Inkscape.<br />
<br />
== Templates ==<br />
The default template of Inkscape document can be localized to make the localization consistent. Localized can be size of the default document and also the name of default layer.<br />
* To translate default template, modify the default.svg file and save it as default.xx.svg where "xx" is ISO code of your language. The file can be found in ''/usr/share/inkscape/templates/'' directory on Linux, or ''C:\Program Files\Inkscape\share\templates\'' directory on MS Windows(tm).<br />
* To test it save it to the proper location and restart Inkscape. Default document should be now based on your localized template. (This is valid if your system is properly set to your locales)<br />
* Upload default.xx.svg to the patch tracker.<br />
<br />
== Man pages ==<br />
A reminder for the moment. Will fill it later (matiphas)<br />
<br />
<br />
== Release notes ==<br />
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape<br />
<br />
- give a general overview of the possibilities of the software to potential users<br />
<br />
- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)<br />
<br />
== User manual ==<br />
Just a reminder for the moment. Will first take a look at user-manual process, get some info from cedric and then fill this section (matiphas).<br />
<br />
== News displayed on Inkscape web site ==<br />
<br />
== Web pages ==<br />
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English. <br />
<br />
Translation efforts should be first oriented on user documentation.<br />
<br />
See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.<br />
<br />
== Others ==<br />
Text files found in the inkscape directory<br />
...<br />
<br />
= Interface Translation =<br />
<br />
== Introduction to PO file format ==<br />
<br />
If you've never translated a PO file before, you will find its syntax very simple. The PO format is a really simple format, which probably at least partly explains its success and widespread use. The format is basically a hash list consisting of msgid and msgstr pairs, with the msgid being the original English string and key, and the msgstr being the translated value of it. Below is an example of a message.<br />
<br />
&#35;: gedit/dialogs/gedit-plugin-program-location-dialog.c:78<br />
&#35;: gedit/dialogs/program-location-dialog.glade2.h:2<br />
msgid "Set program location..."<br />
msgstr "Ställ in programplats..."<br />
<br />
In addition to the msgid and msgstr parts, a message usually also has lines starting with #: that tells what source files and what lines the string used as msgid was extracted from. These lines have no syntactic value. They are only there as a help for translators and developers to know where a message came from. <br />
<br />
A message in a PO file can be in one of essentially three different states. The message can be translated, fuzzy, or untranslated. A message counts as translated as soon as the msgstr part of it is non-empty. In a similar manner, an untranslated message is one where the msgstr is empty. The fuzzy state is special and essentially means that there is a translation in the msgstr part, but that this translation is most likely not entirely correct, and that it thus needs manual attention by a translator. A message can become fuzzy in one of two ways:<br />
<br />
* The original string that the msgid represents was changed in the source code. A typo in the string may have been fixed or the string altered in some other way. The translator needs to check that the msgstr is still valid and make changes if necessary.<br />
* A new string has been added to the source, and the string is very similar, but not identical, to the msgid of an already existing, translated message. Then the msgstr of that message will be automatically reused for the new message, but the new message will also at the same time be marked fuzzy so that the translator knows there is some difference that he or she needs to adapt the translation to match.<br />
<br />
There is always one special message in each valid PO file: the PO file header. It is encoded with the msgid for the empty string ("") as the key, and the actual header values are in the msgstr part. This unfortunately means that if you mark an empty string for translation, you will get the entire PO file header back as the "translation". In almost all cases this is probably not what you want. Hence, do not mark empty strings for translation.<br />
<br />
== Get the PO file for your language ==<br />
<br />
Download the .po file for your language from here:<br />
<br />
http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/<br />
<br />
If a .po file for your language does not yet exist, then you will have to get an empty template file to start a new translation. The most straightforward way to obtain the inkscape.pot template is from the SVN repository above. Alternatively, you can checkout the full SVN project repository and generate the project template. Information on how to get the source tree can be found [http://inkscape.org/svn.php here]. Then, you have to follow some steps in order to generate the template:<br />
<br />
1. "./autogen.sh"<br />
2. "./configure"<br />
3. enter the "po" directory: "cd po"<br />
4. generate the current PO template: "intltool-update --pot"<br />
<br />
To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough), <br />
<br />
1. update your local copy of Inkscape in the usual way: "svn update"<br />
2. merge your existing translations into the new POT file (inkscape.pot):<br />
<br />
"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"<br />
<br />
If you want to update ALL .po files in po/, cd there and run:<br />
<br />
make update-po<br />
<br />
Now that you have an empty PO template, you can start translating the messages. <br />
<br />
== Tools for translators ==<br />
<br />
You can edit PO files from any plain text editor, since they are simple text files. However, many useful tools have been developed to provide a simple experience translating PO files.<br />
<br />
* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)<br />
* kbabel (http://i18n.kde.org/tools/kbabel/)<br />
* gtranslator (http://gtranslator.sourceforge.net/)<br />
* poEdit (http://poedit.sourceforge.net/)<br />
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.<br />
<br />
And last but not least, [http://www.gnu.org/software/gettext/manual/ gettext] utils, which are installed on every linux distribution. You can see a complete reference too from installed info pages by running the command:<br />
<br />
info gettext<br />
<br />
== A few important things to remember ==<br />
<br />
* Some strings that can be ambiguous or having several meanings according to different contexts may have a context prefix : "Context|Amibiguous string". In this case, simply translate "Ambiguous string", the "Context|" string is just a not to translate indication.<br />
* After translating a fuzzy string (one that is marked with a ", fuzzy" comment), please remove its "fuzzy" tag -- otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated. KBabel can do this automatically (see KBabel settings).<br />
* Before publishing your work (after you have finished updating the PO file), please update the "PO-Revision-Date" and "Last-Translator" fields in the PO file header. KBabel can do this automatically.<br />
<br />
== Review ==<br />
<br />
This is the start of a list of places to get translation reviews done. So far:<br />
http://www.linux.it/tp/<br />
<br />
== Verification ==<br />
<br />
Before submitting your file in the patch tracker, please make sure it is valid:<br />
* Make sure the file is encoded in UTF-8 <br />
* Make sure it is a valid po file and obtain some statistics about it: simply run "msgfmt --statistics -cv translationFile.po" from a command window<br />
* Make sure it is correctly formatted: run "check-markup translationFile.po" from a command window and verify it doesn't output any error message. "check-markup" perl script can be found in the /po directory of Inkscape svn trunk<br />
<br />
== Locale Testing ==<br />
<br />
Before reporting that a locale doesn't work in Inkscape, you need to make sure that your system has that locale correctly set up. To do this, you need to generally find a way to run "locale-gen". (Under Debian/Ubuntu this is via "dpkg-reconfigure locales".) If you set both the LANG and LANGUAGE variables and check a regular tool, you should see the correct language for both the libc error (first line) and the tool error (second line):<br />
<br />
LANG=es_MX LANGUAGE=es_MX ls -z<br />
ls: opci&oacute;n inv&aacute;lida -- z<br />
Pruebe `ls --help' para m&aacute;s informaci&oacute;n.<br />
<br />
If it reports the regular C messages, your locale has not been correctly configured, and you'll need to find the right way to run "locale-gen" for your distribution:<br />
<br />
LANG=es_ES LANGUAGE=es_MX ls -z<br />
ls: invalid option -- z<br />
Try `ls --help' for more information.<br />
<br />
== Submit finished work ==<br />
<br />
Upload your work via the [[SourceForge]] patch tracker:<br />
<br />
http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308<br />
<br />
(Check the Upload checkbox and add your file or patch.)<br />
<br />
(Don't forget to compress your file before uploading it, as sourcefoge tracker doesn't accept large files.)<br />
<br />
Additionally, you may send a message to Inskcape's translators mailing list.<br />
<br />
== Programmers ==<br />
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.<br />
<br />
= Tutorial Translation =<br />
<br />
Inkscape tutorial sources are in [[DocBook]] format, with illustrations in SVG. If you want to translate one or more tutorials, first download the [[DocBook]] source here:<br />
<br />
http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/<br />
<br />
Each tutorial is in its own subdirectory. You need the *.xml file, for example basic/tutorial-basic.xml. Get it and simply replace all English text in it with the text in your language, preserving all XML markup. See README at that location for some notes on markup.<br />
<br />
* If there's already such a file in SVN, you can edit it instead :) If there's no xml file at the above location but there's a translation of this tutorial in SVG format (in share/tutorials in Inkscape distribution), you'll need to convert it to [[DocBook]] (and probably update). Conversion can be done simply by: select the text blocks of an SVG tutorial in Inkscape, Ctrl+C, and Ctrl+V in your text editor, then add the markup.<br />
<br />
* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish. <br />
<br />
* Do not use symbolic entities like &amp;aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &amp;#225; or simply write your text in UTF-8.<br />
<br />
* Most illustrations don't need translations, so you leave the references to them from English XML intact. If however an illustration has some text that you want to translate, open the illustration file in Inkscape (e.g. basic/basic-f12.svg), edit it as needed, and save under a different name (e.g. basic/basic-f12-es.svg). Then change the filename reference in the XML source appropriately.<br />
<br />
* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.<br />
<br />
* Send the file to Joshua Andler <scislac at users dot sf dot net>, and he'll convert it to SVG and HTML and upload it to SVN and the web site.<br />
<br />
* If after that you want to make any changes, download the file from the above location again, because it may have changed compared to the one you have.<br />
<br />
==Tools==<br />
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html<br />
* Transolution - http://transolution.python-hosting.com/<br />
<br />
===Transforming XML into PO files===<br />
One can also use xml2po to get PO files out of the XML sources, and also transform the PO files back to XML. After you have a PO file, follow the instructions for editing those files below.<br />
<br />
xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).<br />
<br />
Here are some command lines that were used to translate a German tutorial (the de-locale), please adapt accordingly until we nicely integrate this into our Makefiles.<br />
<br />
<pre><br />
## use this at the very beginning, when there is no translation at all:<br />
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml<br />
<br />
## use this when there is a *.de.xml, but you want a de.po:<br />
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml<br />
<br />
## xml2po is not happy when this directory doesn't exist:<br />
mkdir .tmp.basic<br />
<br />
## use this when the tutorial-basic.xml has been updated and you<br />
## want the new stuff in your de.po:<br />
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml<br />
<br />
## use this to create a tutorial-basic.de.xml from your de.po (ScislaC<br />
## will use this file to create the final tutorial SVG file)<br />
## WARNING: Unfortunately, this doesn't put localized screenshot <br />
## file names into the xml file!<br />
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml<br />
<br />
</pre><br />
<br />
= Keyboard and mouse translation =<br />
<br />
= Wiki and web site =<br />
== Translation of web site ==<br />
# There are two ways of getting files that you need to translate website:<br />
## Checkout actual svn version of inkscape_web module ([http://inkscape.org/svn.php Working with SVN]). To checkout the inkscape_web module use command: <pre>svn co https://svn.sourceforge.net/svnroot/inkscape/inkscape_web/trunk inkscape_web</pre> You need subversion client to do this.<br />
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.<br />
## Files you probably want to translate are:<br />
##* includes/localized.inc (file contains string to translate menu)<br />
##* index-en.inc (main page of inkscape.org)<br />
##* discussion-en.inc<br />
##* download-en.inc<br />
##* mailing-lists-en.inc<br />
##* report-bugs-en.inc<br />
##* submit2webmaster-en.inc<br />
##* submit2webmaster-en-form.inc<br />
##* svn-en.inc<br />
# Copy these files and replace "en" string in their name according to the ISO code of your language ("de" for german, "fr" for french, etc...).<br />
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.<br />
# If you have the file translated and really want to submit it, read it once more and correct errors ;)<br />
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.<br />
# Announce the translated file in the patch tracker in inkscape-translator(and optionally in inkscape-devel) mailing list. Persons responsible for updates of website will reply to you and/or submit the new "patch" directly.<br />
If the translation of website is new, the process of making new translation available can take a bit longer because of a need to create corresponding flag and check consistency of the translation.<br />
=== Translating news and status ===<br />
News and status information are available for translation too. News items are stored in the /news directory of inkscape_module in separate subdirectories named by language version. The structure of directory with news is:<br />
<pre><br />
/news<br />
- en<br />
\- 2005<br />
- 2006<br />
\- 04<br />
- 05<br />
\- 001.inc<br />
- 002.inc<br />
...<br />
- de<br />
- fr<br />
</pre><br />
To translate news into your language download/checkout 00x.inc file from "en" directory, translate and submit to the directory of your language(file has to be in UTF-8 encoding) or submit to the patch tracker and announce on the inkscape-translator list.<br />
If you want to translate status information, the structure of directories is like in the case of news, only the name of directory is different.<br />
<br />
= Status =<br />
<br />
== Interface translation (po files) ==<br />
<br />
The names and e-mail addresses of contributors and last translator can be found in the header of the po file (simply open it with your favorite text editor)<br />
<br />
Total number of PO files: 38<br />
Total number of strings to translate: 2142<br />
<br />
<br />
'''Amharic''': am.po<br />
<br />
translated: 77 ( '''3%''')<br />
<br />
fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)<br />
<br />
Date of last update: 2003-02-01<br />
<br />
<br />
'''Azerbaijani/Turkic''': az.po<br />
<br />
translated: 63 ( '''2%''')<br />
<br />
fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)<br />
<br />
Date of last update: 2001-12-04<br />
<br />
<br />
'''Belarusian''': be.po<br />
<br />
translated: 158 ( '''7%''')<br />
<br />
fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)<br />
<br />
Date of last update: 2003-07-20<br />
<br />
<br />
'''Catalan''': ca.po<br />
<br />
translated: 2039 ( '''95%''')<br />
<br />
fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)<br />
<br />
Date of last update: 2006-05-08<br />
<br />
<br />
'''Czech''': cs.po<br />
<br />
translated: 2096 ( '''97%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)<br />
<br />
Date of last update: 2006-05-22<br />
<br />
<br />
'''Danish''': da.po<br />
<br />
translated: 100 ( '''4%''')<br />
<br />
fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)<br />
<br />
Date of last update: 2002-01-15<br />
<br />
<br />
'''German''': de.po<br />
<br />
translated: 2116 ( '''98%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)<br />
<br />
Date of last update: 2006-05-23<br />
<br />
<br />
'''Greek''': el.po<br />
<br />
translated: 44 ( '''2%''')<br />
<br />
fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)<br />
<br />
Date of last update: 2001-12-28<br />
<br />
<br />
'''Spanish''': es.po<br />
<br />
translated: 2125 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)<br />
<br />
Date of last update: 2006-05-25<br />
<br />
<br />
'''Spanish/Mexico''': es_MX.po<br />
<br />
translated: 337 ( '''15%''')<br />
<br />
fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)<br />
<br />
Date of last update: 2004-04-05<br />
<br />
<br />
'''Estonian''': et.po<br />
<br />
translated: 9 ( '''0%''')<br />
<br />
fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)<br />
<br />
Date of last update: 2000-04-08<br />
<br />
<br />
'''Basque''': eu.po<br />
<br />
translated: 1548 ( '''72%''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)<br />
<br />
Date of last update: 2006-03-16<br />
<br />
<br />
'''French''': fr.po<br />
<br />
translated: 2126 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)<br />
<br />
Date of last update: 2006-05-27<br />
<br />
<br />
'''Irish''': ga.po<br />
<br />
translated: 14 ( '''0%''')<br />
<br />
fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)<br />
<br />
Date of last update: 2000-08-24<br />
<br />
<br />
'''Galician''': gl.po<br />
<br />
translated: 82 ( '''3%''')<br />
<br />
fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)<br />
<br />
Date of last update: 2001-11-10<br />
<br />
<br />
'''Hungarian''': hu.po<br />
<br />
translated: 1564 ( '''73%''')<br />
<br />
fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)<br />
<br />
Date of last update: 2006-05-29<br />
<br />
<br />
'''Italian''': it.po<br />
<br />
translated: 2008 ( '''93%''')<br />
<br />
fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)<br />
<br />
Date of last update: 2006-05-15<br />
<br />
<br />
'''Japanese''': ja.po<br />
<br />
translated: 1294 ( '''60%''')<br />
<br />
fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)<br />
<br />
Date of last update: 2005-11-16<br />
<br />
<br />
'''Korean''': ko.po<br />
<br />
translated: 180 ( '''8%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)<br />
<br />
Date of last update: 2006-04-10<br />
<br />
<br />
'''Lithuanian''': lt.po<br />
<br />
translated: 1774 ( '''82%''')<br />
<br />
fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)<br />
<br />
Date of last update: 2006-05-02<br />
<br />
<br />
'''mk.po'''<br />
<br />
translated: 0 ( '''0%''')<br />
<br />
fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)<br />
<br />
Date of last update: 2003-06-15<br />
<br />
<br />
'''Norwegian/bokmål dialect''': nb.po<br />
<br />
translated: 144 ( '''6%''')<br />
<br />
fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)<br />
<br />
Date of last update: 2003-01-25<br />
<br />
<br />
'''Dutch: nl.po'''<br />
<br />
translated: 1484 ( '''69%''')<br />
<br />
fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)<br />
<br />
Date of last update: 2005-11-07<br />
<br />
<br />
'''Norwegian/Nynorsk''': nn.po<br />
<br />
translated: 1376 ( '''64%''')<br />
<br />
fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)<br />
<br />
Date of last update: 2005-07-14<br />
<br />
<br />
'''Punjabi''': pa.po<br />
<br />
translated: 912 ( '''42%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)<br />
<br />
Date of last update: 2005-09-11<br />
<br />
<br />
'''Polish''': pl.po<br />
<br />
translated: 1503 ( '''70%''')<br />
<br />
fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)<br />
<br />
Date of last update: 2005-10-29<br />
<br />
<br />
'''Portuguese''': pt.po<br />
<br />
translated: 183 ( '''8%''')<br />
<br />
fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)<br />
<br />
Date of last update: 2003-07-28<br />
<br />
<br />
'''Portuguese/Brazillian''': pt_BR.po<br />
<br />
translated: 1546 ( '''72%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)<br />
<br />
Date of last update: 2006-04-27<br />
<br />
<br />
'''Russian''': ru.po<br />
<br />
translated: 1542 ( '''71%''')<br />
<br />
fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)<br />
<br />
Date of last update: 2005-11-08<br />
<br />
<br />
'''Slovak''': sk.po<br />
<br />
translated: 845 ( '''39%''')<br />
<br />
fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)<br />
<br />
Date of last update: 2005-02-13<br />
<br />
<br />
'''Slovenian''': sl.po<br />
<br />
translated: 2055 ( '''95%''')<br />
<br />
fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)<br />
<br />
Date of last update: 2006-05-12<br />
<br />
<br />
'''Serbian''': sr.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Serbian/Latine''': sr@Latn.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Swedish''': sv.po<br />
<br />
translated: 410 ( '''19%''')<br />
<br />
fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)<br />
<br />
Date of last update: 2005-10-08<br />
<br />
<br />
'''Turkish''': tr.po<br />
<br />
translated: 907 ( '''42%''')<br />
<br />
fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)<br />
<br />
Date of last update: 2005-11-26<br />
<br />
<br />
'''Ukrainian''': uk.po<br />
<br />
translated: 1518 ( '''70%''')<br />
<br />
fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)<br />
<br />
Date of last update: 2005-10-21<br />
<br />
<br />
'''Chinese/Simplified''': zh_CN.po<br />
<br />
translated: 2134 ( '''99%''')<br />
<br />
<br />
fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)<br />
<br />
Date of last update: 2006-05-28<br />
<br />
<br />
'''Chinese/Traditional''': zh_TW.po<br />
<br />
translated: 1550 ( '''72 %''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)<br />
<br />
Date of last update: 2006-03-24<br />
<br />
== Tutorials ==<br />
<br />
* Basic: ca, de, en, es, fr, ja, nn, ru, sl<br />
* Shapes: ca, en, es, fr, ja, sl<br />
* Advanced: ca, en, es, fr, ja, sl<br />
* Tracing: ca, de, en, es, fr, sl<br />
* Calligraphy: ca, en, es, fr, sl<br />
* Elements of design: en, es, fr, sl<br />
* Tips and tricks: de, en, es, fr, sl<br />
<br />
<br />
== Keys (shortcuts) ==<br />
Already available in svn :<br />
* en<br />
* fr<br />
* sl<br />
<br />
<br />
== Windows installer ==<br />
<br />
Already available in svn :<br />
* czech.nsh<br />
* english.nsh<br />
* german.nsh<br />
* italian.nsh<br />
<br />
== Wiki translation ==<br />
<br />
== Website ==<br />
<br />
== News ==</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=TestPage&diff=6590TestPage2006-06-02T13:19:02Z<p>Xaviconde: /* Get the PO file for your language */</p>
<hr />
<div>= Introduction =<br />
== Community based, user oriented ==<br />
The translations of the various documents focusing on Inkscape rely on the work of volunteers.<br />
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.<br />
It is very important not to forget that Inkscape is an open source, community based and user oriented software, which implies that software developpers/contributors are generaly users. It also implies that the translation efforts are also user oriented, with a strong focus on interface, user documentation and website.<br />
<br />
== Guidelines/workflow ==<br />
<br />
# '''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 start 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].<br />
# '''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.<br />
# '''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.<br />
# '''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 you are submitting doesn't have syntax errors that would break the building process.<br />
# '''Send a mail on the translator mailing list'''. Your contribution will be reviewed/commited as soon as possible.<br />
<br />
== Best practices ==<br />
<br />
Best case for a good translation : translate from English to your mother tongue.<br />
<br />
Test the behavior of the interface before starting translation<br />
<br />
= Translatable content =<br />
<br />
Inkscape's translation effort covers many areas, from aplication UI itself to web pages and tutorials. This is a summary of all those areas, ordered by priority.<br />
<br />
These tasks, rather than being for hackers only, can be achieved by most software enthusiasts, whether they have a technological background or just plain users. The main requirement is the wish to provide support for Inkscape on your language: the technology required for do that has been developed in a simple approach, and it involves mainly text files and applications used to verify its syntax. Supporting applications exists to make this tasks even easier.<br />
<br />
== User interface ==<br />
<br />
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.<br />
<br />
See section [[#Interface_Translation]] for information on PO files.<br />
<br />
== Tutorials ==<br />
<br />
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.<br />
<br />
See section [[#Tutorial_Translation]] for information on translating tutorials.<br />
<br />
== Windows installer ==<br />
<br />
High value for users, even if the installation process of Inkscape is quite simple, translating the Windows installer helps a lot potential users feeling good with Inkscape.<br />
<br />
== Templates ==<br />
The default template of Inkscape document can be localized to make the localization consistent. Localized can be size of the default document and also the name of default layer.<br />
* To translate default template, modify the default.svg file and save it as default.xx.svg where "xx" is ISO code of your language. The file can be found in ''/usr/share/inkscape/templates/'' directory on Linux, or ''C:\Program Files\Inkscape\share\templates\'' directory on MS Windows(tm).<br />
* To test it save it to the proper location and restart Inkscape. Default document should be now based on your localized template. (This is valid if your system is properly set to your locales)<br />
* Upload default.xx.svg to the patch tracker.<br />
<br />
== Man pages ==<br />
A reminder for the moment. Will fill it later (matiphas)<br />
<br />
<br />
== Release notes ==<br />
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape<br />
<br />
- give a general overview of the possibilities of the software to potential users<br />
<br />
- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)<br />
<br />
== User manual ==<br />
Just a reminder for the moment. Will first take a look at user-manual process, get some info from cedric and then fill this section (matiphas).<br />
<br />
== News displayed on Inkscape web site ==<br />
<br />
== Web pages ==<br />
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English. <br />
<br />
Translation efforts should be first oriented on user documentation.<br />
<br />
See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.<br />
<br />
== Others ==<br />
Text files found in the inkscape directory<br />
...<br />
<br />
= Interface Translation =<br />
<br />
== Introduction to PO file format ==<br />
<br />
If you've never translated a PO file before, you will find its syntax very simple. The PO format is a really simple format, which probably at least partly explains its success and widespread use. The format is basically a hash list consisting of msgid and msgstr pairs, with the msgid being the original English string and key, and the msgstr being the translated value of it. Below is an example of a message.<br />
<br />
&#35;: gedit/dialogs/gedit-plugin-program-location-dialog.c:78<br />
&#35;: gedit/dialogs/program-location-dialog.glade2.h:2<br />
msgid "Set program location..."<br />
msgstr "Ställ in programplats..."<br />
<br />
In addition to the msgid and msgstr parts, a message usually also has lines starting with #: that tells what source files and what lines the string used as msgid was extracted from. These lines have no syntactic value. They are only there as a help for translators and developers to know where a message came from. <br />
<br />
A message in a PO file can be in one of essentially three different states. The message can be translated, fuzzy, or untranslated. A message counts as translated as soon as the msgstr part of it is non-empty. In a similar manner, an untranslated message is one where the msgstr is empty. The fuzzy state is special and essentially means that there is a translation in the msgstr part, but that this translation is most likely not entirely correct, and that it thus needs manual attention by a translator. A message can become fuzzy in one of two ways:<br />
<br />
* The original string that the msgid represents was changed in the source code. A typo in the string may have been fixed or the string altered in some other way. The translator needs to check that the msgstr is still valid and make changes if necessary.<br />
* A new string has been added to the source, and the string is very similar, but not identical, to the msgid of an already existing, translated message. Then the msgstr of that message will be automatically reused for the new message, but the new message will also at the same time be marked fuzzy so that the translator knows there is some difference that he or she needs to adapt the translation to match.<br />
<br />
There is always one special message in each valid PO file: the PO file header. It is encoded with the msgid for the empty string ("") as the key, and the actual header values are in the msgstr part. This unfortunately means that if you mark an empty string for translation, you will get the entire PO file header back as the "translation". In almost all cases this is probably not what you want. Hence, do not mark empty strings for translation.<br />
<br />
== Get the PO file for your language ==<br />
<br />
Download the .po file for your language from here:<br />
<br />
http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/<br />
<br />
If a .po file for your language does not yet exist, then you will have to get an empty template file to start a new translation. The most straightforward way to obtain the inkscape.pot template is from the SVN repository above. Alternatively, you can checkout the full SVN project repository and generate the project template. Information on how to get the source tree can be found [http://inkscape.org/svn.php here]. Then, you have to follow some steps in order to generate the template:<br />
<br />
1. "./autogen.sh"<br />
2. "./configure"<br />
3. enter the "po" directory: "cd po"<br />
4. generate the current PO template: "intltool-update --pot"<br />
<br />
To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough), <br />
<br />
1. update your local copy of Inkscape in the usual way: "svn update"<br />
2. merge your existing translations into the new POT file (inkscape.pot):<br />
<br />
"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"<br />
<br />
If you want to update ALL .po files in po/, cd there and run:<br />
<br />
make update-po<br />
<br />
Now that you have an empty PO template, you can start translating the messages.<br />
<br />
== Tools for translators ==<br />
<br />
You can edit PO files from any plain text editor, since they are simple text files. However, many useful tools have been developed to provide a simple experience translating PO files.<br />
<br />
* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)<br />
* kbabel (http://i18n.kde.org/tools/kbabel/)<br />
* gtranslator (http://gtranslator.sourceforge.net/)<br />
* poEdit (http://poedit.sourceforge.net/)<br />
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.<br />
<br />
And last but not least, gettext utils.<br />
<br />
== A few important things to remember ==<br />
<br />
* Some strings that can ambiguous or having several meanings according to different contexts may have a context prefix : "Context|Amibiguous string". In this case, simply translate "Ambiguous string", the "Context|" string is just a not to translate indication.<br />
* After translating a fuzzy string (one that is marked with a ", fuzzy" comment), please remove its "fuzzy" tag -- otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated. KBabel can do this automatically (see KBabel settings).<br />
* Before publishing your work (after you have finished updating the PO file), please update the "PO-Revision-Date" and "Last-Translator" fields in the PO file header. KBabel can do this automatically.<br />
<br />
== Review ==<br />
This is the start of a list of places to get translation reviews done. So far:<br />
http://www.linux.it/tp/<br />
<br />
== Verification ==<br />
Before submitting your file in the patch tracker, please make sure it is valid:<br />
* Make sure the file is encoded in UTF-8 <br />
* Make sure it is a valid po file and obtain some statistics about it: simply run "msgfmt --statistics -cv translationFile.po" from a command window<br />
* Make sure it is correctly formatted: run "check-markup translationFile.po" from a command window and verify it doesn't output any error message. "check-markup" perl script can be found in the /po directory of Inkscape svn trunk<br />
<br />
== Locale Testing ==<br />
Before reporting that a locale doesn't work in Inkscape, you need to make sure that your system has that locale correctly set up. To do this, you need to generally find a way to run "locale-gen". (Under Debian/Ubuntu this is via "dpkg-reconfigure locales".) If you set both the LANG and LANGUAGE variables and check a regular tool, you should see the correct language for both the libc error (first line) and the tool error (second line):<br />
<br />
LANG=es_MX LANGUAGE=es_MX ls -z<br />
ls: opci&oacute;n inv&aacute;lida -- z<br />
Pruebe `ls --help' para m&aacute;s informaci&oacute;n.<br />
<br />
If it reports the regular C messages, your locale has not been correctly configured, and you'll need to find the right way to run "locale-gen" for your distribution:<br />
<br />
LANG=es_ES LANGUAGE=es_MX ls -z<br />
ls: invalid option -- z<br />
Try `ls --help' for more information.<br />
<br />
== Submit finished work ==<br />
<br />
Upload your work via the [[SourceForge]] patch tracker:<br />
<br />
http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308<br />
<br />
(Check the Upload checkbox and add your file or patch.)<br />
<br />
(Don't forget to compress your file before uploading it, as sourcefoge tracker doesn't accept large files.)<br />
<br />
Additionally, you may send a message to Inskcape's translators mailing list.<br />
<br />
== Programmers ==<br />
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.<br />
<br />
= Tutorial Translation =<br />
<br />
Inkscape tutorial sources are in [[DocBook]] format, with illustrations in SVG. If you want to translate one or more tutorials, first download the [[DocBook]] source here:<br />
<br />
http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/<br />
<br />
Each tutorial is in its own subdirectory. You need the *.xml file, for example basic/tutorial-basic.xml. Get it and simply replace all English text in it with the text in your language, preserving all XML markup. See README at that location for some notes on markup.<br />
<br />
* If there's already such a file in SVN, you can edit it instead :) If there's no xml file at the above location but there's a translation of this tutorial in SVG format (in share/tutorials in Inkscape distribution), you'll need to convert it to [[DocBook]] (and probably update). Conversion can be done simply by: select the text blocks of an SVG tutorial in Inkscape, Ctrl+C, and Ctrl+V in your text editor, then add the markup.<br />
<br />
* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish. <br />
<br />
* Do not use symbolic entities like &amp;aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &amp;#225; or simply write your text in UTF-8.<br />
<br />
* Most illustrations don't need translations, so you leave the references to them from English XML intact. If however an illustration has some text that you want to translate, open the illustration file in Inkscape (e.g. basic/basic-f12.svg), edit it as needed, and save under a different name (e.g. basic/basic-f12-es.svg). Then change the filename reference in the XML source appropriately.<br />
<br />
* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.<br />
<br />
* Send the file to Joshua Andler <scislac at users dot sf dot net>, and he'll convert it to SVG and HTML and upload it to SVN and the web site.<br />
<br />
* If after that you want to make any changes, download the file from the above location again, because it may have changed compared to the one you have.<br />
<br />
==Tools==<br />
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html<br />
* Transolution - http://transolution.python-hosting.com/<br />
<br />
===Transforming XML into PO files===<br />
One can also use xml2po to get PO files out of the XML sources, and also transform the PO files back to XML. After you have a PO file, follow the instructions for editing those files below.<br />
<br />
xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).<br />
<br />
Here are some command lines that were used to translate a German tutorial (the de-locale), please adapt accordingly until we nicely integrate this into our Makefiles.<br />
<br />
<pre><br />
## use this at the very beginning, when there is no translation at all:<br />
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml<br />
<br />
## use this when there is a *.de.xml, but you want a de.po:<br />
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml<br />
<br />
## xml2po is not happy when this directory doesn't exist:<br />
mkdir .tmp.basic<br />
<br />
## use this when the tutorial-basic.xml has been updated and you<br />
## want the new stuff in your de.po:<br />
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml<br />
<br />
## use this to create a tutorial-basic.de.xml from your de.po (ScislaC<br />
## will use this file to create the final tutorial SVG file)<br />
## WARNING: Unfortunately, this doesn't put localized screenshot <br />
## file names into the xml file!<br />
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml<br />
<br />
</pre><br />
<br />
= Keyboard and mouse translation =<br />
<br />
= Wiki and web site =<br />
== Translation of web site ==<br />
# There are two ways of getting files that you need to translate website:<br />
## Checkout actual svn version of inkscape_web module ([http://inkscape.org/svn.php Working with SVN]). To checkout the inkscape_web module use command: <pre>svn co https://svn.sourceforge.net/svnroot/inkscape/inkscape_web/trunk inkscape_web</pre> You need subversion client to do this.<br />
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.<br />
## Files you probably want to translate are:<br />
##* includes/localized.inc (file contains string to translate menu)<br />
##* index-en.inc (main page of inkscape.org)<br />
##* discussion-en.inc<br />
##* download-en.inc<br />
##* mailing-lists-en.inc<br />
##* report-bugs-en.inc<br />
##* submit2webmaster-en.inc<br />
##* submit2webmaster-en-form.inc<br />
##* svn-en.inc<br />
# Copy these files and replace "en" string in their name according to the ISO code of your language ("de" for german, "fr" for french, etc...).<br />
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.<br />
# If you have the file translated and really want to submit it, read it once more and correct errors ;)<br />
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.<br />
# Announce the translated file in the patch tracker in inkscape-translator(and optionally in inkscape-devel) mailing list. Persons responsible for updates of website will reply to you and/or submit the new "patch" directly.<br />
If the translation of website is new, the process of making new translation available can take a bit longer because of a need to create corresponding flag and check consistency of the translation.<br />
=== Translating news and status ===<br />
News and status information are available for translation too. News items are stored in the /news directory of inkscape_module in separate subdirectories named by language version. The structure of directory with news is:<br />
<pre><br />
/news<br />
- en<br />
\- 2005<br />
- 2006<br />
\- 04<br />
- 05<br />
\- 001.inc<br />
- 002.inc<br />
...<br />
- de<br />
- fr<br />
</pre><br />
To translate news into your language download/checkout 00x.inc file from "en" directory, translate and submit to the directory of your language(file has to be in UTF-8 encoding) or submit to the patch tracker and announce on the inkscape-translator list.<br />
If you want to translate status information, the structure of directories is like in the case of news, only the name of directory is different.<br />
<br />
= Status =<br />
<br />
== Interface translation (po files) ==<br />
<br />
The names and e-mail addresses of contributors and last translator can be found in the header of the po file (simply open it with your favorite text editor)<br />
<br />
Total number of PO files: 38<br />
Total number of strings to translate: 2142<br />
<br />
<br />
'''Amharic''': am.po<br />
<br />
translated: 77 ( '''3%''')<br />
<br />
fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)<br />
<br />
Date of last update: 2003-02-01<br />
<br />
<br />
'''Azerbaijani/Turkic''': az.po<br />
<br />
translated: 63 ( '''2%''')<br />
<br />
fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)<br />
<br />
Date of last update: 2001-12-04<br />
<br />
<br />
'''Belarusian''': be.po<br />
<br />
translated: 158 ( '''7%''')<br />
<br />
fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)<br />
<br />
Date of last update: 2003-07-20<br />
<br />
<br />
'''Catalan''': ca.po<br />
<br />
translated: 2039 ( '''95%''')<br />
<br />
fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)<br />
<br />
Date of last update: 2006-05-08<br />
<br />
<br />
'''Czech''': cs.po<br />
<br />
translated: 2096 ( '''97%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)<br />
<br />
Date of last update: 2006-05-22<br />
<br />
<br />
'''Danish''': da.po<br />
<br />
translated: 100 ( '''4%''')<br />
<br />
fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)<br />
<br />
Date of last update: 2002-01-15<br />
<br />
<br />
'''German''': de.po<br />
<br />
translated: 2116 ( '''98%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)<br />
<br />
Date of last update: 2006-05-23<br />
<br />
<br />
'''Greek''': el.po<br />
<br />
translated: 44 ( '''2%''')<br />
<br />
fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)<br />
<br />
Date of last update: 2001-12-28<br />
<br />
<br />
'''Spanish''': es.po<br />
<br />
translated: 2125 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)<br />
<br />
Date of last update: 2006-05-25<br />
<br />
<br />
'''Spanish/Mexico''': es_MX.po<br />
<br />
translated: 337 ( '''15%''')<br />
<br />
fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)<br />
<br />
Date of last update: 2004-04-05<br />
<br />
<br />
'''Estonian''': et.po<br />
<br />
translated: 9 ( '''0%''')<br />
<br />
fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)<br />
<br />
Date of last update: 2000-04-08<br />
<br />
<br />
'''Basque''': eu.po<br />
<br />
translated: 1548 ( '''72%''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)<br />
<br />
Date of last update: 2006-03-16<br />
<br />
<br />
'''French''': fr.po<br />
<br />
translated: 2126 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)<br />
<br />
Date of last update: 2006-05-27<br />
<br />
<br />
'''Irish''': ga.po<br />
<br />
translated: 14 ( '''0%''')<br />
<br />
fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)<br />
<br />
Date of last update: 2000-08-24<br />
<br />
<br />
'''Galician''': gl.po<br />
<br />
translated: 82 ( '''3%''')<br />
<br />
fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)<br />
<br />
Date of last update: 2001-11-10<br />
<br />
<br />
'''Hungarian''': hu.po<br />
<br />
translated: 1564 ( '''73%''')<br />
<br />
fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)<br />
<br />
Date of last update: 2006-05-29<br />
<br />
<br />
'''Italian''': it.po<br />
<br />
translated: 2008 ( '''93%''')<br />
<br />
fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)<br />
<br />
Date of last update: 2006-05-15<br />
<br />
<br />
'''Japanese''': ja.po<br />
<br />
translated: 1294 ( '''60%''')<br />
<br />
fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)<br />
<br />
Date of last update: 2005-11-16<br />
<br />
<br />
'''Korean''': ko.po<br />
<br />
translated: 180 ( '''8%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)<br />
<br />
Date of last update: 2006-04-10<br />
<br />
<br />
'''Lithuanian''': lt.po<br />
<br />
translated: 1774 ( '''82%''')<br />
<br />
fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)<br />
<br />
Date of last update: 2006-05-02<br />
<br />
<br />
'''mk.po'''<br />
<br />
translated: 0 ( '''0%''')<br />
<br />
fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)<br />
<br />
Date of last update: 2003-06-15<br />
<br />
<br />
'''Norwegian/bokmål dialect''': nb.po<br />
<br />
translated: 144 ( '''6%''')<br />
<br />
fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)<br />
<br />
Date of last update: 2003-01-25<br />
<br />
<br />
'''Dutch: nl.po'''<br />
<br />
translated: 1484 ( '''69%''')<br />
<br />
fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)<br />
<br />
Date of last update: 2005-11-07<br />
<br />
<br />
'''Norwegian/Nynorsk''': nn.po<br />
<br />
translated: 1376 ( '''64%''')<br />
<br />
fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)<br />
<br />
Date of last update: 2005-07-14<br />
<br />
<br />
'''Punjabi''': pa.po<br />
<br />
translated: 912 ( '''42%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)<br />
<br />
Date of last update: 2005-09-11<br />
<br />
<br />
'''Polish''': pl.po<br />
<br />
translated: 1503 ( '''70%''')<br />
<br />
fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)<br />
<br />
Date of last update: 2005-10-29<br />
<br />
<br />
'''Portuguese''': pt.po<br />
<br />
translated: 183 ( '''8%''')<br />
<br />
fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)<br />
<br />
Date of last update: 2003-07-28<br />
<br />
<br />
'''Portuguese/Brazillian''': pt_BR.po<br />
<br />
translated: 1546 ( '''72%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)<br />
<br />
Date of last update: 2006-04-27<br />
<br />
<br />
'''Russian''': ru.po<br />
<br />
translated: 1542 ( '''71%''')<br />
<br />
fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)<br />
<br />
Date of last update: 2005-11-08<br />
<br />
<br />
'''Slovak''': sk.po<br />
<br />
translated: 845 ( '''39%''')<br />
<br />
fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)<br />
<br />
Date of last update: 2005-02-13<br />
<br />
<br />
'''Slovenian''': sl.po<br />
<br />
translated: 2055 ( '''95%''')<br />
<br />
fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)<br />
<br />
Date of last update: 2006-05-12<br />
<br />
<br />
'''Serbian''': sr.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Serbian/Latine''': sr@Latn.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Swedish''': sv.po<br />
<br />
translated: 410 ( '''19%''')<br />
<br />
fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)<br />
<br />
Date of last update: 2005-10-08<br />
<br />
<br />
'''Turkish''': tr.po<br />
<br />
translated: 907 ( '''42%''')<br />
<br />
fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)<br />
<br />
Date of last update: 2005-11-26<br />
<br />
<br />
'''Ukrainian''': uk.po<br />
<br />
translated: 1518 ( '''70%''')<br />
<br />
fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)<br />
<br />
Date of last update: 2005-10-21<br />
<br />
<br />
'''Chinese/Simplified''': zh_CN.po<br />
<br />
translated: 2134 ( '''99%''')<br />
<br />
<br />
fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)<br />
<br />
Date of last update: 2006-05-28<br />
<br />
<br />
'''Chinese/Traditional''': zh_TW.po<br />
<br />
translated: 1550 ( '''72 %''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)<br />
<br />
Date of last update: 2006-03-24<br />
<br />
== Tutorials ==<br />
<br />
* Basic: ca, de, en, es, fr, ja, nn, ru, sl<br />
* Shapes: ca, en, es, fr, ja, sl<br />
* Advanced: ca, en, es, fr, ja, sl<br />
* Tracing: ca, de, en, es, fr, sl<br />
* Calligraphy: ca, en, es, fr, sl<br />
* Elements of design: en, es, fr, sl<br />
* Tips and tricks: de, en, es, fr, sl<br />
<br />
<br />
== Keys (shortcuts) ==<br />
Already available in svn :<br />
* en<br />
* fr<br />
* sl<br />
<br />
<br />
== Windows installer ==<br />
<br />
Already available in svn :<br />
* czech.nsh<br />
* english.nsh<br />
* german.nsh<br />
* italian.nsh<br />
<br />
== Wiki translation ==<br />
<br />
== Website ==<br />
<br />
== News ==</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=TestPage&diff=6571TestPage2006-05-31T11:08:27Z<p>Xaviconde: /* Introduction to PO file format */</p>
<hr />
<div>= Introduction =<br />
== Community based, user oriented ==<br />
The translations of the various documents focusing on Inkscape rely on the work of volunteers.<br />
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.<br />
It is very important not to forget that Inkscape is an open source, community based and user oriented software, which implies that software developpers/contributors are generaly users. It also implies that the translation efforts are also user oriented, with a strong focus on interface, user documentation and website.<br />
<br />
== Guidelines/workflow ==<br />
<br />
# '''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 start 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].<br />
# '''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.<br />
# '''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.<br />
# '''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 you are submitting doesn't have syntax errors that would break the building process.<br />
# '''Send a mail on the translator mailing list'''. Your contribution will be reviewed/commited as soon as possible.<br />
<br />
== Best practices ==<br />
<br />
Best case for a good translation : translate from English to your mother tongue.<br />
<br />
Test the behavior of the interface before starting translation<br />
<br />
= Translatable content =<br />
<br />
Inkscape's translation effort covers many areas, from aplication UI itself to web pages and tutorials. This is a summary of all those areas, ordered by priority.<br />
<br />
These tasks, rather than being for hackers only, can be achieved by most software enthusiasts, whether they have a technological background or just plain users. The main requirement is the wish to provide support for Inkscape on your language: the technology required for do that has been developed in a simple approach, and it involves mainly text files and applications used to verify its syntax. Supporting applications exists to make this tasks even easier.<br />
<br />
== User interface ==<br />
<br />
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.<br />
<br />
See section [[#Interface_Translation]] for information on PO files.<br />
<br />
== Tutorials ==<br />
<br />
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.<br />
<br />
See section [[#Tutorial_Translation]] for information on translating tutorials.<br />
<br />
== Windows installer ==<br />
<br />
High value for users, even if the installation process of Inkscape is quite simple, translating the Windows installer helps a lot potential users feeling good with Inkscape.<br />
<br />
== Templates ==<br />
<br />
== Release notes ==<br />
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape<br />
<br />
- give a general overview of the possibilities of the software to potential users<br />
<br />
- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)<br />
<br />
== News displayed on Inkscape web site ==<br />
<br />
== Web pages ==<br />
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English. <br />
<br />
Translation efforts should be first oriented on user documentation.<br />
<br />
See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.<br />
<br />
<br />
== Others ==<br />
Templates (translation and localization)<br />
Text files found in the inkscape directory<br />
...<br />
<br />
= Interface Translation =<br />
<br />
== Introduction to PO file format ==<br />
<br />
If you've never translated a PO file before, you will find its syntax very simple. The PO format is a really simple format, which probably at least partly explains its success and widespread use. The format is basically a hash list consisting of msgid and msgstr pairs, with the msgid being the original English string and key, and the msgstr being the translated value of it. Below is an example of a message.<br />
<br />
&#35;: gedit/dialogs/gedit-plugin-program-location-dialog.c:78<br />
&#35;: gedit/dialogs/program-location-dialog.glade2.h:2<br />
msgid "Set program location..."<br />
msgstr "Ställ in programplats..."<br />
<br />
In addition to the msgid and msgstr parts, a message usually also has lines starting with #: that tells what source files and what lines the string used as msgid was extracted from. These lines have no syntactic value. They are only there as a help for translators and developers to know where a message came from. <br />
<br />
A message in a PO file can be in one of essentially three different states. The message can be translated, fuzzy, or untranslated. A message counts as translated as soon as the msgstr part of it is non-empty. In a similar manner, an untranslated message is one where the msgstr is empty. The fuzzy state is special and essentially means that there is a translation in the msgstr part, but that this translation is most likely not entirely correct, and that it thus needs manual attention by a translator. A message can become fuzzy in one of two ways:<br />
<br />
* The original string that the msgid represents was changed in the source code. A typo in the string may have been fixed or the string altered in some other way. The translator needs to check that the msgstr is still valid and make changes if necessary.<br />
* A new string has been added to the source, and the string is very similar, but not identical, to the msgid of an already existing, translated message. Then the msgstr of that message will be automatically reused for the new message, but the new message will also at the same time be marked fuzzy so that the translator knows there is some difference that he or she needs to adapt the translation to match.<br />
<br />
There is always one special message in each valid PO file: the PO file header. It is encoded with the msgid for the empty string ("") as the key, and the actual header values are in the msgstr part. This unfortunately means that if you mark an empty string for translation, you will get the entire PO file header back as the "translation". In almost all cases this is probably not what you want. Hence, do not mark empty strings for translation.<br />
<br />
== Get the PO file for your language ==<br />
<br />
Download the .po file for your language from here:<br />
<br />
http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/<br />
<br />
If a .po file for your language does not yet exist, then you will have to get a current copy of the working tree from SVN repository in order to generate a template. This empty template contains only English messages. Information on how to get a the source tree can be found [http://inkscape.org/svn.php here].<br />
<br />
Create your own language file by copying the inkscape.pot file that gets generated when you run make in the codebase. <br />
<br />
1. "./autogen.sh"<br />
2. "./configure"<br />
3. enter the "po" directory: "cd po"<br />
4. generate the current PO template: "intltool-update --pot"<br />
<br />
To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough), <br />
<br />
1. update your local copy of Inkscape in the usual way: "svn update"<br />
2. merge your existing translations into the new POT file (inkscape.pot):<br />
<br />
"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"<br />
<br />
Then you just need to complete the translations in the PO file that was<br />
created in step 6.<br />
<br />
If you want to update ALL .po files in po/, cd there and run:<br />
<br />
make update-po<br />
<br />
== Tools for translators ==<br />
<br />
You can edit PO files from any plain text editor, since they are simple text files. However, many useful tools have been developed to provide a simple experience translating PO files.<br />
<br />
* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)<br />
* kbabel (http://i18n.kde.org/tools/kbabel/)<br />
* gtranslator (http://gtranslator.sourceforge.net/)<br />
* poEdit (http://poedit.sourceforge.net/)<br />
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.<br />
<br />
And last but not least, gettext utils.<br />
<br />
== Submit finished work ==<br />
<br />
Upload your work via the [[SourceForge]] patch tracker:<br />
<br />
http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308<br />
<br />
(Check the Upload checkbox and add your file or patch.)<br />
<br />
Additionally, you may send a message to Inskcape's translators mailing list.<br />
<br />
== A few important things to remember ==<br />
<br />
* Some strings that can ambiguous or having several meanings according to different contexts may have a context prefix : "Context|Amibiguous string". In this case, simply translate "Ambiguous string", the "Context|" string is just a not to translate indication.<br />
* After translating a fuzzy string (one that is marked with a ", fuzzy" comment), please remove its "fuzzy" tag -- otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated. KBabel can do this automatically (see KBabel settings).<br />
* Before publishing your work (after you have finished updating the PO file), please update the "PO-Revision-Date" and "Last-Translator" fields in the PO file header. KBabel can do this automatically.<br />
<br />
== Review ==<br />
This is the start of a list of places to get translation reviews done. So far:<br />
http://www.linux.it/tp/<br />
<br />
== Verification ==<br />
Before submitting your file in the patch tracker, please make sure it is valid:<br />
* Make sure the file is encoded in UTF-8 <br />
* Make sure it is a valid po file and obtain some statistics about it: simply run "msgfmt --statistics -cv translationFile.po" from a command window<br />
* Make sure it is correctly formatted: run "check-markup translationFile.po" from a command window and verify it doesn't output any error message. "check-markup" perl script can be found in the /po directory of Inkscape svn trunk<br />
<br />
== Locale Testing ==<br />
Before reporting that a locale doesn't work in Inkscape, you need to make sure that your system has that locale correctly set up. To do this, you need to generally find a way to run "locale-gen". (Under Debian/Ubuntu this is via "dpkg-reconfigure locales".) If you set both the LANG and LANGUAGE variables and check a regular tool, you should see the correct language for both the libc error (first line) and the tool error (second line):<br />
<br />
LANG=es_MX LANGUAGE=es_MX ls -z<br />
ls: opci&oacute;n inv&aacute;lida -- z<br />
Pruebe `ls --help' para m&aacute;s informaci&oacute;n.<br />
<br />
If it reports the regular C messages, your locale has not been correctly configured, and you'll need to find the right way to run "locale-gen" for your distribution:<br />
<br />
LANG=es_ES LANGUAGE=es_MX ls -z<br />
ls: invalid option -- z<br />
Try `ls --help' for more information.<br />
<br />
== Programmers ==<br />
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.<br />
<br />
= Tutorial Translation =<br />
<br />
Inkscape tutorial sources are in [[DocBook]] format, with illustrations in SVG. If you want to translate one or more tutorials, first download the [[DocBook]] source here:<br />
<br />
http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/<br />
<br />
Each tutorial is in its own subdirectory. You need the *.xml file, for example basic/tutorial-basic.xml. Get it and simply replace all English text in it with the text in your language, preserving all XML markup. See README at that location for some notes on markup.<br />
<br />
* If there's already such a file in SVN, you can edit it instead :) If there's no xml file at the above location but there's a translation of this tutorial in SVG format (in share/tutorials in Inkscape distribution), you'll need to convert it to [[DocBook]] (and probably update). Conversion can be done simply by: select the text blocks of an SVG tutorial in Inkscape, Ctrl+C, and Ctrl+V in your text editor, then add the markup.<br />
<br />
* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish. <br />
<br />
* Do not use symbolic entities like &amp;aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &amp;#225; or simply write your text in UTF-8.<br />
<br />
* Most illustrations don't need translations, so you leave the references to them from English XML intact. If however an illustration has some text that you want to translate, open the illustration file in Inkscape (e.g. basic/basic-f12.svg), edit it as needed, and save under a different name (e.g. basic/basic-f12-es.svg). Then change the filename reference in the XML source appropriately.<br />
<br />
* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.<br />
<br />
* Send the file to Joshua Andler <scislac at users dot sf dot net>, and he'll convert it to SVG and HTML and upload it to SVN and the web site.<br />
<br />
* If after that you want to make any changes, download the file from the above location again, because it may have changed compared to the one you have.<br />
<br />
==Tools==<br />
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html<br />
* Transolution - http://transolution.python-hosting.com/<br />
<br />
===Transforming XML into PO files===<br />
One can also use xml2po to get PO files out of the XML sources, and also transform the PO files back to XML. After you have a PO file, follow the instructions for editing those files below.<br />
<br />
xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).<br />
<br />
Here are some command lines that were used to translate a German tutorial (the de-locale), please adapt accordingly until we nicely integrate this into our Makefiles.<br />
<br />
<pre><br />
## use this at the very beginning, when there is no translation at all:<br />
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml<br />
<br />
## use this when there is a *.de.xml, but you want a de.po:<br />
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml<br />
<br />
## xml2po is not happy when this directory doesn't exist:<br />
mkdir .tmp.basic<br />
<br />
## use this when the tutorial-basic.xml has been updated and you<br />
## want the new stuff in your de.po:<br />
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml<br />
<br />
## use this to create a tutorial-basic.de.xml from your de.po (ScislaC<br />
## will use this file to create the final tutorial SVG file)<br />
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml<br />
<br />
</pre><br />
<br />
= Keyboard and mouse translation =<br />
<br />
= Wiki and web site =<br />
<br />
= Status =<br />
<br />
== Interface translation (po files) ==<br />
<br />
The names and e-mail addresses of contributors and last translator can be found in the header of the po file (simply open it with your favorite text editor)<br />
<br />
Total number of PO files: 38<br />
Total number of strings to translate: 2142<br />
<br />
<br />
'''Amharic''': am.po<br />
<br />
translated: 77 ( '''3%''')<br />
<br />
fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)<br />
<br />
Date of last update: 2003-02-01<br />
<br />
<br />
'''Azerbaijani/Turkic''': az.po<br />
<br />
translated: 63 ( '''2%''')<br />
<br />
fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)<br />
<br />
Date of last update: 2001-12-04<br />
<br />
<br />
'''Belarusian''': be.po<br />
<br />
translated: 158 ( '''7%''')<br />
<br />
fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)<br />
<br />
Date of last update: 2003-07-20<br />
<br />
<br />
'''Catalan''': ca.po<br />
<br />
translated: 2039 ( '''95%''')<br />
<br />
fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)<br />
<br />
Date of last update: 2006-05-08<br />
<br />
<br />
'''Czech''': cs.po<br />
<br />
translated: 2096 ( '''97%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)<br />
<br />
Date of last update: 2006-05-22<br />
<br />
<br />
'''Danish''': da.po<br />
<br />
translated: 100 ( '''4%''')<br />
<br />
fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)<br />
<br />
Date of last update: 2002-01-15<br />
<br />
<br />
'''German''': de.po<br />
<br />
translated: 2116 ( '''98%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)<br />
<br />
Date of last update: 2006-05-23<br />
<br />
<br />
'''Greek''': el.po<br />
<br />
translated: 44 ( '''2%''')<br />
<br />
fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)<br />
<br />
Date of last update: 2001-12-28<br />
<br />
<br />
'''Spanish''': es.po<br />
<br />
translated: 2125 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)<br />
<br />
Date of last update: 2006-05-25<br />
<br />
<br />
'''Spanish/Mexico''': es_MX.po<br />
<br />
translated: 337 ( '''15%''')<br />
<br />
fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)<br />
<br />
Date of last update: 2004-04-05<br />
<br />
<br />
'''Estonian''': et.po<br />
<br />
translated: 9 ( '''0%''')<br />
<br />
fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)<br />
<br />
Date of last update: 2000-04-08<br />
<br />
<br />
'''Basque''': eu.po<br />
<br />
translated: 1548 ( '''72%''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)<br />
<br />
Date of last update: 2006-03-16<br />
<br />
<br />
'''French''': fr.po<br />
<br />
translated: 2126 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)<br />
<br />
Date of last update: 2006-05-27<br />
<br />
<br />
'''Irish''': ga.po<br />
<br />
translated: 14 ( '''0%''')<br />
<br />
fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)<br />
<br />
Date of last update: 2000-08-24<br />
<br />
<br />
'''Galician''': gl.po<br />
<br />
translated: 82 ( '''3%''')<br />
<br />
fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)<br />
<br />
Date of last update: 2001-11-10<br />
<br />
<br />
'''Hungarian''': hu.po<br />
<br />
translated: 1564 ( '''73%''')<br />
<br />
fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)<br />
<br />
Date of last update: 2006-05-29<br />
<br />
<br />
'''Italian''': it.po<br />
<br />
translated: 2008 ( '''93%''')<br />
<br />
fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)<br />
<br />
Date of last update: 2006-05-15<br />
<br />
<br />
'''Japanese''': ja.po<br />
<br />
translated: 1294 ( '''60%''')<br />
<br />
fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)<br />
<br />
Date of last update: 2005-11-16<br />
<br />
<br />
'''Korean''': ko.po<br />
<br />
translated: 180 ( '''8%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)<br />
<br />
Date of last update: 2006-04-10<br />
<br />
<br />
'''Lithuanian''': lt.po<br />
<br />
translated: 1774 ( '''82%''')<br />
<br />
fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)<br />
<br />
Date of last update: 2006-05-02<br />
<br />
<br />
'''mk.po'''<br />
<br />
translated: 0 ( '''0%''')<br />
<br />
fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)<br />
<br />
Date of last update: 2003-06-15<br />
<br />
<br />
'''Norwegian/bokmål dialect''': nb.po<br />
<br />
translated: 144 ( '''6%''')<br />
<br />
fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)<br />
<br />
Date of last update: 2003-01-25<br />
<br />
<br />
'''Dutch: nl.po'''<br />
<br />
translated: 1484 ( '''69%''')<br />
<br />
fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)<br />
<br />
Date of last update: 2005-11-07<br />
<br />
<br />
'''Norwegian/Nynorsk''': nn.po<br />
<br />
translated: 1376 ( '''64%''')<br />
<br />
fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)<br />
<br />
Date of last update: 2005-07-14<br />
<br />
<br />
'''Punjabi''': pa.po<br />
<br />
translated: 912 ( '''42%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)<br />
<br />
Date of last update: 2005-09-11<br />
<br />
<br />
'''Polish''': pl.po<br />
<br />
translated: 1503 ( '''70%''')<br />
<br />
fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)<br />
<br />
Date of last update: 2005-10-29<br />
<br />
<br />
'''Portuguese''': pt.po<br />
<br />
translated: 183 ( '''8%''')<br />
<br />
fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)<br />
<br />
Date of last update: 2003-07-28<br />
<br />
<br />
'''Portuguese/Brazillian''': pt_BR.po<br />
<br />
translated: 1546 ( '''72%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)<br />
<br />
Date of last update: 2006-04-27<br />
<br />
<br />
'''Russian''': ru.po<br />
<br />
translated: 1542 ( '''71%''')<br />
<br />
fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)<br />
<br />
Date of last update: 2005-11-08<br />
<br />
<br />
'''Slovak''': sk.po<br />
<br />
translated: 845 ( '''39%''')<br />
<br />
fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)<br />
<br />
Date of last update: 2005-02-13<br />
<br />
<br />
'''Slovenian''': sl.po<br />
<br />
translated: 2055 ( '''95%''')<br />
<br />
fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)<br />
<br />
Date of last update: 2006-05-12<br />
<br />
<br />
'''Serbian''': sr.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Serbian/Latine''': sr@Latn.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Swedish''': sv.po<br />
<br />
translated: 410 ( '''19%''')<br />
<br />
fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)<br />
<br />
Date of last update: 2005-10-08<br />
<br />
<br />
'''Turkish''': tr.po<br />
<br />
translated: 907 ( '''42%''')<br />
<br />
fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)<br />
<br />
Date of last update: 2005-11-26<br />
<br />
<br />
'''Ukrainian''': uk.po<br />
<br />
translated: 1518 ( '''70%''')<br />
<br />
fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)<br />
<br />
Date of last update: 2005-10-21<br />
<br />
<br />
'''Chinese/Simplified''': zh_CN.po<br />
<br />
translated: 2134 ( '''99%''')<br />
<br />
<br />
fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)<br />
<br />
Date of last update: 2006-05-28<br />
<br />
<br />
'''Chinese/Traditional''': zh_TW.po<br />
<br />
translated: 1550 ( '''72 %''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)<br />
<br />
Date of last update: 2006-03-24<br />
<br />
== Tutorials ==<br />
<br />
* Basic: ca, de, en, es, fr, ja, nn, ru, sl<br />
* Shapes: ca, en, es, fr, ja, sl<br />
* Advanced: ca, en, es, fr, ja, sl<br />
* Tracing: ca, de, en, es, fr, sl<br />
* Calligraphy: ca, en, es, fr, sl<br />
* Elements of design: en, es, fr, sl<br />
* Tips and tricks: de, en, es, fr, sl<br />
<br />
<br />
== Keys (shortcuts) ==<br />
Already available in svn :<br />
* en<br />
* fr<br />
* sl<br />
<br />
<br />
== Windows installer ==<br />
<br />
Already available in svn :<br />
* czech.nsh<br />
* english.nsh<br />
* german.nsh<br />
* italian.nsh<br />
<br />
== Wiki translation ==<br />
<br />
== Website ==<br />
<br />
== News ==</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=TestPage&diff=6570TestPage2006-05-31T10:52:49Z<p>Xaviconde: /* Interface Translation */</p>
<hr />
<div>= Introduction =<br />
== Community based, user oriented ==<br />
The translations of the various documents focusing on Inkscape rely on the work of volunteers.<br />
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.<br />
It is very important not to forget that Inkscape is an open source, community based and user oriented software, which implies that software developpers/contributors are generaly users. It also implies that the translation efforts are also user oriented, with a strong focus on interface, user documentation and website.<br />
<br />
== Guidelines/workflow ==<br />
<br />
# '''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 start 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].<br />
# '''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.<br />
# '''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.<br />
# '''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 you are submitting doesn't have syntax errors that would break the building process.<br />
# '''Send a mail on the translator mailing list'''. Your contribution will be reviewed/commited as soon as possible.<br />
<br />
== Best practices ==<br />
<br />
Best case for a good translation : translate from English to your mother tongue.<br />
<br />
Test the behavior of the interface before starting translation<br />
<br />
= Translatable content =<br />
<br />
Inkscape's translation effort covers many areas, from aplication UI itself to web pages and tutorials. This is a summary of all those areas, ordered by priority.<br />
<br />
These tasks, rather than being for hackers only, can be achieved by most software enthusiasts, whether they have a technological background or just plain users. The main requirement is the wish to provide support for Inkscape on your language: the technology required for do that has been developed in a simple approach, and it involves mainly text files and applications used to verify its syntax. Supporting applications exists to make this tasks even easier.<br />
<br />
== User interface ==<br />
<br />
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.<br />
<br />
See section [[#Interface_Translation]] for information on PO files.<br />
<br />
== Tutorials ==<br />
<br />
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.<br />
<br />
See section [[#Tutorial_Translation]] for information on translating tutorials.<br />
<br />
== Windows installer ==<br />
<br />
High value for users, even if the installation process of Inkscape is quite simple, translating the Windows installer helps a lot potential users feeling good with Inkscape.<br />
<br />
== Templates ==<br />
<br />
== Release notes ==<br />
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape<br />
<br />
- give a general overview of the possibilities of the software to potential users<br />
<br />
- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)<br />
<br />
== News displayed on Inkscape web site ==<br />
<br />
== Web pages ==<br />
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English. <br />
<br />
Translation efforts should be first oriented on user documentation.<br />
<br />
See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.<br />
<br />
<br />
== Others ==<br />
Templates (translation and localization)<br />
Text files found in the inkscape directory<br />
...<br />
<br />
= Interface Translation =<br />
<br />
== Introduction to PO file format ==<br />
<br />
If you've never translated a PO file before, you will find its syntax very simple. The PO format is a really simple format, which probably at least partly explains its success and widespread use. The format is basically a hash list consisting of msgid and msgstr pairs, with the msgid being the original English string and key, and the msgstr being the translated value of it. Below is an example of a message.<br />
<br />
<nowiki><br />
<p><br />
#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78<br><br />
#: gedit/dialogs/program-location-dialog.glade2.h:2<br><br />
msgid "Set program location..."<br><br />
msgstr "Ställ in programplats..."<br><br />
</p><br />
</nowiki><br />
<br />
In addition to the msgid and msgstr parts, a message usually also has lines starting with #: that tells what source files and what lines the string used as msgid was extracted from. These lines have no syntactic value. They are only there as a help for translators and developers to know where a message came from. <br />
<br />
A message in a PO file can be in one of essentially three different states. The message can be translated, fuzzy, or untranslated. A message counts as translated as soon as the msgstr part of it is non-empty. In a similar manner, an untranslated message is one where the msgstr is empty. The fuzzy state is special and essentially means that there is a translation in the msgstr part, but that this translation is most likely not entirely correct, and that it thus needs manual attention by a translator. A message can become fuzzy in one of two ways:<br />
<br />
* The original string that the msgid represents was changed in the source code. A typo in the string may have been fixed or the string altered in some other way. The translator needs to check that the msgstr is still valid and make changes if necessary.<br />
* A new string has been added to the source, and the string is very similar, but not identical, to the msgid of an already existing, translated message. Then the msgstr of that message will be automatically reused for the new message, but the new message will also at the same time be marked fuzzy so that the translator knows there is some difference that he or she needs to adapt the translation to match.<br />
<br />
There is always one special message in each valid PO file: the PO file header. It is encoded with the msgid for the empty string ("") as the key, and the actual header values are in the msgstr part. This unfortunately means that if you mark an empty string for translation, you will get the entire PO file header back as the "translation". In almost all cases this is probably not what you want. Hence, do not mark empty strings for translation. <br />
<br />
== Get the PO file for your language ==<br />
<br />
Download the .po file for your language from here:<br />
<br />
http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/<br />
<br />
If a .po file for your language does not yet exist, then you will have to get a current copy of the working tree from SVN repository in order to generate a template. This empty template contains only English messages. Information on how to get a the source tree can be found [http://inkscape.org/svn.php here].<br />
<br />
Create your own language file by copying the inkscape.pot file that gets generated when you run make in the codebase. <br />
<br />
1. "./autogen.sh"<br />
2. "./configure"<br />
3. enter the "po" directory: "cd po"<br />
4. generate the current PO template: "intltool-update --pot"<br />
<br />
To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough), <br />
<br />
1. update your local copy of Inkscape in the usual way: "svn update"<br />
2. merge your existing translations into the new POT file (inkscape.pot):<br />
<br />
"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"<br />
<br />
Then you just need to complete the translations in the PO file that was<br />
created in step 6.<br />
<br />
If you want to update ALL .po files in po/, cd there and run:<br />
<br />
make update-po<br />
<br />
== Tools for translators ==<br />
<br />
You can edit PO files from any plain text editor, since they are simple text files. However, many useful tools have been developed to provide a simple experience translating PO files.<br />
<br />
* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)<br />
* kbabel (http://i18n.kde.org/tools/kbabel/)<br />
* gtranslator (http://gtranslator.sourceforge.net/)<br />
* poEdit (http://poedit.sourceforge.net/)<br />
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.<br />
<br />
And last but not least, gettext utils.<br />
<br />
== Submit finished work ==<br />
<br />
Upload your work via the [[SourceForge]] patch tracker:<br />
<br />
http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308<br />
<br />
(Check the Upload checkbox and add your file or patch.)<br />
<br />
Additionally, you may send a message to Inskcape's translators mailing list.<br />
<br />
== A few important things to remember ==<br />
<br />
* Some strings that can ambiguous or having several meanings according to different contexts may have a context prefix : "Context|Amibiguous string". In this case, simply translate "Ambiguous string", the "Context|" string is just a not to translate indication.<br />
* After translating a fuzzy string (one that is marked with a ", fuzzy" comment), please remove its "fuzzy" tag -- otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated. KBabel can do this automatically (see KBabel settings).<br />
* Before publishing your work (after you have finished updating the PO file), please update the "PO-Revision-Date" and "Last-Translator" fields in the PO file header. KBabel can do this automatically.<br />
<br />
== Review ==<br />
This is the start of a list of places to get translation reviews done. So far:<br />
http://www.linux.it/tp/<br />
<br />
== Verification ==<br />
Before submitting your file in the patch tracker, please make sure it is valid:<br />
* Make sure the file is encoded in UTF-8 <br />
* Make sure it is a valid po file and obtain some statistics about it: simply run "msgfmt --statistics -cv translationFile.po" from a command window<br />
* Make sure it is correctly formatted: run "check-markup translationFile.po" from a command window and verify it doesn't output any error message. "check-markup" perl script can be found in the /po directory of Inkscape svn trunk<br />
<br />
== Locale Testing ==<br />
Before reporting that a locale doesn't work in Inkscape, you need to make sure that your system has that locale correctly set up. To do this, you need to generally find a way to run "locale-gen". (Under Debian/Ubuntu this is via "dpkg-reconfigure locales".) If you set both the LANG and LANGUAGE variables and check a regular tool, you should see the correct language for both the libc error (first line) and the tool error (second line):<br />
<br />
LANG=es_MX LANGUAGE=es_MX ls -z<br />
ls: opci&oacute;n inv&aacute;lida -- z<br />
Pruebe `ls --help' para m&aacute;s informaci&oacute;n.<br />
<br />
If it reports the regular C messages, your locale has not been correctly configured, and you'll need to find the right way to run "locale-gen" for your distribution:<br />
<br />
LANG=es_ES LANGUAGE=es_MX ls -z<br />
ls: invalid option -- z<br />
Try `ls --help' for more information.<br />
<br />
== Programmers ==<br />
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.<br />
<br />
= Tutorial Translation =<br />
<br />
Inkscape tutorial sources are in [[DocBook]] format, with illustrations in SVG. If you want to translate one or more tutorials, first download the [[DocBook]] source here:<br />
<br />
http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/<br />
<br />
Each tutorial is in its own subdirectory. You need the *.xml file, for example basic/tutorial-basic.xml. Get it and simply replace all English text in it with the text in your language, preserving all XML markup. See README at that location for some notes on markup.<br />
<br />
* If there's already such a file in SVN, you can edit it instead :) If there's no xml file at the above location but there's a translation of this tutorial in SVG format (in share/tutorials in Inkscape distribution), you'll need to convert it to [[DocBook]] (and probably update). Conversion can be done simply by: select the text blocks of an SVG tutorial in Inkscape, Ctrl+C, and Ctrl+V in your text editor, then add the markup.<br />
<br />
* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish. <br />
<br />
* Do not use symbolic entities like &amp;aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &amp;#225; or simply write your text in UTF-8.<br />
<br />
* Most illustrations don't need translations, so you leave the references to them from English XML intact. If however an illustration has some text that you want to translate, open the illustration file in Inkscape (e.g. basic/basic-f12.svg), edit it as needed, and save under a different name (e.g. basic/basic-f12-es.svg). Then change the filename reference in the XML source appropriately.<br />
<br />
* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.<br />
<br />
* Send the file to Joshua Andler <scislac at users dot sf dot net>, and he'll convert it to SVG and HTML and upload it to SVN and the web site.<br />
<br />
* If after that you want to make any changes, download the file from the above location again, because it may have changed compared to the one you have.<br />
<br />
==Tools==<br />
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html<br />
* Transolution - http://transolution.python-hosting.com/<br />
<br />
===Transforming XML into PO files===<br />
One can also use xml2po to get PO files out of the XML sources, and also transform the PO files back to XML. After you have a PO file, follow the instructions for editing those files below.<br />
<br />
xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).<br />
<br />
Here are some command lines that were used to translate a German tutorial (the de-locale), please adapt accordingly until we nicely integrate this into our Makefiles.<br />
<br />
<pre><br />
## use this at the very beginning, when there is no translation at all:<br />
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml<br />
<br />
## use this when there is a *.de.xml, but you want a de.po:<br />
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml<br />
<br />
## xml2po is not happy when this directory doesn't exist:<br />
mkdir .tmp.basic<br />
<br />
## use this when the tutorial-basic.xml has been updated and you<br />
## want the new stuff in your de.po:<br />
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml<br />
<br />
## use this to create a tutorial-basic.de.xml from your de.po (ScislaC<br />
## will use this file to create the final tutorial SVG file)<br />
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml<br />
<br />
</pre><br />
<br />
= Keyboard and mouse translation =<br />
<br />
= Wiki and web site =<br />
<br />
= Status =<br />
<br />
== Interface translation (po files) ==<br />
<br />
The names and e-mail addresses of contributors and last translator can be found in the header of the po file (simply open it with your favorite text editor)<br />
<br />
Total number of PO files: 38<br />
Total number of strings to translate: 2142<br />
<br />
<br />
'''Amharic''': am.po<br />
<br />
translated: 77 ( '''3%''')<br />
<br />
fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)<br />
<br />
Date of last update: 2003-02-01<br />
<br />
<br />
'''Azerbaijani/Turkic''': az.po<br />
<br />
translated: 63 ( '''2%''')<br />
<br />
fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)<br />
<br />
Date of last update: 2001-12-04<br />
<br />
<br />
'''Belarusian''': be.po<br />
<br />
translated: 158 ( '''7%''')<br />
<br />
fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)<br />
<br />
Date of last update: 2003-07-20<br />
<br />
<br />
'''Catalan''': ca.po<br />
<br />
translated: 2039 ( '''95%''')<br />
<br />
fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)<br />
<br />
Date of last update: 2006-05-08<br />
<br />
<br />
'''Czech''': cs.po<br />
<br />
translated: 2096 ( '''97%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)<br />
<br />
Date of last update: 2006-05-22<br />
<br />
<br />
'''Danish''': da.po<br />
<br />
translated: 100 ( '''4%''')<br />
<br />
fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)<br />
<br />
Date of last update: 2002-01-15<br />
<br />
<br />
'''German''': de.po<br />
<br />
translated: 2116 ( '''98%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)<br />
<br />
Date of last update: 2006-05-23<br />
<br />
<br />
'''Greek''': el.po<br />
<br />
translated: 44 ( '''2%''')<br />
<br />
fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)<br />
<br />
Date of last update: 2001-12-28<br />
<br />
<br />
'''Spanish''': es.po<br />
<br />
translated: 2125 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)<br />
<br />
Date of last update: 2006-05-25<br />
<br />
<br />
'''Spanish/Mexico''': es_MX.po<br />
<br />
translated: 337 ( '''15%''')<br />
<br />
fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)<br />
<br />
Date of last update: 2004-04-05<br />
<br />
<br />
'''Estonian''': et.po<br />
<br />
translated: 9 ( '''0%''')<br />
<br />
fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)<br />
<br />
Date of last update: 2000-04-08<br />
<br />
<br />
'''Basque''': eu.po<br />
<br />
translated: 1548 ( '''72%''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)<br />
<br />
Date of last update: 2006-03-16<br />
<br />
<br />
'''French''': fr.po<br />
<br />
translated: 2126 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)<br />
<br />
Date of last update: 2006-05-27<br />
<br />
<br />
'''Irish''': ga.po<br />
<br />
translated: 14 ( '''0%''')<br />
<br />
fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)<br />
<br />
Date of last update: 2000-08-24<br />
<br />
<br />
'''Galician''': gl.po<br />
<br />
translated: 82 ( '''3%''')<br />
<br />
fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)<br />
<br />
Date of last update: 2001-11-10<br />
<br />
<br />
'''Hungarian''': hu.po<br />
<br />
translated: 1564 ( '''73%''')<br />
<br />
fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)<br />
<br />
Date of last update: 2006-05-29<br />
<br />
<br />
'''Italian''': it.po<br />
<br />
translated: 2008 ( '''93%''')<br />
<br />
fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)<br />
<br />
Date of last update: 2006-05-15<br />
<br />
<br />
'''Japanese''': ja.po<br />
<br />
translated: 1294 ( '''60%''')<br />
<br />
fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)<br />
<br />
Date of last update: 2005-11-16<br />
<br />
<br />
'''Korean''': ko.po<br />
<br />
translated: 180 ( '''8%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)<br />
<br />
Date of last update: 2006-04-10<br />
<br />
<br />
'''Lithuanian''': lt.po<br />
<br />
translated: 1774 ( '''82%''')<br />
<br />
fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)<br />
<br />
Date of last update: 2006-05-02<br />
<br />
<br />
'''mk.po'''<br />
<br />
translated: 0 ( '''0%''')<br />
<br />
fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)<br />
<br />
Date of last update: 2003-06-15<br />
<br />
<br />
'''Norwegian/bokmål dialect''': nb.po<br />
<br />
translated: 144 ( '''6%''')<br />
<br />
fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)<br />
<br />
Date of last update: 2003-01-25<br />
<br />
<br />
'''Dutch: nl.po'''<br />
<br />
translated: 1484 ( '''69%''')<br />
<br />
fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)<br />
<br />
Date of last update: 2005-11-07<br />
<br />
<br />
'''Norwegian/Nynorsk''': nn.po<br />
<br />
translated: 1376 ( '''64%''')<br />
<br />
fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)<br />
<br />
Date of last update: 2005-07-14<br />
<br />
<br />
'''Punjabi''': pa.po<br />
<br />
translated: 912 ( '''42%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)<br />
<br />
Date of last update: 2005-09-11<br />
<br />
<br />
'''Polish''': pl.po<br />
<br />
translated: 1503 ( '''70%''')<br />
<br />
fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)<br />
<br />
Date of last update: 2005-10-29<br />
<br />
<br />
'''Portuguese''': pt.po<br />
<br />
translated: 183 ( '''8%''')<br />
<br />
fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)<br />
<br />
Date of last update: 2003-07-28<br />
<br />
<br />
'''Portuguese/Brazillian''': pt_BR.po<br />
<br />
translated: 1546 ( '''72%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)<br />
<br />
Date of last update: 2006-04-27<br />
<br />
<br />
'''Russian''': ru.po<br />
<br />
translated: 1542 ( '''71%''')<br />
<br />
fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)<br />
<br />
Date of last update: 2005-11-08<br />
<br />
<br />
'''Slovak''': sk.po<br />
<br />
translated: 845 ( '''39%''')<br />
<br />
fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)<br />
<br />
Date of last update: 2005-02-13<br />
<br />
<br />
'''Slovenian''': sl.po<br />
<br />
translated: 2055 ( '''95%''')<br />
<br />
fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)<br />
<br />
Date of last update: 2006-05-12<br />
<br />
<br />
'''Serbian''': sr.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Serbian/Latine''': sr@Latn.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Swedish''': sv.po<br />
<br />
translated: 410 ( '''19%''')<br />
<br />
fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)<br />
<br />
Date of last update: 2005-10-08<br />
<br />
<br />
'''Turkish''': tr.po<br />
<br />
translated: 907 ( '''42%''')<br />
<br />
fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)<br />
<br />
Date of last update: 2005-11-26<br />
<br />
<br />
'''Ukrainian''': uk.po<br />
<br />
translated: 1518 ( '''70%''')<br />
<br />
fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)<br />
<br />
Date of last update: 2005-10-21<br />
<br />
<br />
'''Chinese/Simplified''': zh_CN.po<br />
<br />
translated: 2134 ( '''99%''')<br />
<br />
<br />
fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)<br />
<br />
Date of last update: 2006-05-28<br />
<br />
<br />
'''Chinese/Traditional''': zh_TW.po<br />
<br />
translated: 1550 ( '''72 %''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)<br />
<br />
Date of last update: 2006-03-24<br />
<br />
== Tutorials ==<br />
<br />
* Basic: ca, de, en, es, fr, ja, nn, ru, sl<br />
* Shapes: ca, en, es, fr, ja, sl<br />
* Advanced: ca, en, es, fr, ja, sl<br />
* Tracing: ca, de, en, es, fr, sl<br />
* Calligraphy: ca, en, es, fr, sl<br />
* Elements of design: en, es, fr, sl<br />
* Tips and tricks: de, en, es, fr, sl<br />
<br />
<br />
== Keys (shortcuts) ==<br />
Already available in svn :<br />
* en<br />
* fr<br />
* sl<br />
<br />
<br />
== Windows installer ==<br />
<br />
Already available in svn :<br />
* czech.nsh<br />
* english.nsh<br />
* german.nsh<br />
* italian.nsh<br />
<br />
== Wiki translation ==<br />
<br />
== Website ==<br />
<br />
== News ==</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=TestPage&diff=6566TestPage2006-05-31T09:16:00Z<p>Xaviconde: /* Translatable content */</p>
<hr />
<div>= Introduction =<br />
== Community based, user oriented ==<br />
The translations of the various documents focusing on Inkscape rely on the work of volunteers.<br />
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.<br />
It is very important not to forget that Inkscape is an open source, community based and user oriented software, which implies that software developpers/contributors are generaly users. It also implies that the translation efforts are also user oriented, with a strong focus on interface, user documentation and website.<br />
<br />
== Guidelines/workflow ==<br />
<br />
# '''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 start 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].<br />
# '''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.<br />
# '''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.<br />
# '''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 you are submitting doesn't have syntax errors that would break the building process.<br />
# '''Send a mail on the translator mailing list'''. Your contribution will be reviewed/commited as soon as possible.<br />
<br />
== Best practices ==<br />
<br />
Best case for a good translation : translate from English to your mother tongue.<br />
<br />
Test the behavior of the interface before starting translation<br />
<br />
= Translatable content =<br />
<br />
Inkscape's translation effort covers many areas, from aplication UI itself to web pages and tutorials. This is a summary of all those areas, ordered by priority.<br />
<br />
These tasks, rather than being for hackers only, can be achieved by most software enthusiasts, whether they have a technological background or just plain users. The main requirement is the wish to provide support for Inkscape on your language: the technology required for do that has been developed in a simple approach, and it involves mainly text files and applications used to verify its syntax. Supporting applications exists to make this tasks even easier.<br />
<br />
== User interface ==<br />
<br />
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.<br />
<br />
See section [[#Interface_Translation]] for information on PO files.<br />
<br />
== Tutorials ==<br />
<br />
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.<br />
<br />
See section [[#Tutorial_Translation]] for information on translating tutorials.<br />
<br />
== Windows installer ==<br />
<br />
High value for users, even if the installation process of Inkscape is quite simple, translating the Windows installer helps a lot potential users feeling good with Inkscape.<br />
<br />
== Templates ==<br />
<br />
== Release notes ==<br />
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape<br />
<br />
- give a general overview of the possibilities of the software to potential users<br />
<br />
- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)<br />
<br />
== News displayed on Inkscape web site ==<br />
<br />
== Web pages ==<br />
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English. <br />
<br />
Translation efforts should be first oriented on user documentation.<br />
<br />
See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.<br />
<br />
<br />
== Others ==<br />
Templates (translation and localization)<br />
Text files found in the inkscape directory<br />
...<br />
<br />
= Interface Translation =<br />
<br />
<br />
If you're interested in helping with providing interface translation for Inkscape,<br />
here are a few links to help you getting started:<br />
<br />
http://www.gtkmm.org/gtkmm2/docs/tutorial/html/ch20s03.html<br />
http://developer.gnome.org/projects/gtp/l10n-guide/<br />
http://developer.gnome.org/projects/gtp/style-guides/<br />
http://developer.gnome.org/doc/tutorials/gnome-i18n/developer.html<br />
<br />
Download the .po file for your language from here:<br />
<br />
http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/<br />
<br />
If a .po file for your language does not yet exist, then create one<br />
by copying the inkscape.pot file that gets generated when you run make<br />
in the codebase.<br />
<br />
Edit the file to add or correct translations of the English strings, and<br />
then upload your work via the [[SourceForge]] patch tracker:<br />
<br />
http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308<br />
<br />
(Check the Upload checkbox and add your file or patch.)<br />
<br />
<br />
<br />
Here's how to make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough):<br />
<br />
1. update your local copy of Inkscape in the usual way: "svn update"<br />
2. "./autogen.sh"<br />
3. "./configure"<br />
4. enter the "po" directory: "cd po"<br />
5. generate the current PO template: "intltool-update --pot"<br />
6. merge your existing translations into the new POT file (inkscape.pot):<br />
"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"<br />
<br />
Then you just need to complete the translations in the PO file that was<br />
created in step 6.<br />
<br />
<br />
If you want to update ALL .po files in po/, cd there and run:<br />
<br />
make update-po<br />
<br />
<br />
== Tools for translators ==<br />
* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)<br />
* kbabel (http://i18n.kde.org/tools/kbabel/)<br />
* gtranslator (http://gtranslator.sourceforge.net/)<br />
* poEdit (http://poedit.sourceforge.net/)<br />
<br />
== A few important things to remember ==<br />
* Some strings that can ambiguous or having several meanings according to different contexts may have a context prefix : "Context|Amibiguous string". In this case, simply translate "Ambiguous string", the "Context|" string is just a not to translate indication.<br />
* After translating a fuzzy string (one that is marked with a ", fuzzy" comment), please remove its "fuzzy" tag -- otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated. KBabel can do this automatically (see KBabel settings).<br />
* Before publishing your work (after you have finished updating the PO file), please update the "PO-Revision-Date" and "Last-Translator" fields in the PO file header. KBabel can do this automatically.<br />
<br />
== Review ==<br />
This is the start of a list of places to get translation reviews done. So far:<br />
http://www.linux.it/tp/<br />
<br />
== Verification ==<br />
Before submitting your file in the patch tracker, please make sure it is valid:<br />
* Make sure the file is encoded in UTF-8 <br />
* Make sure it is a valid po file and obtain some statistics about it: simply run "msgfmt --statistics -cv translationFile.po" from a command window<br />
* Make sure it is correctly formatted: run "check-markup translationFile.po" from a command window and verify it doesn't output any error message. "check-markup" perl script can be found in the /po directory of Inkscape svn trunk<br />
<br />
== Locale Testing ==<br />
Before reporting that a locale doesn't work in Inkscape, you need to make sure that your system has that locale correctly set up. To do this, you need to generally find a way to run "locale-gen". (Under Debian/Ubuntu this is via "dpkg-reconfigure locales".) If you set both the LANG and LANGUAGE variables and check a regular tool, you should see the correct language for both the libc error (first line) and the tool error (second line):<br />
<br />
LANG=es_MX LANGUAGE=es_MX ls -z<br />
ls: opci&oacute;n inv&aacute;lida -- z<br />
Pruebe `ls --help' para m&aacute;s informaci&oacute;n.<br />
<br />
If it reports the regular C messages, your locale has not been correctly configured, and you'll need to find the right way to run "locale-gen" for your distribution:<br />
<br />
LANG=es_ES LANGUAGE=es_MX ls -z<br />
ls: invalid option -- z<br />
Try `ls --help' for more information.<br />
<br />
== Programmers ==<br />
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.<br />
<br />
<br />
= Tutorial Translation =<br />
<br />
Inkscape tutorial sources are in [[DocBook]] format, with illustrations in SVG. If you want to translate one or more tutorials, first download the [[DocBook]] source here:<br />
<br />
http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/<br />
<br />
Each tutorial is in its own subdirectory. You need the *.xml file, for example basic/tutorial-basic.xml. Get it and simply replace all English text in it with the text in your language, preserving all XML markup. See README at that location for some notes on markup.<br />
<br />
* If there's already such a file in SVN, you can edit it instead :) If there's no xml file at the above location but there's a translation of this tutorial in SVG format (in share/tutorials in Inkscape distribution), you'll need to convert it to [[DocBook]] (and probably update). Conversion can be done simply by: select the text blocks of an SVG tutorial in Inkscape, Ctrl+C, and Ctrl+V in your text editor, then add the markup.<br />
<br />
* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish. <br />
<br />
* Do not use symbolic entities like &amp;aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &amp;#225; or simply write your text in UTF-8.<br />
<br />
* Most illustrations don't need translations, so you leave the references to them from English XML intact. If however an illustration has some text that you want to translate, open the illustration file in Inkscape (e.g. basic/basic-f12.svg), edit it as needed, and save under a different name (e.g. basic/basic-f12-es.svg). Then change the filename reference in the XML source appropriately.<br />
<br />
* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.<br />
<br />
* Send the file to Joshua Andler <scislac at users dot sf dot net>, and he'll convert it to SVG and HTML and upload it to SVN and the web site.<br />
<br />
* If after that you want to make any changes, download the file from the above location again, because it may have changed compared to the one you have.<br />
<br />
==Tools==<br />
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html<br />
* Transolution - http://transolution.python-hosting.com/<br />
<br />
===Transforming XML into PO files===<br />
One can also use xml2po to get PO files out of the XML sources, and also transform the PO files back to XML. After you have a PO file, follow the instructions for editing those files below.<br />
<br />
xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).<br />
<br />
Here are some command lines that were used to translate a German tutorial (the de-locale), please adapt accordingly until we nicely integrate this into our Makefiles.<br />
<br />
<pre><br />
## use this at the very beginning, when there is no translation at all:<br />
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml<br />
<br />
## use this when there is a *.de.xml, but you want a de.po:<br />
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml<br />
<br />
## xml2po is not happy when this directory doesn't exist:<br />
mkdir .tmp.basic<br />
<br />
## use this when the tutorial-basic.xml has been updated and you<br />
## want the new stuff in your de.po:<br />
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml<br />
<br />
## use this to create a tutorial-basic.de.xml from your de.po (ScislaC<br />
## will use this file to create the final tutorial SVG file)<br />
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml<br />
<br />
</pre><br />
<br />
= Keyboard and mouse translation =<br />
<br />
= Wiki and web site =<br />
<br />
= Status =<br />
<br />
== Interface translation (po files) ==<br />
<br />
The names and e-mail addresses of contributors and last translator can be found in the header of the po file (simply open it with your favorite text editor)<br />
<br />
Total number of PO files: 38<br />
Total number of strings to translate: 2142<br />
<br />
<br />
'''Amharic''': am.po<br />
<br />
translated: 77 ( '''3%''')<br />
<br />
fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)<br />
<br />
Date of last update: 2003-02-01<br />
<br />
<br />
'''Azerbaijani/Turkic''': az.po<br />
<br />
translated: 63 ( '''2%''')<br />
<br />
fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)<br />
<br />
Date of last update: 2001-12-04<br />
<br />
<br />
'''Belarusian''': be.po<br />
<br />
translated: 158 ( '''7%''')<br />
<br />
fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)<br />
<br />
Date of last update: 2003-07-20<br />
<br />
<br />
'''Catalan''': ca.po<br />
<br />
translated: 2039 ( '''95%''')<br />
<br />
fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)<br />
<br />
Date of last update: 2006-05-08<br />
<br />
<br />
'''Czech''': cs.po<br />
<br />
translated: 2096 ( '''97%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)<br />
<br />
Date of last update: 2006-05-22<br />
<br />
<br />
'''Danish''': da.po<br />
<br />
translated: 100 ( '''4%''')<br />
<br />
fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)<br />
<br />
Date of last update: 2002-01-15<br />
<br />
<br />
'''German''': de.po<br />
<br />
translated: 2116 ( '''98%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)<br />
<br />
Date of last update: 2006-05-23<br />
<br />
<br />
'''Greek''': el.po<br />
<br />
translated: 44 ( '''2%''')<br />
<br />
fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)<br />
<br />
Date of last update: 2001-12-28<br />
<br />
<br />
'''Spanish''': es.po<br />
<br />
translated: 2125 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)<br />
<br />
Date of last update: 2006-05-25<br />
<br />
<br />
'''Spanish/Mexico''': es_MX.po<br />
<br />
translated: 337 ( '''15%''')<br />
<br />
fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)<br />
<br />
Date of last update: 2004-04-05<br />
<br />
<br />
'''Estonian''': et.po<br />
<br />
translated: 9 ( '''0%''')<br />
<br />
fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)<br />
<br />
Date of last update: 2000-04-08<br />
<br />
<br />
'''Basque''': eu.po<br />
<br />
translated: 1548 ( '''72%''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)<br />
<br />
Date of last update: 2006-03-16<br />
<br />
<br />
'''French''': fr.po<br />
<br />
translated: 2126 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)<br />
<br />
Date of last update: 2006-05-27<br />
<br />
<br />
'''Irish''': ga.po<br />
<br />
translated: 14 ( '''0%''')<br />
<br />
fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)<br />
<br />
Date of last update: 2000-08-24<br />
<br />
<br />
'''Galician''': gl.po<br />
<br />
translated: 82 ( '''3%''')<br />
<br />
fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)<br />
<br />
Date of last update: 2001-11-10<br />
<br />
<br />
'''Hungarian''': hu.po<br />
<br />
translated: 1564 ( '''73%''')<br />
<br />
fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)<br />
<br />
Date of last update: 2006-05-29<br />
<br />
<br />
'''Italian''': it.po<br />
<br />
translated: 2008 ( '''93%''')<br />
<br />
fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)<br />
<br />
Date of last update: 2006-05-15<br />
<br />
<br />
'''Japanese''': ja.po<br />
<br />
translated: 1294 ( '''60%''')<br />
<br />
fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)<br />
<br />
Date of last update: 2005-11-16<br />
<br />
<br />
'''Korean''': ko.po<br />
<br />
translated: 180 ( '''8%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)<br />
<br />
Date of last update: 2006-04-10<br />
<br />
<br />
'''Lithuanian''': lt.po<br />
<br />
translated: 1774 ( '''82%''')<br />
<br />
fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)<br />
<br />
Date of last update: 2006-05-02<br />
<br />
<br />
'''mk.po'''<br />
<br />
translated: 0 ( '''0%''')<br />
<br />
fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)<br />
<br />
Date of last update: 2003-06-15<br />
<br />
<br />
'''Norwegian/bokmål dialect''': nb.po<br />
<br />
translated: 144 ( '''6%''')<br />
<br />
fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)<br />
<br />
Date of last update: 2003-01-25<br />
<br />
<br />
'''Dutch: nl.po'''<br />
<br />
translated: 1484 ( '''69%''')<br />
<br />
fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)<br />
<br />
Date of last update: 2005-11-07<br />
<br />
<br />
'''Norwegian/Nynorsk''': nn.po<br />
<br />
translated: 1376 ( '''64%''')<br />
<br />
fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)<br />
<br />
Date of last update: 2005-07-14<br />
<br />
<br />
'''Punjabi''': pa.po<br />
<br />
translated: 912 ( '''42%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)<br />
<br />
Date of last update: 2005-09-11<br />
<br />
<br />
'''Polish''': pl.po<br />
<br />
translated: 1503 ( '''70%''')<br />
<br />
fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)<br />
<br />
Date of last update: 2005-10-29<br />
<br />
<br />
'''Portuguese''': pt.po<br />
<br />
translated: 183 ( '''8%''')<br />
<br />
fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)<br />
<br />
Date of last update: 2003-07-28<br />
<br />
<br />
'''Portuguese/Brazillian''': pt_BR.po<br />
<br />
translated: 1546 ( '''72%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)<br />
<br />
Date of last update: 2006-04-27<br />
<br />
<br />
'''Russian''': ru.po<br />
<br />
translated: 1542 ( '''71%''')<br />
<br />
fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)<br />
<br />
Date of last update: 2005-11-08<br />
<br />
<br />
'''Slovak''': sk.po<br />
<br />
translated: 845 ( '''39%''')<br />
<br />
fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)<br />
<br />
Date of last update: 2005-02-13<br />
<br />
<br />
'''Slovenian''': sl.po<br />
<br />
translated: 2055 ( '''95%''')<br />
<br />
fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)<br />
<br />
Date of last update: 2006-05-12<br />
<br />
<br />
'''Serbian''': sr.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Serbian/Latine''': sr@Latn.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Swedish''': sv.po<br />
<br />
translated: 410 ( '''19%''')<br />
<br />
fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)<br />
<br />
Date of last update: 2005-10-08<br />
<br />
<br />
'''Turkish''': tr.po<br />
<br />
translated: 907 ( '''42%''')<br />
<br />
fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)<br />
<br />
Date of last update: 2005-11-26<br />
<br />
<br />
'''Ukrainian''': uk.po<br />
<br />
translated: 1518 ( '''70%''')<br />
<br />
fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)<br />
<br />
Date of last update: 2005-10-21<br />
<br />
<br />
'''Chinese/Simplified''': zh_CN.po<br />
<br />
translated: 2134 ( '''99%''')<br />
<br />
<br />
fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)<br />
<br />
Date of last update: 2006-05-28<br />
<br />
<br />
'''Chinese/Traditional''': zh_TW.po<br />
<br />
translated: 1550 ( '''72 %''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)<br />
<br />
Date of last update: 2006-03-24<br />
<br />
== Tutorials ==<br />
<br />
* Basic: ca, de, es, fr, ja, nn, ru, sl<br />
* Shapes: ca, es, fr, ja, sl<br />
* Advanced: ca, es, fr, ja, sl<br />
* Tracing: ca, de, es, fr, sl<br />
* Calligraphy: ca, es, fr, sl<br />
* Elements of design: es, fr, sl<br />
* Tips and tricks: de, es, fr, sl<br />
<br />
<br />
== Windows installer ==<br />
<br />
Already available in svn :<br />
* czech.nsh<br />
* english.nsh<br />
* german.nsh<br />
* italian.nsh</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=TestPage&diff=6551TestPage2006-05-30T17:24:13Z<p>Xaviconde: /* Translatable content */</p>
<hr />
<div>= Introduction =<br />
== Community based, user oriented ==<br />
The translations of the various documents focusing on Inkscape rely on the work of volunteers.<br />
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.<br />
It is very important not to forget that Inkscape is an open source, community based and user oriented software, which implies that software developpers/contributors are generaly users. It also implies that the translation efforts are also user oriented, with a strong focus on interface, user documentation and website.<br />
<br />
== Guidelines/workflow ==<br />
<br />
# '''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 start 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].<br />
# '''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.<br />
# '''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.<br />
# '''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 you are submitting doesn't have syntax errors that would break the building process.<br />
# '''Send a mail on the translator mailing list'''. Your contribution will be reviewed/commited as soon as possible.<br />
<br />
== Best practices ==<br />
<br />
Best case for a good translation : translate from English to your mother tongue.<br />
<br />
Test the behavior of the interface before starting translation<br />
<br />
= Translatable content =<br />
<br />
Inkscape's translation effort covers many areas, from aplication UI itself to web pages and tutorials. This is a summary of all those areas, ordered by priority.<br />
<br />
== User interface ==<br />
<br />
PO files contain the strings for the Inkscape user interface (main software and extentions). That's why it is obviously the translation to start with.<br />
<br />
See section [[#Interface_Translation]] for information on PO files.<br />
<br />
== tutorials ==<br />
Tutorials are documents of very high value for users.<br />
<br />
== Windows installer ==<br />
High value for users, even if the installation process of Inkscape is quite simple, translating the Windows installer helps a lot potential users feeling good with Inkscape.<br />
<br />
== Release notes ==<br />
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape<br />
<br />
- give a general overview of the possibilities of the software to potential users<br />
<br />
- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)<br />
<br />
== Web pages ==<br />
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English. <br />
<br />
Translation efforts should be first oriented on user documentation.<br />
<br />
See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.<br />
<br />
<br />
== Others ==<br />
Templates (translation and localization)<br />
Text files found in the inkscape directory<br />
...<br />
<br />
= Interface Translation =<br />
<br />
<br />
If you're interested in helping with providing interface translation for Inkscape,<br />
here are a few links to help you getting started:<br />
<br />
http://www.gtkmm.org/gtkmm2/docs/tutorial/html/ch20s03.html<br />
http://developer.gnome.org/projects/gtp/l10n-guide/<br />
http://developer.gnome.org/projects/gtp/style-guides/<br />
http://developer.gnome.org/doc/tutorials/gnome-i18n/developer.html<br />
<br />
Download the .po file for your language from here:<br />
<br />
http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/<br />
<br />
If a .po file for your language does not yet exist, then create one<br />
by copying the inkscape.pot file that gets generated when you run make<br />
in the codebase.<br />
<br />
Edit the file to add or correct translations of the English strings, and<br />
then upload your work via the [[SourceForge]] patch tracker:<br />
<br />
http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308<br />
<br />
(Check the Upload checkbox and add your file or patch.)<br />
<br />
<br />
<br />
Here's how to make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough):<br />
<br />
1. update your local copy of Inkscape in the usual way: "svn update"<br />
2. "./autogen.sh"<br />
3. "./configure"<br />
4. enter the "po" directory: "cd po"<br />
5. generate the current PO template: "intltool-update --pot"<br />
6. merge your existing translations into the new POT file (inkscape.pot):<br />
"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"<br />
<br />
Then you just need to complete the translations in the PO file that was<br />
created in step 6.<br />
<br />
<br />
If you want to update ALL .po files in po/, cd there and run:<br />
<br />
make update-po<br />
<br />
<br />
== Tools for translators ==<br />
* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)<br />
* kbabel (http://i18n.kde.org/tools/kbabel/)<br />
* gtranslator (http://gtranslator.sourceforge.net/)<br />
* poEdit (http://poedit.sourceforge.net/)<br />
<br />
== A few important things to remember ==<br />
* Some strings that can ambiguous or having several meanings according to different contexts may have a context prefix : "Context|Amibiguous string". In this case, simply translate "Ambiguous string", the "Context|" string is just a not to translate indication.<br />
* After translating a fuzzy string (one that is marked with a ", fuzzy" comment), please remove its "fuzzy" tag -- otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated. KBabel can do this automatically (see KBabel settings).<br />
* Before publishing your work (after you have finished updating the PO file), please update the "PO-Revision-Date" and "Last-Translator" fields in the PO file header. KBabel can do this automatically.<br />
<br />
== Review ==<br />
This is the start of a list of places to get translation reviews done. So far:<br />
http://www.linux.it/tp/<br />
<br />
== Locale Testing ==<br />
Before reporting that a locale doesn't work in Inkscape, you need to make sure that your system has that locale correctly set up. To do this, you need to generally find a way to run "locale-gen". (Under Debian/Ubuntu this is via "dpkg-reconfigure locales".) If you set both the LANG and LANGUAGE variables and check a regular tool, you should see the correct language for both the libc error (first line) and the tool error (second line):<br />
<br />
LANG=es_MX LANGUAGE=es_MX ls -z<br />
ls: opci&oacute;n inv&aacute;lida -- z<br />
Pruebe `ls --help' para m&aacute;s informaci&oacute;n.<br />
<br />
If it reports the regular C messages, your locale has not been correctly configured, and you'll need to find the right way to run "locale-gen" for your distribution:<br />
<br />
LANG=es_ES LANGUAGE=es_MX ls -z<br />
ls: invalid option -- z<br />
Try `ls --help' for more information.<br />
<br />
== Programmers ==<br />
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.<br />
<br />
<br />
= Tutorial Translation =<br />
<br />
Inkscape tutorial sources are in [[DocBook]] format, with illustrations in SVG. If you want to translate one or more tutorials, first download the [[DocBook]] source here:<br />
<br />
http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/<br />
<br />
Each tutorial is in its own subdirectory. You need the *.xml file, for example basic/tutorial-basic.xml. Get it and simply replace all English text in it with the text in your language, preserving all XML markup. See README at that location for some notes on markup.<br />
<br />
* If there's already such a file in CVS, you can edit it instead :) If there's no xml file at the above location but there's a translation of this tutorial in SVG format (in share/tutorials in Inkscape distribution), you'll need to convert it to [[DocBook]] (and probably update). Conversion can be done simply by: select the text blocks of an SVG tutorial in Inkscape, Ctrl+C, and Ctrl+V in your text editor, then add the markup.<br />
<br />
* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish. <br />
<br />
* Do not use symbolic entities like &amp;aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &amp;#225; or simply write your text in UTF-8.<br />
<br />
* Most illustrations don't need translations, so you leave the references to them from English XML intact. If however an illustration has some text that you want to translate, open the illustration file in Inkscape (e.g. basic/basic-f12.svg), edit it as needed, and save under a different name (e.g. basic/basic-f12-es.svg). Then change the filename reference in the XML source appropriately.<br />
<br />
* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.<br />
<br />
* Send the file to Joshua Andler <scislac at users dot sf dot net>, and he'll convert it to SVG and HTML and upload it to SVN and the web site.<br />
<br />
* If after that you want to make any changes, download the file from the above location again, because it may have changed compared to the one you have.<br />
<br />
==Tools==<br />
* xml2po in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/)<br />
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html<br />
* Transolution - http://transolution.python-hosting.com/<br />
<br />
= Keyboard and mouse translation =<br />
<br />
= Wiki and web site =<br />
<br />
= Status and contacts =<br />
<br />
Total number of PO files: 38<br />
Total number of strings to translate: 2142<br />
<br />
<br />
'''Amharic''': am.po<br />
<br />
translated: 77 ( '''3%''')<br />
<br />
fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)<br />
<br />
Last translator: Ge'ez Frontier Foundation <locales@geez.org><br />
Date of last update: 2003-02-01<br />
<br />
<br />
'''Azerbaijani/Turkic''': az.po<br />
<br />
translated: 63 ( '''2%''')<br />
<br />
fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)<br />
<br />
Last translator: Vasif İsmayıloğlu MD <azerb_linux@hotmail.com><br />
Date of last update: 2001-12-04<br />
<br />
<br />
'''Belarusian''': be.po<br />
<br />
translated: 158 ( '''7%''')<br />
<br />
fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)<br />
<br />
Last translator: Vital Khilko <dojlid@mova.org><br />
Date of last update: 2003-07-20<br />
<br />
<br />
'''Catalan''': ca.po<br />
<br />
translated: 2039 ( '''95%''')<br />
<br />
fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)<br />
<br />
Last translator: Xavier Conde Rueda <xavi.conde@gmail.com><br />
Date of last update: 2006-05-08<br />
<br />
<br />
'''Czech''': cs.po<br />
<br />
translated: 2096 ( '''97%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)<br />
<br />
Last translator: Josef Vybíral <josef.vybiral@gmail.com><br />
Date of last update: 2006-05-22<br />
<br />
<br />
'''Danish''': da.po<br />
<br />
translated: 100 ( '''4%''')<br />
<br />
fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)<br />
<br />
Last translator: Keld Simonsen <keld@dkuug.dk><br />
Date of last update: 2002-01-15<br />
<br />
<br />
'''German''': de.po<br />
<br />
translated: 2116 ( '''98%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)<br />
<br />
Last translator: Colin Marquardt <colin@marquardt-home.de><br />
Date of last update: 2006-05-23<br />
<br />
<br />
'''Greek''': el.po<br />
<br />
translated: 44 ( '''2%''')<br />
<br />
fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)<br />
<br />
Last translator: Simos Xenitellis <simos@hellug.gr><br />
Date of last update: 2001-12-28<br />
<br />
<br />
'''Spanish''': es.po<br />
<br />
translated: 2125 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)<br />
<br />
Last translator: Lucas Vieites Fariña<lucas@asixinformatica.com><br />
Date of last update: 2006-05-25<br />
<br />
<br />
'''Spanish/Mexico''': es_MX.po<br />
<br />
translated: 337 ( '''15%''')<br />
<br />
fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)<br />
<br />
Last translator: Daniel Díaz <yosoy@danieldiaz.org><br />
Date of last update: 2004-04-05<br />
<br />
<br />
'''Estonian''': et.po<br />
<br />
translated: 9 ( '''0%''')<br />
<br />
fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)<br />
<br />
Last translator: Lauris Kaplinski <lauris@ariman.ee><br />
Date of last update: 2000-04-08<br />
<br />
<br />
'''Basque''': eu.po<br />
<br />
translated: 1548 ( '''72%''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)<br />
<br />
Last translator: Iñaki Larrañaga <dooteo@euskalgnu.org><br />
Date of last update: 2006-03-16<br />
<br />
<br />
'''French''': fr.po<br />
<br />
translated: 2126 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)<br />
<br />
Last translator: matiphas <matiphas@free.fr><br />
Date of last update: 2006-05-27<br />
<br />
<br />
'''Irish''': ga.po<br />
<br />
translated: 14 ( '''0%''')<br />
<br />
fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)<br />
<br />
Last translator: Alastair McKinstry <mckinstry@computer.org><br />
Date of last update: 2000-08-24<br />
<br />
<br />
'''Galician''': gl.po<br />
<br />
translated: 82 ( '''3%''')<br />
<br />
fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)<br />
<br />
Last translator: Francisco Xosé Vázquez Grandal <fxvazquez@arrakis.es><br />
Date of last update: 2001-11-10<br />
<br />
<br />
'''Hungarian''': hu.po<br />
<br />
translated: 1564 ( '''73%''')<br />
<br />
fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)<br />
<br />
Last translator: Arpad Biro <biro_arpad@yahoo.com><br />
Date of last update: 2006-05-29<br />
<br />
<br />
'''Italian''': it.po<br />
<br />
translated: 2008 ( '''93%''')<br />
<br />
fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)<br />
<br />
Last translator: Luca Bruno <luca.br@uno.it><br />
Date of last update: 2006-05-15<br />
<br />
<br />
'''Japanese''': ja.po<br />
<br />
translated: 1294 ( '''60%''')<br />
<br />
fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)<br />
<br />
Last translator: shivaken <shivaken@owls-nest.net><br />
Date of last update: 2005-11-16<br />
<br />
<br />
'''Korean''': ko.po<br />
<br />
translated: 180 ( '''8%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)<br />
<br />
Last translator: Kitae <bluetux@gmail.com><br />
Date of last update: 2006-04-10<br />
<br />
<br />
'''Lithuanian''': lt.po<br />
<br />
translated: 1774 ( '''82%''')<br />
<br />
fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)<br />
<br />
Last translator: Andrius R. <knutux@gmail.com><br />
Date of last update: 2006-05-02<br />
<br />
<br />
'''mk.po'''<br />
<br />
translated: 0 ( '''0%''')<br />
<br />
fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)<br />
<br />
Last translator: <br />
Date of last update: 2003-06-15<br />
<br />
<br />
'''Norwegian/bokmål dialect''': nb.po<br />
<br />
translated: 144 ( '''6%''')<br />
<br />
fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)<br />
<br />
Last translator: Kjartan Maraas <kmaraas@gnome.org><br />
Date of last update: 2003-01-25<br />
<br />
<br />
'''Dutch: nl.po'''<br />
<br />
translated: 1484 ( '''69%''')<br />
<br />
fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)<br />
<br />
Last translator: Jeroen van der Vegt <ajvdvegt (at) 123mail.org><br />
Date of last update: 2005-11-07<br />
<br />
<br />
'''Norwegian/Nynorsk''': nn.po<br />
<br />
translated: 1376 ( '''64%''')<br />
<br />
fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)<br />
<br />
Last translator: Karl Ove Hufthammer <karl@huftis.org><br />
Date of last update: 2005-07-14<br />
<br />
<br />
'''Punjabi''': pa.po<br />
<br />
translated: 912 ( '''42%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)<br />
<br />
Last translator: Amanpreet Singh Brar <amanpreetalam@yahoo.com><br />
Date of last update: 2005-09-11<br />
<br />
<br />
'''Polish''': pl.po<br />
<br />
translated: 1503 ( '''70%''')<br />
<br />
fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)<br />
<br />
Last translator: Przemysław Loesch <p_loesch@poczta.onet.pl><br />
Date of last update: 2005-10-29<br />
<br />
<br />
'''Portuguese''': pt.po<br />
<br />
translated: 183 ( '''8%''')<br />
<br />
fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)<br />
<br />
Last translator: Duarte Loreto <happyguy_pt@hotmail.com><br />
Date of last update: 2003-07-28<br />
<br />
<br />
'''Portuguese/Brazillian''': pt_BR.po<br />
<br />
translated: 1546 ( '''72%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)<br />
<br />
Last translator: Antônio Cláudio (LedStyle) <ledstyle@gmail.com><br />
Date of last update: 2006-04-27<br />
<br />
<br />
'''Russian''': ru.po<br />
<br />
translated: 1542 ( '''71%''')<br />
<br />
fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)<br />
<br />
Last translator: Alexandre Prokoudine <alexandre.prokoudine@gmail.com><br />
Date of last update: 2005-11-08<br />
<br />
<br />
'''Slovak''': sk.po<br />
<br />
translated: 845 ( '''39%''')<br />
<br />
fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)<br />
<br />
Last translator: Zdenko Podobný <zdpo@mailbox.sk><br />
Date of last update: 2005-02-13<br />
<br />
<br />
'''Slovenian''': sl.po<br />
<br />
translated: 2055 ( '''95%''')<br />
<br />
fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)<br />
<br />
Last translator: Martin Srebotnjak <miles@filmsi.net><br />
Date of last update: 2006-05-12<br />
<br />
<br />
'''Serbian''': sr.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Last translator: ÐлекÑандар Урошевић <urke@users.sourceforge.net><br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Serbian/Latine''': sr@Latn.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Last translator: Aleksandar Urošević <urke@users.sourceforge.net><br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Swedish''': sv.po<br />
<br />
translated: 410 ( '''19%''')<br />
<br />
fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)<br />
<br />
Last translator: Mattias Hultgren <mattias_hultgren@tele2.se><br />
Date of last update: 2005-10-08<br />
<br />
<br />
'''Turkish''': tr.po<br />
<br />
translated: 907 ( '''42%''')<br />
<br />
fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)<br />
<br />
Last translator: Serdar Soytetir <sendirom@gmail.com><br />
Date of last update: 2005-11-26<br />
<br />
<br />
'''Ukrainian''': uk.po<br />
<br />
translated: 1518 ( '''70%''')<br />
<br />
fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)<br />
<br />
Last translator: Maxim V. Dziumanenko <mvd@mylinux.com.ua><br />
Date of last update: 2005-10-21<br />
<br />
<br />
'''Chinese/Simplified''': zh_CN.po<br />
<br />
translated: 2134 ( '''99%''')<br />
<br />
fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)<br />
<br />
Last translator: Chris Jia <Chrisjiasl@gmail.com><br />
Date of last update: 2006-05-28<br />
<br />
<br />
'''Chinese/Traditional''': zh_TW.po<br />
<br />
translated: 1550 ( '''72 %''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)<br />
<br />
Last translator: Wei-Lun Chao <william.chao@ossii.com.tw><br />
Date of last update: 2006-03-24</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=TestPage&diff=6545TestPage2006-05-30T12:44:41Z<p>Xaviconde: /* Guidelines/workflow */</p>
<hr />
<div>= Introduction =<br />
== Community based, user oriented ==<br />
The translations of the various documents focusing on Inkscape rely on the work of volunteers.<br />
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.<br />
It is very important not to forget that Inkscape is an open source, community based and user oriented software, which implies that software developpers/contributors are generaly users. It also implies that the translation efforts are also user oriented, with a strong focus on interface, user documentation and website.<br />
<br />
== Guidelines/workflow ==<br />
<br />
# '''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 start 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].<br />
# '''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.<br />
# '''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.<br />
# '''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 you are submitting doesn't have syntax errors that would break the building process.<br />
# '''Send a mail on the translator mailing list'''. Your contribution will be reviewed/commited as soon as possible.<br />
<br />
== Best practices ==<br />
<br />
Best case for a good translation : translate from English to your mother tongue.<br />
<br />
Test the behavior of the interface before starting translation<br />
<br />
= Translatable content =<br />
<br />
== po files ==<br />
The po files contain the strings for the Inkscape Interface (main software and extentions).<br />
<br />
That's why it is obviously the translation to start with.<br />
<br />
== tutorials ==<br />
Tutorials are documents of very high value for users.<br />
<br />
== Windows installer ==<br />
High value for users, even if the installation process of Inkscape is quite simple, translating the Windows installer helps a lot potential users feeling good with Inkscape.<br />
<br />
== Release notes ==<br />
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape<br />
<br />
- give a general overview of the possibilities of the software to potential users<br />
<br />
- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)<br />
<br />
== Web pages ==<br />
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English. <br />
<br />
Translation efforts should be first oriented on user documentation.<br />
<br />
See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.<br />
<br />
<br />
== Others ==<br />
Templates (translation and localization)<br />
<br />
...<br />
<br />
= Interface Translation =<br />
<br />
<br />
If you're interested in helping with providing interface translation for Inkscape,<br />
here are a few links to help you getting started:<br />
<br />
http://www.gtkmm.org/gtkmm2/docs/tutorial/html/ch20s03.html<br />
http://developer.gnome.org/projects/gtp/l10n-guide/<br />
http://developer.gnome.org/projects/gtp/style-guides/<br />
http://developer.gnome.org/doc/tutorials/gnome-i18n/developer.html<br />
<br />
Download the .po file for your language from here:<br />
<br />
http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/<br />
<br />
If a .po file for your language does not yet exist, then create one<br />
by copying the inkscape.pot file that gets generated when you run make<br />
in the codebase.<br />
<br />
Edit the file to add or correct translations of the English strings, and<br />
then upload your work via the [[SourceForge]] patch tracker:<br />
<br />
http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308<br />
<br />
(Check the Upload checkbox and add your file or patch.)<br />
<br />
<br />
<br />
Here's how to make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough):<br />
<br />
1. update your local copy of Inkscape in the usual way: "svn update"<br />
2. "./autogen.sh"<br />
3. "./configure"<br />
4. enter the "po" directory: "cd po"<br />
5. generate the current PO template: "intltool-update --pot"<br />
6. merge your existing translations into the new POT file (inkscape.pot):<br />
"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"<br />
<br />
Then you just need to complete the translations in the PO file that was<br />
created in step 6.<br />
<br />
<br />
If you want to update ALL .po files in po/, cd there and run:<br />
<br />
make update-po<br />
<br />
<br />
== Tools for translators ==<br />
* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)<br />
* kbabel (http://i18n.kde.org/tools/kbabel/)<br />
* gtranslator (http://gtranslator.sourceforge.net/)<br />
* poEdit (http://poedit.sourceforge.net/)<br />
<br />
== A few important things to remember ==<br />
* Some strings that can ambiguous or having several meanings according to different contexts may have a context prefix : "Context|Amibiguous string". In this case, simply translate "Ambiguous string", the "Context|" string is just a not to translate indication.<br />
* After translating a fuzzy string (one that is marked with a ", fuzzy" comment), please remove its "fuzzy" tag -- otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated. KBabel can do this automatically (see KBabel settings).<br />
* Before publishing your work (after you have finished updating the PO file), please update the "PO-Revision-Date" and "Last-Translator" fields in the PO file header. KBabel can do this automatically.<br />
<br />
== Review ==<br />
This is the start of a list of places to get translation reviews done. So far:<br />
http://www.linux.it/tp/<br />
<br />
== Locale Testing ==<br />
Before reporting that a locale doesn't work in Inkscape, you need to make sure that your system has that locale correctly set up. To do this, you need to generally find a way to run "locale-gen". (Under Debian/Ubuntu this is via "dpkg-reconfigure locales".) If you set both the LANG and LANGUAGE variables and check a regular tool, you should see the correct language for both the libc error (first line) and the tool error (second line):<br />
<br />
LANG=es_MX LANGUAGE=es_MX ls -z<br />
ls: opci&oacute;n inv&aacute;lida -- z<br />
Pruebe `ls --help' para m&aacute;s informaci&oacute;n.<br />
<br />
If it reports the regular C messages, your locale has not been correctly configured, and you'll need to find the right way to run "locale-gen" for your distribution:<br />
<br />
LANG=es_ES LANGUAGE=es_MX ls -z<br />
ls: invalid option -- z<br />
Try `ls --help' for more information.<br />
<br />
== Programmers ==<br />
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.<br />
<br />
<br />
= Tutorial Translation =<br />
<br />
Inkscape tutorial sources are in [[DocBook]] format, with illustrations in SVG. If you want to translate one or more tutorials, first download the [[DocBook]] source here:<br />
<br />
http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/<br />
<br />
Each tutorial is in its own subdirectory. You need the *.xml file, for example basic/tutorial-basic.xml. Get it and simply replace all English text in it with the text in your language, preserving all XML markup. See README at that location for some notes on markup.<br />
<br />
* If there's already such a file in CVS, you can edit it instead :) If there's no xml file at the above location but there's a translation of this tutorial in SVG format (in share/tutorials in Inkscape distribution), you'll need to convert it to [[DocBook]] (and probably update). Conversion can be done simply by: select the text blocks of an SVG tutorial in Inkscape, Ctrl+C, and Ctrl+V in your text editor, then add the markup.<br />
<br />
* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish. <br />
<br />
* Do not use symbolic entities like &amp;aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &amp;#225; or simply write your text in UTF-8.<br />
<br />
* Most illustrations don't need translations, so you leave the references to them from English XML intact. If however an illustration has some text that you want to translate, open the illustration file in Inkscape (e.g. basic/basic-f12.svg), edit it as needed, and save under a different name (e.g. basic/basic-f12-es.svg). Then change the filename reference in the XML source appropriately.<br />
<br />
* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.<br />
<br />
* Send the file to Joshua Andler <scislac at users dot sf dot net>, and he'll convert it to SVG and HTML and upload it to SVN and the web site.<br />
<br />
* If after that you want to make any changes, download the file from the above location again, because it may have changed compared to the one you have.<br />
<br />
==Tools==<br />
* xml2po in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/)<br />
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html<br />
* Transolution - http://transolution.python-hosting.com/<br />
<br />
= Keyboard and mouse translation =<br />
<br />
= Wiki and web site =<br />
<br />
= Status and contacts =<br />
<br />
Total number of PO files: 38<br />
Total number of strings to translate: 2142<br />
<br />
<br />
'''Amharic''': am.po<br />
<br />
translated: 77 ( '''3%''')<br />
<br />
fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)<br />
<br />
Last translator: Ge'ez Frontier Foundation <locales@geez.org><br />
Date of last update: 2003-02-01<br />
<br />
<br />
'''Azerbaijani/Turkic''': az.po<br />
<br />
translated: 63 ( '''2%''')<br />
<br />
fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)<br />
<br />
Last translator: Vasif İsmayıloğlu MD <azerb_linux@hotmail.com><br />
Date of last update: 2001-12-04<br />
<br />
<br />
'''Belarusian''': be.po<br />
<br />
translated: 158 ( '''7%''')<br />
<br />
fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)<br />
<br />
Last translator: Vital Khilko <dojlid@mova.org><br />
Date of last update: 2003-07-20<br />
<br />
<br />
'''Catalan''': ca.po<br />
<br />
translated: 2039 ( '''95%''')<br />
<br />
fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)<br />
<br />
Last translator: Xavier Conde Rueda <xavi.conde@gmail.com><br />
Date of last update: 2006-05-08<br />
<br />
<br />
'''Czech''': cs.po<br />
<br />
translated: 2096 ( '''97%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)<br />
<br />
Last translator: Josef Vybíral <josef.vybiral@gmail.com><br />
Date of last update: 2006-05-22<br />
<br />
<br />
'''Danish''': da.po<br />
<br />
translated: 100 ( '''4%''')<br />
<br />
fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)<br />
<br />
Last translator: Keld Simonsen <keld@dkuug.dk><br />
Date of last update: 2002-01-15<br />
<br />
<br />
'''German''': de.po<br />
<br />
translated: 2116 ( '''98%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)<br />
<br />
Last translator: Colin Marquardt <colin@marquardt-home.de><br />
Date of last update: 2006-05-23<br />
<br />
<br />
'''Greek''': el.po<br />
<br />
translated: 44 ( '''2%''')<br />
<br />
fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)<br />
<br />
Last translator: Simos Xenitellis <simos@hellug.gr><br />
Date of last update: 2001-12-28<br />
<br />
<br />
'''Spanish''': es.po<br />
<br />
translated: 2125 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)<br />
<br />
Last translator: Lucas Vieites Fariña<lucas@asixinformatica.com><br />
Date of last update: 2006-05-25<br />
<br />
<br />
'''Spanish/Mexico''': es_MX.po<br />
<br />
translated: 337 ( '''15%''')<br />
<br />
fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)<br />
<br />
Last translator: Daniel Díaz <yosoy@danieldiaz.org><br />
Date of last update: 2004-04-05<br />
<br />
<br />
'''Estonian''': et.po<br />
<br />
translated: 9 ( '''0%''')<br />
<br />
fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)<br />
<br />
Last translator: Lauris Kaplinski <lauris@ariman.ee><br />
Date of last update: 2000-04-08<br />
<br />
<br />
'''Basque''': eu.po<br />
<br />
translated: 1548 ( '''72%''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)<br />
<br />
Last translator: Iñaki Larrañaga <dooteo@euskalgnu.org><br />
Date of last update: 2006-03-16<br />
<br />
<br />
'''French''': fr.po<br />
<br />
translated: 2126 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)<br />
<br />
Last translator: matiphas <matiphas@free.fr><br />
Date of last update: 2006-05-27<br />
<br />
<br />
'''Irish''': ga.po<br />
<br />
translated: 14 ( '''0%''')<br />
<br />
fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)<br />
<br />
Last translator: Alastair McKinstry <mckinstry@computer.org><br />
Date of last update: 2000-08-24<br />
<br />
<br />
'''Galician''': gl.po<br />
<br />
translated: 82 ( '''3%''')<br />
<br />
fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)<br />
<br />
Last translator: Francisco Xosé Vázquez Grandal <fxvazquez@arrakis.es><br />
Date of last update: 2001-11-10<br />
<br />
<br />
'''Hungarian''': hu.po<br />
<br />
translated: 1564 ( '''73%''')<br />
<br />
fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)<br />
<br />
Last translator: Arpad Biro <biro_arpad@yahoo.com><br />
Date of last update: 2006-05-29<br />
<br />
<br />
'''Italian''': it.po<br />
<br />
translated: 2008 ( '''93%''')<br />
<br />
fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)<br />
<br />
Last translator: Luca Bruno <luca.br@uno.it><br />
Date of last update: 2006-05-15<br />
<br />
<br />
'''Japanese''': ja.po<br />
<br />
translated: 1294 ( '''60%''')<br />
<br />
fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)<br />
<br />
Last translator: shivaken <shivaken@owls-nest.net><br />
Date of last update: 2005-11-16<br />
<br />
<br />
'''Korean''': ko.po<br />
<br />
translated: 180 ( '''8%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)<br />
<br />
Last translator: Kitae <bluetux@gmail.com><br />
Date of last update: 2006-04-10<br />
<br />
<br />
'''Lithuanian''': lt.po<br />
<br />
translated: 1774 ( '''82%''')<br />
<br />
fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)<br />
<br />
Last translator: Andrius R. <knutux@gmail.com><br />
Date of last update: 2006-05-02<br />
<br />
<br />
'''mk.po'''<br />
<br />
translated: 0 ( '''0%''')<br />
<br />
fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)<br />
<br />
Last translator: <br />
Date of last update: 2003-06-15<br />
<br />
<br />
'''Norwegian/bokmål dialect''': nb.po<br />
<br />
translated: 144 ( '''6%''')<br />
<br />
fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)<br />
<br />
Last translator: Kjartan Maraas <kmaraas@gnome.org><br />
Date of last update: 2003-01-25<br />
<br />
<br />
'''Dutch: nl.po'''<br />
<br />
translated: 1484 ( '''69%''')<br />
<br />
fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)<br />
<br />
Last translator: Jeroen van der Vegt <ajvdvegt (at) 123mail.org><br />
Date of last update: 2005-11-07<br />
<br />
<br />
'''Norwegian/Nynorsk''': nn.po<br />
<br />
translated: 1376 ( '''64%''')<br />
<br />
fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)<br />
<br />
Last translator: Karl Ove Hufthammer <karl@huftis.org><br />
Date of last update: 2005-07-14<br />
<br />
<br />
'''Punjabi''': pa.po<br />
<br />
translated: 912 ( '''42%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)<br />
<br />
Last translator: Amanpreet Singh Brar <amanpreetalam@yahoo.com><br />
Date of last update: 2005-09-11<br />
<br />
<br />
'''Polish''': pl.po<br />
<br />
translated: 1503 ( '''70%''')<br />
<br />
fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)<br />
<br />
Last translator: Przemysław Loesch <p_loesch@poczta.onet.pl><br />
Date of last update: 2005-10-29<br />
<br />
<br />
'''Portuguese''': pt.po<br />
<br />
translated: 183 ( '''8%''')<br />
<br />
fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)<br />
<br />
Last translator: Duarte Loreto <happyguy_pt@hotmail.com><br />
Date of last update: 2003-07-28<br />
<br />
<br />
'''Portuguese/Brazillian''': pt_BR.po<br />
<br />
translated: 1546 ( '''72%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)<br />
<br />
Last translator: Antônio Cláudio (LedStyle) <ledstyle@gmail.com><br />
Date of last update: 2006-04-27<br />
<br />
<br />
'''Russian''': ru.po<br />
<br />
translated: 1542 ( '''71%''')<br />
<br />
fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)<br />
<br />
Last translator: Alexandre Prokoudine <alexandre.prokoudine@gmail.com><br />
Date of last update: 2005-11-08<br />
<br />
<br />
'''Slovak''': sk.po<br />
<br />
translated: 845 ( '''39%''')<br />
<br />
fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)<br />
<br />
Last translator: Zdenko Podobný <zdpo@mailbox.sk><br />
Date of last update: 2005-02-13<br />
<br />
<br />
'''Slovenian''': sl.po<br />
<br />
translated: 2055 ( '''95%''')<br />
<br />
fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)<br />
<br />
Last translator: Martin Srebotnjak <miles@filmsi.net><br />
Date of last update: 2006-05-12<br />
<br />
<br />
'''Serbian''': sr.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Last translator: ÐлекÑандар Урошевић <urke@users.sourceforge.net><br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Serbian/Latine''': sr@Latn.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Last translator: Aleksandar Urošević <urke@users.sourceforge.net><br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Swedish''': sv.po<br />
<br />
translated: 410 ( '''19%''')<br />
<br />
fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)<br />
<br />
Last translator: Mattias Hultgren <mattias_hultgren@tele2.se><br />
Date of last update: 2005-10-08<br />
<br />
<br />
'''Turkish''': tr.po<br />
<br />
translated: 907 ( '''42%''')<br />
<br />
fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)<br />
<br />
Last translator: Serdar Soytetir <sendirom@gmail.com><br />
Date of last update: 2005-11-26<br />
<br />
<br />
'''Ukrainian''': uk.po<br />
<br />
translated: 1518 ( '''70%''')<br />
<br />
fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)<br />
<br />
Last translator: Maxim V. Dziumanenko <mvd@mylinux.com.ua><br />
Date of last update: 2005-10-21<br />
<br />
<br />
'''Chinese/Simplified''': zh_CN.po<br />
<br />
translated: 2134 ( '''99%''')<br />
<br />
fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)<br />
<br />
Last translator: Chris Jia <Chrisjiasl@gmail.com><br />
Date of last update: 2006-05-28<br />
<br />
<br />
'''Chinese/Traditional''': zh_TW.po<br />
<br />
translated: 1550 ( '''72 %''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)<br />
<br />
Last translator: Wei-Lun Chao <william.chao@ossii.com.tw><br />
Date of last update: 2006-03-24</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=TestPage&diff=6544TestPage2006-05-30T12:40:52Z<p>Xaviconde: /* Guidelines/workflow */</p>
<hr />
<div>= Introduction =<br />
== Community based, user oriented ==<br />
The translations of the various documents focusing on Inkscape rely on the work of volunteers.<br />
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.<br />
It is very important not to forget that Inkscape is an open source, community based and user oriented software, which implies that software developpers/contributors are generaly users. It also implies that the translation efforts are also user oriented, with a strong focus on interface, user documentation and website.<br />
<br />
== Guidelines/workflow ==<br />
<br />
# '''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 start point is subscribing to your local [http://developer.gnome.org/projects/gtp/teams.html GNOME translation team] or KDE translation team.<br />
# '''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.<br />
# '''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.<br />
# '''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 you are submitting doesn't have syntax errors that would break the building process.<br />
# '''Send a mail on the translator mailing list'''. Your contribution will be reviewed/commited as soon as possible.<br />
<br />
== Best practices ==<br />
<br />
Best case for a good translation : translate from English to your mother tongue.<br />
<br />
Test the behavior of the interface before starting translation<br />
<br />
= Translatable content =<br />
<br />
== po files ==<br />
The po files contain the strings for the Inkscape Interface (main software and extentions).<br />
<br />
That's why it is obviously the translation to start with.<br />
<br />
== tutorials ==<br />
Tutorials are documents of very high value for users.<br />
<br />
== Windows installer ==<br />
High value for users, even if the installation process of Inkscape is quite simple, translating the Windows installer helps a lot potential users feeling good with Inkscape.<br />
<br />
== Release notes ==<br />
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape<br />
<br />
- give a general overview of the possibilities of the software to potential users<br />
<br />
- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)<br />
<br />
== Web pages ==<br />
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English. <br />
<br />
Translation efforts should be first oriented on user documentation.<br />
<br />
See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.<br />
<br />
<br />
== Others ==<br />
Templates (translation and localization)<br />
<br />
...<br />
<br />
= Interface Translation =<br />
<br />
<br />
If you're interested in helping with providing interface translation for Inkscape,<br />
here are a few links to help you getting started:<br />
<br />
http://www.gtkmm.org/gtkmm2/docs/tutorial/html/ch20s03.html<br />
http://developer.gnome.org/projects/gtp/l10n-guide/<br />
http://developer.gnome.org/projects/gtp/style-guides/<br />
http://developer.gnome.org/doc/tutorials/gnome-i18n/developer.html<br />
<br />
Download the .po file for your language from here:<br />
<br />
http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/<br />
<br />
If a .po file for your language does not yet exist, then create one<br />
by copying the inkscape.pot file that gets generated when you run make<br />
in the codebase.<br />
<br />
Edit the file to add or correct translations of the English strings, and<br />
then upload your work via the [[SourceForge]] patch tracker:<br />
<br />
http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308<br />
<br />
(Check the Upload checkbox and add your file or patch.)<br />
<br />
<br />
<br />
Here's how to make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough):<br />
<br />
1. update your local copy of Inkscape in the usual way: "svn update"<br />
2. "./autogen.sh"<br />
3. "./configure"<br />
4. enter the "po" directory: "cd po"<br />
5. generate the current PO template: "intltool-update --pot"<br />
6. merge your existing translations into the new POT file (inkscape.pot):<br />
"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"<br />
<br />
Then you just need to complete the translations in the PO file that was<br />
created in step 6.<br />
<br />
<br />
If you want to update ALL .po files in po/, cd there and run:<br />
<br />
make update-po<br />
<br />
<br />
== Tools for translators ==<br />
* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)<br />
* kbabel (http://i18n.kde.org/tools/kbabel/)<br />
* gtranslator (http://gtranslator.sourceforge.net/)<br />
* poEdit (http://poedit.sourceforge.net/)<br />
<br />
== A few important things to remember ==<br />
* Some strings that can ambiguous or having several meanings according to different contexts may have a context prefix : "Context|Amibiguous string". In this case, simply translate "Ambiguous string", the "Context|" string is just a not to translate indication.<br />
* After translating a fuzzy string (one that is marked with a ", fuzzy" comment), please remove its "fuzzy" tag -- otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated. KBabel can do this automatically (see KBabel settings).<br />
* Before publishing your work (after you have finished updating the PO file), please update the "PO-Revision-Date" and "Last-Translator" fields in the PO file header. KBabel can do this automatically.<br />
<br />
== Review ==<br />
This is the start of a list of places to get translation reviews done. So far:<br />
http://www.linux.it/tp/<br />
<br />
== Locale Testing ==<br />
Before reporting that a locale doesn't work in Inkscape, you need to make sure that your system has that locale correctly set up. To do this, you need to generally find a way to run "locale-gen". (Under Debian/Ubuntu this is via "dpkg-reconfigure locales".) If you set both the LANG and LANGUAGE variables and check a regular tool, you should see the correct language for both the libc error (first line) and the tool error (second line):<br />
<br />
LANG=es_MX LANGUAGE=es_MX ls -z<br />
ls: opci&oacute;n inv&aacute;lida -- z<br />
Pruebe `ls --help' para m&aacute;s informaci&oacute;n.<br />
<br />
If it reports the regular C messages, your locale has not been correctly configured, and you'll need to find the right way to run "locale-gen" for your distribution:<br />
<br />
LANG=es_ES LANGUAGE=es_MX ls -z<br />
ls: invalid option -- z<br />
Try `ls --help' for more information.<br />
<br />
== Programmers ==<br />
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.<br />
<br />
<br />
= Tutorial Translation =<br />
<br />
Inkscape tutorial sources are in [[DocBook]] format, with illustrations in SVG. If you want to translate one or more tutorials, first download the [[DocBook]] source here:<br />
<br />
http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/<br />
<br />
Each tutorial is in its own subdirectory. You need the *.xml file, for example basic/tutorial-basic.xml. Get it and simply replace all English text in it with the text in your language, preserving all XML markup. See README at that location for some notes on markup.<br />
<br />
* If there's already such a file in CVS, you can edit it instead :) If there's no xml file at the above location but there's a translation of this tutorial in SVG format (in share/tutorials in Inkscape distribution), you'll need to convert it to [[DocBook]] (and probably update). Conversion can be done simply by: select the text blocks of an SVG tutorial in Inkscape, Ctrl+C, and Ctrl+V in your text editor, then add the markup.<br />
<br />
* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish. <br />
<br />
* Do not use symbolic entities like &amp;aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &amp;#225; or simply write your text in UTF-8.<br />
<br />
* Most illustrations don't need translations, so you leave the references to them from English XML intact. If however an illustration has some text that you want to translate, open the illustration file in Inkscape (e.g. basic/basic-f12.svg), edit it as needed, and save under a different name (e.g. basic/basic-f12-es.svg). Then change the filename reference in the XML source appropriately.<br />
<br />
* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.<br />
<br />
* Send the file to Joshua Andler <scislac at users dot sf dot net>, and he'll convert it to SVG and HTML and upload it to SVN and the web site.<br />
<br />
* If after that you want to make any changes, download the file from the above location again, because it may have changed compared to the one you have.<br />
<br />
==Tools==<br />
* xml2po in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/)<br />
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html<br />
* Transolution - http://transolution.python-hosting.com/<br />
<br />
= Keyboard and mouse translation =<br />
<br />
= Wiki and web site =<br />
<br />
= Status and contacts =<br />
<br />
Total number of PO files: 38<br />
Total number of strings to translate: 2142<br />
<br />
<br />
'''Amharic''': am.po<br />
<br />
translated: 77 ( '''3%''')<br />
<br />
fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)<br />
<br />
Last translator: Ge'ez Frontier Foundation <locales@geez.org><br />
Date of last update: 2003-02-01<br />
<br />
<br />
'''Azerbaijani/Turkic''': az.po<br />
<br />
translated: 63 ( '''2%''')<br />
<br />
fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)<br />
<br />
Last translator: Vasif İsmayıloğlu MD <azerb_linux@hotmail.com><br />
Date of last update: 2001-12-04<br />
<br />
<br />
'''Belarusian''': be.po<br />
<br />
translated: 158 ( '''7%''')<br />
<br />
fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)<br />
<br />
Last translator: Vital Khilko <dojlid@mova.org><br />
Date of last update: 2003-07-20<br />
<br />
<br />
'''Catalan''': ca.po<br />
<br />
translated: 2039 ( '''95%''')<br />
<br />
fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)<br />
<br />
Last translator: Xavier Conde Rueda <xavi.conde@gmail.com><br />
Date of last update: 2006-05-08<br />
<br />
<br />
'''Czech''': cs.po<br />
<br />
translated: 2096 ( '''97%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)<br />
<br />
Last translator: Josef Vybíral <josef.vybiral@gmail.com><br />
Date of last update: 2006-05-22<br />
<br />
<br />
'''Danish''': da.po<br />
<br />
translated: 100 ( '''4%''')<br />
<br />
fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)<br />
<br />
Last translator: Keld Simonsen <keld@dkuug.dk><br />
Date of last update: 2002-01-15<br />
<br />
<br />
'''German''': de.po<br />
<br />
translated: 2116 ( '''98%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)<br />
<br />
Last translator: Colin Marquardt <colin@marquardt-home.de><br />
Date of last update: 2006-05-23<br />
<br />
<br />
'''Greek''': el.po<br />
<br />
translated: 44 ( '''2%''')<br />
<br />
fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)<br />
<br />
Last translator: Simos Xenitellis <simos@hellug.gr><br />
Date of last update: 2001-12-28<br />
<br />
<br />
'''Spanish''': es.po<br />
<br />
translated: 2125 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)<br />
<br />
Last translator: Lucas Vieites Fariña<lucas@asixinformatica.com><br />
Date of last update: 2006-05-25<br />
<br />
<br />
'''Spanish/Mexico''': es_MX.po<br />
<br />
translated: 337 ( '''15%''')<br />
<br />
fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)<br />
<br />
Last translator: Daniel Díaz <yosoy@danieldiaz.org><br />
Date of last update: 2004-04-05<br />
<br />
<br />
'''Estonian''': et.po<br />
<br />
translated: 9 ( '''0%''')<br />
<br />
fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)<br />
<br />
Last translator: Lauris Kaplinski <lauris@ariman.ee><br />
Date of last update: 2000-04-08<br />
<br />
<br />
'''Basque''': eu.po<br />
<br />
translated: 1548 ( '''72%''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)<br />
<br />
Last translator: Iñaki Larrañaga <dooteo@euskalgnu.org><br />
Date of last update: 2006-03-16<br />
<br />
<br />
'''French''': fr.po<br />
<br />
translated: 2126 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)<br />
<br />
Last translator: matiphas <matiphas@free.fr><br />
Date of last update: 2006-05-27<br />
<br />
<br />
'''Irish''': ga.po<br />
<br />
translated: 14 ( '''0%''')<br />
<br />
fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)<br />
<br />
Last translator: Alastair McKinstry <mckinstry@computer.org><br />
Date of last update: 2000-08-24<br />
<br />
<br />
'''Galician''': gl.po<br />
<br />
translated: 82 ( '''3%''')<br />
<br />
fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)<br />
<br />
Last translator: Francisco Xosé Vázquez Grandal <fxvazquez@arrakis.es><br />
Date of last update: 2001-11-10<br />
<br />
<br />
'''Hungarian''': hu.po<br />
<br />
translated: 1564 ( '''73%''')<br />
<br />
fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)<br />
<br />
Last translator: Arpad Biro <biro_arpad@yahoo.com><br />
Date of last update: 2006-05-29<br />
<br />
<br />
'''Italian''': it.po<br />
<br />
translated: 2008 ( '''93%''')<br />
<br />
fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)<br />
<br />
Last translator: Luca Bruno <luca.br@uno.it><br />
Date of last update: 2006-05-15<br />
<br />
<br />
'''Japanese''': ja.po<br />
<br />
translated: 1294 ( '''60%''')<br />
<br />
fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)<br />
<br />
Last translator: shivaken <shivaken@owls-nest.net><br />
Date of last update: 2005-11-16<br />
<br />
<br />
'''Korean''': ko.po<br />
<br />
translated: 180 ( '''8%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)<br />
<br />
Last translator: Kitae <bluetux@gmail.com><br />
Date of last update: 2006-04-10<br />
<br />
<br />
'''Lithuanian''': lt.po<br />
<br />
translated: 1774 ( '''82%''')<br />
<br />
fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)<br />
<br />
Last translator: Andrius R. <knutux@gmail.com><br />
Date of last update: 2006-05-02<br />
<br />
<br />
'''mk.po'''<br />
<br />
translated: 0 ( '''0%''')<br />
<br />
fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)<br />
<br />
Last translator: <br />
Date of last update: 2003-06-15<br />
<br />
<br />
'''Norwegian/bokmål dialect''': nb.po<br />
<br />
translated: 144 ( '''6%''')<br />
<br />
fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)<br />
<br />
Last translator: Kjartan Maraas <kmaraas@gnome.org><br />
Date of last update: 2003-01-25<br />
<br />
<br />
'''Dutch: nl.po'''<br />
<br />
translated: 1484 ( '''69%''')<br />
<br />
fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)<br />
<br />
Last translator: Jeroen van der Vegt <ajvdvegt (at) 123mail.org><br />
Date of last update: 2005-11-07<br />
<br />
<br />
'''Norwegian/Nynorsk''': nn.po<br />
<br />
translated: 1376 ( '''64%''')<br />
<br />
fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)<br />
<br />
Last translator: Karl Ove Hufthammer <karl@huftis.org><br />
Date of last update: 2005-07-14<br />
<br />
<br />
'''Punjabi''': pa.po<br />
<br />
translated: 912 ( '''42%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)<br />
<br />
Last translator: Amanpreet Singh Brar <amanpreetalam@yahoo.com><br />
Date of last update: 2005-09-11<br />
<br />
<br />
'''Polish''': pl.po<br />
<br />
translated: 1503 ( '''70%''')<br />
<br />
fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)<br />
<br />
Last translator: Przemysław Loesch <p_loesch@poczta.onet.pl><br />
Date of last update: 2005-10-29<br />
<br />
<br />
'''Portuguese''': pt.po<br />
<br />
translated: 183 ( '''8%''')<br />
<br />
fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)<br />
<br />
Last translator: Duarte Loreto <happyguy_pt@hotmail.com><br />
Date of last update: 2003-07-28<br />
<br />
<br />
'''Portuguese/Brazillian''': pt_BR.po<br />
<br />
translated: 1546 ( '''72%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)<br />
<br />
Last translator: Antônio Cláudio (LedStyle) <ledstyle@gmail.com><br />
Date of last update: 2006-04-27<br />
<br />
<br />
'''Russian''': ru.po<br />
<br />
translated: 1542 ( '''71%''')<br />
<br />
fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)<br />
<br />
Last translator: Alexandre Prokoudine <alexandre.prokoudine@gmail.com><br />
Date of last update: 2005-11-08<br />
<br />
<br />
'''Slovak''': sk.po<br />
<br />
translated: 845 ( '''39%''')<br />
<br />
fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)<br />
<br />
Last translator: Zdenko Podobný <zdpo@mailbox.sk><br />
Date of last update: 2005-02-13<br />
<br />
<br />
'''Slovenian''': sl.po<br />
<br />
translated: 2055 ( '''95%''')<br />
<br />
fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)<br />
<br />
Last translator: Martin Srebotnjak <miles@filmsi.net><br />
Date of last update: 2006-05-12<br />
<br />
<br />
'''Serbian''': sr.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Last translator: ÐлекÑандар Урошевић <urke@users.sourceforge.net><br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Serbian/Latine''': sr@Latn.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Last translator: Aleksandar Urošević <urke@users.sourceforge.net><br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Swedish''': sv.po<br />
<br />
translated: 410 ( '''19%''')<br />
<br />
fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)<br />
<br />
Last translator: Mattias Hultgren <mattias_hultgren@tele2.se><br />
Date of last update: 2005-10-08<br />
<br />
<br />
'''Turkish''': tr.po<br />
<br />
translated: 907 ( '''42%''')<br />
<br />
fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)<br />
<br />
Last translator: Serdar Soytetir <sendirom@gmail.com><br />
Date of last update: 2005-11-26<br />
<br />
<br />
'''Ukrainian''': uk.po<br />
<br />
translated: 1518 ( '''70%''')<br />
<br />
fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)<br />
<br />
Last translator: Maxim V. Dziumanenko <mvd@mylinux.com.ua><br />
Date of last update: 2005-10-21<br />
<br />
<br />
'''Chinese/Simplified''': zh_CN.po<br />
<br />
translated: 2134 ( '''99%''')<br />
<br />
fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)<br />
<br />
Last translator: Chris Jia <Chrisjiasl@gmail.com><br />
Date of last update: 2006-05-28<br />
<br />
<br />
'''Chinese/Traditional''': zh_TW.po<br />
<br />
translated: 1550 ( '''72 %''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)<br />
<br />
Last translator: Wei-Lun Chao <william.chao@ossii.com.tw><br />
Date of last update: 2006-03-24</div>Xavicondehttps://wiki.inkscape.org/wiki/index.php?title=TestPage&diff=6541TestPage2006-05-30T10:14:37Z<p>Xaviconde: /* Guidelines/workflow */</p>
<hr />
<div>= Introduction =<br />
== Community based, user oriented ==<br />
The translations of the various documents focusing on Inkscape rely on the work of volunteers.<br />
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.<br />
It is very important not to forget that Inkscape is an open source, community based and user oriented software, which implies that software developpers/contributors are generaly users. It also implies that the translation efforts are also user oriented, with a strong focus on interface, user documentation and website.<br />
<br />
== Guidelines/workflow ==<br />
<br />
# '''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 start point is subscribing to your local GNOME or KDE translation team.<br />
# '''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.<br />
# '''Get PO file for your language'''. If you only want to translate the interface messages, you can get the PO file from [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape/trunk/po/ Inkscape's svn repository web interface]. Each *.po file is for a single language (fr.po for French, es.po por Spanish, ca.po for Catalan, an so on). If there is no PO file for your language, get the inkscape.pot file (a blank translation template), adn start working on it. You will have to rename it to the two-letter code of your language. Besides getting files from web interface, you can download the full repository; instructions on how to do this are found [http://inkscape.org/svn.php here]<br />
# '''Submit finished work to patch tracker'''. Finished translations must be sent to patch tracker and/or mailing list in order to be integrated on the trunk. You will need a Sourceforge.net account to commit patches to [http://sourceforge.net/tracker/?group_id=93438&atid=604308http://sourceforge.net/tracker/?group_id=93438&atid=604308 Inkscape's patch tracker]. Before sending a patch, remember to check that your PO file syntax is correct. <br />
# '''Send a mail on the translator ML'''. Your patch will be reviewed/commited as soon as possible.<br />
<br />
== Best practices ==<br />
<br />
Best case for a good translation : translate from English to your mother tongue.<br />
<br />
Test the behavior of the interface before starting translation<br />
<br />
= Translatable content =<br />
<br />
== po files ==<br />
The po files contain the strings for the Inkscape Interface (main software and extentions).<br />
<br />
That's why it is obviously the translation to start with.<br />
<br />
== tutorials ==<br />
Tutorials are documents of very high value for users.<br />
<br />
== Windows installer ==<br />
High value for users, even if the installation process of Inkscape is quite simple, translating the Windows installer helps a lot potential users feeling good with Inkscape.<br />
<br />
== Release notes ==<br />
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape<br />
<br />
- give a general overview of the possibilities of the software to potential users<br />
<br />
- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)<br />
<br />
<br />
<br />
== Web pages ==<br />
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English. <br />
<br />
Translation efforts should be first oriented on user documentation.<br />
<br />
See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.<br />
<br />
<br />
== Others ==<br />
Templates (translation and localization)<br />
<br />
...<br />
<br />
= Interface Translation =<br />
<br />
<br />
If you're interested in helping with providing interface translation for Inkscape,<br />
here are a few links to help you getting started:<br />
<br />
http://www.gtkmm.org/gtkmm2/docs/tutorial/html/ch20s03.html<br />
http://developer.gnome.org/projects/gtp/l10n-guide/<br />
http://developer.gnome.org/projects/gtp/style-guides/<br />
http://developer.gnome.org/doc/tutorials/gnome-i18n/developer.html<br />
<br />
Download the .po file for your language from here:<br />
<br />
http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/<br />
<br />
If a .po file for your language does not yet exist, then create one<br />
by copying the inkscape.pot file that gets generated when you run make<br />
in the codebase.<br />
<br />
Edit the file to add or correct translations of the English strings, and<br />
then upload your work via the [[SourceForge]] patch tracker:<br />
<br />
http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308<br />
<br />
(Check the Upload checkbox and add your file or patch.)<br />
<br />
<br />
<br />
Here's how to make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough):<br />
<br />
1. update your local copy of Inkscape in the usual way: "svn update"<br />
2. "./autogen.sh"<br />
3. "./configure"<br />
4. enter the "po" directory: "cd po"<br />
5. generate the current PO template: "intltool-update --pot"<br />
6. merge your existing translations into the new POT file (inkscape.pot):<br />
"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"<br />
<br />
Then you just need to complete the translations in the PO file that was<br />
created in step 6.<br />
<br />
<br />
If you want to update ALL .po files in po/, cd there and run:<br />
<br />
make update-po<br />
<br />
<br />
== Tools for translators ==<br />
* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)<br />
* kbabel (http://i18n.kde.org/tools/kbabel/)<br />
* gtranslator (http://gtranslator.sourceforge.net/)<br />
* poEdit (http://poedit.sourceforge.net/)<br />
<br />
== A few important things to remember ==<br />
* Some strings that can ambiguous or having several meanings according to different contexts may have a context prefix : "Context|Amibiguous string". In this case, simply translate "Ambiguous string", the "Context|" string is just a not to translate indication.<br />
* After translating a fuzzy string (one that is marked with a ", fuzzy" comment), please remove its "fuzzy" tag -- otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated. KBabel can do this automatically (see KBabel settings).<br />
* Before publishing your work (after you have finished updating the PO file), please update the "PO-Revision-Date" and "Last-Translator" fields in the PO file header. KBabel can do this automatically.<br />
<br />
== Review ==<br />
This is the start of a list of places to get translation reviews done. So far:<br />
http://www.linux.it/tp/<br />
<br />
== Locale Testing ==<br />
Before reporting that a locale doesn't work in Inkscape, you need to make sure that your system has that locale correctly set up. To do this, you need to generally find a way to run "locale-gen". (Under Debian/Ubuntu this is via "dpkg-reconfigure locales".) If you set both the LANG and LANGUAGE variables and check a regular tool, you should see the correct language for both the libc error (first line) and the tool error (second line):<br />
<br />
LANG=es_MX LANGUAGE=es_MX ls -z<br />
ls: opci&oacute;n inv&aacute;lida -- z<br />
Pruebe `ls --help' para m&aacute;s informaci&oacute;n.<br />
<br />
If it reports the regular C messages, your locale has not been correctly configured, and you'll need to find the right way to run "locale-gen" for your distribution:<br />
<br />
LANG=es_ES LANGUAGE=es_MX ls -z<br />
ls: invalid option -- z<br />
Try `ls --help' for more information.<br />
<br />
== Programmers ==<br />
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.<br />
<br />
<br />
= Tutorial Translation =<br />
<br />
Inkscape tutorial sources are in [[DocBook]] format, with illustrations in SVG. If you want to translate one or more tutorials, first download the [[DocBook]] source here:<br />
<br />
http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/<br />
<br />
Each tutorial is in its own subdirectory. You need the *.xml file, for example basic/tutorial-basic.xml. Get it and simply replace all English text in it with the text in your language, preserving all XML markup. See README at that location for some notes on markup.<br />
<br />
* If there's already such a file in CVS, you can edit it instead :) If there's no xml file at the above location but there's a translation of this tutorial in SVG format (in share/tutorials in Inkscape distribution), you'll need to convert it to [[DocBook]] (and probably update). Conversion can be done simply by: select the text blocks of an SVG tutorial in Inkscape, Ctrl+C, and Ctrl+V in your text editor, then add the markup.<br />
<br />
* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish. <br />
<br />
* Do not use symbolic entities like &amp;aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &amp;#225; or simply write your text in UTF-8.<br />
<br />
* Most illustrations don't need translations, so you leave the references to them from English XML intact. If however an illustration has some text that you want to translate, open the illustration file in Inkscape (e.g. basic/basic-f12.svg), edit it as needed, and save under a different name (e.g. basic/basic-f12-es.svg). Then change the filename reference in the XML source appropriately.<br />
<br />
* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.<br />
<br />
* Send the file to buliabyak at gmail dot com, and I'll convert it to SVG and HTML and upload it to CVS and the web site.<br />
<br />
* If after that you want to make any changes, download the file from the above location again, because it may have changed compared to the one you have.<br />
<br />
==Tools==<br />
* xml2po in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/)<br />
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html<br />
* Transolution - http://transolution.python-hosting.com/<br />
<br />
= Keyboard and mouse translation =<br />
<br />
= Wiki and web site =<br />
<br />
= Status and contacts =<br />
<br />
Total number of PO files: 38<br />
Total number of strings to translate: 2142<br />
<br />
<br />
'''Amharic''': am.po<br />
<br />
translated: 77 ( '''3%''')<br />
<br />
fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)<br />
<br />
Last translator: Ge'ez Frontier Foundation <locales@geez.org><br />
Date of last update: 2003-02-01<br />
<br />
<br />
'''Azerbaijani/Turkic''': az.po<br />
<br />
translated: 63 ( '''2%''')<br />
<br />
fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)<br />
<br />
Last translator: Vasif İsmayıloğlu MD <azerb_linux@hotmail.com><br />
Date of last update: 2001-12-04<br />
<br />
<br />
'''Belarusian''': be.po<br />
<br />
translated: 158 ( '''7%''')<br />
<br />
fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)<br />
<br />
Last translator: Vital Khilko <dojlid@mova.org><br />
Date of last update: 2003-07-20<br />
<br />
<br />
'''Catalan''': ca.po<br />
<br />
translated: 2039 ( '''95%''')<br />
<br />
fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)<br />
<br />
Last translator: Xavier Conde Rueda <xavi.conde@gmail.com><br />
Date of last update: 2006-05-08<br />
<br />
<br />
'''Czech''': cs.po<br />
<br />
translated: 2096 ( '''97%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)<br />
<br />
Last translator: Josef Vybíral <josef.vybiral@gmail.com><br />
Date of last update: 2006-05-22<br />
<br />
<br />
'''Danish''': da.po<br />
<br />
translated: 100 ( '''4%''')<br />
<br />
fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)<br />
<br />
Last translator: Keld Simonsen <keld@dkuug.dk><br />
Date of last update: 2002-01-15<br />
<br />
<br />
'''German''': de.po<br />
<br />
translated: 2116 ( '''98%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)<br />
<br />
Last translator: Colin Marquardt <colin@marquardt-home.de><br />
Date of last update: 2006-05-23<br />
<br />
<br />
'''Greek''': el.po<br />
<br />
translated: 44 ( '''2%''')<br />
<br />
fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)<br />
<br />
Last translator: Simos Xenitellis <simos@hellug.gr><br />
Date of last update: 2001-12-28<br />
<br />
<br />
'''Spanish''': es.po<br />
<br />
translated: 2125 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)<br />
<br />
Last translator: Lucas Vieites Fariña<lucas@asixinformatica.com><br />
Date of last update: 2006-05-25<br />
<br />
<br />
'''Spanish/Mexico''': es_MX.po<br />
<br />
translated: 337 ( '''15%''')<br />
<br />
fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)<br />
<br />
Last translator: Daniel Díaz <yosoy@danieldiaz.org><br />
Date of last update: 2004-04-05<br />
<br />
<br />
'''Estonian''': et.po<br />
<br />
translated: 9 ( '''0%''')<br />
<br />
fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)<br />
<br />
Last translator: Lauris Kaplinski <lauris@ariman.ee><br />
Date of last update: 2000-04-08<br />
<br />
<br />
'''Basque''': eu.po<br />
<br />
translated: 1548 ( '''72%''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)<br />
<br />
Last translator: Iñaki Larrañaga <dooteo@euskalgnu.org><br />
Date of last update: 2006-03-16<br />
<br />
<br />
'''French''': fr.po<br />
<br />
translated: 2126 ( '''99%''')<br />
<br />
fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)<br />
<br />
Last translator: matiphas <matiphas@free.fr><br />
Date of last update: 2006-05-27<br />
<br />
<br />
'''Irish''': ga.po<br />
<br />
translated: 14 ( '''0%''')<br />
<br />
fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)<br />
<br />
Last translator: Alastair McKinstry <mckinstry@computer.org><br />
Date of last update: 2000-08-24<br />
<br />
<br />
'''Galician''': gl.po<br />
<br />
translated: 82 ( '''3%''')<br />
<br />
fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)<br />
<br />
Last translator: Francisco Xosé Vázquez Grandal <fxvazquez@arrakis.es><br />
Date of last update: 2001-11-10<br />
<br />
<br />
'''Hungarian''': hu.po<br />
<br />
translated: 1564 ( '''73%''')<br />
<br />
fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)<br />
<br />
Last translator: Arpad Biro <biro_arpad@yahoo.com><br />
Date of last update: 2006-05-29<br />
<br />
<br />
'''Italian''': it.po<br />
<br />
translated: 2008 ( '''93%''')<br />
<br />
fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)<br />
<br />
Last translator: Luca Bruno <luca.br@uno.it><br />
Date of last update: 2006-05-15<br />
<br />
<br />
'''Japanese''': ja.po<br />
<br />
translated: 1294 ( '''60%''')<br />
<br />
fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)<br />
<br />
Last translator: shivaken <shivaken@owls-nest.net><br />
Date of last update: 2005-11-16<br />
<br />
<br />
'''Korean''': ko.po<br />
<br />
translated: 180 ( '''8%''')<br />
<br />
fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)<br />
<br />
Last translator: Kitae <bluetux@gmail.com><br />
Date of last update: 2006-04-10<br />
<br />
<br />
'''Lithuanian''': lt.po<br />
<br />
translated: 1774 ( '''82%''')<br />
<br />
fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)<br />
<br />
Last translator: Andrius R. <knutux@gmail.com><br />
Date of last update: 2006-05-02<br />
<br />
<br />
'''mk.po'''<br />
<br />
translated: 0 ( '''0%''')<br />
<br />
fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)<br />
<br />
Last translator: <br />
Date of last update: 2003-06-15<br />
<br />
<br />
'''Norwegian/bokmål dialect''': nb.po<br />
<br />
translated: 144 ( '''6%''')<br />
<br />
fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)<br />
<br />
Last translator: Kjartan Maraas <kmaraas@gnome.org><br />
Date of last update: 2003-01-25<br />
<br />
<br />
'''Dutch: nl.po'''<br />
<br />
translated: 1484 ( '''69%''')<br />
<br />
fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)<br />
<br />
Last translator: Jeroen van der Vegt <ajvdvegt (at) 123mail.org><br />
Date of last update: 2005-11-07<br />
<br />
<br />
'''Norwegian/Nynorsk''': nn.po<br />
<br />
translated: 1376 ( '''64%''')<br />
<br />
fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)<br />
<br />
Last translator: Karl Ove Hufthammer <karl@huftis.org><br />
Date of last update: 2005-07-14<br />
<br />
<br />
'''Punjabi''': pa.po<br />
<br />
translated: 912 ( '''42%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)<br />
<br />
Last translator: Amanpreet Singh Brar <amanpreetalam@yahoo.com><br />
Date of last update: 2005-09-11<br />
<br />
<br />
'''Polish''': pl.po<br />
<br />
translated: 1503 ( '''70%''')<br />
<br />
fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)<br />
<br />
Last translator: Przemysław Loesch <p_loesch@poczta.onet.pl><br />
Date of last update: 2005-10-29<br />
<br />
<br />
'''Portuguese''': pt.po<br />
<br />
translated: 183 ( '''8%''')<br />
<br />
fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)<br />
<br />
Last translator: Duarte Loreto <happyguy_pt@hotmail.com><br />
Date of last update: 2003-07-28<br />
<br />
<br />
'''Portuguese/Brazillian''': pt_BR.po<br />
<br />
translated: 1546 ( '''72%''')<br />
<br />
fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)<br />
<br />
Last translator: Antônio Cláudio (LedStyle) <ledstyle@gmail.com><br />
Date of last update: 2006-04-27<br />
<br />
<br />
'''Russian''': ru.po<br />
<br />
translated: 1542 ( '''71%''')<br />
<br />
fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)<br />
<br />
Last translator: Alexandre Prokoudine <alexandre.prokoudine@gmail.com><br />
Date of last update: 2005-11-08<br />
<br />
<br />
'''Slovak''': sk.po<br />
<br />
translated: 845 ( '''39%''')<br />
<br />
fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)<br />
<br />
Last translator: Zdenko Podobný <zdpo@mailbox.sk><br />
Date of last update: 2005-02-13<br />
<br />
<br />
'''Slovenian''': sl.po<br />
<br />
translated: 2055 ( '''95%''')<br />
<br />
fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)<br />
<br />
Last translator: Martin Srebotnjak <miles@filmsi.net><br />
Date of last update: 2006-05-12<br />
<br />
<br />
'''Serbian''': sr.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Last translator: ÐлекÑандар Урошевић <urke@users.sourceforge.net><br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Serbian/Latine''': sr@Latn.po<br />
<br />
translated: 1359 ( '''63%''')<br />
<br />
fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)<br />
<br />
Last translator: Aleksandar Urošević <urke@users.sourceforge.net><br />
Date of last update: 2005-07-08<br />
<br />
<br />
'''Swedish''': sv.po<br />
<br />
translated: 410 ( '''19%''')<br />
<br />
fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)<br />
<br />
Last translator: Mattias Hultgren <mattias_hultgren@tele2.se><br />
Date of last update: 2005-10-08<br />
<br />
<br />
'''Turkish''': tr.po<br />
<br />
translated: 907 ( '''42%''')<br />
<br />
fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)<br />
<br />
Last translator: Serdar Soytetir <sendirom@gmail.com><br />
Date of last update: 2005-11-26<br />
<br />
<br />
'''Ukrainian''': uk.po<br />
<br />
translated: 1518 ( '''70%''')<br />
<br />
fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)<br />
<br />
Last translator: Maxim V. Dziumanenko <mvd@mylinux.com.ua><br />
Date of last update: 2005-10-21<br />
<br />
<br />
'''Chinese/Simplified''': zh_CN.po<br />
<br />
translated: 2134 ( '''99%''')<br />
<br />
fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)<br />
<br />
Last translator: Chris Jia <Chrisjiasl@gmail.com><br />
Date of last update: 2006-05-28<br />
<br />
<br />
'''Chinese/Traditional''': zh_TW.po<br />
<br />
translated: 1550 ( '''72 %''')<br />
<br />
fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)<br />
<br />
Last translator: Wei-Lun Chao <william.chao@ossii.com.tw><br />
Date of last update: 2006-03-24</div>Xaviconde