Inkscape Wiki - User contributions [en]

AboutScreenTranslation

2009-11-03T09:20:55Z

Cornelius:

"Draw Freely" about screen translations:

*about.be.svg -> Рысуй вольна (0.47)
*about.bg.svg -> РИϹУВАЙ ϹВОБОДНО (!)
*about.br.svg -> Tresit Dinask (0.47)
*about.cs.svg -> Kreslete svobodně  (!)
*about.de.svg -> frei zeichnen (0.47)
*about.es.svg -> Dibuja en libertad (0.47)
*about.fi.svg -> Piirrä vapaasti (0.47)
*about.fr.svg -> Dessiner librement (0.47)
*about.gl.svg -> Debuxa con liberdade (0.47)
*about.hu.svg -> Rajzoljon szabadon (0.47)
*about.it.svg -> Disegna in Libertà (0.47)
*about.nl.svg -> Vrij tekenen (0.47)
*about.pl.svg -> Rysuj swobodnie (0.47)
*about.pt_BR.svg -> Desenhe Livremente  (0.47)
*about.ru.svg -> Рисуй свободно (0.47)
*about.sk.svg -> Kreslite slobodne (0.47)
*about.sl.svg -> Rišite svobodno (0.47)
*about.sr@latin.svg -> Slobodno crtaj
*about.sr.svg -> Слободно цртај
*about.uk.svg -> Малюй вільно (0.47)
*about.ca.svg -> Dibuixa amb llibertat

(!) To be confirmed
(0.47) Screen translated in 0.47.

User:Cornelius

2007-03-23T13:43:18Z

Cornelius: /* Partially DONE */

= BIO =
* Name: Josef Vybíral
* Nickname: cornelius or cornelius[cz]
* Inkscape jobs: My main task in Inkscape world is to translate program and related documents to czech language. Also I have my fingers in inkscape.org website and in some presentations of Inkscape to the public too.
* Nationality: Czech republic, actually living near Moravian border with Poland.
As a creative artist and webdesigner I use Inkscape daily for my dayjob tasks together with GIMP and Scribus apps.

== Contact ==
* email: josef.vybiral (a) gmail (dot) com
* jabber: cornelius (a) njs (dot) netlab (dot) cz
* website: http://cornelius.gimp.cz

= My TODOs =
== Longterm tasks ==
* Translation of Inkscape
* Translation of website and wiki
* Update design of wiki.inkscape.org

== Partially DONE ==
* Translation of Inkscape 0.46
* Translation of website and wiki. Website is translated from 99% mainly thanks to Richard Szlachta(ricardo) and Lukáš Mašek(Luciash). Thanks guys for your help
* Translation of Tutorials for 0.44. Basic, advanced and tools tutorials translated by Lukáš Hess(lunreal) as high school semestral project, thanks for your help.

== Already DONE ==
* Translation of Inkscape 0.41, 0.42, 0.43, 0.44, 0.45
* Website translation

== Would like to do ==
* Conversion of inkscape.org to use .po files for translations
* Design ultimate icons theme for Inkscape

= Presentations of Inkscape =
* November 2005 - Inkscape, draw freely - conference LinuXChange 2005 Olomouc, CZ
* June 2006 - Inkscape, kresleme svobodně - Article in local Linux magazine presenting Inkscape 0.44

= Created by =
Hi Cornelius,

Thanks for all your work on the wiki! I have activated your sysop permissions, so you have some extra tools for managing the translated wiki pages and controlling spam. [[User:BryceHarrington|BryceHarrington]] 10:26, 13 June 2006 (PDT)

User:Cornelius

2007-03-23T13:43:05Z

Cornelius: /* Already DONE */

= BIO =
* Name: Josef Vybíral
* Nickname: cornelius or cornelius[cz]
* Inkscape jobs: My main task in Inkscape world is to translate program and related documents to czech language. Also I have my fingers in inkscape.org website and in some presentations of Inkscape to the public too.
* Nationality: Czech republic, actually living near Moravian border with Poland.
As a creative artist and webdesigner I use Inkscape daily for my dayjob tasks together with GIMP and Scribus apps.

== Contact ==
* email: josef.vybiral (a) gmail (dot) com
* jabber: cornelius (a) njs (dot) netlab (dot) cz
* website: http://cornelius.gimp.cz

= My TODOs =
== Longterm tasks ==
* Translation of Inkscape
* Translation of website and wiki
* Update design of wiki.inkscape.org

== Partially DONE ==
* Translation of Inkscape 0.45
* Translation of website and wiki. Website is translated from 99% mainly thanks to Richard Szlachta(ricardo) and Lukáš Mašek(Luciash). Thanks guys for your help
* Translation of Tutorials for 0.44. Basic, advanced and tools tutorials translated by Lukáš Hess(lunreal) as high school semestral project, thanks for your help.

== Already DONE ==
* Translation of Inkscape 0.41, 0.42, 0.43, 0.44, 0.45
* Website translation

== Would like to do ==
* Conversion of inkscape.org to use .po files for translations
* Design ultimate icons theme for Inkscape

= Presentations of Inkscape =
* November 2005 - Inkscape, draw freely - conference LinuXChange 2005 Olomouc, CZ
* June 2006 - Inkscape, kresleme svobodně - Article in local Linux magazine presenting Inkscape 0.44

= Created by =
Hi Cornelius,

Thanks for all your work on the wiki! I have activated your sysop permissions, so you have some extra tools for managing the translated wiki pages and controlling spam. [[User:BryceHarrington|BryceHarrington]] 10:26, 13 June 2006 (PDT)

Release notes/0.45

2007-03-20T06:16:52Z

Cornelius: /* Inkscape 0.45.1 changes with respect to 0.45 */ - adding updated translations

= Inkscape 0.45.1 changes with respect to 0.45 =

*Patch [ 1667939 ]: fix crash when tile-tracing with too small clones
*Patch [ 1666532 ]: Broken link in inkview man page
*Patch [ 1665447 ]: fix for the blur quantization bug 1617082
*Patch [ 1664849 ]: fix for 1662589: increase blur margins
*Patch [ 1664004 ]: embedimage.py with fixed search order
*Patch [ 1662649 ]: markers.svg with reversed order
*Crudely improve check-markup for { markup, fix translations with bugs in that area (dz and zh_TW).
*Patch [ 1659404 ]: Set locale directory from environment variable
*Patch [ 1657072 ]: fix for bug 1654495
*Patch [ 1654636 ]: defocus dropper checkboxes
*Adding japanese.nsh and russian.nsh into files that should go into the release tarball
*Correct russian translation
*Patch [ 1651797 ]: fix for attributes when saving/save-a-copy
*Patch [ 1651752 ]: fix dropper tool
*Pattern along path extension fixed on Windows
*Include libtiff3.dll in the Windows distribution, fixing crash when opening TIFF files
*Patch [ 1673067 ]: fix blur export on flowtext
*Patch [ 1678075 ]: fix FontInstance.cpp compile issue
*Patch [ 1673502 ]: fix broken Envelope (Summers Night) effect
*Patch [ 1680182 ]: fix pattern inversion on bool op (bug 1659445)
*Patch [ 1681754 ]: fix crash when editing text with multiple tspans
*Patch [ 1682425 ]: fix bug 1679477 (crash exporting gradients to ODG)
*Khmer translation now installs correctly
*Updated Slovak translation
*Updated Bulgarian translation
*Updated Catalan translation
*Updated Czech translation

= Inkscape 0.45: overview =

This release brings the exciting new features developed by the Google Summer of Code 2006 participants, as well as tons of other improvements across the board. Here are the highlights:

* '''Gaussian blur''' is the first SVG filter supported by Inkscape. You can blur any object to any extent - yet it remains vector and fully editable. This gives a huge boost to Inkscape as a creative art tool.

* '''Display speed and interactivity''': not only does Inkscape render faster, but it can now respond to user input before it finished redrawing the screen, which greatly improves the responsiveness (perceived speed or interactivity) of the program.

* '''History dialog''' makes it easy to to review your editing session and jump to any step of it, undoing and redoing multiple actions with one click.

* Several important tool features are added, notably the new selection mode in '''Node tool''' and the adjustable rounded caps in '''Calligraphic pen'''.

* '''Bitmap tracing''' works better for multi-color traces, sports a redesigned dialog and several new options.

* Many new '''extension effects''' are added, including '''Color effects''' and '''Pattern along path'''.

* The '''Outline mode''' has got many fixes and improvements, including a keyboard shortcut.

* Several new commands in '''Help''' menu open various Inkscape-related pages in your default browser, making Inkscape reference information more accessible as you work.

* Dozens of smaller '''features''' are added throughout the program, and hundreds of '''bugs''' are fixed.

= SVG filters: Gaussian blur =

Thanks to Google's Summer of Code program, Inkscape now has basic support for [http://www.w3.org/TR/SVG11/filters.html SVG filters]. The only filter enabled so far is '''Gaussian blur'''.

With it, you can softly and naturally blur any Inkscape objects: paths, shapes, groups, text, images. Clones inherit blurring from their original, but they can also be blurred independently from the original (you can create blurred clones with Tile Clones, too). Both the fill and stroke of an object are blurred together, creating semitransparent margins that smoothly blend into the background.

Gaussian blur 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.

* To blur selected objects, open the Fill and Stroke dialog (Ctrl+Shift+F) and use the '''Blur''' slider. The blur value is a percentage, with 100% corresponding to a blurring radius (standard deviation of Gaussian function) of 1/8 of the object's bounding box' perimeter (that is, for a square, a blur of 100% will have the radius equal to half a side, which turns any shape into an amorphous cloud).

* The '''Tile Clones''' dialog also supports blurring. On the '''Blur & opacity''' tab, you can set the blur percentage per row or per column of your tiling, as well as randomize blurring and make it alternate (all the same options as for Opacity).

* The quality of on-screen blur display is controlled by the '''Blur quality''' option on the new '''Filters''' tab of Inkscape Preferences (Ctrl+Shift+P). The available options range from best quality/slowest display to worst quality/fastest display, the default being in the middle of the range. Any setting except the "best quality" may introduce some rendering artifacts, especially when blurring thin strokes; on the other hand, the "best quality" setting may make Inkscape extremely slow at high zooms. These settings only affect the screen display of blurred objects; bitmap export always uses the best quality (and may therefore become quite slow for images with a lot of blur).

Here are a few tips on using blur:

* '''Masks and clipping''' are applied ''after'' blur. That is, if you clip an object and then blur it (or blur it first and then clip - it makes no difference), the clipped edges will remain crisp. Often, this is what you want. If, however, you want to blur the clipped/masked edges too (possibly with a different radius), you can use grouping: group the clipped object with some other object (which you can then delete from the group) and blur the group.

* A simple '''drop shadow''' is now very easy to do: just copy the object, paint the copy black, blur it, shift away a bit and lower it to the bottom. However, such a shadow does not update when you edit the foreground object. If your object is already black (or, more generally, if you want the shadow to be the same color as the object), you can clone instead of copy to make the shadow auto-updating. But what if your foreground object is not black but you need an auto-updating black shadow? Here's a recipe: unset the object's fill (it becomes black); create ''two'' clones of it; put one clone on top and paint any color you want; put the other clone at bottom, blur it and shift sideways. Now you can edit the unset-fill original (use Alt+click to select it) and everything will update.

* If an object has a fill that you don't want to blur (e.g. pattern, or if it's a bitmap), but you just want to '''feather the edges''', use a blurred transparency mask. For this, copy the object; paint it white; blur it as needed; scale the blurred copy down so its blur margins are entirely within the original object; select both the original and the blurred mask; do Object > Mask > Set.

* '''Transforming''' a blurred object '''transforms its blur''', too. This applies to a non-uniform scaling as well, so by squeezing a blurred object you make its blur squeezed as well. So, the easiest way to blur a path horizontally more than vertically is this: stretch it upwards without blur, then apply blur and squeeze it back into the original shape. (This only works if the stretched path does not already have a Transform attribute.)

* You can combine '''blurring with gradients'''. For example, an ellipse with elliptic opacity gradient will look much softer and more natural when blurred. An object with a horizontal linear opacity gradient, when blurred, will look as if it's more blurred on its transparent side than on its opaque side.

* A '''clone of a blurred object''' inherits the blur of the original. Therefore, such a clone can be blurred ''more'', but you can't "unblur" it to make the clone sharper than its original (unless, of course, you unlink it). The Fill and Stroke dialog shows you the amount of the blur applied to this particular object; however, if the object is a clone of an already blurred original, the dialog does not reflect that.

* Note that '''Firefox 2.0''' does not support SVG filters, so your files will be displayed in Firefox 2.0 without blur. However, filter support has been added in the current development version and will be included in Firefox 3.0. The Opera web browser, as well as librsvg (used by Wikipedia) and Batik, support filters correctly in their current versions.

= Undo history =

* Inkscape now features a History Dialog accessible via Ctrl+Shift+H or Edit > Undo History. All changes made to the document since it was opened are recorded here.

:* In the dialog, changes are listed from the '''oldest (top)''' to the '''newest (bottom)'''.

:* The type of each change is indicated by an '''icon''' and a short '''description'''.

:* For readability, consecutive changes of the same type are placed in a '''collapsible branch''' showing a triangle marker and the number of the hidden actions in the branch.

:* By clicking on an event in the list, you can easily '''move through the undo history''', i.e. undo or redo any number of actions with one click.

* The Undo and Redo commands in the Edit menu display the descriptions of the commands to be undone and redone, correspondingly. (These are the same descriptions that you see in the History dialog.)

= Rendering improvements =

* Interruptible display: Previously, Inkscape could not do anything until it finishes the current screen redraw. Now the redraw is made interruptible, so that Inkscape responds to mouse and keyboard input and can abort the current redraw and start over if you do some screen-changing operation. As a result, Inkscape now feels '''much snappier and more interactive'''. This interruptibility is fine-tuned for some continuous-drag operations (such as node dragging) so that a balance is achieved between responsiveness and completeness of display.

* Screen render is faster by '''2-3%''' overall:

:* Complex drawings with '''transparency''' are faster by up to '''5%'''.

:* '''Radial gradients''' are rendered faster by at least '''10%'''.

* Rendering (compositing) quality has been improved. This is most visible with (partially) transparent gradients: '''banding''' is a lot less pronounced now. Speed has also been improved in some cases.

* Display is more responsive when working at high zoom levels when using a tablet.

= Tools =

== Node tool ==

* You can grow or shrink node selection by hovering the mouse pointer over a node and using mousewheel (up = grow, down = shrink) or the keys PageUp (grow) and PageDown (shrink). ''Growing'' adds the closest unselected node to the selection; shrinking deselects the farthest selected node. There are two modes that differ by how the closest/farthest nodes are chosen:

:* Spatial selection (mousewheel, PageUp/PageDown): distances to nodes are measured directly, regardless of which subpath a node belongs to.

:* Linear selection (Ctrl+mousewheel, Ctrl+PageUp/Ctrl+PageDown): node distances are measured ''along the path'', and only the nodes belonging to the same subpath as the hovered node are considered (i.e. other subpaths are never selected).

:This technique is convenient for quickly selecting an area in a complex path starting from a center - for example, for node sculpting.

== Dropper ==

* Instead of the confusing toggle button, now the Controls bar for the Dropper tool has two checkboxes, '''Pick alpha''' and '''Set alpha''', which work as follows. Suppose you have an object selected and, using Dropper, click on an object which has red (#FF0000) fill and 0.5 opacity (half-transparent).

:* If the "Pick alpha" checkbox is off, the selected object will get the fill color #800000 (i.e. faded-out red) and fill opacity will be at 1.0 (opaque).

:* If the "Pick alpha" checkbox is on but "Set alpha" is off, the selected object will get the fill color #FF0000 (red) and fill opacity will be at 1.0.

:* If both "Pick alpha" and "Set alpha" are on, the selected object will get the fill color #FF0000 (red) and fill opacity will be at 0.5 (half-transparent).

:If you Shift+click instead of click, the same changes will be made to stroke color and stroke opacity, correspondingly. Note that in no situation can Dropper change the ''master opacity'' of the selected object(s) (only the fill/stroke opacity), although it can pick it just as it does any other kind of opacity.

== Calligraphy ==

* A new numeric parameter, Caps, controls the amount of protruding at the ends of calligraphic strokes. This parameter can range from 0 (flat caps, default behavior in previous versions) through 1 (approximately half-circle caps) and up to 5 (long elliptic caps). Rounded caps much improve the look of low-fixation strokes, simulating a rounded pen.

* The "Drag" parameter has been renamed to Wiggle with a value inversion (i.e. low drag corresponds to high wiggle, and vice versa). Increase this parameter (default is 0) to make the pen waver and wiggle in curly patterns.

* As a first step towards a redesign of the tools' controls, the '''Controls bar of the Calligraphy pen''' has been upgraded. Now it no longer prevents the Inkscape window from resizing narrower than the bar. The items on the far right end of the bar which didn't fit in a narrow window are still accessible through an '''expansion menu''' which allows you to toggle switches, select commands, and set values of numeric fields. Also, each editable numeric value field has a new '''right-click menu''' with some common values which often allows you to set a desired value much faster than by scrolling the control or typing the value into it.

* With low or zero Fixation parameter, some users of tablet pens experienced "blobs" (brief reversals of a stroke's right/left edges, causing "holes" and "bubbles" in a calligraphic stroke), especially often at the start of a stroke. Hopefully this problem is now fixed without reducing the responsiveness of the tool.

= Outline mode =

* A new menu command (View > Display Mode > Toggle) and a new keyboard shortcut (Ctrl+<keypad 5>) switch the display mode from Normal to Outline and back.

* The window title displays "(outline)" next to the file name when that editing window is in Outline mode.

* An object with mask and/or clipping path, when viewed in Outline mode, now displays both the object itself and its clipping path and mask as objects, using different outline colors. By default, clippaths use green outlines, and masks use blue.

* Images in Outline mode are displayed as red (by default) frames with two diagonals.

* An object with no fill and no stroke, invisible and not selectable by mouse clicking in normal mode, can now be picked by a mouse click in the Outline mode using its visible outline.

* The bug whereby stroked shapes didn't change stroke width when switching to Outline mode or back is fixed.

* All outline colors are changeable by editing the "wireframecolors" group inside "options" in the preferences file (~/.inkscape/preferences.xml). The "onlight" and "ondark" attributes set the colors of the regular object outlines on light and dark backgrounds (default black and white correspondingly); the "images", "clips", and "masks" attributes set the colors of images, clipping paths, and masks (defaults are red, green, and blue correspondingly). Each attribute is a decimal integer corresponding to the hex RRGGBBAA of the color.

* To cater for specialized uses, such as preparing input for personal media cutters, Inkscape now has an option to start in the Outline mode upon launch. To enable this, add the following line to your preferences.xml file:

:: <group id="startmode" outline="1"/>

:placing it after the <group id="options"> opening tag.

= Keyboard profiles =

The previous release allowed sets of keybindings (keymaps) to be created for Inkscape in the style of other applications. Two more keymaps have been added:

* '''Adobe Illustrator'''
* '''Macromedia Freehand'''

Of course not every feature in these other programs has a direct match to features in Inkscape; so, if you can, please '''help us out''' by reporting any problems you may have or improvements you would like to request.

Additionally, a keymap that focuses on tablet-based illustration and drawing work has been added:

* '''right-handed-illustration.xml'''

This keymap places all commonly-used commands under the left hand, so that the user's hands rarely leave the keyboard or the tablet/stylus.

(To enable a profile, copy it into <code>default.xml</code> in the same directory, overwriting the old file. To restore the default Inkscape set, copy <code>inkscape.xml</code> into <code>default.xml</code>.)

More of Inkscape's keys are implemented as actions and are therefore available for remapping via keyboard profiles. New actions include '''EditSelectNext''' and '''EditSelectPrev''' for selecting next/previous object or node (by default, they are bound to Tab/Shift+Tab; as a result of becoming global actions, these keys now work in all tools and not only in Selector and Node tool as before).

= Extension effects =

Inkscape's extension effects, written in Python using the '''inkex''' utility class, are currently a major growth point of the project. They allow new developers to create functionality very quickly, without having to learn Inkscape's huge C/C++ codebase. However, eventually we plan to move many of these effects into the core of Inkscape, which will make them much faster and more interactive. From this viewpoint, effects can be considered a quick way to prototype and test the algorithms and UI controls of the future Inkscape features. However, this does not prevent effects from being genuinely useful in everyday work, and in this version we have several excellent additions.

== New effects ==

* '''Pattern along path''': A new powerful extension in the "Generate from path" submenu allows you to bend, repeat and/or stretch a pattern object (which can be a path or a group) along a "skeleton" path. This makes it easy to create a variety of patterned and shaped strokes. (This obsoletes the old "Kochify" extension which is removed.)

:Effect's parameters include:

:* ''Copies of the pattern'' selects one of the four modes: '''Single stretched''': one copy of the pattern is placed on the skeleton path and stretched/squeezed to match its length; '''Repeated stretched''': as many copies as would fit are placed along the skeleton path and stretched to fit exactly; '''Single''' and '''Repeated''': same but without stretching.

:* ''Deformation type'' can be one of: '''Snake''' bends the pattern flatly in the plane of the drawing, the width not depending on direction; '''Ribbon''' bends it as a vertical ribbon or like a calligraphic stroke with maximum fixation, so that width depends on direction (minimum for vertical parts of the stroke, maximum for horizontal).

:* Several parameters allow you to adjust spacing between the copies of the pattern (for Multiple modes) and their offset in two directions (along the skeleton path and perpendicular to it).

:* Normally the effect assumes that the pattern object is horizontal and bends its horizontal axis (at mid-height) along the skeleton path. There's a checkbox that allows you to use a '''vertical pattern''' instead.

:Some examples of using this effect are shown on a screenshot at [http://inkscape.org/screenshots/gallery/inkscape-0.45-patternalongpath.png].

* '''Color effects''': A new group of extensions in the '''Color''' submenu of the Effects menu allows you to adjust all colors of a selection at once. These commands affect both fill and stroke colors, including gradients (but not bitmaps). The commands include:

:* a full set of '''HSL adjustments''' (increasing/decreasing hue, saturation, or lightness by 5%),

:* '''Brighter''' and '''Darker''' (adjust brightness up or down by 10%),

:* '''Desaturate''',

:* '''Grayscale''',

:* '''Negative''',

:* commands for removing or swapping the '''Red''', '''Green''', '''Blue''' channels,

:* a '''Custom''' command where you can set your own formulas for modifying the color channels.

:Some examples of using this effect are shown on a screenshot at [http://inkscape.org/screenshots/gallery/inkscape-0.45-coloreffects.png].

:Note: undoing color changes on gradients exposes a bug where an object seems to "disappear"; this is only a display issue (caused by the order in which gradients and their users are restored on undo) not causing any loss of information. Also, on large documents and large selections with gradients, Python's XPath code may get quite slow. Despite these shortcomings, we decided to add this extension, because it's genuinely useful functionality which was so far missing in Inkscape.

* Recent fixes in the processing of SVG <defs /> have made it possible to implement the often requested '''Color Markers to Match Stroke''' effect. It is no longer necessary to hand-edit XML to recolor arrowheads; just change the stroke color of your path and call this effect to recolor its markers to match.

* '''Lorem ipsum''' (in "Render" submenu) is a new extension that creates the traditional Latin-like random text for design mock-ups. The number of paragraphs, the number of sentences per paragraph and the possible fluctuation of the number of sentences (for uneven paragraphs) can be adjusted. If no flowed text element is selected, a new one in a new layer is created, matching the size of the canvas.

* '''Fractalize''' (in "Modify Path" submenu) replaces each segment of the selected path by a crooked line, subdivided to the given depth, with randomly displaced nodes.

* '''g2png''': The new group-to-PNG Python extension (g2png) is an easy way to export any group or layer to individual PNG files. It was first created for use in the [http://www.le-radar.com/?mm/inkscape Inkscape User Manual] (also available in SVN in the user_manual module) but is also interesting for many other uses. If e.g. you have to draw a set of icons, you can draw them in the same document, thus making copying, duplicating, cloning etc. easier. Then just create a group for each icon, and with the extension, each group ends up in its own PNG file.

== Improved effects ==

* The '''Function Plotter''' has been extended, providing greater flexibility in x- and y-range definition.

* The '''Measure Path''' extension is improved with several new parameters added (units, scale, precision, distance from path).

* The '''Extract One Image''' extension is fixed to automatically append filename extension to the created bitmap file.

* The "Blur Edge" extension is renamed into '''Inset/Outset Halo''' to avoid confusion with the real Gaussian blur that we now support, as well as to better describe what this extension actually does: From the selected path, it creates a group of inset and outset paths that form a stepped "halo" around the object.

== Infrastructure ==

* '''3 new parameter types''' have been added to the extension effect UI: '''tabs''', '''enumerations''' and '''optiongroups''' (radio buttons). Examples are available of how to use these parameters in INX files: the new Function Plotter uses tabs; enumerations are used by the Pattern along path extension; and a small developer example is given to illustrate the use of optiongroups (identical to enumerations).

* In an extension's INX file, you can specify <code><effects-menu hidden="yes"/></code> to hide that extension from the Effects menu. However, such a "hidden" extension can still be assigned a keyboard shortcut (by using its <code>id</code> as an "action" in your <code>~/.inkscape/keys/default.xml</code>).

* In an extension's INX file, you can add <code>needs-document="no"</code> attribute to the <code><effect></code> element. This indicates that the extension does not process the current SVG document, and Inkscape will not bother saving and restoring the document from a temporary file which allows this extension to run faster and smoother. (This is used for the new open-in-default-browser Help menu commands which are technically implemented as extensions.)

= Export formats =

== AI import/export ==

* We only support AI import and export for Adobe Illustrator 8.0 and older. This has been clarified in the Open and Save As lists.

== PDF export ==

Inkscape's PDF exporter has been improved:

* '''New features:''' bitmap images can be embedded; PDF files can be exported from command line using the <code>--export-pdf</code> parameter.

* '''Changed behavior:''' the pointless text to path question is gone.

* '''Fixed bugs:''' save failure is now detected, miter limits are now >= 1, PDFs with transparent gradient are now embeddable, eccentric elliptic gradients fixed, dash style inheritance fixed, transparency inheritance fixed.

== PS/EPS export ==

There's a new option to embed the fonts used in the document in the PS or EPS exported file. As of now, this works for Type 1 fonts only, not TrueType. The option is available when performing the export from the GUI as well as from the command line via the <code>--export-embed-fonts</code> option.

== EMF export ==

Inkscape has a limited support for exporting EMF (Enhanced Meta File) format. This works only on Windows, and only exports strokes and fills with constant colors. No text, no images, no gradients, no transparency.

= SVG output =

For specialized uses, several aspects of Inkscape's SVG output can now be customized via editing the preferences.xml file (there's no UI for these options). A <group id="svgoutput"> inside <group id="options"> can have the following attributes:

* usenamedcolors (default is 0). If nonzero, Inkscape uses symbolic color names (such as "white" or "lime") and three-digit color designations (such as $dfe) where appropriate; otherwise, it always uses six-digit colors (such as $d0f0e0). Note that in 0.44, the default was to use named colors, which created problems for some extension effects.

* numericprecision (default is 8). This is the number of significant digits written for each number into SVG. You can lower this number to get slightly more compact SVG at the expense of precision.

* minimumexponent (default is -8). In transform= attributes, any number whose absolute value is less than 10 to the power of minimumexponent (i.e. less than 10-8 by default) is written as 0.

* indent (default is 2) controls the number of spaces that each level of nesting in SVG is shifted. Set this to 0 to disable indentation.

* inlineattrs (default is 0). If nonzero, attributes are placed on the same line as their tags; otherwise they are separated by newlines.

= Bitmap tracing =

* A '''new color quantization algorithm''' for multiscan traces works faster (especially for large numbers of colors) and gives more adequate results with less colors used. This improves tracing results both for full-color photographs and for limited-color drawings.

* The Trace Bitmap dialog now provides access to three more tracing parameters:

:* '''Suppress speckles''': If set, spots or speckles larger than the given size (in pixels) are suppressed in the trace.

:* '''Smooth corners''': This parameter controls how much smoothing is applied to corners in the traced path.

:* '''Optimize paths''': If set, trace paths are optimized by joining adjacent Bezier segments with the given tolerance.

* All controls in the Trace Bitmap dialog are reorganized to be easier to find. The dialog is redesigned to use two main tabs: '''Mode''' (where you select the tracing mode, such as brightness cutoff or color multiscan) and '''Options''' (where you set various tracing options, such as corner smoothing). The preview is placed horizontally to the right of the tabs. Most labels and tooltips are rewritten for clarity. The trace preview image is made twice larger.

= Even more improvements =

* The '''opacity''' of objects is now displayed as percentage, '''from 0 to 100''', both in the Fill & Stroke dialog (with one fractional digit) and in the statusbar style indicator (with no fractional digits), instead of from 0 to 1.0 as before. This makes opacity values easier to read, type, and say.

* A '''Save a copy''' command has been added to the file menu, similar to the 'Save a copy' functionality of e.g. Adobe Illustrator. With this command, you can save your document under a new filename, but Inkscape will then "forget" it has done this: later saves will be to the old filename. The default shortcut assigned to this function is '''Shift+Ctrl+Alt+S'''.

* Text and flowed text objects behave more consistently. Now you can put a flowed text on path or (re)flow it into a shape just as you would do with a regular (unflowed) text. Previously, the need to convert a flowed text to text before these operations was a stumble for many users.

* Several commands were added to the '''Help menu''', providing the long-missing access to basic information about Inkscape and SVG right from the program: [http://tavmjong.free.fr/INKSCAPE/MANUAL/html/index.php Inkscape manual], [http://inkscape.org/doc/inkscape-man.html Command line options], [http://wiki.inkscape.org/wiki/index.php/FAQ FAQ], Release notes, [http://inkscape.org/report_bugs.php Bug report page], and the [http://www.w3.org/TR/SVG11/ SVG 1.1 specification]. All these commands open the corresponding web pages in the user's default web browser.

* Exported PNG images have the correct '''resolution''' set in the header.

* The Path -> '''Union''' (Ctrl++) operation now functions when only a '''single object''' is selected. Use this to '''remove self-intersections''' in path objects.

* We removed the "hacked" '''filename entry field''' that we had added to the Open and Save dialogs because starting from version 2.10, GTK+ has finally restored this field in their '''standard file dialog'''. The standard field at the top of the dialog supports type-ahead find and performs the default dialog action (open or save) by pressing Enter, which means you can now do a quick '''Ctrl+O, Ctrl+V, Enter''' sequence to open the file whose path is in your clipboard (this closes a long-standing usability bug). Those who use older versions of GTK are advised either to upgrade to 2.10 or use Ctrl+L to open a pop-up filename box. (Our Windows builds are shipped with GTK+ 2.10.)

* The '''Create Bitmap''' function (Alt+B in the default keymap) is made more useful. Unless you have specific resolution or minimum size set for this command in preferences.xml (<code><group id="createbitmap"/></code>), it will take the '''resolution hint''' from the object whose bitmap copy you are creating (in other words, it will use the resolution that you specified for that object when exporting it via the Export Bitmap dialog), or the default '''90 dpi''' if that object was not yet exported. Also, a 90 dpi bitmap (with its pixels exactly 1 px in size) will be '''snapped''' to the pixel grid. This makes it easy to use Create Bitmap for quick '''rasterization preview''' of an object or document. (Note: if you have used a previous version of Inkscape, your preferences.xml may contain <code>minsize="250"</code>; delete this for objects' resolution hints to work.)

* Using extended input (i.e. tablet pressure and tilt) can now be disabled via Preferences (Misc tab). This is intended to be a last-resort option for those platform/hardware combinations that are not properly supported by GTK. With extended input disabled, you can still use your tablet as a mouse.

* Simplify Path now has two modes when working with a group of paths: the default mode, which treats all of the paths as one large object to simplify, or the new mode, which acts the same as using Simplify on each path in a group separately. In preferences.xml, set '''options.simplifyindividualpaths''' to 1 to get the new mode.

* For long Simplify operations (more than 20 paths at a time), Inkscape provides user feedback via the status bar as to how many paths have been simplified. This change also prevents Inkscape from appearing to have locked up during the operation.

* New '''templates''' added for '''video formats''' (PAL, NTSC and HDTV 1080) as well as DVD cover templates that were not installed in the previous version. This will help video and DVD authoring with Inkscape. The business card 85×54 template is now installed as well.

* "Other" license type was added to the metadata/license dialog so that people know that they are entering a URI to an "other" license.

= Examples =

* With all the recent additions - clipping, masking, and especially blur - Inkscape is now able to produce extremely photorealistic art. In the share/examples folder in Inkscape distribution, you will find two brand new, stunningly realistic images of shiny cars: car.svgz by Konstantin Rotkevich and gallardo.svgz by Michael Grosberg.

* Inkscape 0.45 does not yet have gradient meshes. But with the addition of Gaussian Blur, this feature suddenly got within reach. A new example file, gradient-mesh-experimental.svgz, explains the approach Inkscape will likely take to implement this feature in a fully SVG-compatible way.

* Although Inkscape does not support animation yet, you can add any animation scripts and attributes to your SVG file manually in a text editor - and the file will still be editable in Inkscape. Tavmjong Bah used this technique to create animated-clock.svg which, when loaded in an SVG viewer supporting animation (such as Firefox, Opera, or Batik), demonstrates the intricate moving clockwork of a watch - and shows real time to boot! If loaded in Inkscape, the image is static, but instead you can freely edit any of the objects.

= Translations, tutorials, templates =

* Remarkable improvements are in the '''Danish''', '''Finnish''', '''Nepalese''' and the '''Vietnamese''' translations of the user interface. They all jumped from 0 to over 90 percent in a very short timespan.

* All people which are familiar with '''pig latin''' are now able to use Inkscape's user interface in that language. Isthay isway oughtbray otay usway ybay away ewnay anslatortray.

* Updated '''British English''', '''Catalan''', '''Czech''', '''Bulgarian''', '''French''', '''Danish''', '''Finnish''', '''German''', '''Brazilian Portuguese''' and '''Thai''', '''Vietnamese''' and '''Dzongkha''' translations.

* A new Esperanto translation added including default document template.

* Default Lithuanian template was not installed before, which is now fixed.

* New tutorial "Easter Eggs" by Steve Karg.

* Added Catalan default template and elements tutorial.

* Russian header and footer templates for tutorials are added.

* Several tutorial translations were updated, namely '''Catalan''', '''Brazilian Portuguese''', '''Russian''', '''German''', '''Danish''' and '''French'''.

* There are also new Russian and Japanese translations of Windows installer strings.

= Dependency changes =

* We have changed the '''GTK+''' requirement for compilation to version 2.8. However, it is highly recommended to use at least the version '''2.10.7''' because previous versions contain at least one crash bug which may cause Inkscape to crash after typing in a value into a spinbutton.

= Notable bugfixes =

* When deleting a node, neighboring smooth nodes are converted to cusp.

* Releasing the mouse button while dragging nodes using a tablet will now always release the nodes. Before this, a race condition could occur where dragging could continue after the mouse button was released.

* An object's mask and clipping path are now preserved after Simplify, Object/Stroke to path, or boolean operations.

* Ungrouping a group containing clipped/masked objects might sometime break the clip/mask (move it away); this is fixed.

* Transforming an object and its clone no longer behaves unexpectedly when they are both within a transformed group.

* User-supplied templates in ~/.inkscape/templates can now be SVGZ files in addition to SVG.

* Previously, Inkscape didn't check if there's enough free memory for its pixel buffers and could crash without warning due to insufficient memory e.g. upon zooming in. This problem became much worse after implementing Gaussian blur, because rendering blurred objects at high zooms may require a pixel buffer much bigger than the visible canvas. Now this situation is handled more gracefully: if a display operation requires more memory than available, or more than 100Mb (which corresponds to a 5000x5000 pixel buffer), it is skipped. This may result in blurred objects "disappearing" at high zooms. This is purely a display issue, however, and it never corrupts data; just zoom out (or reduce blur radius) and the disappeared object will show up OK.

* When resizing objects, scaling numbers in the statusbar are no longer overwritten by other text when pressing the modifier keys (Alt, Shift, Ctrl).

* To work around problems some users had with pressure-sensitive tablets ([http://sourceforge.net/tracker/index.php?func=detail&aid=1281512&group_id=93438&atid=604306 bug 1281512]), the pressure sensitivity can be disabled from the Misc tab of Inkscape Preferences dialog. After that, the tablet can still be used as a regular mouse.

* The layer widget in the statusbar used to lose its current layer after an effect run; this is fixed.

* When using different display resolutions or a dual screen setup, dialogs could be displayed off-screen; this is fixed: now Inkscape checks whether the saved position of the dialog is offscreen, if so it will move the dialog to the center of the screen. Note that this not solve all problems. If the dialog is still not visible, go to the [http://sourceforge.net/tracker/?func=detail&atid=604306&aid=1250236&group_id=93438 bug 1250236] where a procedure is given to make the dialog visible (by editing preferences.xml).

* Grid and guidelines no longer vanish when changing their color.

* Group transformation is now correctly re-applied when ungrouping and then undoing the ungroup operation.

* Text dialog no longer discards the style of the selected text.

* Inkscape no longer crashes when you try to unflow an empty flowed text.

* Thanks to patches submitted by users of our community, Inkscape can now be built on SGI IRIX 6.5.28, gcc 3.4.0 systems and on Tru64 systems.

= Known problems =

==== Problem with "Dialogs on Top" on Windows ====

* Although the "Dialogs on Top" option is now available on Windows (File > Inkscape Preferences > Windows), it does not work exactly as it should (yet!). When the document window is minimized, the dialogs remain visible, i.e. are not minimized together with the document window. Because of this, it is not possible to get the document window back by clicking its taskbar button. A workaround to this problem is to '''right-click the Inkscape taskbar button and select "Restore".''' We expect that future releases of GTK will solve this problem.

==== Spinbuttons may crash if you have GTK+ older than 2.10.7 ====

* You may experience crashes after typing in a value into a spinbutton if you have a version of GTK+ 2.10.6 or older. Upgrade your GTK+ to fix this. (This does not affect the Windows package as it comes with GTK+ 2.10.9.)

==== Numerical Python required for Perspective effect ====

* This effect will not work until you install a python module called '''numpy''' (Numerical Python). It can be downloaded at [http://numpy.scipy.org/ numpy.scipy.org]. The Windows package already contains this module.

==== Do not use a clone of an object as its clipping path/mask ====

* In this version, you cannot use an object's clone as its clipping path or mask. Either unlink the clone first, or clip one clone of a source object (not the source itself) by another clone of the same. Properly fixing this bug requires some deep changes in the code and therefore was postponed until after 0.45 so as not to delay the release.

==== Non-Unicode symbol fonts on Windows don't work ====

* On Windows, symbol fonts without a Unicode map do not work. This is a limitation of the Pango library that we use.

==== Problems with some Debian libgc-6.7 packages ====

* Inkscape will hang or crash when linked with the first Debian packaged version of the Boehm garbage collection library. This problem was fixed in version 1:6.7-2 of the package. If you have libgc 6.7 on your Debian-based system, make sure that you are using that version of the package or later.

==== Beware of defective themes on Linux ====

* Inkscape and other Gtk programs can crash on any Linux, when the gtk2-engines-smooth / libsmooth 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. Update: this bug appears to be fixed in newer versions of gtk-engines. If you are affected by this problem please update to a newer version of gtk-engines. If problems persist then please inform the gtk-engines maintainers of the problem.

* A similar crash happens if the KDE Baghira theme or the package gtk_qt_engine 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.

= Previous releases =

* [[ReleaseNotes044]]
* [[ReleaseNotes043]]
* [[ReleaseNotes042]]
* [[ReleaseNotes041]]
* [[ReleaseNotes040]]
* [[ReleaseNotes039]]
* [[ReleaseNotes038]]
* [[ReleaseNotes037]]
* [[ReleaseNotes036]]
* [[ReleaseNotes035]]

Release notes/0.45

2007-03-18T11:54:12Z

Cornelius: removing spam by user Fe

= Inkscape 0.45.1 changes with respect to 0.45 =

*Patch [ 1667939 ]: fix crash when tile-tracing with too small clones
*Patch [ 1666532 ]: Broken link in inkview man page
*Patch [ 1665447 ]: fix for the blur quantization bug 1617082
*Patch [ 1664849 ]: fix for 1662589: increase blur margins
*Patch [ 1664004 ]: embedimage.py with fixed search order
*Patch [ 1662649 ]: markers.svg with reversed order
*Crudely improve check-markup for { markup, fix translations with bugs in that area (dz and zh_TW).
*Patch [ 1659404 ]: Set locale directory from environment variable
*Patch [ 1657072 ]: fix for bug 1654495
*Patch [ 1654636 ]: defocus dropper checkboxes
*Updated slovak translation
*Adding japanese.nsh and russian.nsh into files that should go into the release tarball
*Correct russian translation
*Patch [ 1651797 ]: fix for attributes when saving/save-a-copy
*Patch [ 1651752 ]: fix dropper tool
*Pattern along path extension fixed on Windows
*Include libtiff3.dll in the Windows distribution, fixing crash when opening TIFF files
*Patch [ 1673067 ]: fix blur export on flowtext
*Patch [ 1678075 ]: fix FontInstance.cpp compile issue
*Patch [ 1673502 ]: fix broken Envelope (Summers Night) effect
*Patch [ 1680182 ]: fix pattern inversion on bool op (bug 1659445)
*Patch [ 1681754 ]: fix crash when editing text with multiple tspans
*Patch [ 1682425 ]: fix bug 1679477 (crash exporting gradients to ODG)

= Inkscape 0.45: overview =

This release brings the exciting new features developed by the Google Summer of Code 2006 participants, as well as tons of other improvements across the board. Here are the highlights:

* '''Gaussian blur''' is the first SVG filter supported by Inkscape. You can blur any object to any extent - yet it remains vector and fully editable. This gives a huge boost to Inkscape as a creative art tool.

* '''Display speed and interactivity''': not only does Inkscape render faster, but it can now respond to user input before it finished redrawing the screen, which greatly improves the responsiveness (perceived speed or interactivity) of the program.

* '''History dialog''' makes it easy to to review your editing session and jump to any step of it, undoing and redoing multiple actions with one click.

* Several important tool features are added, notably the new selection mode in '''Node tool''' and the adjustable rounded caps in '''Calligraphic pen'''.

* '''Bitmap tracing''' works better for multi-color traces, sports a redesigned dialog and several new options.

* Many new '''extension effects''' are added, including '''Color effects''' and '''Pattern along path'''.

* The '''Outline mode''' has got many fixes and improvements, including a keyboard shortcut.

* Several new commands in '''Help''' menu open various Inkscape-related pages in your default browser, making Inkscape reference information more accessible as you work.

* Dozens of smaller '''features''' are added throughout the program, and hundreds of '''bugs''' are fixed.

= SVG filters: Gaussian blur =

Thanks to Google's Summer of Code program, Inkscape now has basic support for [http://www.w3.org/TR/SVG11/filters.html SVG filters]. The only filter enabled so far is '''Gaussian blur'''.

With it, you can softly and naturally blur any Inkscape objects: paths, shapes, groups, text, images. Clones inherit blurring from their original, but they can also be blurred independently from the original (you can create blurred clones with Tile Clones, too). Both the fill and stroke of an object are blurred together, creating semitransparent margins that smoothly blend into the background.

Gaussian blur 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.

* To blur selected objects, open the Fill and Stroke dialog (Ctrl+Shift+F) and use the '''Blur''' slider. The blur value is a percentage, with 100% corresponding to a blurring radius (standard deviation of Gaussian function) of 1/8 of the object's bounding box' perimeter (that is, for a square, a blur of 100% will have the radius equal to half a side, which turns any shape into an amorphous cloud).

* The '''Tile Clones''' dialog also supports blurring. On the '''Blur & opacity''' tab, you can set the blur percentage per row or per column of your tiling, as well as randomize blurring and make it alternate (all the same options as for Opacity).

* The quality of on-screen blur display is controlled by the '''Blur quality''' option on the new '''Filters''' tab of Inkscape Preferences (Ctrl+Shift+P). The available options range from best quality/slowest display to worst quality/fastest display, the default being in the middle of the range. Any setting except the "best quality" may introduce some rendering artifacts, especially when blurring thin strokes; on the other hand, the "best quality" setting may make Inkscape extremely slow at high zooms. These settings only affect the screen display of blurred objects; bitmap export always uses the best quality (and may therefore become quite slow for images with a lot of blur).

Here are a few tips on using blur:

* '''Masks and clipping''' are applied ''after'' blur. That is, if you clip an object and then blur it (or blur it first and then clip - it makes no difference), the clipped edges will remain crisp. Often, this is what you want. If, however, you want to blur the clipped/masked edges too (possibly with a different radius), you can use grouping: group the clipped object with some other object (which you can then delete from the group) and blur the group.

* A simple '''drop shadow''' is now very easy to do: just copy the object, paint the copy black, blur it, shift away a bit and lower it to the bottom. However, such a shadow does not update when you edit the foreground object. If your object is already black (or, more generally, if you want the shadow to be the same color as the object), you can clone instead of copy to make the shadow auto-updating. But what if your foreground object is not black but you need an auto-updating black shadow? Here's a recipe: unset the object's fill (it becomes black); create ''two'' clones of it; put one clone on top and paint any color you want; put the other clone at bottom, blur it and shift sideways. Now you can edit the unset-fill original (use Alt+click to select it) and everything will update.

* If an object has a fill that you don't want to blur (e.g. pattern, or if it's a bitmap), but you just want to '''feather the edges''', use a blurred transparency mask. For this, copy the object; paint it white; blur it as needed; scale the blurred copy down so its blur margins are entirely within the original object; select both the original and the blurred mask; do Object > Mask > Set.

* '''Transforming''' a blurred object '''transforms its blur''', too. This applies to a non-uniform scaling as well, so by squeezing a blurred object you make its blur squeezed as well. So, the easiest way to blur a path horizontally more than vertically is this: stretch it upwards without blur, then apply blur and squeeze it back into the original shape. (This only works if the stretched path does not already have a Transform attribute.)

* You can combine '''blurring with gradients'''. For example, an ellipse with elliptic opacity gradient will look much softer and more natural when blurred. An object with a horizontal linear opacity gradient, when blurred, will look as if it's more blurred on its transparent side than on its opaque side.

* A '''clone of a blurred object''' inherits the blur of the original. Therefore, such a clone can be blurred ''more'', but you can't "unblur" it to make the clone sharper than its original (unless, of course, you unlink it). The Fill and Stroke dialog shows you the amount of the blur applied to this particular object; however, if the object is a clone of an already blurred original, the dialog does not reflect that.

* Note that '''Firefox 2.0''' does not support SVG filters, so your files will be displayed in Firefox 2.0 without blur. However, filter support has been added in the current development version and will be included in Firefox 3.0. The Opera web browser, as well as librsvg (used by Wikipedia) and Batik, support filters correctly in their current versions.

= Undo history =

* Inkscape now features a History Dialog accessible via Ctrl+Shift+H or Edit > Undo History. All changes made to the document since it was opened are recorded here.

:* In the dialog, changes are listed from the '''oldest (top)''' to the '''newest (bottom)'''.

:* The type of each change is indicated by an '''icon''' and a short '''description'''.

:* For readability, consecutive changes of the same type are placed in a '''collapsible branch''' showing a triangle marker and the number of the hidden actions in the branch.

:* By clicking on an event in the list, you can easily '''move through the undo history''', i.e. undo or redo any number of actions with one click.

* The Undo and Redo commands in the Edit menu display the descriptions of the commands to be undone and redone, correspondingly. (These are the same descriptions that you see in the History dialog.)

= Rendering improvements =

* Interruptible display: Previously, Inkscape could not do anything until it finishes the current screen redraw. Now the redraw is made interruptible, so that Inkscape responds to mouse and keyboard input and can abort the current redraw and start over if you do some screen-changing operation. As a result, Inkscape now feels '''much snappier and more interactive'''. This interruptibility is fine-tuned for some continuous-drag operations (such as node dragging) so that a balance is achieved between responsiveness and completeness of display.

* Screen render is faster by '''2-3%''' overall:

:* Complex drawings with '''transparency''' are faster by up to '''5%'''.

:* '''Radial gradients''' are rendered faster by at least '''10%'''.

* Rendering (compositing) quality has been improved. This is most visible with (partially) transparent gradients: '''banding''' is a lot less pronounced now. Speed has also been improved in some cases.

* Display is more responsive when working at high zoom levels when using a tablet.

= Tools =

== Node tool ==

* You can grow or shrink node selection by hovering the mouse pointer over a node and using mousewheel (up = grow, down = shrink) or the keys PageUp (grow) and PageDown (shrink). ''Growing'' adds the closest unselected node to the selection; shrinking deselects the farthest selected node. There are two modes that differ by how the closest/farthest nodes are chosen:

:* Spatial selection (mousewheel, PageUp/PageDown): distances to nodes are measured directly, regardless of which subpath a node belongs to.

:* Linear selection (Ctrl+mousewheel, Ctrl+PageUp/Ctrl+PageDown): node distances are measured ''along the path'', and only the nodes belonging to the same subpath as the hovered node are considered (i.e. other subpaths are never selected).

:This technique is convenient for quickly selecting an area in a complex path starting from a center - for example, for node sculpting.

== Dropper ==

* Instead of the confusing toggle button, now the Controls bar for the Dropper tool has two checkboxes, '''Pick alpha''' and '''Set alpha''', which work as follows. Suppose you have an object selected and, using Dropper, click on an object which has red (#FF0000) fill and 0.5 opacity (half-transparent).

:* If the "Pick alpha" checkbox is off, the selected object will get the fill color #800000 (i.e. faded-out red) and fill opacity will be at 1.0 (opaque).

:* If the "Pick alpha" checkbox is on but "Set alpha" is off, the selected object will get the fill color #FF0000 (red) and fill opacity will be at 1.0.

:* If both "Pick alpha" and "Set alpha" are on, the selected object will get the fill color #FF0000 (red) and fill opacity will be at 0.5 (half-transparent).

:If you Shift+click instead of click, the same changes will be made to stroke color and stroke opacity, correspondingly. Note that in no situation can Dropper change the ''master opacity'' of the selected object(s) (only the fill/stroke opacity), although it can pick it just as it does any other kind of opacity.

== Calligraphy ==

* A new numeric parameter, Caps, controls the amount of protruding at the ends of calligraphic strokes. This parameter can range from 0 (flat caps, default behavior in previous versions) through 1 (approximately half-circle caps) and up to 5 (long elliptic caps). Rounded caps much improve the look of low-fixation strokes, simulating a rounded pen.

* The "Drag" parameter has been renamed to Wiggle with a value inversion (i.e. low drag corresponds to high wiggle, and vice versa). Increase this parameter (default is 0) to make the pen waver and wiggle in curly patterns.

* As a first step towards a redesign of the tools' controls, the '''Controls bar of the Calligraphy pen''' has been upgraded. Now it no longer prevents the Inkscape window from resizing narrower than the bar. The items on the far right end of the bar which didn't fit in a narrow window are still accessible through an '''expansion menu''' which allows you to toggle switches, select commands, and set values of numeric fields. Also, each editable numeric value field has a new '''right-click menu''' with some common values which often allows you to set a desired value much faster than by scrolling the control or typing the value into it.

* With low or zero Fixation parameter, some users of tablet pens experienced "blobs" (brief reversals of a stroke's right/left edges, causing "holes" and "bubbles" in a calligraphic stroke), especially often at the start of a stroke. Hopefully this problem is now fixed without reducing the responsiveness of the tool.

= Outline mode =

* A new menu command (View > Display Mode > Toggle) and a new keyboard shortcut (Ctrl+<keypad 5>) switch the display mode from Normal to Outline and back.

* The window title displays "(outline)" next to the file name when that editing window is in Outline mode.

* An object with mask and/or clipping path, when viewed in Outline mode, now displays both the object itself and its clipping path and mask as objects, using different outline colors. By default, clippaths use green outlines, and masks use blue.

* Images in Outline mode are displayed as red (by default) frames with two diagonals.

* An object with no fill and no stroke, invisible and not selectable by mouse clicking in normal mode, can now be picked by a mouse click in the Outline mode using its visible outline.

* The bug whereby stroked shapes didn't change stroke width when switching to Outline mode or back is fixed.

* All outline colors are changeable by editing the "wireframecolors" group inside "options" in the preferences file (~/.inkscape/preferences.xml). The "onlight" and "ondark" attributes set the colors of the regular object outlines on light and dark backgrounds (default black and white correspondingly); the "images", "clips", and "masks" attributes set the colors of images, clipping paths, and masks (defaults are red, green, and blue correspondingly). Each attribute is a decimal integer corresponding to the hex RRGGBBAA of the color.

* To cater for specialized uses, such as preparing input for personal media cutters, Inkscape now has an option to start in the Outline mode upon launch. To enable this, add the following line to your preferences.xml file:

:: <group id="startmode" outline="1"/>

:placing it after the <group id="options"> opening tag.

= Keyboard profiles =

The previous release allowed sets of keybindings (keymaps) to be created for Inkscape in the style of other applications. Two more keymaps have been added:

* '''Adobe Illustrator'''
* '''Macromedia Freehand'''

Of course not every feature in these other programs has a direct match to features in Inkscape; so, if you can, please '''help us out''' by reporting any problems you may have or improvements you would like to request.

Additionally, a keymap that focuses on tablet-based illustration and drawing work has been added:

* '''right-handed-illustration.xml'''

This keymap places all commonly-used commands under the left hand, so that the user's hands rarely leave the keyboard or the tablet/stylus.

(To enable a profile, copy it into <code>default.xml</code> in the same directory, overwriting the old file. To restore the default Inkscape set, copy <code>inkscape.xml</code> into <code>default.xml</code>.)

More of Inkscape's keys are implemented as actions and are therefore available for remapping via keyboard profiles. New actions include '''EditSelectNext''' and '''EditSelectPrev''' for selecting next/previous object or node (by default, they are bound to Tab/Shift+Tab; as a result of becoming global actions, these keys now work in all tools and not only in Selector and Node tool as before).

= Extension effects =

Inkscape's extension effects, written in Python using the '''inkex''' utility class, are currently a major growth point of the project. They allow new developers to create functionality very quickly, without having to learn Inkscape's huge C/C++ codebase. However, eventually we plan to move many of these effects into the core of Inkscape, which will make them much faster and more interactive. From this viewpoint, effects can be considered a quick way to prototype and test the algorithms and UI controls of the future Inkscape features. However, this does not prevent effects from being genuinely useful in everyday work, and in this version we have several excellent additions.

== New effects ==

* '''Pattern along path''': A new powerful extension in the "Generate from path" submenu allows you to bend, repeat and/or stretch a pattern object (which can be a path or a group) along a "skeleton" path. This makes it easy to create a variety of patterned and shaped strokes. (This obsoletes the old "Kochify" extension which is removed.)

:Effect's parameters include:

:* ''Copies of the pattern'' selects one of the four modes: '''Single stretched''': one copy of the pattern is placed on the skeleton path and stretched/squeezed to match its length; '''Repeated stretched''': as many copies as would fit are placed along the skeleton path and stretched to fit exactly; '''Single''' and '''Repeated''': same but without stretching.

:* ''Deformation type'' can be one of: '''Snake''' bends the pattern flatly in the plane of the drawing, the width not depending on direction; '''Ribbon''' bends it as a vertical ribbon or like a calligraphic stroke with maximum fixation, so that width depends on direction (minimum for vertical parts of the stroke, maximum for horizontal).

:* Several parameters allow you to adjust spacing between the copies of the pattern (for Multiple modes) and their offset in two directions (along the skeleton path and perpendicular to it).

:* Normally the effect assumes that the pattern object is horizontal and bends its horizontal axis (at mid-height) along the skeleton path. There's a checkbox that allows you to use a '''vertical pattern''' instead.

:Some examples of using this effect are shown on a screenshot at [http://inkscape.org/screenshots/gallery/inkscape-0.45-patternalongpath.png].

* '''Color effects''': A new group of extensions in the '''Color''' submenu of the Effects menu allows you to adjust all colors of a selection at once. These commands affect both fill and stroke colors, including gradients (but not bitmaps). The commands include:

:* a full set of '''HSL adjustments''' (increasing/decreasing hue, saturation, or lightness by 5%),

:* '''Brighter''' and '''Darker''' (adjust brightness up or down by 10%),

:* '''Desaturate''',

:* '''Grayscale''',

:* '''Negative''',

:* commands for removing or swapping the '''Red''', '''Green''', '''Blue''' channels,

:* a '''Custom''' command where you can set your own formulas for modifying the color channels.

:Some examples of using this effect are shown on a screenshot at [http://inkscape.org/screenshots/gallery/inkscape-0.45-coloreffects.png].

:Note: undoing color changes on gradients exposes a bug where an object seems to "disappear"; this is only a display issue (caused by the order in which gradients and their users are restored on undo) not causing any loss of information. Also, on large documents and large selections with gradients, Python's XPath code may get quite slow. Despite these shortcomings, we decided to add this extension, because it's genuinely useful functionality which was so far missing in Inkscape.

* Recent fixes in the processing of SVG <defs /> have made it possible to implement the often requested '''Color Markers to Match Stroke''' effect. It is no longer necessary to hand-edit XML to recolor arrowheads; just change the stroke color of your path and call this effect to recolor its markers to match.

* '''Lorem ipsum''' (in "Render" submenu) is a new extension that creates the traditional Latin-like random text for design mock-ups. The number of paragraphs, the number of sentences per paragraph and the possible fluctuation of the number of sentences (for uneven paragraphs) can be adjusted. If no flowed text element is selected, a new one in a new layer is created, matching the size of the canvas.

* '''Fractalize''' (in "Modify Path" submenu) replaces each segment of the selected path by a crooked line, subdivided to the given depth, with randomly displaced nodes.

* '''g2png''': The new group-to-PNG Python extension (g2png) is an easy way to export any group or layer to individual PNG files. It was first created for use in the [http://www.le-radar.com/?mm/inkscape Inkscape User Manual] (also available in SVN in the user_manual module) but is also interesting for many other uses. If e.g. you have to draw a set of icons, you can draw them in the same document, thus making copying, duplicating, cloning etc. easier. Then just create a group for each icon, and with the extension, each group ends up in its own PNG file.

== Improved effects ==

* The '''Function Plotter''' has been extended, providing greater flexibility in x- and y-range definition.

* The '''Measure Path''' extension is improved with several new parameters added (units, scale, precision, distance from path).

* The '''Extract One Image''' extension is fixed to automatically append filename extension to the created bitmap file.

* The "Blur Edge" extension is renamed into '''Inset/Outset Halo''' to avoid confusion with the real Gaussian blur that we now support, as well as to better describe what this extension actually does: From the selected path, it creates a group of inset and outset paths that form a stepped "halo" around the object.

== Infrastructure ==

* '''3 new parameter types''' have been added to the extension effect UI: '''tabs''', '''enumerations''' and '''optiongroups''' (radio buttons). Examples are available of how to use these parameters in INX files: the new Function Plotter uses tabs; enumerations are used by the Pattern along path extension; and a small developer example is given to illustrate the use of optiongroups (identical to enumerations).

* In an extension's INX file, you can specify <code><effects-menu hidden="yes"/></code> to hide that extension from the Effects menu. However, such a "hidden" extension can still be assigned a keyboard shortcut (by using its <code>id</code> as an "action" in your <code>~/.inkscape/keys/default.xml</code>).

* In an extension's INX file, you can add <code>needs-document="no"</code> attribute to the <code><effect></code> element. This indicates that the extension does not process the current SVG document, and Inkscape will not bother saving and restoring the document from a temporary file which allows this extension to run faster and smoother. (This is used for the new open-in-default-browser Help menu commands which are technically implemented as extensions.)

= Export formats =

== AI import/export ==

* We only support AI import and export for Adobe Illustrator 8.0 and older. This has been clarified in the Open and Save As lists.

== PDF export ==

Inkscape's PDF exporter has been improved:

* '''New features:''' bitmap images can be embedded; PDF files can be exported from command line using the <code>--export-pdf</code> parameter.

* '''Changed behavior:''' the pointless text to path question is gone.

* '''Fixed bugs:''' save failure is now detected, miter limits are now >= 1, PDFs with transparent gradient are now embeddable, eccentric elliptic gradients fixed, dash style inheritance fixed, transparency inheritance fixed.

== PS/EPS export ==

There's a new option to embed the fonts used in the document in the PS or EPS exported file. As of now, this works for Type 1 fonts only, not TrueType. The option is available when performing the export from the GUI as well as from the command line via the <code>--export-embed-fonts</code> option.

== EMF export ==

Inkscape has a limited support for exporting EMF (Enhanced Meta File) format. This works only on Windows, and only exports strokes and fills with constant colors. No text, no images, no gradients, no transparency.

= SVG output =

For specialized uses, several aspects of Inkscape's SVG output can now be customized via editing the preferences.xml file (there's no UI for these options). A <group id="svgoutput"> inside <group id="options"> can have the following attributes:

* usenamedcolors (default is 0). If nonzero, Inkscape uses symbolic color names (such as "white" or "lime") and three-digit color designations (such as $dfe) where appropriate; otherwise, it always uses six-digit colors (such as $d0f0e0). Note that in 0.44, the default was to use named colors, which created problems for some extension effects.

* numericprecision (default is 8). This is the number of significant digits written for each number into SVG. You can lower this number to get slightly more compact SVG at the expense of precision.

* minimumexponent (default is -8). In transform= attributes, any number whose absolute value is less than 10 to the power of minimumexponent (i.e. less than 10-8 by default) is written as 0.

* indent (default is 2) controls the number of spaces that each level of nesting in SVG is shifted. Set this to 0 to disable indentation.

* inlineattrs (default is 0). If nonzero, attributes are placed on the same line as their tags; otherwise they are separated by newlines.

= Bitmap tracing =

* A '''new color quantization algorithm''' for multiscan traces works faster (especially for large numbers of colors) and gives more adequate results with less colors used. This improves tracing results both for full-color photographs and for limited-color drawings.

* The Trace Bitmap dialog now provides access to three more tracing parameters:

:* '''Suppress speckles''': If set, spots or speckles larger than the given size (in pixels) are suppressed in the trace.

:* '''Smooth corners''': This parameter controls how much smoothing is applied to corners in the traced path.

:* '''Optimize paths''': If set, trace paths are optimized by joining adjacent Bezier segments with the given tolerance.

* All controls in the Trace Bitmap dialog are reorganized to be easier to find. The dialog is redesigned to use two main tabs: '''Mode''' (where you select the tracing mode, such as brightness cutoff or color multiscan) and '''Options''' (where you set various tracing options, such as corner smoothing). The preview is placed horizontally to the right of the tabs. Most labels and tooltips are rewritten for clarity. The trace preview image is made twice larger.

= Even more improvements =

* The '''opacity''' of objects is now displayed as percentage, '''from 0 to 100''', both in the Fill & Stroke dialog (with one fractional digit) and in the statusbar style indicator (with no fractional digits), instead of from 0 to 1.0 as before. This makes opacity values easier to read, type, and say.

* A '''Save a copy''' command has been added to the file menu, similar to the 'Save a copy' functionality of e.g. Adobe Illustrator. With this command, you can save your document under a new filename, but Inkscape will then "forget" it has done this: later saves will be to the old filename. The default shortcut assigned to this function is '''Shift+Ctrl+Alt+S'''.

* Text and flowed text objects behave more consistently. Now you can put a flowed text on path or (re)flow it into a shape just as you would do with a regular (unflowed) text. Previously, the need to convert a flowed text to text before these operations was a stumble for many users.

* Several commands were added to the '''Help menu''', providing the long-missing access to basic information about Inkscape and SVG right from the program: [http://tavmjong.free.fr/INKSCAPE/MANUAL/html/index.php Inkscape manual], [http://inkscape.org/doc/inkscape-man.html Command line options], [http://wiki.inkscape.org/wiki/index.php/FAQ FAQ], Release notes, [http://inkscape.org/report_bugs.php Bug report page], and the [http://www.w3.org/TR/SVG11/ SVG 1.1 specification]. All these commands open the corresponding web pages in the user's default web browser.

* Exported PNG images have the correct '''resolution''' set in the header.

* The Path -> '''Union''' (Ctrl++) operation now functions when only a '''single object''' is selected. Use this to '''remove self-intersections''' in path objects.

* We removed the "hacked" '''filename entry field''' that we had added to the Open and Save dialogs because starting from version 2.10, GTK+ has finally restored this field in their '''standard file dialog'''. The standard field at the top of the dialog supports type-ahead find and performs the default dialog action (open or save) by pressing Enter, which means you can now do a quick '''Ctrl+O, Ctrl+V, Enter''' sequence to open the file whose path is in your clipboard (this closes a long-standing usability bug). Those who use older versions of GTK are advised either to upgrade to 2.10 or use Ctrl+L to open a pop-up filename box. (Our Windows builds are shipped with GTK+ 2.10.)

* The '''Create Bitmap''' function (Alt+B in the default keymap) is made more useful. Unless you have specific resolution or minimum size set for this command in preferences.xml (<code><group id="createbitmap"/></code>), it will take the '''resolution hint''' from the object whose bitmap copy you are creating (in other words, it will use the resolution that you specified for that object when exporting it via the Export Bitmap dialog), or the default '''90 dpi''' if that object was not yet exported. Also, a 90 dpi bitmap (with its pixels exactly 1 px in size) will be '''snapped''' to the pixel grid. This makes it easy to use Create Bitmap for quick '''rasterization preview''' of an object or document. (Note: if you have used a previous version of Inkscape, your preferences.xml may contain <code>minsize="250"</code>; delete this for objects' resolution hints to work.)

* Using extended input (i.e. tablet pressure and tilt) can now be disabled via Preferences (Misc tab). This is intended to be a last-resort option for those platform/hardware combinations that are not properly supported by GTK. With extended input disabled, you can still use your tablet as a mouse.

* Simplify Path now has two modes when working with a group of paths: the default mode, which treats all of the paths as one large object to simplify, or the new mode, which acts the same as using Simplify on each path in a group separately. In preferences.xml, set '''options.simplifyindividualpaths''' to 1 to get the new mode.

* For long Simplify operations (more than 20 paths at a time), Inkscape provides user feedback via the status bar as to how many paths have been simplified. This change also prevents Inkscape from appearing to have locked up during the operation.

* New '''templates''' added for '''video formats''' (PAL, NTSC and HDTV 1080) as well as DVD cover templates that were not installed in the previous version. This will help video and DVD authoring with Inkscape. The business card 85×54 template is now installed as well.

* "Other" license type was added to the metadata/license dialog so that people know that they are entering a URI to an "other" license.

= Examples =

* With all the recent additions - clipping, masking, and especially blur - Inkscape is now able to produce extremely photorealistic art. In the share/examples folder in Inkscape distribution, you will find two brand new, stunningly realistic images of shiny cars: car.svgz by Konstantin Rotkevich and gallardo.svgz by Michael Grosberg.

* Inkscape 0.45 does not yet have gradient meshes. But with the addition of Gaussian Blur, this feature suddenly got within reach. A new example file, gradient-mesh-experimental.svgz, explains the approach Inkscape will likely take to implement this feature in a fully SVG-compatible way.

* Although Inkscape does not support animation yet, you can add any animation scripts and attributes to your SVG file manually in a text editor - and the file will still be editable in Inkscape. Tavmjong Bah used this technique to create animated-clock.svg which, when loaded in an SVG viewer supporting animation (such as Firefox, Opera, or Batik), demonstrates the intricate moving clockwork of a watch - and shows real time to boot! If loaded in Inkscape, the image is static, but instead you can freely edit any of the objects.

= Translations, tutorials, templates =

* Remarkable improvements are in the '''Danish''', '''Finnish''', '''Nepalese''' and the '''Vietnamese''' translations of the user interface. They all jumped from 0 to over 90 percent in a very short timespan.

* All people which are familiar with '''pig latin''' are now able to use Inkscape's user interface in that language. Isthay isway oughtbray otay usway ybay away ewnay anslatortray.

* Updated '''British English''', '''Catalan''', '''Czech''', '''Bulgarian''', '''French''', '''Danish''', '''Finnish''', '''German''', '''Brazilian Portuguese''' and '''Thai''', '''Vietnamese''' and '''Dzongkha''' translations.

* A new Esperanto translation added including default document template.

* Default Lithuanian template was not installed before, which is now fixed.

* New tutorial "Easter Eggs" by Steve Karg.

* Added Catalan default template and elements tutorial.

* Russian header and footer templates for tutorials are added.

* Several tutorial translations were updated, namely '''Catalan''', '''Brazilian Portuguese''', '''Russian''', '''German''', '''Danish''' and '''French'''.

* There are also new Russian and Japanese translations of Windows installer strings.

= Dependency changes =

* We have changed the '''GTK+''' requirement for compilation to version 2.8. However, it is highly recommended to use at least the version '''2.10.7''' because previous versions contain at least one crash bug which may cause Inkscape to crash after typing in a value into a spinbutton.

= Notable bugfixes =

* When deleting a node, neighboring smooth nodes are converted to cusp.

* Releasing the mouse button while dragging nodes using a tablet will now always release the nodes. Before this, a race condition could occur where dragging could continue after the mouse button was released.

* An object's mask and clipping path are now preserved after Simplify, Object/Stroke to path, or boolean operations.

* Ungrouping a group containing clipped/masked objects might sometime break the clip/mask (move it away); this is fixed.

* Transforming an object and its clone no longer behaves unexpectedly when they are both within a transformed group.

* User-supplied templates in ~/.inkscape/templates can now be SVGZ files in addition to SVG.

* Previously, Inkscape didn't check if there's enough free memory for its pixel buffers and could crash without warning due to insufficient memory e.g. upon zooming in. This problem became much worse after implementing Gaussian blur, because rendering blurred objects at high zooms may require a pixel buffer much bigger than the visible canvas. Now this situation is handled more gracefully: if a display operation requires more memory than available, or more than 100Mb (which corresponds to a 5000x5000 pixel buffer), it is skipped. This may result in blurred objects "disappearing" at high zooms. This is purely a display issue, however, and it never corrupts data; just zoom out (or reduce blur radius) and the disappeared object will show up OK.

* When resizing objects, scaling numbers in the statusbar are no longer overwritten by other text when pressing the modifier keys (Alt, Shift, Ctrl).

* To work around problems some users had with pressure-sensitive tablets ([http://sourceforge.net/tracker/index.php?func=detail&aid=1281512&group_id=93438&atid=604306 bug 1281512]), the pressure sensitivity can be disabled from the Misc tab of Inkscape Preferences dialog. After that, the tablet can still be used as a regular mouse.

* The layer widget in the statusbar used to lose its current layer after an effect run; this is fixed.

* When using different display resolutions or a dual screen setup, dialogs could be displayed off-screen; this is fixed: now Inkscape checks whether the saved position of the dialog is offscreen, if so it will move the dialog to the center of the screen. Note that this not solve all problems. If the dialog is still not visible, go to the [http://sourceforge.net/tracker/?func=detail&atid=604306&aid=1250236&group_id=93438 bug 1250236] where a procedure is given to make the dialog visible (by editing preferences.xml).

* Grid and guidelines no longer vanish when changing their color.

* Group transformation is now correctly re-applied when ungrouping and then undoing the ungroup operation.

* Text dialog no longer discards the style of the selected text.

* Inkscape no longer crashes when you try to unflow an empty flowed text.

* Thanks to patches submitted by users of our community, Inkscape can now be built on SGI IRIX 6.5.28, gcc 3.4.0 systems and on Tru64 systems.

= Known problems =

==== Problem with "Dialogs on Top" on Windows ====

* Although the "Dialogs on Top" option is now available on Windows (File > Inkscape Preferences > Windows), it does not work exactly as it should (yet!). When the document window is minimized, the dialogs remain visible, i.e. are not minimized together with the document window. Because of this, it is not possible to get the document window back by clicking its taskbar button. A workaround to this problem is to '''right-click the Inkscape taskbar button and select "Restore".''' We expect that future releases of GTK will solve this problem.

==== Spinbuttons may crash if you have GTK+ older than 2.10.7 ====

* You may experience crashes after typing in a value into a spinbutton if you have a version of GTK+ 2.10.6 or older. Upgrade your GTK+ to fix this. (This does not affect the Windows package as it comes with GTK+ 2.10.9.)

==== Numerical Python required for Perspective effect ====

* This effect will not work until you install a python module called '''numpy''' (Numerical Python). It can be downloaded at [http://numpy.scipy.org/ numpy.scipy.org]. The Windows package already contains this module.

==== Do not use a clone of an object as its clipping path/mask ====

* In this version, you cannot use an object's clone as its clipping path or mask. Either unlink the clone first, or clip one clone of a source object (not the source itself) by another clone of the same. Properly fixing this bug requires some deep changes in the code and therefore was postponed until after 0.45 so as not to delay the release.

==== Non-Unicode symbol fonts on Windows don't work ====

* On Windows, symbol fonts without a Unicode map do not work. This is a limitation of the Pango library that we use.

==== Problems with some Debian libgc-6.7 packages ====

* Inkscape will hang or crash when linked with the first Debian packaged version of the Boehm garbage collection library. This problem was fixed in version 1:6.7-2 of the package. If you have libgc 6.7 on your Debian-based system, make sure that you are using that version of the package or later.

==== Beware of defective themes on Linux ====

* Inkscape and other Gtk programs can crash on any Linux, when the gtk2-engines-smooth / libsmooth 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. Update: this bug appears to be fixed in newer versions of gtk-engines. If you are affected by this problem please update to a newer version of gtk-engines. If problems persist then please inform the gtk-engines maintainers of the problem.

* A similar crash happens if the KDE Baghira theme or the package gtk_qt_engine 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.

= Previous releases =

* [[ReleaseNotes044]]
* [[ReleaseNotes043]]
* [[ReleaseNotes042]]
* [[ReleaseNotes041]]
* [[ReleaseNotes040]]
* [[ReleaseNotes039]]
* [[ReleaseNotes038]]
* [[ReleaseNotes037]]
* [[ReleaseNotes036]]
* [[ReleaseNotes035]]

ReleaseAnnounce045-cs

2007-02-04T08:12:54Z

Cornelius: updated 0.45 Release Announcement in czech language

Toto je koncept oznámení o vydání pro verzi 0.45

== Inkscape oznamuje vydání verze 0.45 :: http://www.inkscape.org :: Draw Freely ==

''The original version of this [http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045 release announcement].''

Komunita kolem Inkscape dnes oznamuje vydání nejnovější verze vektorového grafického editoru, který vyvíjí. Inkscape 0.45 přidává nový SVG filtr pro Gaussovské rozostření, který byl vyvinut díky sponzorství programem Google Summer of Code. Díky Gaussovskému rozostření můžete měkce a přirozeně rozmazat jakýkoliv z objektů v Inkscape a to včetně tvarů, textů a obrázků. Toto přináší široké možnosti při tvorbě fotorealistických efektů: libovolně tvarované odstíny a osvětlení, simulace hloubky ostrosti, stínu, sálání atd... Rozostřené objekty lze také použít jako masky pro ostatní objekty k dosažení efektu rozostřených okrajů.

Byly přidány i další nové funkce, vylepšeny ty současné a opraveno množství chyb. Dialogové okno Historie Vám například dovolí procházet hitorií změn. Přidány byly i nové efekty přidávané pomocí rozšíření včetně například efektu pro umístění Vzorku podél křivky nebo efektů pro manipulaci s barvami. Také byl vylepšen výkon při vykreslování obrazu a to o 2-3% obecně a kolem 5-10% pro kresby silně využívající průhlednost a/nebo kruhových barevných přechodů. Vylepšena byla také kvalita vazeb a to odebráním odstupňování převážně pozorovatelných v barevných přechodech.

Stáhněte si balíčky pro Linux, Windows a Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Pro více informací si můžete přečíst kompletní Poznámky o vydání verze 0.45:

http://wiki.inkscape.org/wiki/index.php/Release_Notes

Komunitou zaslané snímky obrazovky:

http://www.inkscape.org/screenshots/

===O Inkscape===

Inkscape je kreslící nástroj s otevřeným zdrojovým kódem využívající formát pro šálovatelnou vektorovou grafiku (SVG) World Wide Web Konzorcia ([[W3C]]). Mezi podporované vlastnosti SVG patří například základní tvary, křivky, text, značky, klony, alfa průhlednost, transformace, barevné přechody a seskupování objektů.

Inkscape dále podporuje Creative Commons metadata, editaci uzlů, vrstvy, operace se složitými křivkami, text na křivce, text ve tvaru, a úpravy SVG XML. Také je schopný načíst množství formátů jako EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP a TIFF a exportuje do PNG jakož i do mnoha vektorových formátů.

Hlavní motivací Inkscape je poskytnout Open Source komunitě kreslící nástroj plně podporující standardy [[W3C]], zejména XML, SVG a CSS2. Další práce zahrnují konverzi zdrojových kódů z <nowiki>C/Gtk</nowiki> na <nowiki>C++/Gtkmm</nowiki>, s důrazem na malé jádro s výkonnými funkceme přidávány pomocí rozšíření a udržováním prátelského, otevřeného a na komunitu orientovaného vývojového procesu.

Release notes/0.45

2007-02-04T07:50:00Z

Cornelius: /* Translations, tutorials, templates */

= Inkscape 0.45: overview =

This release brings the exciting new features developed by the Google Summer of Code 2006 participants, as well as tons of other improvements across the board. Here are the highlights:

* '''Gaussian blur''' is the first SVG filter supported by Inkscape. You can blur any object to any extent - yet it remains vector and fully editable. This gives a huge boost to Inkscape as a creative art tool.

* '''Display speed and interactivity''': not only does Inkscape render faster, but it can now respond to user input before it finished redrawing the screen, which greatly improves the interactivity of the program.

* '''History dialog''' makes it easy to to review your editing session and jump to any step of it, undoing and redoing multiple actions with one click.

* Several important tool features are added, notably the new selection mode in '''Node tool''' and the adjustable rounded caps in '''Calligraphic pen'''.

* '''Bitmap tracing''' works better for multi-color traces, sports a redesigned dialog and several new options.

* Many new '''extension effects''' are added, including '''Color effects''' and '''Pattern along path'''.

* The '''Outline mode''' has got many fixes and improvements, including a keyboard shortcut.

* Several new commands in '''Help''' menu open various Inkscape-related pages in your default browser, making Inkscape reference information more accessible as you work.

* Dozens of smaller '''features''' are added throughout the program, and hundreds of '''bugs''' are fixed.

= SVG filters: Gaussian blur =

Thanks to Google's Summer of Code program, Inkscape now has basic support for [http://www.w3.org/TR/SVG11/filters.html SVG filters]. The only filter enabled so far is '''Gaussian blur'''.

With it, you can softly and naturally blur any Inkscape objects: paths, shapes, groups, text, images. Clones inherit blurring from their original, but they can also be blurred independently from the original (you can create blurred clones with Tile Clones, too). Both the fill and stroke of an object are blurred together, creating semitransparent margins that smoothly blend into the background.

Gaussian blur 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.

* To blur selected objects, open the Fill and Stroke dialog (Ctrl+Shift+F) and use the '''Blur''' slider. The blur value is a percentage, with 100% corresponding to a blurring radius (standard deviation of Gaussian function) of 1/8 of the object's bounding box' perimeter (that is, for a square, a blur of 100% will have the radius equal to half a side, which turns any shape into an amorphous cloud).

* The '''Tile Clones''' dialog also supports blurring. On the '''Blur & opacity''' tab, you can set the blur percentage per row or per column of your tiling, as well as randomize blurring and make it alternate (all the same options as for Opacity).

* The quality of on-screen blur display is controlled by the '''Blur quality''' option on the new '''Filters''' tab of Inkscape Preferences (Ctrl+Shift+P). The available options range from best quality/slowest display to worst quality/fastest display, the default being in the middle of the range. Any setting except the "best quality" may introduce some rendering artifacts, especially when blurring thin strokes; on the other hand, the "best quality" setting may make Inkscape extremely slow at high zooms. These settings only affect the screen display of blurred objects; bitmap export always uses the best quality (and may therefore become quite slow for images with a lot of blur).

Here are a few tips on using blur:

* '''Masks and clipping''' are applied ''after'' blur. That is, if you clip an object and then blur it (or blur it first and then clip - it makes no difference), the clipped edges will remain crisp. Often, this is what you want. If, however, you want to blur the clipped/masked edges too (possibly with a different radius), you can use grouping: group the clipped object with some other object (which you can then delete from the group) and blur the group.

* A simple '''drop shadow''' is now very easy to do: just copy the object, paint the copy black, blur it, shift away a bit and lower it to the bottom. However, such a shadow does not update when you edit the foreground object. If your object is already black (or, more generally, if you want the shadow to be the same color as the object), you can clone instead of copy to make the shadow auto-updating. But what if your foreground object is not black but you need an auto-updating black shadow? Here's a recipe: unset the object's fill (it becomes black); create ''two'' clones of it; put one clone on top and paint any color you want; put the other clone at bottom, blur it and shift sideways. Now you can edit the unset-fill original (use Alt+click to select it) and everything will update.

* If an object has a fill that you don't want to blur (e.g. pattern, or if it's a bitmap), but you just want to '''feather the edges''', use a blurred transparency mask. For this, copy the object; paint it white; blur it as needed; scale the blurred copy down so its blur margins are entirely within the original object; select both the original and the blurred mask; do Object > Mask > Set.

* '''Transforming''' a blurred object '''transforms its blur''', too. This applies to a non-uniform scaling as well, so by squeezing a blurred object you make its blur squeezed as well. So, the easiest way to blur a path horizontally more than vertically is this: stretch it upwards without blur, then apply blur and squeeze it back into the original shape. (This only works if the stretched path does not already have a Transform attribute.)

* You can combine '''blurring with gradients'''. For example, an ellipse with elliptic opacity gradient will look much softer and more natural when blurred. An object with a horizontal linear opacity gradient, when blurred, will look as if it's more blurred on its transparent side than on its opaque side.

* A '''clone of a blurred object''' inherits the blur of the original. Therefore, such a clone can be blurred ''more'', but you can't "unblur" it to make the clone sharper than its original (unless, of course, you unlink it). The Fill and Stroke dialog shows you the amount of the blur applied to this particular object; however, if the object is a clone of an already blurred original, the dialog does not reflect that.

* Note that '''Firefox 2.0''' does not support SVG filters, so your files will be displayed in Firefox 2.0 without blur. However, filter support has been added in the current development version and will be included in Firefox 3.0. The Opera web browser, as well as librsvg (used by Wikipedia) and Batik, support filters correctly in their current versions.

= Undo history =

* Inkscape now features a History Dialog accessible via Ctrl+Shift+H or Edit > Undo History. All changes made to the document since it was opened are recorded here.

:* In the dialog, changes are listed from the '''oldest (top)''' to the '''newest (bottom)'''.

:* The type of each change is indicated by an '''icon''' and a short '''description'''.

:* For readability, consecutive changes of the same type are placed in a '''collapsible branch''' showing a triangle marker and the number of the hidden actions in the branch.

:* By clicking on an event in the list, you can easily '''move through the undo history''', i.e. undo or redo any number of actions with one click.

* The Undo and Redo commands in the Edit menu display the descriptions of the commands to be undone and redone, correspondingly. (These are the same descriptions that you see in the History dialog.)

= Rendering improvements =

* Interruptible display: Previously, Inkscape could not do anything until it finishes the current screen redraw. Now the redraw is made interruptible, so that Inkscape responds to mouse and keyboard input and can abort the current redraw and start over if you do some screen-changing operation. As a result, Inkscape now feels '''much snappier and more interactive'''. This interruptibility is fine-tuned for some continuous-drag operations (such as node dragging) so that a balance is achieved between responsiveness and completeness of display.

* Screen render is faster by '''2-3%''' overall:

:* Complex drawings with '''transparency''' are faster by up to '''5%'''.

:* '''Radial gradients''' are rendered faster by at least '''10%'''.

* Rendering (compositing) quality has been improved. This is most visible with (partially) transparent gradients: '''banding''' is a lot less pronounced now. Speed has also been improved in some cases.

* Display is more responsive when working at high zoom levels when using a tablet.

= Tools =

== Node tool ==

* You can grow or shrink node selection by hovering the mouse pointer over a node and using mousewheel (up = grow, down = shrink) or the keys PageUp (grow) and PageDown (shrink). ''Growing'' adds the closest unselected node to the selection; shrinking deselects the farthest selected node. There are two modes that differ by how the closest/farthest nodes are chosen:

:* Spatial selection (mousewheel, PageUp/PageDown): distances to nodes are measured directly, regardless of which subpath a node belongs to.

:* Linear selection (Ctrl+mousewheel, Ctrl+PageUp/Ctrl+PageDown): node distances are measured ''along the path'', and only the nodes belonging to the same subpath as the hovered node are considered (i.e. other subpaths are never selected).

:This technique is convenient for quickly selecting an area in a complex path starting from a center - for example, for node sculpting.

== Dropper ==

* Instead of the confusing toggle button, now the Controls bar for the Dropper tool has two checkboxes, '''Pick alpha''' and '''Set alpha''', which work as follows. Suppose you have an object selected and, using Dropper, click on an object which has red (#FF0000) fill and 0.5 opacity (half-transparent).

:* If the "Pick alpha" checkbox is off, the selected object will get the fill color #800000 (i.e. faded-out red) and fill opacity will be at 1.0 (opaque).

:* If the "Pick alpha" checkbox is on but "Set alpha" is off, the selected object will get the fill color #FF0000 (red) and fill opacity will be at 1.0.

:* If both "Pick alpha" and "Set alpha" are on, the selected object will get the fill color #FF0000 (red) and fill opacity will be at 0.5 (half-transparent).

:If you Shift+click instead of click, the same changes will be made to stroke color and stroke opacity, correspondingly. Note that in no situation can Dropper change the ''master opacity'' of the selected object(s) (only the fill/stroke opacity), although it can pick it just as it does any other kind of opacity.

== Calligraphy ==

* A new numeric parameter, Caps, controls the amount of protruding at the ends of calligraphic strokes. This parameter can range from 0 (flat caps, default behavior in previous versions) through 1 (approximately half-circle caps) and up to 5 (long elliptic caps). Rounded caps much improve the look of low-fixation strokes, simulating a rounded pen.

* The "Drag" parameter has been renamed to Wiggle with a value inversion (i.e. low drag corresponds to high wiggle, and vice versa). Increase this parameter (default is 0) to make the pen waver and wiggle in curly patterns.

* As a first step towards a redesign of the tools' controls, the '''Controls bar of the Calligraphy pen''' has been upgraded. Now it no longer prevents the Inkscape window from resizing narrower than the bar. The items on the far right end of the bar which didn't fit in a narrow window are still accessible through an '''expansion menu''' which allows you to toggle switches, select commands, and set values of numeric fields. Also, each editable numeric value field has a new '''right-click menu''' with some common values which often allows you to set a desired value much faster than by scrolling the control or typing the value into it.

* With low or zero Fixation parameter, some users of tablet pens experienced "blobs" (brief reversals of a stroke's right/left edges, causing "holes" and "bubbles" in a calligraphic stroke), especially often at the start of a stroke. Hopefully this problem is now fixed without reducing the responsiveness of the tool.

= Outline mode =

* A new menu command (View > Display Mode > Toggle) and a new keyboard shortcut (Ctrl+<keypad 5>) switch the display mode from Normal to Outline and back.

* The window title displays "(outline)" next to the file name when that editing window is in Outline mode.

* An object with mask and/or clipping path, when viewed in Outline mode, now displays both the object itself and its clipping path and mask as objects, using different outline colors. By default, clippaths use green outlines, and masks use blue.

* Images in Outline mode are displayed as red (by default) frames with two diagonals.

* An object with no fill and no stroke, invisible and not selectable by mouse clicking in normal mode, can now be picked by a mouse click in the Outline mode using its visible outline.

* The bug whereby stroked shapes didn't change stroke width when switching to Outline mode or back is fixed.

* All outline colors are changeable by editing the "wireframecolors" group inside "options" in the preferences file (~/.inkscape/preferences.xml). The "onlight" and "ondark" attributes set the colors of the regular object outlines on light and dark backgrounds (default black and white correspondingly); the "images", "clips", and "masks" attributes set the colors of images, clipping paths, and masks (defaults are red, green, and blue correspondingly). Each attribute is a decimal integer corresponding to the hex RRGGBBAA of the color.

* To cater for specialized uses, such as preparing input for personal media cutters, Inkscape now has an option to start in the Outline mode upon launch. To enable this, add the following line to your preferences.xml file:

:: <group id="startmode" outline="1"/>

:placing it after the <group id="options"> opening tag.

= Keyboard profiles =

The previous release allowed sets of keybindings (keymaps) to be created for Inkscape in the style of other applications. Two more keymaps have been added:

* '''Adobe Illustrator'''
* '''Macromedia Freehand'''

Of course not every feature in these other programs has a direct match to features in Inkscape; so, if you can, please '''help us out''' by reporting any problems you may have or improvements you would like to request.

Additionally, a keymap that focuses on tablet-based illustration and drawing work has been added:

* '''right-handed-illustration.xml'''

This keymap places all commonly-used commands under the left hand, so that the user's hands rarely leave the keyboard or the tablet/stylus.

(To enable a profile, copy it into <code>default.xml</code> in the same directory, overwriting the old file. To restore the default Inkscape set, copy <code>inkscape.xml</code> into <code>default.xml</code>.)

More of Inkscape's keys are implemented as actions and are therefore available for remapping via keyboard profiles. New actions include '''EditSelectNext''' and '''EditSelectPrev''' for selecting next/previous object or node (by default, they are bound to Tab/Shift+Tab; as a result of becoming global actions, these keys now work in all tools and not only in Selector and Node tool as before).

= Extension effects =

Inkscape's extension effects, written in Python using the '''inkex''' utility class, are currently a major growth point of the project. They allow new developers to create functionality very quickly, without having to learn Inkscape's huge C/C++ codebase. However, eventually we plan to move many of these effects into the core of Inkscape, which will make them much faster and more interactive. From this viewpoint, effects can be considered a quick way to prototype and test the algorithms and UI controls of the future Inkscape features. However, this does not prevent effects from being genuinely useful in everyday work, and in this version we have several excellent additions.

== New effects ==

* '''Pattern along path''': A new powerful extension in the "Generate from path" submenu allows you to bend, repeat and/or stretch a pattern object (which can be a path or a group) along a "skeleton" path. This makes it easy to create a variety of patterned and shaped strokes. (This obsoletes the old "Kochify" extension which is removed.)

:Effect's parameters include:

:* ''Copies of the pattern'' selects one of the four modes: '''Single stretched''': one copy of the pattern is placed on the skeleton path and stretched/squeezed to match its length; '''Repeated stretched''': as many copies as would fit are placed along the skeleton path and stretched to fit exactly; '''Single''' and '''Repeated''': same but without stretching.

:* ''Deformation type'' can be one of: '''Snake''' bends the pattern flatly in the plane of the drawing, the width not depending on direction; '''Ribbon''' bends it as a vertical ribbon or like a calligraphic stroke with maximum fixation, so that width depends on direction (minimum for vertical parts of the stroke, maximum for horizontal).

:* Several parameters allow you to adjust spacing between the copies of the pattern (for Multiple modes) and their offset in two directions (along the skeleton path and perpendicular to it).

:* Normally the effect assumes that the pattern object is horizontal and bends its horizontal axis (at mid-height) along the skeleton path. There's a checkbox that allows you to use a '''vertical pattern''' instead.

:Some examples of using this effect are shown on a screenshot at [http://inkscape.org/screenshots/gallery/inkscape-0.45-patternalongpath.png].

* '''Color effects''': A new group of extensions in the '''Color''' submenu of the Effects menu allows you to adjust all colors of a selection at once. These commands affect both fill and stroke colors, including gradients (but not bitmaps). The commands include:

:* a full set of '''HSL adjustments''' (increasing/decreasing hue, saturation, or lightness by 5%),

:* '''Brighter''' and '''Darker''' (adjust brightness up or down by 10%),

:* '''Desaturate''',

:* '''Grayscale''',

:* '''Negative''',

:* commands for removing or swapping the '''Red''', '''Green''', '''Blue''' channels,

:* a '''Custom''' command where you can set your own formulas for modifying the color channels.

:Some examples of using this effect are shown on a screenshot at [http://inkscape.org/screenshots/gallery/inkscape-0.45-coloreffects.png].

:Note: undoing color changes on gradients exposes a bug where an object seems to "disappear"; this is only a display issue (caused by the order in which gradients and their users are restored on undo) not causing any loss of information. Also, on large documents and large selections with gradients, Python's XPath code may get quite slow. Despite these shortcomings, we decided to add this extension, because it's genuinely useful functionality which was so far missing in Inkscape.

* Recent fixes in the processing of SVG <defs /> have made it possible to implement the often requested '''Color Markers to Match Stroke''' effect. It is no longer necessary to hand-edit XML to recolor arrowheads; just change the stroke color of your path and call this effect to recolor its markers to match.

* '''Lorem ipsum''' (in "Render" submenu) is a new extension that creates the traditional Latin-like random text for design mock-ups. The number of paragraphs, the number of sentences per paragraph and the possible fluctuation of the number of sentences (for uneven paragraphs) can be adjusted. If no flowed text element is selected, a new one in a new layer is created, matching the size of the canvas.

* '''Fractalize''' (in "Modify Path" submenu) replaces each segment of the selected path by a crooked line, subdivided to the given depth, with randomly displaced nodes.

* '''g2png''': The new group-to-PNG Python extension (g2png) is an easy way to export any group or layer to individual PNG files. It was first created for use in the [http://www.le-radar.com/?mm/inkscape Inkscape User Manual] (also available in SVN in the user_manual module) but is also interesting for many other uses. If e.g. you have to draw a set of icons, you can draw them in the same document, thus making copying, duplicating, cloning etc. easier. Then just create a group for each icon, and with the extension, each group ends up in its own PNG file.

== Improved effects ==

* The '''Function Plotter''' has been extended, providing greater flexibility in x- and y-range definition.

* The '''Measure Path''' extension is improved with several new parameters added (units, scale, precision, distance from path).

* The '''Extract One Image''' extension is fixed to automatically append filename extension to the created bitmap file.

* The "Blur Edge" extension is renamed into '''Inset/Outset Halo''' to avoid confusion with the real Gaussian blur that we now support, as well as to better describe what this extension actually does: From the selected path, it creates a group of inset and outset paths that form a stepped "halo" around the object.

== Infrastructure ==

* '''3 new parameter types''' have been added to the extension effect UI: '''tabs''', '''enumerations''' and '''optiongroups''' (radio buttons). Examples are available of how to use these parameters in INX files: the new Function Plotter uses tabs; enumerations are used by the Pattern along path extension; and a small developer example is given to illustrate the use of optiongroups (identical to enumerations).

* In an extension's INX file, you can specify <code><effects-menu hidden="yes"/></code> to hide that extension from the Effects menu. However, such a "hidden" extension can still be assigned a keyboard shortcut (by using its <code>id</code> as an "action" in your <code>~/.inkscape/keys/default.xml</code>).

* In an extension's INX file, you can add <code>needs-document="no"</code> attribute to the <code><effect></code> element. This indicates that the extension does not process the current SVG document, and Inkscape will not bother saving and restoring the document from a temporary file which allows this extension to run faster and smoother. (This is used for the new open-in-default-browser Help menu commands which are technically implemented as extensions.)

= Export formats =

== AI import/export ==

* We only support AI import and export for Adobe Illustrator 8.0 and older. This has been clarified in the Open and Save As lists.

== PDF export ==

Inkscape's PDF exporter has been improved:

* '''New features:''' bitmap images can be embedded; PDF files can be exported from command line using the <code>--export-pdf</code> parameter.

* '''Changed behavior:''' the pointless text to path question is gone.

* '''Fixed bugs:''' save failure is now detected, miter limits are now >= 1, PDFs with transparent gradient are now embeddable, eccentric elliptic gradients fixed, dash style inheritance fixed, transparency inheritance fixed.

== PS/EPS export ==

There's a new option to embed the fonts used in the document in the PS or EPS exported file. As of now, this works for Type 1 fonts only, not TrueType. The option is available when performing the export from the GUI as well as from the command line via the <code>--export-embed-fonts</code> option.

== EMF export ==

Inkscape has a limited support for exporting EMF (Enhanced Meta File) format. This works only on Windows, and only exports strokes and fills with constant colors. No text, no images, no gradients, no transparency.

= SVG output =

For specialized uses, several aspects of Inkscape's SVG output can now be customized via editing the preferences.xml file (there's no UI for these options). A <group id="svgoutput"> inside <group id="options"> can have the following attributes:

* usenamedcolors (default is 0). If nonzero, Inkscape uses symbolic color names (such as "white" or "lime") and three-digit color designations (such as $dfe) where appropriate; otherwise, it always uses six-digit colors (such as $d0f0e0). Note that in 0.44, the default was to use named colors, which created problems for some extension effects.

* numericprecision (default is 8). This is the number of significant digits written for each number into SVG. You can lower this number to get slightly more compact SVG at the expense of precision.

* minimumexponent (default is -8). In transform= attributes, any number whose absolute value is less than 10 to the power of minimumexponent (i.e. less than 10-8 by default) is written as 0.

* indent (default is 2) controls the number of spaces that each level of nesting in SVG is shifted. Set this to 0 to disable indentation.

* inlineattrs (default is 0). If nonzero, attributes are placed on the same line as their tags; otherwise they are separated by newlines.

= Bitmap tracing =

* A '''new color quantization algorithm''' for multiscan traces works faster (especially for large numbers of colors) and gives more adequate results with less colors used. This improves tracing results both for full-color photographs and for limited-color drawings.

* The Trace Bitmap dialog now provides access to three more tracing parameters:

:* '''Suppress speckles''': If set, spots or speckles larger than the given size (in pixels) are suppressed in the trace.

:* '''Smooth corners''': This parameter controls how much smoothing is applied to corners in the traced path.

:* '''Optimize paths''': If set, trace paths are optimized by joining adjacent Bezier segments with the given tolerance.

* All controls in the Trace Bitmap dialog are reorganized to be easier to find. The dialog is redesigned to use two main tabs: '''Mode''' (where you select the tracing mode, such as brightness cutoff or color multiscan) and '''Options''' (where you set various tracing options, such as corner smoothing). The preview is placed horizontally to the right of the tabs. Most labels and tooltips are rewritten for clarity. The trace preview image is made twice larger.

= Even more improvements =

* The '''opacity''' of objects is now displayed as percentage, '''from 0 to 100''', both in the Fill & Stroke dialog (with one fractional digit) and in the statusbar style indicator (with no fractional digits), instead of from 0 to 1.0 as before. This makes opacity values easier to read, type, and say.

* A '''Save a copy''' command has been added to the file menu, similar to the 'Save a copy' functionality of e.g. Adobe Illustrator. With this command, you can save your document under a new filename, but Inkscape will then "forget" it has done this: later saves will be to the old filename. The default shortcut assigned to this function is '''Shift+Ctrl+Alt+S'''.

* Text and flowed text objects behave more consistently. Now you can put a flowed text on path or (re)flow it into a shape just as you would do with a regular (unflowed) text. Previously, the need to convert a flowed text to text before these operations was a stumble for many users.

* Several commands were added to the '''Help menu''', providing the long-missing access to basic information about Inkscape and SVG right from the program: [http://tavmjong.free.fr/INKSCAPE/MANUAL/html/index.php Inkscape manual], [http://inkscape.org/doc/inkscape-man.html Command line options], [http://wiki.inkscape.org/wiki/index.php/FAQ FAQ], Release notes, [http://inkscape.org/report_bugs.php Bug report page], and the [http://www.w3.org/TR/SVG11/ SVG 1.1 specification]. All these commands open the corresponding web pages in the user's default web browser.

* Exported PNG images have the correct '''resolution''' set in the header.

* The Path -> '''Union''' (Ctrl++) operation now functions when only a '''single object''' is selected. Use this to '''remove self-intersections''' in path objects.

* We removed the "hacked" '''filename entry field''' that we had added to the Open and Save dialogs because starting from version 2.10, GTK+ has finally restored this field in their '''standard file dialog'''. The standard field at the top of the dialog supports type-ahead find and performs the default dialog action (open or save) by pressing Enter, which means you can now do a quick '''Ctrl+O, Ctrl+V, Enter''' sequence to open the file whose path is in your clipboard (this closes a long-standing usability bug). Those who use older versions of GTK are advised either to upgrade to 2.10 or use Ctrl+L to open a pop-up filename box. (Our Windows builds are shipped with GTK+ 2.10.)

* The '''Create Bitmap''' function (Alt+B in the default keymap) is made more useful. Unless you have specific resolution or minimum size set for this command in preferences.xml (<code><group id="createbitmap"/></code>), it will take the '''resolution hint''' from the object whose bitmap copy you are creating (in other words, it will use the resolution that you specified for that object when exporting it via the Export Bitmap dialog), or the default '''90 dpi''' if that object was not yet exported. Also, a 90 dpi bitmap (with its pixels exactly 1 px in size) will be '''snapped''' to the pixel grid. This makes it easy to use Create Bitmap for quick '''rasterization preview''' of an object or document. (Note: if you have used a previous version of Inkscape, your preferences.xml may contain <code>minsize="250"</code>; delete this for objects' resolution hints to work.)

* Using extended input (i.e. tablet pressure and tilt) can now be disabled via Preferences (Misc tab). This is intended to be a last-resort option for those platform/hardware combinations that are not properly supported by GTK. With extended input disabled, you can still use your tablet as a mouse.

* Simplify Path now has two modes when working with a group of paths: the default mode, which treats all of the paths as one large object to simplify, or the new mode, which acts the same as using Simplify on each path in a group separately. In preferences.xml, set '''options.simplifyindividualpaths''' to 1 to get the new mode.

* For long Simplify operations (more than 20 paths at a time), Inkscape provides user feedback via the status bar as to how many paths have been simplified. This change also prevents Inkscape from appearing to have locked up during the operation.

* New '''templates''' added for '''video formats''' (PAL, NTSC and HDTV 1080) as well as DVD cover templates that were not installed in the previous version. This will help video and DVD authoring with Inkscape. The business card 85×54 template is now installed as well.

* "Other" license type was added to the metadata/license dialog so that people know that they are entering a URI to an "other" license.

= Examples =

* With all the recent additions - clipping, masking, and especially blur - Inkscape is now able to produce extremely photorealistic art. In the share/examples folder in Inkscape distribution, you will find two brand new, stunningly realistic images of shiny cars: car.svgz by Konstantin Rotkevich and gallardo.svgz by Michael Grosberg.

* Inkscape 0.45 does not yet have gradient meshes. But with the addition of Gaussian Blur, this feature suddenly got within reach. A new example file, gradient-mesh-experimental.svgz, explains the approach Inkscape will likely take to implement this feature in a fully SVG-compatible way.

* Although Inkscape does not support animation yet, you can add any animation scripts and attributes to your SVG file manually in a text editor - and the file will still be editable in Inkscape. Tavmjong Bah used this technique to create animated-clock.svg which, when loaded in an SVG viewer supporting animation (such as Firefox, Opera, or Batik), demonstrates the intricate moving clockwork of a watch - and shows real time to boot! If loaded in Inkscape, the image is static, but instead you can freely edit any of the objects.

= Translations, tutorials, templates =

* Remarkable improvements are in the '''Danish''', '''Finnish''', '''Nepalese''' and the '''Vietnamese''' translations of the user interface. They all jumped from 0 to over 90 percent in a very short timespan.

* All people which are familiar with '''pig latin''' are now able to use Inkscape's user interface in that language. Isthay isway oughtbray otay usway ybay away ewnay anslatortray.

* Updated '''British English''', '''Catalan''', '''Czech''', '''Bulgarian''', '''French''', '''Danish''', '''Finnish''', '''German''', '''Brazilian Portuguese''' and '''Thai''', '''Vietnamese''' and '''Dzongkha''' translations.

* A new Esperanto translation added including default document template.

* Default Lithuanian template was not installed before, which is now fixed.

* New tutorial "Easter Eggs" by Steve Karg.

* Added Catalan default template and elements tutorial.

* Russian header and footer templates for tutorials are added.

* Several tutorial translations were updated, namely '''Catalan''', '''Brazilian Portuguese''', '''Russian''', '''German''', '''Danish''' and '''French'''.

* There are also new Russian and Japanese translations of Windows installer strings.

= Dependency changes =

* We have changed the '''GTK+''' requirement for compilation to version 2.8. However, it is highly recommended to use at least the version '''2.10.7''' because previous versions contain at least one crash bug which may cause Inkscape to crash after typing in a value into a spinbutton.

= Notable bugfixes =

* When deleting a node, neighboring smooth nodes are converted to cusp.

* Releasing the mouse button while dragging nodes using a tablet will now always release the nodes. Before this, a race condition could occur where dragging could continue after the mouse button was released.

* An object's mask and clipping path are now preserved after Simplify, Object/Stroke to path, or boolean operations.

* Ungrouping a group containing clipped/masked objects might sometime break the clip/mask (move it away); this is fixed.

* Transforming an object and its clone no longer behaves unexpectedly when they are both within a transformed group.

* User-supplied templates in ~/.inkscape/templates can now be SVGZ files in addition to SVG.

* Previously, Inkscape didn't check if there's enough free memory for its pixel buffers and could crash without warning due to insufficient memory e.g. upon zooming in. This problem became much worse after implementing Gaussian blur, because rendering blurred objects at high zooms may require a pixel buffer much bigger than the visible canvas. Now this situation is handled more gracefully: if a display operation requires more memory than available, or more than 100Mb (which corresponds to a 5000x5000 pixel buffer), it is skipped. This may result in blurred objects "disappearing" at high zooms. This is purely a display issue, however, and it never corrupts data; just zoom out (or reduce blur radius) and the disappeared object will show up OK.

* When resizing objects, scaling numbers in the statusbar are no longer overwritten by other text when pressing the modifier keys (Alt, Shift, Ctrl).

* To work around problems some users had with pressure-sensitive tablets ([http://sourceforge.net/tracker/index.php?func=detail&aid=1281512&group_id=93438&atid=604306 bug 1281512]), the pressure sensitivity can be disabled from the Misc tab of Inkscape Preferences dialog. After that, the tablet can still be used as a regular mouse.

* The layer widget in the statusbar used to lose its current layer after an effect run; this is fixed.

* When using different display resolutions or a dual screen setup, dialogs could be displayed off-screen; this is fixed: now Inkscape checks whether the saved position of the dialog is offscreen, if so it will move the dialog to the center of the screen. Note that this not solve all problems. If the dialog is still not visible, go to the [http://sourceforge.net/tracker/?func=detail&atid=604306&aid=1250236&group_id=93438 bug 1250236] where a procedure is given to make the dialog visible (by editing preferences.xml).

* Grid and guidelines no longer vanish when changing their color.

* Group transformation is now correctly re-applied when ungrouping and then undoing the ungroup operation.

* Text dialog no longer discards the style of the selected text.

* Inkscape no longer crashes when you try to unflow an empty flowed text.

* Thanks to patches submitted by users of our community, Inkscape can now be built on SGI IRIX 6.5.28, gcc 3.4.0 systems and on Tru64 systems.

= Known problems =

==== Problem with "Dialogs on Top" on Windows ====

* Although the "Dialogs on Top" option is now available on Windows (File > Inkscape Preferences > Windows), it does not work exactly as it should (yet!). When the document window is minimized, the dialogs remain visible, i.e. are not minimized together with the document window. Because of this, it is not possible to get the document window back by clicking its taskbar button. A workaround to this problem is to '''right-click the Inkscape taskbar button and select "Restore".''' We expect that future releases of GTK will solve this problem.

==== Spinbuttons may crash if you have GTK+ older than 2.10.7 ====

* You may experience crashes after typing in a value into a spinbutton if you have a version of GTK+ 2.10.6 or older. Upgrade your GTK+ to fix this. (This does not affect the Windows package as it comes with GTK+ 2.10.9.)

==== Numerical Python required for Perspective effect ====

* This effect will not work until you install a python module called '''numpy''' (Numerical Python). It can be downloaded at [http://numpy.scipy.org/ numpy.scipy.org]. The Windows package already contains this module.

==== Do not use a clone of an object as its clipping path/mask ====

* In this version, you cannot use an object's clone as its clipping path or mask. Either unlink the clone first, or clip one clone of a source object (not the source itself) by another clone of the same. Properly fixing this bug requires some deep changes in the code and therefore was postponed until after 0.45 so as not to delay the release.

==== Non-Unicode symbol fonts on Windows don't work ====

* On Windows, symbol fonts without a Unicode map do not work. This is a limitation of the Pango library that we use.

==== Problems with some Debian libgc-6.7 packages ====

* Inkscape will hang or crash when linked with the first Debian packaged version of the Boehm garbage collection library. This problem was fixed in version 1:6.7-2 of the package. If you have libgc 6.7 on your Debian-based system, make sure that you are using that version of the package or later.

==== Beware of defective themes on Linux ====

* Inkscape and other Gtk programs can crash on any Linux, when the gtk2-engines-smooth / libsmooth 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. Update: this bug appears to be fixed in newer versions of gtk-engines. If you are affected by this problem please update to a newer version of gtk-engines. If problems persist then please inform the gtk-engines maintainers of the problem.

* A similar crash happens if the KDE Baghira theme or the package gtk_qt_engine 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.

= Previous releases =

* [[ReleaseNotes044]]
* [[ReleaseNotes043]]
* [[ReleaseNotes042]]
* [[ReleaseNotes041]]
* [[ReleaseNotes040]]
* [[ReleaseNotes039]]
* [[ReleaseNotes038]]
* [[ReleaseNotes037]]
* [[ReleaseNotes036]]
* [[ReleaseNotes035]]

[[Category:Marketing]]

ReleaseAnnounce045-cs

2007-02-04T07:35:42Z

Cornelius:

Toto je koncept oznámení o vydání pro verzi 0.45

== Inkscape oznamuje vydání verze 0.45 :: http://www.inkscape.org :: Draw Freely ==

''The original version of this [http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045 release announcement].''

Inkscape komunita dnes oficiálně vydala nejnovější verzi svého editoru vektorové grafiky. Inkscape 0.45 přidává mnoho nových funkcí, je rychlejší a více použitelná, lépe podporuje SVG, je přeložená do více jazyků a množství jiných novinek a zlepšení.

Mezi hlavní novinky mezi finkcemi patří dialogové okno Vrstvy, podpora pro ořez a maskování objektů, vylepšení export do PDF podporující průhlednost, konfigurovatelné klávesové zkratky, inovativní funkce "vyřezávání uzlů" v Nástroji pro tvorbu a úpravu uzlů, a nový mód Outline zobrazující z kresby pouze obrysy. Značných vylepšení bylo dosaženo v oblasti výkonu aplikace, zejména při překreslování scény a u Nástroje pro úpravu uzlů.

Mezi viditelné změny v uživatelském rozhraní patří barevné palety umístitelné nad stavový panel, interaktivní indikátor stylu ve stavovém panelu, změněný dialog Nastavení Inkscape, nový panel pro nástroj Text a nové ikony. Naše shoda se SVG standardem také pokročila dopředu, byla přidána podpora pro značku <switch> a ICC barevné profily pro obrázky. Tato verze také obsahuje stovky menších vlastností, vylepšení použitelnosti a oprav chyb.

V několika předchozích verzích byl Inkscape vydáván s kolekcí efektů, jejichž menu (Efekty) bylo ale ve výchozím nastavení vypnuto. S touto verzí se efekty staly natolik vyzrálými a fungujícími na všech platformách, že toto menu již bude aktivní hned po instalaci.

Chtěli bychom poděkovat Google, že sponzorují práci pěti studentů při vývoji těchto nových vlastností pro Inkscape: SVG filtry, Inkboard protokol, PDF export využívající Cairo a paměťové optimalizace.

Stáhněte si balíčky pro Linux, Windows a Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Pro více informací si můžete přečíst kompletní Poznámky o vydání verze 0.45:

http://wiki.inkscape.org/wiki/index.php/Release_Notes

Komunitou zaslané snímky obrazovky:

http://www.inkscape.org/screenshots/

===O Inkscape===

Inkscape je kreslící nástroj s otevřeným zdrojovým kódem využívající formát pro šálovatelnou vektorovou grafiku (SVG) World Wide Web Konzorcia ([[W3C]]). Mezi podporované vlastnosti SVG patří například základní tvary, křivky, text, značky, klony, alfa průhlednost, transformace, barevné přechody a seskupování objektů.

Inkscape dále podporuje Creative Commons metadata, editaci uzlů, vrstvy, operace se složitými křivkami, text na křivce, text ve tvaru, a úpravy SVG XML. Také je schopný načíst množství formátů jako EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP a TIFF a exportuje do PNG jakož i do mnoha vektorových formátů.

Hlavní motivací Inkscape je poskytnout Open Source komunitě kreslící nástroj plně podporující standardy [[W3C]], zejména XML, SVG a CSS2. Další práce zahrnují konverzi zdrojových kódů z <nowiki>C/Gtk</nowiki> na <nowiki>C++/Gtkmm</nowiki>, s důrazem na malé jádro s výkonnými funkceme přidávány pomocí rozšíření a udržováním prátelského, otevřeného a na komunitu orientovaného vývojového procesu.

ReleaseAnnounce045-cs

2007-02-04T07:34:39Z

Cornelius: Release Announcement for 0.45 in czech language

Toto je koncept oznámení o vydání pro verzi 0.45

== Inkscape oznamuje vydání verze 0.45 :: http://www.inkscape.org :: Draw Freely ==

''The original version of this [http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045 release announcement].''

Inkscape komunita dnes oficiálně vydala nejnovější verzi svého editoru vektorové grafiky. Inkscape 0.44 přidává mnoho nových funkcí, je rychlejší a více použitelná, lépe podporuje SVG, je přeložená do více jazyků a množství jiných novinek a zlepšení.

Mezi hlavní novinky mezi finkcemi patří dialogové okno Vrstvy, podpora pro ořez a maskování objektů, vylepšení export do PDF podporující průhlednost, konfigurovatelné klávesové zkratky, inovativní funkce "vyřezávání uzlů" v Nástroji pro tvorbu a úpravu uzlů, a nový mód Outline zobrazující z kresby pouze obrysy. Značných vylepšení bylo dosaženo v oblasti výkonu aplikace, zejména při překreslování scény a u Nástroje pro úpravu uzlů.

Mezi viditelné změny v uživatelském rozhraní patří barevné palety umístitelné nad stavový panel, interaktivní indikátor stylu ve stavovém panelu, změněný dialog Nastavení Inkscape, nový panel pro nástroj Text a nové ikony. Naše shoda se SVG standardem také pokročila dopředu, byla přidána podpora pro značku <switch> a ICC barevné profily pro obrázky. Tato verze také obsahuje stovky menších vlastností, vylepšení použitelnosti a oprav chyb.

V několika předchozích verzích byl Inkscape vydáván s kolekcí efektů, jejichž menu (Efekty) bylo ale ve výchozím nastavení vypnuto. S touto verzí se efekty staly natolik vyzrálými a fungujícími na všech platformách, že toto menu již bude aktivní hned po instalaci.

Chtěli bychom poděkovat Google, že sponzorují práci pěti studentů při vývoji těchto nových vlastností pro Inkscape: SVG filtry, Inkboard protokol, PDF export využívající Cairo a paměťové optimalizace.

Stáhněte si balíčky pro Linux, Windows a Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Pro více informací si můžete přečíst kompletní Poznámky o vydání verze 0.45:

http://wiki.inkscape.org/wiki/index.php/Release_Notes

Komunitou zaslané snímky obrazovky:

http://www.inkscape.org/screenshots/

===O Inkscape===

Inkscape je kreslící nástroj s otevřeným zdrojovým kódem využívající formát pro šálovatelnou vektorovou grafiku (SVG) World Wide Web Konzorcia ([[W3C]]). Mezi podporované vlastnosti SVG patří například základní tvary, křivky, text, značky, klony, alfa průhlednost, transformace, barevné přechody a seskupování objektů.

Inkscape dále podporuje Creative Commons metadata, editaci uzlů, vrstvy, operace se složitými křivkami, text na křivce, text ve tvaru, a úpravy SVG XML. Také je schopný načíst množství formátů jako EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP a TIFF a exportuje do PNG jakož i do mnoha vektorových formátů.

Hlavní motivací Inkscape je poskytnout Open Source komunitě kreslící nástroj plně podporující standardy [[W3C]], zejména XML, SVG a CSS2. Další práce zahrnují konverzi zdrojových kódů z <nowiki>C/Gtk</nowiki> na <nowiki>C++/Gtkmm</nowiki>, s důrazem na malé jádro s výkonnými funkceme přidávány pomocí rozšíření a udržováním prátelského, otevřeného a na komunitu orientovaného vývojového procesu.

PresentationInkscapeOverview

2007-01-10T10:25:22Z

Cornelius: Removing spam added by Avol

== Inkscape: Open Source Scalable Vector Graphics Editor ==

* PUT YOUR NAME HERE
* PUT YOUR AFFILIATION HERE

Inkscape is an open source SVG editor with capabilities similar to Illustrator, [[CorelDraw]], Visio, etc. Supported SVG features include basic shapes, paths, text, alpha blending, transforms, gradients, node editing, svg-to-png export, grouping, and more.

Inkscape's main motivation is to provide the Open Source community with a fully XML, SVG, and CSS2 compliant SVG drawing tool. Additional planned work includes conversion of the codebase from C[[/Gtk]] to C++[[/Gtkmm]], emphasizing a lightweight core with powerful features added through an extension mechanism, and establishment of a friendly, open, community-oriented development processes.

In this presentation, Inkscape will be presented and the community development process discussed.

=== Introduction ===
* Scalable Vector Graphics Editor -- Cross-Platform, Open Source, C++ codebase
* Started in November of 2003 from the [[SodiPodi/Gill]] codebase with 4 devs.
* Already grown to 10-20 developers by Spring 2004 & still growing
* This talk is going to be a technical introduction to the project.

=== Scalable Vector Graphics (SVG) ===
* Like HTML, but for graphics. XML standard for vector graphics
* Can write in a text editor using a straightforward & obvious syntax
* Vector vs. Raster
** Raster is an array of dots that "appear" to be shapes
*** Pro: With sufficient resolution can be photo-realistic
*** Con: Takes up lots of space even for simple geometric representations
*** Con: Difficult to split into component pieces for further editing
** Vector is real 2D shapes
*** Pro: Geometric representations scalable to any resolution
*** Pro: Easy to edit component pieces
*** Con: Difficult to do photo-realistic images at small file sizes

=== Cross-Platform & Open Source ===
* Platforms include Linux[[/UNIX]], Mac OS X, Win32
* Open Source means:
** The source code is available for free to the whole world
** The development process is open to all to participate in and enjoy

=== Uses of Inkscape ===
* Vector Art
* Symbology - Logos, Flags, Street Signs
* Webpage Graphics, Buttons, and Flourishes
* Visually Attractive Maps, Diagrams, and Technical Drawings

=== Development Community[[/Process]] ===
* This is a collaborative open source program involving around 10-20 developers from all over the world.
* It uses the standard open source development process with some smoothed out concepts to make it even more effective.
* Patch first, discuss later
* low barrier for developer commit access to CVS
* uses sourceforge.net
* Uses Network of Social Software (the key to distributive writing/dev)
** Website
** CVS
** Wiki
** Mailing List(s) and E-mail
** Chat (jabber.org)
* Bus Factor of the project (It has a high one)
* more?

=== Why is this important? ===
* In order to define this, one must decide to which community this is important.
* A production ready software does not exist in the GNU[[/Linux]] world.
** As you all would be concerned, this type of tool doesn't exist!
* Art Community
** It is free.
** It is high quality and production ready!
** Supports positive ideals!
*** Copyright is what it is, but we would like to see more opened up tools and codebases. Promotes development and honesty.
* Scientific Community
* Visualization Community

=== Common Misconceptions (Low Hanging Fruit) ===
* Isn't this just an open source Illustrator?
* Isn't there X, Y, and Z projects that already do this?
* Open Source doesn't innovate, it only imitates

=== Problems to be solved ===
* Not enough viewers
** solution: mozilla is pushing it
** solution: inkview
** solution: adobe svg is pushing hard!!!
* Our program is not fully compliant yet
** solution: need more developers and more integration

=== Future ===
* extension system
** quicker development
** don't have to know as much about the internals
* networked editing (shared space)
* layers
* clipart.freedesktop.org

----

=== Also Check the [[TufteStylePresentation]] ===

ScribusInteroperability

2007-01-10T10:24:57Z

Cornelius: Removing spam added by Avol

This will serve as a page to discuss Inkscape's interoperability with [http://www.scribus.net/ the SCRIBUS Desktop Publishing App.]

== Meeting 02 ==

=== Update 01:09:2004 ===

A second meet is planned for 19 Sept 2004 0800 UTC, pending acceptance by Inkscape devels. Scribus Team has been mailed already.

==== Preliminary Topics List ====

* SVG import/exports.. Where are we.. what's broken, what's works
* Further cooperation.. I suggested we could help first with beginning lcms support in Inkscape, its easier.. and it will get my butt in gear to finish the openicc paper
* Give inkscape folks some clues for what we are working on for 1.3+
* Can we work on a complementary set of keyboard shortcuts? Inkscape has loads and they work well
** see http://devwiki.scribus.net/index.php/Harmonzing_Scribus/Inkscape_Keyboard_Shortcuts
** complete list for Inkscape: http://inkscape.org/doc/keys.html
* Now 1.2 is done, a good lookover by the Inkscape UI folks at Scribus wrt to Usability. This is the perfect time to do this type of study.
* Scope out perhaps some help with them for EPS import/export. Maybe they could pinch Franz's EPS[[/PS]] import code and write it as an external module for inkscape.
** As aside note, I'll encourage Suse to add Inkscape as part of their 9.2 distro

--Mrdocs

----

== Meeting 01 ==

=== Updates 04:30:2004 ===
* A number of import bug fixes have been made to Scribus SVG import. Bulia's text features have drastically improved text import. More work is planned before 1.2 is released. New SVG rendering code has dramatically sped up import and display of SVG objects.

* Things that would help:

** Somewhere some notes on the differences between "Plain SVG" and Inkscape native formats.

** We have added Inkscape links to the home page of www.scribus.net and added news items for each Inkscape release, as well as annoucements to the mailing list.

** Scribus needs more sophisticated gradient handling. It is on the roadmap. This would be the last major shape or object barrier.

** We cannot forget color sets. Scribus now has four included.

== Initial Meeting Plan ==

Bryce from Inkscape and I, MRDOCS, worked out some preliminary stuff on the initial meeting to happen on IRC, server irc.freenode.net.

We'll do it on #scribus-dev. Inkscape members can be invited from #scribus

Best times considering where Inkscape developers live are: US[[/Eastern]] Sat 1-2 am EST; US[[/Pacific]] Fri 10-11 pm PST; Central Europe Sat 7-8 am CET; Australia[[/Melbourne]] Sat 5-6 pm AEST.

We decided Sat Feb 28 06:00:00 UTC 2004. (Try date --date='2004-02-28 06:00:00 +0000' to convert to your timezone.)

Let's have a definite start and finish time. Uncovered subjects can be done at a later date. 1 hr MAX!

==== Preliminary Topic List ====

1. SVG Text - What sort of issues need to be resolved in order for SVG Text import between Inkscape and Scribus to work better? What steps could be taken to get us moving in that direction?

2. Shared Color Names and Sets - Is it feasible to have a set of common default color names or color sets, that could be standardized between Scribus and Inkscape? What things could be done to help achieve this?

3. Color Management - Might be premature...but not forgotten.

4. METADATA Support - Inkscape plans to start tagging clipart with XMP (XML[[/RDF]] format) info (Author, title, license, etc.) What could we do to ensure METADATA compatibility between Inkscape and Scribus? Could we push our work on XMP into a library that SCRIBUS (and other apps really) could use?

5. Improved Postscript Support - Inkscape's printing support is not as good as users would like. Does Scribus have PS expertise we could tap for questions/advice, or code that we could use in Inkscape?

Since testing Inkscape's first release I have come to appreciate their progress and the way they have managed their whole project. It's a textbook example of OSS. I am very confident collaboration will yield good things for the future. --MRDOCS

=== Who's Who: ===
==== Scribus ====

==== fschmid ====
Franz Schmid - Started coding Scribus in 2001. Commercial Manager in Germany. Primary coder handles all the cvs commits. (Note to Inkscape..Scribus CVS is not public and anoncvs is rsync'd to the Salford site.)

==== nodoid ====
Paul F. Johnson - Joined Scribus around 0.8 release. IT manager and lecturer for School of Music - U. Salford UK. Works on code optimization, profiling, code review, patch reviews and code docs. scribus.net is hosted there by his Uni.

==== [[MrB]] ====
Craig Bradney - Joined Scribus during 1.1 releases. Setup Bug Tracker, IRC channel, handles most of the mailing list[[/IRC]] questions, works with Franz on bug triaging and bug fixing. Setting up IT company in Luxembourg. Australian national. Constant presence on IRC :) Helps mrdocs with Scribus website.

==== Mrdocs ====
Peter Linnell - Started testing Scribus early on 0.3.7. Professional DTP[[/IT]] consultant. Tests Scribus in clients pre-press/service bureau. Wrote most all of the English docs and web content. Works with [[MrB]] on bug testing and handles rpm builds. Bugs Inkscape team on Jabber ;)

==== subik ====
Petr Vanek - Newest member of Scribus team. Written some useful plug-ins including a plug-in howto, works on adding more functions to the python scripter. Does Czech translation of Scribus and has written some English and Czech docs.

-mrdocs

=== Inkscape ===

Anyone else going to attend the meeting? This is off the top of my head...johan, kees

==== bryce ====
Bryce Harrington - One of the project founders. Focuses on organizational stuff to try to keep the project chugging along well. Coded the original extension system. Works on getting the marker code hooked up, and helps with bug fixing and code cleanup. Considering writing a lib for better numeric localization 'ftos'.

njh

I joined mental and bryce in the initial planning and setup stages of the inkscape project. As I'm currently trying to finish off my [[PhD]] I've only really had time for behind the scenes works, such as rebuilding the mathematics (NR::Point, Matrix etc). My [[PhD]] research is on page layout algorithms, which I intend to add to inkscape once I've finished writing up.

bbyak

IANAP (I Am Not A Programmer), I am a usability freak :) All kinds of interface rearrangements and polish, shortcuts and mouse behaviors, documentation, lots of bug reporting and bugfixing. Some new functionality, too; I especially grok the text tool (added kerning and letterspacing) and the node editor.

[[JonCruz]]

Jon A. Cruz - Joined right after the initial announcement (Had just had a 'refocusing experience' and was getting going with Sodipodi usage and looking for Open Source projects to join when the notice came out). Has multimedia as well as multiple platform background. Dabbler in Unicode, I18n, UI, Color[[/Palettes/Patterns/etc]]., XML, metadata[[/RDF/XMP]], DOM, Animation, Language bindings, Win32 tricks, OS X Usage...

[[TedGould]]

Official title should probably be "Jabber chat room heckler" but I also do some development on the side. I initially helped with splitting off the project and I am usually the guy who builds the releases (but really I'm the guy who fixes 'make distcheck' :). I took Bryce's scripting idea and expanded it some and I'm still working on cleaning it up. Everyone agrees that extensions are where Inkscape needs to be going in the future, and that is a target of our next release.

mental

Co-founded the project with bryce, njh, and Ted. Graphic designer by training, but highly proficient in programming and software design. Does a little bit of everything -- if you need to know something about Inkscape's architecture, he's probably the person to ask. He also (tries) to go to bed not too long after midnight, so 1am meetings (in his timezone, EST) are out of the question. Not that he isn't often up that late anyway. :P

[http://www.rejon.org/ rejon] (Jon Phillips)

Joined the project right after the initial announcement. His main interest is in promoting Inkscape and linking the project with larger goals through the cleaning up usability, bugs and the implementation of new ideas (mainly the extension system). He is taking a lead on the new clipart project with Ted, Bryce and some sodipodi developers.
Tasks: planner, writer, administrative, website, help/tutorials, code cleanup, tester, some work on the codebase.

pjrm

Programmer for constraints-related research; shares office with njh. Mainly cleanup & bug fix work on inkscape so far.

ishmal

sk1p

mrdocs

=== Meeting Notes ===

1. SVG Text - What sort of issues need to be resolved in order for SVG Text import between Inkscape and Scribus to work better? What steps could be taken to get us moving in that direction?

::Decided to setup [[SvgTestCases]]. This is where Scribus and Inkscape developers can look test and compare SVG files. This will mainly be used to coordinate efforts between scribus and Inkscape developers to have consistent display of SVG content. We need to setup an SVG Test Cases CVS Modules

2. Shared Color Names and Sets - Is it feasible to have a set of common default color names or color sets, that could be standardized between Scribus and Inkscape? What things could be done to help achieve this?

::Look into this further, but [[LittleCMS]] implementation will help smooth between teams.
::[http://www.w3.org/TR/SVG11/types.html#DataTypeColor svg data[[TypeColor]]]
::[http://www.w3.org/TR/SVG11/types.html#ColorKeywords colorKeywords]
::[http://www.w3.org/Graphics/Color/sRGB.html w3 sRGB research]

3. Color Management - Might be premature...but not forgotten.

::Color Management - [[LittleCMS]]

4. METADATA Support - Inkscape plans to start tagging clipart with XMP (XML[[/RDF]] format) info (Author, title, license, etc.) What could we do to ensure METADATA compatibility between Inkscape and Scribus? Could we push our work on XMP into a library that SCRIBUS (and other apps really) could use?

::XMP and Scribus will follow our lead. [[JonCruz]] will look into after implementing basic support and then possibly push work into a library. Decided that how people use their files and rights management is up to the user and not our projects.
::[http://partners.adobe.com/asn/tech/xmp/index.jsp adobe xmp info]

5. Improved Postscript Support - Inkscape's printing support is not as good as users would like. Does Scribus have PS expertise we could tap for questions/advice, or code that we could use in Inkscape?

::Could someone else add notes to PS support. We decided that Inkscape drastically needs import/export of EPS and PDF.
::IMHO we could prepare Scribus PDF[[/PS]] libraries for Inkscape export (just after quick examination of the code) [subik]

EXTRAS:

scripting - hopefully we can share the same languages, some keywords, etc, [http://www.swig.org/ swig]
- any experiences with [http://riverbankcomputing.co.uk/sip/ sip]?

Log [http://www.atlantictechsolutions.com/inkscape/28022004.log IRC Log 28022004]

CompilingSuse

2006-12-14T21:52:36Z

Cornelius: /* OpenSUSE 10.2 */

== OpenSUSE 10.2 ==

You need to install these packages to pass the compilation of SVN trunk:
* gtkmm-devel
* glibmm-devel
* cairomm-devel
* libsigc-2.0-devel
* gc-6.6 (Boehm's collector)
* intltool
* + their dependencies
* AND automake-1.8.5 or any other then 1.9.6 that is installed by default.
* and any other optionally required packages

If you compile automake-1.8.5 by yourself then be sure that you install it to /usr prefix and not to /usr/local. If you still install to /usr/local, then instead of running "autogen.sh" on svn version, run:

ACLOCAL_FLAGS="$ACLOCAL_FLAGS -I /usr/share/aclocal" ./autogen.sh

Then run ./configure; make; sudo make install as usually.

Thanks go to Dobey who helped a lot to figure out what was the problem.

== Suse 9.0 ==

One of the challenges with Suse 9.0 is the lack of a distro provided gtkmm2 and libsigc++ packages.

Best place to find them: ftp://ftp.gwdg.de/pub/linux/misc/apt4rpm/suse/usr-local-bin/9.0/
[ This URL does not exist anymore :-( ]

Suse 9.1 includes both now in the GNOME supplemental downloads.

Note that for SuSE the gtk+2 packages are called gtk2. The gtk+2 2.4 package is not provided via Yast but can be found via rpmseek as gtk2 and gtk2-devel

To find the .pc files, I had to set:

setenv PKG_CONFIG_PATH/usr/local/lib/pkgconfig:/usr/lib/pkgconfig:/opt/gnome/lib/pkgconfig/

In SuSE 9.1 I ran into this error:

configure.in:25: required file `./ltmain.sh' not found

Copying /usr/share/libtool/ltmain.sh into the top directory fixed it.

For 0.40cvs the libgc dependency is added. In [[SuSE]] 9.1 this is package 'boehm-gc', but it doesn't work - you need to compile from source. Download from:

http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.3.tar.gz

Then configure it with the command:

$ ./configure --enable-cplus-plus

SuSE 9.1 also does not have libsigc++ 2.0; I couldn't find an rpm for it so ended up having to compile it from source, from http://prdownloads.sourceforge.net/libsigc/libsigc++-2.0.3.tar.gz

I also had to compile gtkmm 2.4 and glib 2.4 from source; download them from ftp://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.4/ and http://ftp.gnome.org/pub/GNOME/sources/glibmm/2.4/

Looks like these packages are also available from here:ftp://ftp.gwdg.de/pub/linux/suse/apt/SuSE/9.1-i386/RPMS.gnome/

Also, stuff got installed to /opt/gnome/bin/, so I had to also
`export PATH=$PATH:/opt/gnome/bin/`

[[Category:Developer Documentation]]
[[Category:Needs Work]]

CompilingSuse

2006-12-14T21:49:50Z

Cornelius: OpenSUSE 10.2 compilation instructions

== OpenSUSE 10.2 ==

You need to install thes packages to pass the compilation of SVN trunk:
* gtkmm-devel
* glibmm-devel
* cairomm-devel
* libsigc-2.0-devel
* gc-6.6 (Boehm's collector)
* intltool
* + their dependencies
* AND automake-1.8.5 or any other then 1.9.6 that is installed by default.
* and any other optionally required packages

If you compile automake-1.8.5 by yourself then be sure that you install it to /usr prefix and not to /usr/local. If you still install to /usr/local, then instead of running "autogen.sh" on svn version, run:

ACLOCAL_FLAGS="$ACLOCAL_FLAGS -I /usr/share/aclocal" ./autogen.sh

Then run ./configure; make; sudo make install as usually. Thanks go to Dobey who helped a lot to figure out what was the problem.

== Suse 9.0 ==

One of the challenges with Suse 9.0 is the lack of a distro provided gtkmm2 and libsigc++ packages.

Best place to find them: ftp://ftp.gwdg.de/pub/linux/misc/apt4rpm/suse/usr-local-bin/9.0/
[ This URL does not exist anymore :-( ]

Suse 9.1 includes both now in the GNOME supplemental downloads.

Note that for SuSE the gtk+2 packages are called gtk2. The gtk+2 2.4 package is not provided via Yast but can be found via rpmseek as gtk2 and gtk2-devel

To find the .pc files, I had to set:

setenv PKG_CONFIG_PATH/usr/local/lib/pkgconfig:/usr/lib/pkgconfig:/opt/gnome/lib/pkgconfig/

In SuSE 9.1 I ran into this error:

configure.in:25: required file `./ltmain.sh' not found

Copying /usr/share/libtool/ltmain.sh into the top directory fixed it.

For 0.40cvs the libgc dependency is added. In [[SuSE]] 9.1 this is package 'boehm-gc', but it doesn't work - you need to compile from source. Download from:

http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.3.tar.gz

Then configure it with the command:

$ ./configure --enable-cplus-plus

SuSE 9.1 also does not have libsigc++ 2.0; I couldn't find an rpm for it so ended up having to compile it from source, from http://prdownloads.sourceforge.net/libsigc/libsigc++-2.0.3.tar.gz

I also had to compile gtkmm 2.4 and glib 2.4 from source; download them from ftp://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.4/ and http://ftp.gnome.org/pub/GNOME/sources/glibmm/2.4/

Looks like these packages are also available from here:ftp://ftp.gwdg.de/pub/linux/suse/apt/SuSE/9.1-i386/RPMS.gnome/

Also, stuff got installed to /opt/gnome/bin/, so I had to also
`export PATH=$PATH:/opt/gnome/bin/`

[[Category:Developer Documentation]]
[[Category:Needs Work]]

Tools

2006-11-24T06:38:50Z

Cornelius: removing spam added by user Vasst

=== SVG Validator ===
A [http://jiggles.w3.org/svgvalidator/ validator service] (and downloadable tool) is provided by the [[W3C]]. It will complain about sodipodi or inkscape namespaced items in the document, unless you've exported to plain SVG.

=== SVG::Metadata ===
[http://search.cpan.org/CPAN/authors/id/B/BR/BRYCE/SVG-Metadata-0.10.tar.gz Perl module and set of scripts] to help in adding and processing metadata in SVG files.

=== Potrace ===
[[Potrace]] is now embedded into Inkscape. You don't need to run it separately.
*[[Potrace|Using Potrace through Inkscape]]
*[http://potrace.sourceforge.net/ Potrace page at Sourceforge]

=== Autotrace and Frontline (alternatives to Potrace) ===
'''Autotrace''' an open source vectorization program by Martin Weber. That means you can convert bitmap images (like scans) to vector graphics. While not optimal for photos, it does good job on line art and poster-like images. Doesn't do too well with color.

Autotrace has some features not available in the embedded [[Potrace]] dialog in Inkscape. For example, there is a ''centerline'' switch that is especially usefull for tracing roads (in maps) or font characters.

'''Frontline''' is GUI frontend to Autotrace by Masatake Yamato. Frontline can be run as standalone aplication, but it can also be directly accessed from Inkscape and GIMP.

If you want to have tracing option, you have to install both Autotrace and rontline before compiling Inkscape. Inkscape automatically detects these programs, and adds inline raster to vector conversion option to image menu.

Both autotrace and frontline can be downloaded from [http://autotrace.sourceforge.net/ Sourceforge]. Binaries are available for windows and linux.

=== Delineate ===
Front end written in java that does interesting things with color images.
*[http://delineate.sourceforge.net/ Delineate at Sourceforge]

=== ill2svg ===
ill2svg (Illustrator to SVG) is a small script that helps turn Adobe
Illustrator .ai files into SVG. While it doesn't always do a perfect job,
it can sometimes be of great help.

To use the program, just type:

<pre>ill2svg.pl [-l "string" -h] infile > outfile.svg

options:
-l specify the file's line-ending convention: dos, mac,
or unix; the default is unix

-h print this message and exit
</pre>

=== ai2svg.py ===
ai2svg (Illustrator to SVG, recoded in python) is as well a small script that helps turn Adobe Illustrator .ai files into SVG. The Python recode aims to help developers more familiar to python than perl, as well fixing some lacks from ill2svg.pl - supports dashes, layers, textboxes (ascii-latin), and joined pathes.

To use the program, just type:

<pre>python ai2svg.py drawing.ai

the result will appear as neighbour, named drawing.ai.svg

options:
--help print this message and exit
</pre>

available at http://www15.brinkster.com/nitrofurano/python/ (that .zip file, in the tools folder)

=== gimp2sodipodi ===
Shandy Brown has assembled a somewhat obscure but useful set of tools to get from GIMP to Sodipodi (and thus to Inkscape). That is, convert raster to vector.
*[http://sjbrown.users.geeky.net/gimp2sodi/HOWTO.html gimp2sodipodi instructions.]

=== GIMP ===
GIMP is a bitmap graphics tool in the first place, but:
* it imports SVG (with help of librsvg) into bitmap or vector path, exports SVG.
* GIMP's selection can be converted to a vector path, and paths can be exported/imported as SVG.

GIMP can be used to create nice textures to use in Inkscape or shapes that can be vectorized in Inkscape. Importing SVG drawings from Inkscape to GIMP allows you to do several effects by filling and stroking shapes.

There is a limited support for drag'n'drop between GIMP and Inkscape:
* path, can be drag'n'droped from Gimp path dialog to Inkscape
* pictures can be drag'n'droped from Gimp document history to Inkscape if it's in a file format that Inkscape understands.

*[http://www.gimp.org gimp.org]

=== Linux Video Editing System ===
LIVES is the Linux Video Editing System that permits editing and
making video without worries about formats, frame sizes, or frame
rates. It doesn't support SVG directly yet, but you can create animated
works by moving your shapes in Inkscape and exporting as numbered
png's.

*[http://www.xs4all.nl/%7Esalsaman/lives/ LIVES]

[[Category:About Inkscape]]

Inkscape

2006-10-15T16:53:07Z

Cornelius: removing spam

This is a freeform area for Inkscape development and discussion.
Curious about [[WikiSyntax]]?

Other languages: [[Inkscape en español|Wiki en español]], [[L'Inkscape en Català|Wiki en Català]], [[Inkscape em Português|Wiki em Português]], [[Startseite|Wiki auf Deutsch]]...

<table cellspacing="11" width="100%"><tr valign="top">
<td style="width:33%;background-color: #EFFBFF; padding:.5em; border: 1px solid #BFEEFF">
=== About Inkscape ===
* [http://www.inkscape.org/ Inkscape Homepage]
* [[About Inkscape]]
* [[InkscapeFeatures]]
* [[FAQ]] - Frequently Asked Questions
* [[ProjectInfo]]
* [[SupportedOperatingSystems]]
* [[Tools]] - Supporting Tools and Applications
* [[Galleries]]
* [[ArticlesAndPresentations]]
* [[TestimonialComments]]
* [[InkscapePopularity]]
* [[ContactInfo]] our heroes

</td><td style="width:33%;;background-color: #FFF1EF; padding:.5em; border: 1px solid #FFC7BF;margin:.5em">

=== User Documentation ===
* [[InstallHelp]]
* [[InkscapeTerminology]]
* [[UserManual]]
* [http://inkscape.org/doc/ Tutorials]
* [[InkscapeSVG|Inkscape SVG vs. Plain SVG]]
* [[GettingExtensionsWorking]]
* [[GettingEffectsWorking]]
* [[WhatEffectsDo]]
* [[UsingTheConnectorTool]]
* [[Installing Fonts as a User]]
* [[EmergencySave]]
* [[ReleaseNotes045|Release Notes]] for 0.45 (unstable)
* [[ReleaseNotes044|Release Notes]] for 0.44 and past
* [[Announcing Releases]] for 0.44 and past
* [[ArticleIntroducingInkscape0_40|Introducing Inkscape 0.40]]
* [[TricksAndTips]]
</td><td style="width:33%;background-color: #FFFAE5; padding:.5em; border: 1px solid #FFFF66; margin:.5em">

=== Help Inkscape Without Coding ===

* [[PrintingConsensusPoll]]
* [[HelpWanted]]
* [[CreatingDists]]: how to build packages
* [[WebsiteEditing]]
* [[UpdatingTrackerItems]]
* [[TutorialIdeas]]
* [[How_To_Start_A_Page]] how to use the wiki
* [[TestingInkscape]]

</td></tr></table><table cellspacing="0" width="100%" style="background-color: #FFFAE5; border-width:0em .5em; border-style:solid; border-color:white"><tr valign="top" style="padding:11px 0em 0em 11px">
<th colspan="2" align="left" style="padding:.5em 0em 0em .5em">

=== Developer Documentation ===
</th></tr><tr valign="top" align="left"><td style="width:50%;padding:.5em">
==== General ====
* [[DeveloperManual]]
* [[CompilingInkscape]]
* [[WorkingWithSVN]]
* [[HandlingPreferences]]: creating and using preference values
* [[AddSPObject]]: how to add a new SPObject type
* [[ReprListeners]]: responding to XML doc changes
* [[ErrorsAndWarnings]]: how to deal with reporting errors, warnings, and other messages
* [[DebuggingTips]]: random tips to help debug problems

* [[DeveloperTitles]]: terms for various roles in Inkscape
* [[InkscapeJanitors]]: small tasks that need doing
* [http://livarot.sourceforge.net/ Livarot]: for boolean ops
* [[ExtensionAttributes]]: currently defined attributes in Inkscape's XML namespace and what they do
* [[MakingAnExtension]]: how extension must work and how to write an INX file
* [[ExtensionsRepository]]: an Internet central for Inkscape Extensions
* [[OtherProjects]] (outside links)

</td><td style="width:50%;padding:.5em">

==== Development Discussion ====
* [[Roadmap]]: the main todo list
* [[NewFeatureProposals]]
* [[ExtensionArchitectureProposals]]
* [[Coding Style|Coding Style Discussion]]
* [[FileTypes]]
* [[ApplicationIcons]] ( Application + Interface )
* [[InkscapeColor]]
* [[PrintingSubsystem]]
* [[SVG Competitors Plan]] - MS WVG vs SVG, etc
* [[SVG Tiny Compliance]]
* [[SVG Test Suite Compliance]] - [[W3C]] full test suite
* [[CSS Support]]
* [[OpenVG]] Standard (draft)
* [[OpenDocument proposal]]
* [[Googles Summer Of Code]]
* [[UI MockupScreenshots]]
* [[lib2geom]]

</td></tr><tr valign="top" align="left"><td style="width:50%;padding:.5em">

==== User Interface Discussion ====
* [[Translation_information]]
* [[AccessibleGraphics]]
* [[ObjectManager]]
* [[DialogsReorganization]]
* [[DialogReplacement]]
* [[ModalInterfaces]]
* [[TextUsability]]: text tool /dialog dialog
* [[KeyboardShortcutsToDo]]
** [[KeyboardProfiles]]: how you can help
* [[StatusbarAPI]]
* [[Animation-(Timeline)]]
* [[Free Desktop Graphic Suite]]

</td><td style="width:50%;padding:.5em">
==== Rearchitecture Discussion ====
* [[SubsystemRearchitecture]]
* [[GtkMMification]]: replace C boilerplate with gtkmm objects
* [[PathRepresentation]]
* [[Cairoification]]
* [[ScribusInteroperability]]

</td></tr></table>

----
* [[WikiAttic]]: pages that are no longer relevant but kept for historical value

__NOTOC__

[[Category:About Inkscape]]
[[Category:User Documentation]]

Inkscape

2006-10-14T20:39:53Z

Cornelius: reverting spam

Script extensions

2006-10-04T15:02:00Z

Cornelius: updating link to ted's blog

=== Introduction ===

Inkscape provides the ability for its functionality to be extended using traditional unix scripts. By this, we mean a program that takes in a stream of data through standard in, and then outputs that data on standard out. This is a very easy way to expand Inkscape, and provide custom functionality, without learning the internals of Inkscape. Plus, there are SVG read and writing libraries out there for almost any language, and the rest of them all have XML support (which is really what you probably want to use anyway). This HOWTO discusses the ends and outs of writing one of these scripts and getting it to work with the Inkscape core functionality.

=== Types of scripts ===

Basically there are three functions that added with a script:

* Input, providing translation from a file format to SVG
* Output, providing translation from SVG to a format
* Filter, taking in SVG, changing it, and then outputing SVG

While all of these are very similar in the scripting interface, there are slight differences between them.

=== Interaction ===

It is important for a script author to understand how Inkscape and scripts communicate.

(interpreter)? your_script (--param=value)* /path/to/input[[/SVGfile]] | inkscape

Inkscape runs your script (optionally with an interpreter) passing it any number of parameters in long gnu style. The final argument is the name of the temporary svg file your script should read. After processing, the script should return the modified svg file to inkscape on STDOUT.

=== Localisation of extensions ===

To allow localisation of strings in extension for Inkscape, some xml tags have to be adapted to variant readable by intltool. It means that tags or parametres has to have "_" prepended to their name, e.g. <_name>name of extension</_name>

Also the path to the extension has to be included in POTFILES.in file to tell intltool where to look for translatable content.

Usefull information, before this section gets fully updated, can be found at [http://gould.cx/ted/blog/Translating_Custom_XML Ted's blog].

=== Description ===

In order for Inkscape to make use of an external script or program, you must describe that script to inkscape using an INX file. See the inkscape share directory for examples.

==== Parameters ====
The INX file describes which parameters the extension needs. Inkscape will prompt the user with a UI to fill out these parameters before the

extension is called. Each parameter will be passed through the commandline as "--paramname=paramvalue". Eg. if you have described a string

parameter with name 'string1' in the INX file, Inkscape will present a textbox to the user. When the user fills in "text" and presses OK, it

will pass '--string1="text"' to the program specified by the <command> tag.

There are several types of parameters that can be requested by the INX description:

===== Boolean =====

===== Int =====

===== Float =====

===== String =====

===== Description =====

===== Enum =====

===== Notebook =====

=== Installing ===

Installing is as simple as copying the script (unless it resides in your path) and its INX file to the inkscape/share/extensions (home/.inkscape/extensions) directory.

If you are looking to use scripts that have already been written, the most difficult part will likely be the installation. Since scripts are seperate programs they may have any number of dependencies that are not included with inkscape. Currently, the best way to find missing dependencies is by reading the error messages produced by running the script from the command line.

=== See Also ===

*http://www.ekips.org/comp/inkscape/extending.php#ignorance

Script extensions

2006-10-04T14:56:58Z

Cornelius: Adding information about localisation of extensions

=== Introduction ===

Inkscape provides the ability for its functionality to be extended using traditional unix scripts. By this, we mean a program that takes in a stream of data through standard in, and then outputs that data on standard out. This is a very easy way to expand Inkscape, and provide custom functionality, without learning the internals of Inkscape. Plus, there are SVG read and writing libraries out there for almost any language, and the rest of them all have XML support (which is really what you probably want to use anyway). This HOWTO discusses the ends and outs of writing one of these scripts and getting it to work with the Inkscape core functionality.

=== Types of scripts ===

Basically there are three functions that added with a script:

* Input, providing translation from a file format to SVG
* Output, providing translation from SVG to a format
* Filter, taking in SVG, changing it, and then outputing SVG

While all of these are very similar in the scripting interface, there are slight differences between them.

=== Interaction ===

It is important for a script author to understand how Inkscape and scripts communicate.

(interpreter)? your_script (--param=value)* /path/to/input[[/SVGfile]] | inkscape

Inkscape runs your script (optionally with an interpreter) passing it any number of parameters in long gnu style. The final argument is the name of the temporary svg file your script should read. After processing, the script should return the modified svg file to inkscape on STDOUT.

=== Localisation of extensions ===

To allow localisation of strings in extension for Inkscape, some xml tags have to be adapted to variant readable by intltool. It means that tags or parametres has to have "_" prepended to their name, e.g. <_name>name of extension</_name>

Also the path to the extension has to be included in POTFILES.in file to tell intltool where to look for translatable content.

Usefull information, before this section gets fully updated, can be found at [http://gould.cx/ted/blog/2005/Dec Ted's blog] at the bottom of the page: "Translating Custom XML" paragraph.

=== Description ===

In order for Inkscape to make use of an external script or program, you must describe that script to inkscape using an INX file. See the inkscape share directory for examples.

==== Parameters ====
The INX file describes which parameters the extension needs. Inkscape will prompt the user with a UI to fill out these parameters before the

extension is called. Each parameter will be passed through the commandline as "--paramname=paramvalue". Eg. if you have described a string

parameter with name 'string1' in the INX file, Inkscape will present a textbox to the user. When the user fills in "text" and presses OK, it

will pass '--string1="text"' to the program specified by the <command> tag.

There are several types of parameters that can be requested by the INX description:

===== Boolean =====

===== Int =====

===== Float =====

===== String =====

===== Description =====

===== Enum =====

===== Notebook =====

=== Installing ===

Installing is as simple as copying the script (unless it resides in your path) and its INX file to the inkscape/share/extensions (home/.inkscape/extensions) directory.

If you are looking to use scripts that have already been written, the most difficult part will likely be the installation. Since scripts are seperate programs they may have any number of dependencies that are not included with inkscape. Currently, the best way to find missing dependencies is by reading the error messages produced by running the script from the command line.

=== See Also ===

*http://www.ekips.org/comp/inkscape/extending.php#ignorance

Inkscape

2006-10-04T06:01:13Z

Cornelius: removing spam added by user BigF

Inkscape

2006-09-30T17:54:48Z

Cornelius: removing spam by Asfgas

Inkscape

2006-09-26T19:05:43Z

Cornelius: Reverting spam by China001 to latest version by VonHalenbach

User:Cornelius

2006-09-06T10:13:14Z

Cornelius: Filling resume for inkscape

= BIO =
* Name: Josef Vybíral
* Nickname: cornelius or cornelius[cz]
* Inkscape jobs: My main task in Inkscape world is to translate program and related documents to czech language. Also I have my fingers in inkscape.org website and in some presentations of Inkscape to the public too.
* Nationality: Czech republic, actually living near Moravian border with Poland.
As a creative artist and webdesigner I use Inkscape daily for my dayjob tasks together with GIMP and Scribus apps.

== Contact ==
* email: josef.vybiral (a) gmail (dot) com
* jabber: cornelius (a) njs (dot) netlab (dot) cz
* website: http://cornelius.gimp.cz

= My TODOs =
== Longterm tasks ==
* Translation of Inkscape
* Translation of website and wiki
* Update design of wiki.inkscape.org

== Partially DONE ==
* Translation of Inkscape 0.45
* Translation of website and wiki. Website is translated from 99% mainly thanks to Richard Szlachta(ricardo) and Lukáš Mašek(Luciash). Thanks guys for your help
* Translation of Tutorials for 0.44. Basic, advanced and tools tutorials translated by Lukáš Hess(lunreal) as high school semestral project, thanks for your help.

== Already DONE ==
* Translation of Inkscape 0.41, 0.42, 0.43, 0.44
* Website translation

== Would like to do ==
* Conversion of inkscape.org to use .po files for translations
* Design ultimate icons theme for Inkscape

= Presentations of Inkscape =
* November 2005 - Inkscape, draw freely - conference LinuXChange 2005 Olomouc, CZ
* June 2006 - Inkscape, kresleme svobodně - Article in local Linux magazine presenting Inkscape 0.44

= Created by =
Hi Cornelius,

Thanks for all your work on the wiki! I have activated your sysop permissions, so you have some extra tools for managing the translated wiki pages and controlling spam. [[User:BryceHarrington|BryceHarrington]] 10:26, 13 June 2006 (PDT)

WebSiteTranslation

2006-09-05T14:08:47Z

Cornelius: /* Translation of web site */ updating list of translatable content

Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.

= Translation of web site =
# There are two ways of getting files that you need to translate website:
## 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. Be aware that the module is about 40MB to download because of screenshots!
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
##* screenshots/*
##* showcase/*
##* docs/* (at least main page for docs)
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.
# 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.
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.
== Translating news and status ==
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Wiki =

Translating the pages og the wiki is quite straightforward.

In a few steps :
- start by creating a main page for your language: create a new page (with an explicit translated title), and provide a link to it from the [[http://wiki.inkscape.org/wiki/index.php/Main_Page main wiki page of Inkscape]].
- then, start a new page for each wiki page translation, and link translated page to the main page of your language.

Don't forget to get some information about wiki syntax before creating/modifying some wiki pages.

= Release notes =
[[http://wiki.inkscape.org/wiki/index.php/Release_Notes Release notes]] simply consist in a wiki page.
You can apply the process stated [[http://wiki.inkscape.org/wiki/index.php/WebSiteTranslation#Wiki above]] for translating this content.

= Translation information =
Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.

WebSiteTranslation

2006-08-09T07:00:01Z

Cornelius: /* Translation of web site */ added warning about big size of inkscape_web module

Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.

= Translation of web site =
# There are two ways of getting files that you need to translate website:
## 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. Be aware that the module is about 40MB to download because of screenshots!
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.
# 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.
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.
== Translating news and status ==
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Wiki =

Translating the pages og the wiki is quite straightforward.

In a few steps :
- start by creating a main page for your language: create a new page (with an explicit translated title), and provide a link to it from the [[http://wiki.inkscape.org/wiki/index.php/Main_Page main wiki page of Inkscape]].
- then, start a new page for each wiki page translation, and link translated page to the main page of your language.

Don't forget to get some information about wiki syntax before creating/modifying some wiki pages.

= Release notes =
[[http://wiki.inkscape.org/wiki/index.php/Release_Notes Release notes]] simply consist in a wiki page.
You can apply the process stated [[http://wiki.inkscape.org/wiki/index.php/WebSiteTranslation#Wiki above]] for translating this content.

= Translation information =
Go Back to the main [http://wiki.inkscape.org/wiki/index.php/Translation_information Translation information] page.

Inkscape glossary

2006-06-12T21:36:23Z

Cornelius: /* Verbs (actions on objetcs) */

This is a beginning of an Inkscape glossary. Please respect it and contribute to it if you work on Inkscape UI. If you are doing translations, please create and link below a similar glossary for your language.

==General==
* '''Node''': point of a path that you can manipulate with. If you use Node tool, then it is displayed as gray or blue (if selected) rectangle on a path. Shapes do not have nodes, only handles. Node can have one or two handles too - displayed as circles connected to node. They modify bezier's tangents.

* '''Handle''': 1) one of two points around a node, displayed (for selected nodes) as a circle connected with its node by a line (node handles); 2) the arrows around the selected object in selector (scale handles, rotation handles); 3) points on a shape that can be dragged by node tool to edit the shape, displayed as small white diamonds (shape handles); 4) the things that you drag on canvas to set the placement, direction, and size of a gradient or pattern (gradient handles, pattern handles). (Internally this is called a Knot, but this is a deprecated term in user documentation.)

* '''Path''': object, with nodes, but without handles. For example a line created using the Freehand tool.

* '''Live Shape''': an object that does not display nodes but may have controls. An example is a circle or star. A live shape can be converted to path by Convert to Path command.

* '''Stroke''': a visible outline of a shape or path. Not the same as path; a path may or may not have a stroke. If the stroke is present, it can be converted to path by Convert Stroke to Path command.
** '''Stroke shape''' (to be implemented): the dependency of the stroke width on distance along the stroke. Currently only constant-width strokes are supported.
** '''Stroke pattern''' (to be implemented): the representation of a stroke as a sequence of arbitrary objects positioned along the path.

* '''Object''': an independent editable thing on the canvas. May be a path, a shape, a text object, a group, etc.

==User Interface==

* Document window: the window with a Canvas, Menu, Commands bar, etc. Note that the same instance of the program may have several document windows. Some dialog are referred to as "windows" therefore it is important to distinguish between them and the Document window.
* Menu, bar at the top.
* Commands bar, beneath the Menu, with buttons for commands like New, Open, ... Note that this one will likely be broken into many smaller toolbars, each covering one topic, so the user will be able to switch them on/off and rearrange. So this name is temporary.
* Tool Controls bar, beneath the Commands bar. Has the controls for the currently active tool. Note the capitalization. One should not refer to it as the "Tool bar," nor is it a "Tool" edition of the "controls" variety of "bar". It's proper name should be "Tool Controls" bar.
* Tools, along the left side
** Selector tool
** Node tool
** Zoom tool
** Rectangle tool
** Elipse tool
** Star tool
** Spiral tool
** Pencil tool: to preserve consistency, please do not refer to this tool as freehand tool. Pencil tool (freehand) is better to use.
** Pen tool: to preserve consistency, please do not refer to this tool as Bezier tool. Pen tool (Bezier) is better to use.
** Calligraphy tool
** Text tool
** Gradient tool
** Color dropper tool
* Canvas, main part, with optional border, rulers and scrollbars
* Status bar, along the bottom side of the window

== Dialog Boxes ==

* Fill and Stroke
* Swatches
* XML Editor
* Text and fonts
* Gradients
* Align and Distribute
* Tile Clones
* Global preferences
* Document preferences
* Document metadata

== Verbs (actions on objects) ==

== Effects ==
* Fretboard designer
* Generate from path
* Render
* Modify path

==Depreceated terms==
These are used inside the code. Never use them for documentation.

* knot (this may be a "handle", "control", "node" etc as seen by the user)
* item (use "object")
* desktop (use "canvas" or "document window" depending on context)
* event contexts (they are known to users as "tools")

Inkscape glossary

2006-06-12T21:17:24Z

Cornelius: /* General */

This is a beginning of an Inkscape glossary. Please respect it and contribute to it if you work on Inkscape UI. If you are doing translations, please create and link below a similar glossary for your language.

==General==
* '''Node''': point of a path that you can manipulate with. If you use Node tool, then it is displayed as gray or blue (if selected) rectangle on a path. Shapes do not have nodes, only handles. Node can have one or two handles too - displayed as circles connected to node. They modify bezier's tangents.

* '''Handle''': 1) one of two points around a node, displayed (for selected nodes) as a circle connected with its node by a line (node handles); 2) the arrows around the selected object in selector (scale handles, rotation handles); 3) points on a shape that can be dragged by node tool to edit the shape, displayed as small white diamonds (shape handles); 4) the things that you drag on canvas to set the placement, direction, and size of a gradient or pattern (gradient handles, pattern handles). (Internally this is called a Knot, but this is a deprecated term in user documentation.)

* '''Path''': object, with nodes, but without handles. For example a line created using the Freehand tool.

* '''Live Shape''': an object that does not display nodes but may have controls. An example is a circle or star. A live shape can be converted to path by Convert to Path command.

* '''Stroke''': a visible outline of a shape or path. Not the same as path; a path may or may not have a stroke. If the stroke is present, it can be converted to path by Convert Stroke to Path command.
** '''Stroke shape''' (to be implemented): the dependency of the stroke width on distance along the stroke. Currently only constant-width strokes are supported.
** '''Stroke pattern''' (to be implemented): the representation of a stroke as a sequence of arbitrary objects positioned along the path.

* '''Object''': an independent editable thing on the canvas. May be a path, a shape, a text object, a group, etc.

==User Interface==

* Document window: the window with a Canvas, Menu, Commands bar, etc. Note that the same instance of the program may have several document windows. Some dialog are referred to as "windows" therefore it is important to distinguish between them and the Document window.
* Menu, bar at the top.
* Commands bar, beneath the Menu, with buttons for commands like New, Open, ... Note that this one will likely be broken into many smaller toolbars, each covering one topic, so the user will be able to switch them on/off and rearrange. So this name is temporary.
* Tool Controls bar, beneath the Commands bar. Has the controls for the currently active tool. Note the capitalization. One should not refer to it as the "Tool bar," nor is it a "Tool" edition of the "controls" variety of "bar". It's proper name should be "Tool Controls" bar.
* Tools, along the left side
** Selector tool
** Node tool
** Zoom tool
** Rectangle tool
** Elipse tool
** Star tool
** Spiral tool
** Pencil tool: to preserve consistency, please do not refer to this tool as freehand tool. Pencil tool (freehand) is better to use.
** Pen tool: to preserve consistency, please do not refer to this tool as Bezier tool. Pen tool (Bezier) is better to use.
** Calligraphy tool
** Text tool
** Gradient tool
** Color dropper tool
* Canvas, main part, with optional border, rulers and scrollbars
* Status bar, along the bottom side of the window

== Dialog Boxes ==

* Fill and Stroke
* Swatches
* XML Editor
* Text and fonts
* Gradients
* Align and Distribute
* Tile Clones
* Global preferences
* Document preferences
* Document metadata

== Verbs (actions on objetcs) ==

== Effects ==
* Fretboard designer
* Generate from path
* Render
* Modify path

==Depreceated terms==
These are used inside the code. Never use them for documentation.

* knot (this may be a "handle", "control", "node" etc as seen by the user)
* item (use "object")
* desktop (use "canvas" or "document window" depending on context)
* event contexts (they are known to users as "tools")

Inkscape glossary

2006-06-12T21:13:02Z

Cornelius: /* Effects */

This is a beginning of an Inkscape glossary. Please respect it and contribute to it if you work on Inkscape UI. If you are doing translations, please create and link below a similar glossary for your language.

==General==
* Node: point of a path that you can manipulate with. If you use Node tool, then it is displayed as gray or blue (if selected) rectangle on a path. Shapes do not have nodes, only handles. Node can have one or two handles too - displayed as circles connected to node. They modify bezier's tangents.
* Handle: 1) one of two points around a node, displayed (for selected nodes) as a circle connected with its node by a line (node handles); 2) the arrows around the selected object in selector (scale handles, rotation handles); 3) points on a shape that can be dragged by node tool to edit the shape, displayed as small white diamonds (shape handles); 4) the things that you drag on canvas to set the placement, direction, and size of a gradient or pattern (gradient handles, pattern handles). (Internally this is called a Knot, but this is a deprecated term in user documentation.)
* Path: object, with nodes, but without handles. For example a line created using the Freehand tool.
* Live Shape: an object that does not display nodes but may have controls. An example is a circle or star. A live shape can be converted to path by Convert to Path command.
* Stroke: a visible outline of a shape or path. Not the same as path; a path may or may not have a stroke. If the stroke is present, it can be converted to path by Convert Stroke to Path command.
** Stroke shape (to be implemented): the dependency of the stroke width on distance along the stroke. Currently only constant-width strokes are supported.
** Stroke pattern (to be implemented): the representation of a stroke as a sequence of arbitrary objects positioned along the path.
* Object: an independent editable thing on the canvas. May be a path, a shape, a text object, a group, etc.

==User Interface==

* Document window: the window with a Canvas, Menu, Commands bar, etc. Note that the same instance of the program may have several document windows. Some dialog are referred to as "windows" therefore it is important to distinguish between them and the Document window.
* Menu, bar at the top.
* Commands bar, beneath the Menu, with buttons for commands like New, Open, ... Note that this one will likely be broken into many smaller toolbars, each covering one topic, so the user will be able to switch them on/off and rearrange. So this name is temporary.
* Tool Controls bar, beneath the Commands bar. Has the controls for the currently active tool. Note the capitalization. One should not refer to it as the "Tool bar," nor is it a "Tool" edition of the "controls" variety of "bar". It's proper name should be "Tool Controls" bar.
* Tools, along the left side
** Selector tool
** Node tool
** Zoom tool
** Rectangle tool
** Elipse tool
** Star tool
** Spiral tool
** Pencil tool: to preserve consistency, please do not refer to this tool as freehand tool. Pencil tool (freehand) is better to use.
** Pen tool: to preserve consistency, please do not refer to this tool as Bezier tool. Pen tool (Bezier) is better to use.
** Calligraphy tool
** Text tool
** Gradient tool
** Color dropper tool
* Canvas, main part, with optional border, rulers and scrollbars
* Status bar, along the bottom side of the window

== Dialog Boxes ==

* Fill and Stroke
* Swatches
* XML Editor
* Text and fonts
* Gradients
* Align and Distribute
* Tile Clones
* Global preferences
* Document preferences
* Document metadata

== Verbs (actions on objetcs) ==

== Effects ==
* Fretboard designer
* Generate from path
* Render
* Modify path

==Depreceated terms==
These are used inside the code. Never use them for documentation.

* knot (this may be a "handle", "control", "node" etc as seen by the user)
* item (use "object")
* desktop (use "canvas" or "document window" depending on context)
* event contexts (they are known to users as "tools")

Inkscape glossary

2006-06-12T21:10:17Z

Cornelius: /* Dialog Boxes */

This is a beginning of an Inkscape glossary. Please respect it and contribute to it if you work on Inkscape UI. If you are doing translations, please create and link below a similar glossary for your language.

==General==
* Node: point of a path that you can manipulate with. If you use Node tool, then it is displayed as gray or blue (if selected) rectangle on a path. Shapes do not have nodes, only handles. Node can have one or two handles too - displayed as circles connected to node. They modify bezier's tangents.
* Handle: 1) one of two points around a node, displayed (for selected nodes) as a circle connected with its node by a line (node handles); 2) the arrows around the selected object in selector (scale handles, rotation handles); 3) points on a shape that can be dragged by node tool to edit the shape, displayed as small white diamonds (shape handles); 4) the things that you drag on canvas to set the placement, direction, and size of a gradient or pattern (gradient handles, pattern handles). (Internally this is called a Knot, but this is a deprecated term in user documentation.)
* Path: object, with nodes, but without handles. For example a line created using the Freehand tool.
* Live Shape: an object that does not display nodes but may have controls. An example is a circle or star. A live shape can be converted to path by Convert to Path command.
* Stroke: a visible outline of a shape or path. Not the same as path; a path may or may not have a stroke. If the stroke is present, it can be converted to path by Convert Stroke to Path command.
** Stroke shape (to be implemented): the dependency of the stroke width on distance along the stroke. Currently only constant-width strokes are supported.
** Stroke pattern (to be implemented): the representation of a stroke as a sequence of arbitrary objects positioned along the path.
* Object: an independent editable thing on the canvas. May be a path, a shape, a text object, a group, etc.

==User Interface==

* Document window: the window with a Canvas, Menu, Commands bar, etc. Note that the same instance of the program may have several document windows. Some dialog are referred to as "windows" therefore it is important to distinguish between them and the Document window.
* Menu, bar at the top.
* Commands bar, beneath the Menu, with buttons for commands like New, Open, ... Note that this one will likely be broken into many smaller toolbars, each covering one topic, so the user will be able to switch them on/off and rearrange. So this name is temporary.
* Tool Controls bar, beneath the Commands bar. Has the controls for the currently active tool. Note the capitalization. One should not refer to it as the "Tool bar," nor is it a "Tool" edition of the "controls" variety of "bar". It's proper name should be "Tool Controls" bar.
* Tools, along the left side
** Selector tool
** Node tool
** Zoom tool
** Rectangle tool
** Elipse tool
** Star tool
** Spiral tool
** Pencil tool: to preserve consistency, please do not refer to this tool as freehand tool. Pencil tool (freehand) is better to use.
** Pen tool: to preserve consistency, please do not refer to this tool as Bezier tool. Pen tool (Bezier) is better to use.
** Calligraphy tool
** Text tool
** Gradient tool
** Color dropper tool
* Canvas, main part, with optional border, rulers and scrollbars
* Status bar, along the bottom side of the window

== Dialog Boxes ==

* Fill and Stroke
* Swatches
* XML Editor
* Text and fonts
* Gradients
* Align and Distribute
* Tile Clones
* Global preferences
* Document preferences
* Document metadata
* Trace bitmap
* Export dialog

== Verbs (actions on objetcs) ==

== Effects ==

==Depreceated terms==
These are used inside the code. Never use them for documentation.

* knot (this may be a "handle", "control", "node" etc as seen by the user)
* item (use "object")
* desktop (use "canvas" or "document window" depending on context)
* event contexts (they are known to users as "tools")

Inkscape glossary

2006-06-12T20:54:44Z

Cornelius: /* User Interface */

This is a beginning of an Inkscape glossary. Please respect it and contribute to it if you work on Inkscape UI. If you are doing translations, please create and link below a similar glossary for your language.

==General==
* Node: point of a path that you can manipulate with. If you use Node tool, then it is displayed as gray or blue (if selected) rectangle on a path. Shapes do not have nodes, only handles. Node can have one or two handles too - displayed as circles connected to node. They modify bezier's tangents.
* Handle: 1) one of two points around a node, displayed (for selected nodes) as a circle connected with its node by a line (node handles); 2) the arrows around the selected object in selector (scale handles, rotation handles); 3) points on a shape that can be dragged by node tool to edit the shape, displayed as small white diamonds (shape handles); 4) the things that you drag on canvas to set the placement, direction, and size of a gradient or pattern (gradient handles, pattern handles). (Internally this is called a Knot, but this is a deprecated term in user documentation.)
* Path: object, with nodes, but without handles. For example a line created using the Freehand tool.
* Live Shape: an object that does not display nodes but may have controls. An example is a circle or star. A live shape can be converted to path by Convert to Path command.
* Stroke: a visible outline of a shape or path. Not the same as path; a path may or may not have a stroke. If the stroke is present, it can be converted to path by Convert Stroke to Path command.
** Stroke shape (to be implemented): the dependency of the stroke width on distance along the stroke. Currently only constant-width strokes are supported.
** Stroke pattern (to be implemented): the representation of a stroke as a sequence of arbitrary objects positioned along the path.
* Object: an independent editable thing on the canvas. May be a path, a shape, a text object, a group, etc.

==User Interface==

* Document window: the window with a Canvas, Menu, Commands bar, etc. Note that the same instance of the program may have several document windows. Some dialog are referred to as "windows" therefore it is important to distinguish between them and the Document window.
* Menu, bar at the top.
* Commands bar, beneath the Menu, with buttons for commands like New, Open, ... Note that this one will likely be broken into many smaller toolbars, each covering one topic, so the user will be able to switch them on/off and rearrange. So this name is temporary.
* Tool Controls bar, beneath the Commands bar. Has the controls for the currently active tool. Note the capitalization. One should not refer to it as the "Tool bar," nor is it a "Tool" edition of the "controls" variety of "bar". It's proper name should be "Tool Controls" bar.
* Tools, along the left side
** Selector tool
** Node tool
** Zoom tool
** Rectangle tool
** Elipse tool
** Star tool
** Spiral tool
** Pencil tool: to preserve consistency, please do not refer to this tool as freehand tool. Pencil tool (freehand) is better to use.
** Pen tool: to preserve consistency, please do not refer to this tool as Bezier tool. Pen tool (Bezier) is better to use.
** Calligraphy tool
** Text tool
** Gradient tool
** Color dropper tool
* Canvas, main part, with optional border, rulers and scrollbars
* Status bar, along the bottom side of the window

==Depreceated terms==
These are used inside the code. Never use them for documentation.

* knot (this may be a "handle", "control", "node" etc as seen by the user)
* item (use "object")
* desktop (use "canvas" or "document window" depending on context)
* event contexts (they are known to users as "tools")

Inkscape glossary

2006-06-12T20:52:28Z

Cornelius: czech -> english

This is a beginning of an Inkscape glossary. Please respect it and contribute to it if you work on Inkscape UI. If you are doing translations, please create and link below a similar glossary for your language.

==General==
* Node: point of a path that you can manipulate with. If you use Node tool, then it is displayed as gray or blue (if selected) rectangle on a path. Shapes do not have nodes, only handles. Node can have one or two handles too - displayed as circles connected to node. They modify bezier's tangents.
* Handle: 1) one of two points around a node, displayed (for selected nodes) as a circle connected with its node by a line (node handles); 2) the arrows around the selected object in selector (scale handles, rotation handles); 3) points on a shape that can be dragged by node tool to edit the shape, displayed as small white diamonds (shape handles); 4) the things that you drag on canvas to set the placement, direction, and size of a gradient or pattern (gradient handles, pattern handles). (Internally this is called a Knot, but this is a deprecated term in user documentation.)
* Path: object, with nodes, but without handles. For example a line created using the Freehand tool.
* Live Shape: an object that does not display nodes but may have controls. An example is a circle or star. A live shape can be converted to path by Convert to Path command.
* Stroke: a visible outline of a shape or path. Not the same as path; a path may or may not have a stroke. If the stroke is present, it can be converted to path by Convert Stroke to Path command.
** Stroke shape (to be implemented): the dependency of the stroke width on distance along the stroke. Currently only constant-width strokes are supported.
** Stroke pattern (to be implemented): the representation of a stroke as a sequence of arbitrary objects positioned along the path.
* Object: an independent editable thing on the canvas. May be a path, a shape, a text object, a group, etc.

==User Interface==

* Document window: the window with a Canvas, Menu, Commands bar, etc. Note that the same instance of the program may have several document windows. Some dialog are referred to as "windows" therefore it is important to distinguish between them and the Document window.
* Menu, bar at the top.
* Commands bar, beneath the Menu, with buttons for commands like New, Open, ... Note that this one will likely be broken into many smaller toolbars, each covering one topic, so the user will be able to switch them on/off and rearrange. So this name is temporary.
* Tool Controls bar, beneath the Commands bar. Has the controls for the currently active tool. Note the capitalization. One should not refer to it as the "Tool bar," nor is it a "Tool" edition of the "controls" variety of "bar". It's proper name should be "Tool Controls" bar.
* Tools, along the left side
** Selector tool
** Node tool
** Zoom tool
** Rectangle tool
** Elipse tool
** Star tool
** Spiral tool
** Pencil tool: to preserve consistency, please do not refer to this tool as freehand tool. Pencil tool (freehand) is better to use.
** Pen tool: to preserve consistency, please do not refer to this tool as Bezier tool. Pen tool (Bezier) is better to use.
** Calligraphy tool
** Text tool
** Gradient tool
** Color dropper tool
* Plátno, hlavni oblast, s volitelným ohraničením pravítky a posuvníky
* Stavový řádek, podél spodní strany okna

==Depreceated terms==
These are used inside the code. Never use them for documentation.

* knot (this may be a "handle", "control", "node" etc as seen by the user)
* item (use "object")
* desktop (use "canvas" or "document window" depending on context)
* event contexts (they are known to users as "tools")

InkscapeTerminology-cs

2006-06-12T20:21:10Z

Cornelius: Creating the page

This is a beginning of an Inkscape glossary. Please respect it and contribute to it if you work on Inkscape UI. If you are doing translations, please create and link below a similar glossary for your language.

------
Poznámka: tato verze překladu je velmi raná.
== Obecné ==

* '''Uzel''': bod na ''křivce'', který můžete přesunovat. Pokud použijete nástroj pro úpravu uzlů, pak je zobrazen jako šedý (pokud není vybrán) nebo modrý (když je vybrán) čtvereček na křivce. ''Tvary'' uzly nemají; mají ''handle''. Uzel může mít také jeden nebo dva ''handle'' - jsou to malé kružnice spojené s uzlem a upravují se jimi bezierovy tangenty.

* '''Handle''': 1) one of two points around a ''node'', displayed (for selected nodes) as a circle connected with its node by a line (node handles); 2) the arrows around the selected object in selector (scale handles, rotation handles); 3) points on a ''shape'' that can be dragged by node tool to edit the shape, displayed as small white diamonds (shape handles); 4) the things that you drag on canvas to set the placement, direction, and size of a gradient or pattern (gradient handles, pattern handles). (Internally this is called a '''Knot''', but this is a deprecated term in user documentation.)

* '''Křivka''': objekt, který má ''uzly'', ale nemá ''ovládací prvky'' (při použití nástroje pro úpravu uzlů). Mapříklad se jedná o čáru vytvořenou nástrojem pro kreslení od ruky.

* '''Live Shape''': an object that does not display ''nodes'' but may have ''controls''. An example is a circle or star. A live shape can be converted to ''path'' by Convert to Path command.

* '''Stroke''': a visible outline of a ''shape'' or ''path''. Not the same as ''path''; a path may or may not have a stroke. If the stroke is present, it can be converted to path by Convert Stroke to Path command.

** '''Stroke shape''' (''to be implemented''): the dependency of the stroke width on distance along the stroke. Currently only constant-width strokes are supported.

** '''Stroke pattern''' (''to be implemented''): the representation of a stroke as a sequence of arbitrary objects positioned along the path.

* '''Object''': an independent editable thing on the canvas. May be a ''path'', a ''shape'', a text object, a group, etc.

== Uživatelské rozhranní ==

* '''Okno dokumentu''': the window with a Canvas, Menu, Commands bar, etc. Note that the same instance of the program may have several document windows. Some dialog are referred to as "windows" therefore it is important to distinguish between them and the Document window.

** '''Menu''', bar at the top.

** '''Commands bar''', beneath the Menu, with buttons for commands like New, Open, ... Note that this one will likely be broken into many smaller toolbars, each covering one topic, so the user will be able to switch them on/off and rearrange. So this name is temporary.

** '''Tool Controls bar''', beneath the Commands bar. Has the controls for the currently active tool. Note the capitalization. One should not refer to it as the "Tool bar," nor is it a "Tool" edition of the "controls" variety of "bar". It's proper name should be "Tool Controls" bar.

** '''Nástroje''', along the left side
*** '''Nástroj pro výběr''', nebo jednodušeji '''Selektor'''
*** '''Nátroj pro úpravu uzlů'''
*** '''Nástroj pro přiblížení a nebo oddálení obrázku''' (Lupa)
*** '''Nástroj pro tvorbu obdélníků'''
*** '''Nástroj pro tvorbu elips'''
*** '''Nástroj pro tvorbu hvězd'''
*** '''Nástroj pro tvorbu spirál'''
*** '''Nástro Tužka''': pro zachování konzistence, prosím, neodkazujte na tento nástroj jako na ''Nástroj pro kreslení od ruky''. Je lepší použít termín ''Tužka (kreslení od ruky)''.
*** '''Nástroj Pero''': pro zachování konzistence, prosím, neodkazujte na tento nástroj jako na ''Nástroj pro tvorbu bezierovych křivek'' nebo ''Bezier (pen) Tool''. Je lepší použít termín ''Nástroj Pero (Bezier)''.
*** '''Nástroj pro tvorbu kaligafických křivek'''
*** '''Nástroj pro tvorbu textu'''
*** '''Nástroj pro tvorbu barevných přechodů'''
*** '''Nástroj pro získání barvy''' (Kapátko)

** '''Plátno''', hlavni oblast, s volitelným ohraničením '''pravítky''' a '''posuvníky'''

** '''Stavový řádek''', podél spodní strany okna

== ZASTARALÉ A VYŘAZENÉ TERMÍNY ==

Tyto jsou použitelné pouze uvnitř kódu, nikdy je nepoužívejte v dokumentaci.
* knot (this may be a "handle", "control", "node" etc as seen by the user)
* item (use "object")
* desktop (use "canvas" or "document window" depending on context)
* event contexts (they are known to users as "tools")

ReleaseAnnounce044

2006-06-06T09:52:52Z

Cornelius: Link to release notes correction

This is concept of Release Announcement for 0.44 version

== Inkscape Announces 0.44 Release :: http://www.inkscape.org :: Draw Freely ==

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.

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.

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.

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.

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.

Download Linux, Windows, and Mac OS X packages:

http://sourceforge.net/project/showfiles.php?group_id=93438

For many more details, see the complete Release Notes for 0.44:

http://wiki.inkscape.org/wiki/index.php/Release_Notes

Community submitted screenshots:

http://www.inkscape.org/screenshots/

About Inkscape

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.

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.

TestPage

2006-06-03T20:34:46Z

Cornelius: /* Windows installer */

= Introduction =
== Community based, user oriented ==
The translations of the various documents focusing on Inkscape rely on the work of volunteers.
Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes.
It is very important not to forget that Inkscape is an open source, community based and user oriented 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.

== Guidelines/workflow ==

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

== Best practices ==

Best case for a good translation : translate from English to your mother tongue.

Test the behavior of the interface before starting translation

= Translatable content =

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

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.

== User interface ==

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

See section [[#Interface_Translation]] for information on PO files.

== Tutorials ==

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.

See section [[#Tutorial_Translation]] for information on translating tutorials.

== Windows installer ==

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. More information in [[#Windows_installer_translation]] section.

== Templates ==

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. For information about translation of default document's template, please see [[#Default_template_translation]] section.

== Man pages ==
A reminder for the moment. Will fill it later (matiphas)

== Release notes ==
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape

- give a general overview of the possibilities of the software to potential users

- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

== User manual ==
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).

== News displayed on Inkscape web site ==

== Web pages ==
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.

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

= Interface Translation =

== Introduction to PO file format ==

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.

#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
#: gedit/dialogs/program-location-dialog.glade2.h:2
msgid "Set program location..."
msgstr "Ställ in programplats..."

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.

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:

* 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.
* 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.

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.

== Get the PO file for your language ==

Download the .po file for your language from here:

http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/

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:

1. "./autogen.sh"
2. "./configure"
3. enter the "po" directory: "cd po"
4. generate the current PO template: "intltool-update --pot"

To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough),

1. update your local copy of Inkscape in the usual way: "svn update"
2. merge your existing translations into the new POT file (inkscape.pot):

"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"

If you want to update ALL .po files in po/, cd there and run:

make update-po

Now that you have an empty PO template, you can start translating the messages.

== Tools for translators ==

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.

* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)
* kbabel (http://i18n.kde.org/tools/kbabel/)
* gtranslator (http://gtranslator.sourceforge.net/)
* poEdit (http://poedit.sourceforge.net/)
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.

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:

info gettext

== A few important things to remember ==

* 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.
* 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).
* 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.

== Review ==

This is the start of a list of places to get translation reviews done. So far:
http://www.linux.it/tp/

== Verification ==

Before submitting your file in the patch tracker, please make sure it is valid:
* Make sure the file is encoded in UTF-8
* 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
* 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

== Locale Testing ==

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):

LANG=es_MX LANGUAGE=es_MX ls -z
ls: opción inválida -- z
Pruebe `ls --help' para más información.

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:

LANG=es_ES LANGUAGE=es_MX ls -z
ls: invalid option -- z
Try `ls --help' for more information.

== Submit finished work ==

Upload your work via the [[SourceForge]] patch tracker:

http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308

(Check the Upload checkbox and add your file or patch.)

(Don't forget to compress your file before uploading it, as sourcefoge tracker doesn't accept large files.)

Additionally, you may send a message to Inskcape's translators mailing list.

== Programmers ==
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.

= Windows installer translation =

Strings for Windows installer are saved in *.nsh files. Each translation has its own file located in ''packaging\win32\'' directory of subversion checkout. Get this file in similar way of getting *.po file.
=== Translating ===
# Get the file according to your language. If there is not such a file, copy ''english.nsh'' file and rename it to ''yourlanguage.nsh''.
# Translate strings in the file
# Change '''!insertmacro MUI_LANGUAGE "English"''' and each occurence of '''${LANG_ENGLISH}''' to values corresponding with your language. For example '''!insertmacro MUI_LANGUAGE "Czech"''' and '''${LANG_CZECH}'''.
# Change header information in '''yourlanguage.nsh''' file, like "windows code page" and "Authors" to proper values.
=== Testing the translation ===
# This part is optional but recommended. For this part you need [http://nsis.sourceforge.net/Main_Page NSIS installer] and run <pre>make -f Makefile.mingw dist</pre> command after succesfull compilation of Inkscape. This command prepares binary of Inkscape for installator creation.
# Add filename of your file to '''inkscape.nsi''' file, "STRING LOCALIZATION" section, "Language files" subsection.
# Right click on the inkscape.nsi file and choose "Compile NSIS Script". The installer compilation will start.
# When the installer is finished, run it to test translations of strings in Installer and Uninstaller parts.
# If the translation is tested succesfully, submit it to the patch tracker at sourceforge.net and mark as "Translation". If you haven't tested your translation yet, submit it too but enter this information to the patch information. You will be contacted about its correctness.

= Default template translation =

* 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].
* 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.
* 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).
* Upload default.xx.svg to the patch tracker.

To translate default template can be used Inkscape as well as any UTF-8 encoding capable text editor.

= Tutorial Translation =

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:

http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/

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.

* 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.

* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.

* Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.

* 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.

* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.

* 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.

* 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.

==Tools==
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html
* Transolution - http://transolution.python-hosting.com/

===Transforming XML into PO files===
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.

xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).

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.

<pre>
## use this at the very beginning, when there is no translation at all:
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml

## use this when there is a *.de.xml, but you want a de.po:
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml

## xml2po is not happy when this directory doesn't exist:
mkdir .tmp.basic

## use this when the tutorial-basic.xml has been updated and you
## want the new stuff in your de.po:
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml

## use this to create a tutorial-basic.de.xml from your de.po (ScislaC
## will use this file to create the final tutorial SVG file)
## WARNING: Unfortunately, this doesn't put localized screenshot
## file names into the xml file!
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml

</pre>

= Keyboard and mouse translation =

= Wiki and web site =
== Translation of web site ==
# There are two ways of getting files that you need to translate website:
## 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.
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.
# 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.
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.
=== Translating news and status ===
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Status =
See this [[http://wiki.inkscape.org/wiki/index.php/TranslationStatus dedicated page]]

TestPage

2006-06-03T20:32:38Z

Cornelius: /* Testing the translation */

= Introduction =
== Community based, user oriented ==
The translations of the various documents focusing on Inkscape rely on the work of volunteers.
Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes.
It is very important not to forget that Inkscape is an open source, community based and user oriented 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.

== Guidelines/workflow ==

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

== Best practices ==

Best case for a good translation : translate from English to your mother tongue.

Test the behavior of the interface before starting translation

= Translatable content =

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

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.

== User interface ==

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

See section [[#Interface_Translation]] for information on PO files.

== Tutorials ==

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.

See section [[#Tutorial_Translation]] for information on translating tutorials.

== Windows installer ==

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.

== Templates ==

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. For information about translation of default document's template, please see [[#Default_template_translation]] section.

== Man pages ==
A reminder for the moment. Will fill it later (matiphas)

== Release notes ==
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape

- give a general overview of the possibilities of the software to potential users

- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

== User manual ==
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).

== News displayed on Inkscape web site ==

== Web pages ==
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.

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

= Interface Translation =

== Introduction to PO file format ==

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.

#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
#: gedit/dialogs/program-location-dialog.glade2.h:2
msgid "Set program location..."
msgstr "Ställ in programplats..."

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.

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:

* 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.
* 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.

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.

== Get the PO file for your language ==

Download the .po file for your language from here:

http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/

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:

1. "./autogen.sh"
2. "./configure"
3. enter the "po" directory: "cd po"
4. generate the current PO template: "intltool-update --pot"

To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough),

1. update your local copy of Inkscape in the usual way: "svn update"
2. merge your existing translations into the new POT file (inkscape.pot):

"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"

If you want to update ALL .po files in po/, cd there and run:

make update-po

Now that you have an empty PO template, you can start translating the messages.

== Tools for translators ==

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.

* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)
* kbabel (http://i18n.kde.org/tools/kbabel/)
* gtranslator (http://gtranslator.sourceforge.net/)
* poEdit (http://poedit.sourceforge.net/)
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.

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:

info gettext

== A few important things to remember ==

* 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.
* 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).
* 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.

== Review ==

This is the start of a list of places to get translation reviews done. So far:
http://www.linux.it/tp/

== Verification ==

Before submitting your file in the patch tracker, please make sure it is valid:
* Make sure the file is encoded in UTF-8
* 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
* 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

== Locale Testing ==

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):

LANG=es_MX LANGUAGE=es_MX ls -z
ls: opción inválida -- z
Pruebe `ls --help' para más información.

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:

LANG=es_ES LANGUAGE=es_MX ls -z
ls: invalid option -- z
Try `ls --help' for more information.

== Submit finished work ==

Upload your work via the [[SourceForge]] patch tracker:

http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308

(Check the Upload checkbox and add your file or patch.)

(Don't forget to compress your file before uploading it, as sourcefoge tracker doesn't accept large files.)

Additionally, you may send a message to Inskcape's translators mailing list.

== Programmers ==
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.

= Windows installer translation =

Strings for Windows installer are saved in *.nsh files. Each translation has its own file located in ''packaging\win32\'' directory of subversion checkout. Get this file in similar way of getting *.po file.
=== Translating ===
# Get the file according to your language. If there is not such a file, copy ''english.nsh'' file and rename it to ''yourlanguage.nsh''.
# Translate strings in the file
# Change '''!insertmacro MUI_LANGUAGE "English"''' and each occurence of '''${LANG_ENGLISH}''' to values corresponding with your language. For example '''!insertmacro MUI_LANGUAGE "Czech"''' and '''${LANG_CZECH}'''.
# Change header information in '''yourlanguage.nsh''' file, like "windows code page" and "Authors" to proper values.
=== Testing the translation ===
# This part is optional but recommended. For this part you need [http://nsis.sourceforge.net/Main_Page NSIS installer] and run <pre>make -f Makefile.mingw dist</pre> command after succesfull compilation of Inkscape. This command prepares binary of Inkscape for installator creation.
# Add filename of your file to '''inkscape.nsi''' file, "STRING LOCALIZATION" section, "Language files" subsection.
# Right click on the inkscape.nsi file and choose "Compile NSIS Script". The installer compilation will start.
# When the installer is finished, run it to test translations of strings in Installer and Uninstaller parts.
# If the translation is tested succesfully, submit it to the patch tracker at sourceforge.net and mark as "Translation". If you haven't tested your translation yet, submit it too but enter this information to the patch information. You will be contacted about its correctness.

= Default template translation =

* 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].
* 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.
* 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).
* Upload default.xx.svg to the patch tracker.

To translate default template can be used Inkscape as well as any UTF-8 encoding capable text editor.

= Tutorial Translation =

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:

http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/

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.

* 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.

* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.

* Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.

* 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.

* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.

* 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.

* 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.

==Tools==
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html
* Transolution - http://transolution.python-hosting.com/

===Transforming XML into PO files===
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.

xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).

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.

<pre>
## use this at the very beginning, when there is no translation at all:
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml

## use this when there is a *.de.xml, but you want a de.po:
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml

## xml2po is not happy when this directory doesn't exist:
mkdir .tmp.basic

## use this when the tutorial-basic.xml has been updated and you
## want the new stuff in your de.po:
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml

## use this to create a tutorial-basic.de.xml from your de.po (ScislaC
## will use this file to create the final tutorial SVG file)
## WARNING: Unfortunately, this doesn't put localized screenshot
## file names into the xml file!
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml

</pre>

= Keyboard and mouse translation =

= Wiki and web site =
== Translation of web site ==
# There are two ways of getting files that you need to translate website:
## 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.
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.
# 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.
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.
=== Translating news and status ===
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Status =
See this [[http://wiki.inkscape.org/wiki/index.php/TranslationStatus dedicated page]]

TestPage

2006-06-03T20:30:43Z

Cornelius: /* Testing the translation */

= Introduction =
== Community based, user oriented ==
The translations of the various documents focusing on Inkscape rely on the work of volunteers.
Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes.
It is very important not to forget that Inkscape is an open source, community based and user oriented 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.

== Guidelines/workflow ==

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

== Best practices ==

Best case for a good translation : translate from English to your mother tongue.

Test the behavior of the interface before starting translation

= Translatable content =

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

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.

== User interface ==

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

See section [[#Interface_Translation]] for information on PO files.

== Tutorials ==

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.

See section [[#Tutorial_Translation]] for information on translating tutorials.

== Windows installer ==

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.

== Templates ==

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. For information about translation of default document's template, please see [[#Default_template_translation]] section.

== Man pages ==
A reminder for the moment. Will fill it later (matiphas)

== Release notes ==
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape

- give a general overview of the possibilities of the software to potential users

- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

== User manual ==
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).

== News displayed on Inkscape web site ==

== Web pages ==
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.

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

= Interface Translation =

== Introduction to PO file format ==

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.

#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
#: gedit/dialogs/program-location-dialog.glade2.h:2
msgid "Set program location..."
msgstr "Ställ in programplats..."

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.

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:

* 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.
* 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.

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.

== Get the PO file for your language ==

Download the .po file for your language from here:

http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/

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:

1. "./autogen.sh"
2. "./configure"
3. enter the "po" directory: "cd po"
4. generate the current PO template: "intltool-update --pot"

To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough),

1. update your local copy of Inkscape in the usual way: "svn update"
2. merge your existing translations into the new POT file (inkscape.pot):

"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"

If you want to update ALL .po files in po/, cd there and run:

make update-po

Now that you have an empty PO template, you can start translating the messages.

== Tools for translators ==

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.

* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)
* kbabel (http://i18n.kde.org/tools/kbabel/)
* gtranslator (http://gtranslator.sourceforge.net/)
* poEdit (http://poedit.sourceforge.net/)
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.

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:

info gettext

== A few important things to remember ==

* 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.
* 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).
* 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.

== Review ==

This is the start of a list of places to get translation reviews done. So far:
http://www.linux.it/tp/

== Verification ==

Before submitting your file in the patch tracker, please make sure it is valid:
* Make sure the file is encoded in UTF-8
* 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
* 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

== Locale Testing ==

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):

LANG=es_MX LANGUAGE=es_MX ls -z
ls: opción inválida -- z
Pruebe `ls --help' para más información.

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:

LANG=es_ES LANGUAGE=es_MX ls -z
ls: invalid option -- z
Try `ls --help' for more information.

== Submit finished work ==

Upload your work via the [[SourceForge]] patch tracker:

http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308

(Check the Upload checkbox and add your file or patch.)

(Don't forget to compress your file before uploading it, as sourcefoge tracker doesn't accept large files.)

Additionally, you may send a message to Inskcape's translators mailing list.

== Programmers ==
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.

= Windows installer translation =

Strings for Windows installer are saved in *.nsh files. Each translation has its own file located in ''packaging\win32\'' directory of subversion checkout. Get this file in similar way of getting *.po file.
=== Translating ===
# Get the file according to your language. If there is not such a file, copy ''english.nsh'' file and rename it to ''yourlanguage.nsh''.
# Translate strings in the file
# Change '''!insertmacro MUI_LANGUAGE "English"''' and each occurence of '''${LANG_ENGLISH}''' to values corresponding with your language. For example '''!insertmacro MUI_LANGUAGE "Czech"''' and '''${LANG_CZECH}'''.
# Change header information in '''yourlanguage.nsh''' file, like "windows code page" and "Authors" to proper values.
=== Testing the translation ===
# This part is optional but recommended. For this part you need [http://nsis.sourceforge.net/Main_Page NSIS installer] and run ''make -f Makefile.mingw dist'' command after succesfull compilation of Inkscape.
# Add filename of your file to '''inkscape.nsi''' file, "STRING LOCALIZATION" section, "Language files" subsection.
# Right click on the inkscape.nsi file and choose "Compile NSIS Script". The installer compilation will start.
# When the installer is finished, run it to test translations of strings in Installer and Uninstaller parts.
# If the translation is tested succesfully, submit it to the patch tracker at sourceforge.net and mark as "Translation". If you haven't tested your translation yet, submit it too but enter this information to the patch information. You will be contacted about its correctness.

= Default template translation =

* 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].
* 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.
* 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).
* Upload default.xx.svg to the patch tracker.

To translate default template can be used Inkscape as well as any UTF-8 encoding capable text editor.

= Tutorial Translation =

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:

http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/

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.

* 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.

* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.

* Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.

* 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.

* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.

* 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.

* 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.

==Tools==
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html
* Transolution - http://transolution.python-hosting.com/

===Transforming XML into PO files===
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.

xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).

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.

<pre>
## use this at the very beginning, when there is no translation at all:
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml

## use this when there is a *.de.xml, but you want a de.po:
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml

## xml2po is not happy when this directory doesn't exist:
mkdir .tmp.basic

## use this when the tutorial-basic.xml has been updated and you
## want the new stuff in your de.po:
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml

## use this to create a tutorial-basic.de.xml from your de.po (ScislaC
## will use this file to create the final tutorial SVG file)
## WARNING: Unfortunately, this doesn't put localized screenshot
## file names into the xml file!
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml

</pre>

= Keyboard and mouse translation =

= Wiki and web site =
== Translation of web site ==
# There are two ways of getting files that you need to translate website:
## 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.
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.
# 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.
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.
=== Translating news and status ===
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Status =
See this [[http://wiki.inkscape.org/wiki/index.php/TranslationStatus dedicated page]]

TestPage

2006-06-03T20:25:59Z

Cornelius: /* Windows installer translation */

= Introduction =
== Community based, user oriented ==
The translations of the various documents focusing on Inkscape rely on the work of volunteers.
Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes.
It is very important not to forget that Inkscape is an open source, community based and user oriented 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.

== Guidelines/workflow ==

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

== Best practices ==

Best case for a good translation : translate from English to your mother tongue.

Test the behavior of the interface before starting translation

= Translatable content =

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

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.

== User interface ==

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

See section [[#Interface_Translation]] for information on PO files.

== Tutorials ==

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.

See section [[#Tutorial_Translation]] for information on translating tutorials.

== Windows installer ==

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.

== Templates ==

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. For information about translation of default document's template, please see [[#Default_template_translation]] section.

== Man pages ==
A reminder for the moment. Will fill it later (matiphas)

== Release notes ==
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape

- give a general overview of the possibilities of the software to potential users

- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

== User manual ==
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).

== News displayed on Inkscape web site ==

== Web pages ==
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.

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

= Interface Translation =

== Introduction to PO file format ==

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.

#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
#: gedit/dialogs/program-location-dialog.glade2.h:2
msgid "Set program location..."
msgstr "Ställ in programplats..."

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.

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:

* 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.
* 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.

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.

== Get the PO file for your language ==

Download the .po file for your language from here:

http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/

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:

1. "./autogen.sh"
2. "./configure"
3. enter the "po" directory: "cd po"
4. generate the current PO template: "intltool-update --pot"

To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough),

1. update your local copy of Inkscape in the usual way: "svn update"
2. merge your existing translations into the new POT file (inkscape.pot):

"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"

If you want to update ALL .po files in po/, cd there and run:

make update-po

Now that you have an empty PO template, you can start translating the messages.

== Tools for translators ==

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.

* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)
* kbabel (http://i18n.kde.org/tools/kbabel/)
* gtranslator (http://gtranslator.sourceforge.net/)
* poEdit (http://poedit.sourceforge.net/)
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.

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:

info gettext

== A few important things to remember ==

* 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.
* 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).
* 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.

== Review ==

This is the start of a list of places to get translation reviews done. So far:
http://www.linux.it/tp/

== Verification ==

Before submitting your file in the patch tracker, please make sure it is valid:
* Make sure the file is encoded in UTF-8
* 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
* 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

== Locale Testing ==

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):

LANG=es_MX LANGUAGE=es_MX ls -z
ls: opción inválida -- z
Pruebe `ls --help' para más información.

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:

LANG=es_ES LANGUAGE=es_MX ls -z
ls: invalid option -- z
Try `ls --help' for more information.

== Submit finished work ==

Upload your work via the [[SourceForge]] patch tracker:

http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308

(Check the Upload checkbox and add your file or patch.)

(Don't forget to compress your file before uploading it, as sourcefoge tracker doesn't accept large files.)

Additionally, you may send a message to Inskcape's translators mailing list.

== Programmers ==
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.

= Windows installer translation =

Strings for Windows installer are saved in *.nsh files. Each translation has its own file located in ''packaging\win32\'' directory of subversion checkout. Get this file in similar way of getting *.po file.
=== Translating ===
# Get the file according to your language. If there is not such a file, copy ''english.nsh'' file and rename it to ''yourlanguage.nsh''.
# Translate strings in the file
# Change '''!insertmacro MUI_LANGUAGE "English"''' and each occurence of '''${LANG_ENGLISH}''' to values corresponding with your language. For example '''!insertmacro MUI_LANGUAGE "Czech"''' and '''${LANG_CZECH}'''.
# Change header information in '''yourlanguage.nsh''' file, like "windows code page" and "Authors" to proper values.
=== Testing the translation ===
# For this part is optional but recommended. For this part you need [http://nsis.sourceforge.net/Main_Page NSIS installer] and run ''make -f Makefile.mingw dist'' command after succesfull compilation of Inkscape.
# Add filename of your file to '''inkscape.nsi''' file, "STRING LOCALIZATION" section, "Language files" subsection.
# Right click on the inkscape.nsi file and choose "Compile NSIS Script". The installer compilation will start.
# When the installer is finished, run it to test translations of strings in Installer and Uninstaller parts.
# If the translation is tested succesfully, submit it to the patch tracker at sourceforge.net and mark as "Translation". If you haven't tested your translation yet, submit it too but enter this information to the patch information. You will be contacted about its correctness.

= Default template translation =

* 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].
* 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.
* 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).
* Upload default.xx.svg to the patch tracker.

To translate default template can be used Inkscape as well as any UTF-8 encoding capable text editor.

= Tutorial Translation =

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:

http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/

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.

* 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.

* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.

* Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.

* 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.

* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.

* 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.

* 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.

==Tools==
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html
* Transolution - http://transolution.python-hosting.com/

===Transforming XML into PO files===
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.

xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).

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.

<pre>
## use this at the very beginning, when there is no translation at all:
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml

## use this when there is a *.de.xml, but you want a de.po:
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml

## xml2po is not happy when this directory doesn't exist:
mkdir .tmp.basic

## use this when the tutorial-basic.xml has been updated and you
## want the new stuff in your de.po:
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml

## use this to create a tutorial-basic.de.xml from your de.po (ScislaC
## will use this file to create the final tutorial SVG file)
## WARNING: Unfortunately, this doesn't put localized screenshot
## file names into the xml file!
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml

</pre>

= Keyboard and mouse translation =

= Wiki and web site =
== Translation of web site ==
# There are two ways of getting files that you need to translate website:
## 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.
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.
# 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.
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.
=== Translating news and status ===
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Status =
See this [[http://wiki.inkscape.org/wiki/index.php/TranslationStatus dedicated page]]

TestPage

2006-06-03T19:58:02Z

Cornelius: Moving Template translation section to translations from "translatable content" + adding how to translate windows installer

= Introduction =
== Community based, user oriented ==
The translations of the various documents focusing on Inkscape rely on the work of volunteers.
Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes.
It is very important not to forget that Inkscape is an open source, community based and user oriented 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.

== Guidelines/workflow ==

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

== Best practices ==

Best case for a good translation : translate from English to your mother tongue.

Test the behavior of the interface before starting translation

= Translatable content =

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

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.

== User interface ==

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

See section [[#Interface_Translation]] for information on PO files.

== Tutorials ==

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.

See section [[#Tutorial_Translation]] for information on translating tutorials.

== Windows installer ==

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.

== Templates ==

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. For information about translation of default document's template, please see [[#Default_template_translation]] section.

== Man pages ==
A reminder for the moment. Will fill it later (matiphas)

== Release notes ==
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape

- give a general overview of the possibilities of the software to potential users

- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

== User manual ==
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).

== News displayed on Inkscape web site ==

== Web pages ==
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.

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

= Interface Translation =

== Introduction to PO file format ==

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.

#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
#: gedit/dialogs/program-location-dialog.glade2.h:2
msgid "Set program location..."
msgstr "Ställ in programplats..."

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.

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:

* 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.
* 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.

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.

== Get the PO file for your language ==

Download the .po file for your language from here:

http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/

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:

1. "./autogen.sh"
2. "./configure"
3. enter the "po" directory: "cd po"
4. generate the current PO template: "intltool-update --pot"

To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough),

1. update your local copy of Inkscape in the usual way: "svn update"
2. merge your existing translations into the new POT file (inkscape.pot):

"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"

If you want to update ALL .po files in po/, cd there and run:

make update-po

Now that you have an empty PO template, you can start translating the messages.

== Tools for translators ==

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.

* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)
* kbabel (http://i18n.kde.org/tools/kbabel/)
* gtranslator (http://gtranslator.sourceforge.net/)
* poEdit (http://poedit.sourceforge.net/)
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.

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:

info gettext

== A few important things to remember ==

* 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.
* 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).
* 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.

== Review ==

This is the start of a list of places to get translation reviews done. So far:
http://www.linux.it/tp/

== Verification ==

Before submitting your file in the patch tracker, please make sure it is valid:
* Make sure the file is encoded in UTF-8
* 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
* 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

== Locale Testing ==

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):

LANG=es_MX LANGUAGE=es_MX ls -z
ls: opción inválida -- z
Pruebe `ls --help' para más información.

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:

LANG=es_ES LANGUAGE=es_MX ls -z
ls: invalid option -- z
Try `ls --help' for more information.

== Submit finished work ==

Upload your work via the [[SourceForge]] patch tracker:

http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308

(Check the Upload checkbox and add your file or patch.)

(Don't forget to compress your file before uploading it, as sourcefoge tracker doesn't accept large files.)

Additionally, you may send a message to Inskcape's translators mailing list.

== Programmers ==
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.

= Windows installer translation =

Strings for Windows installer are saved in *.nsh files. Each translation has its own file located in ''/packaging/win32'' directory of subversion checkout. Get this file in similar way of getting *.po file.
# Get the file according to your language. If there is not such a file, copy english.nsh file and rename it to ''yourlanguage.nsh''.
# Translate

= Default template translation =

* 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].
* 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.
* 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).
* Upload default.xx.svg to the patch tracker.

To translate default template can be used Inkscape as well as any UTF-8 encoding capable text editor.

= Tutorial Translation =

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:

http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/

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.

* 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.

* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.

* Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.

* 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.

* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.

* 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.

* 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.

==Tools==
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html
* Transolution - http://transolution.python-hosting.com/

===Transforming XML into PO files===
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.

xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).

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.

<pre>
## use this at the very beginning, when there is no translation at all:
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml

## use this when there is a *.de.xml, but you want a de.po:
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml

## xml2po is not happy when this directory doesn't exist:
mkdir .tmp.basic

## use this when the tutorial-basic.xml has been updated and you
## want the new stuff in your de.po:
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml

## use this to create a tutorial-basic.de.xml from your de.po (ScislaC
## will use this file to create the final tutorial SVG file)
## WARNING: Unfortunately, this doesn't put localized screenshot
## file names into the xml file!
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml

</pre>

= Keyboard and mouse translation =

= Wiki and web site =
== Translation of web site ==
# There are two ways of getting files that you need to translate website:
## 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.
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.
# 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.
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.
=== Translating news and status ===
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Status =
See this [[http://wiki.inkscape.org/wiki/index.php/TranslationStatus dedicated page]]

ReleaseAnnounce044

2006-06-03T17:46:52Z

Cornelius:

This is concept of Release Announcement for 0.44 version

List of interresting new features and improvements:
* Outline mode and speed improvements
* Docked swatches
* Layers dialog + layers improvements
* Improvements in calligraphic pen
* Improvements in node editing (Sculpting nodes)
* Improved SVG compliance - added <switch> tag
* Text bar
* Significant improvement of translations

TranslationStatus

2006-06-03T17:16:09Z

Cornelius: /* Windows installer */ added french and spanish.nsh

== Interface translation (po files) ==

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)

Total number of PO files: 38
Total number of strings to translate: 2142

'''Amharic''': am.po

translated: 77 ( '''3%''')

fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)

Date of last update: 2003-02-01

'''Azerbaijani/Turkic''': az.po

translated: 63 ( '''2%''')

fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)

Date of last update: 2001-12-04

'''Belarusian''': be.po

translated: 158 ( '''7%''')

fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)

Date of last update: 2003-07-20

'''Catalan''': ca.po

translated: 2039 ( '''95%''')

fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)

Date of last update: 2006-05-08

'''Czech''': cs.po

translated: 2096 ( '''97%''')

fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)

Date of last update: 2006-05-22

'''Danish''': da.po

translated: 100 ( '''4%''')

fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)

Date of last update: 2002-01-15

'''German''': de.po

translated: 2116 ( '''98%''')

fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)

Date of last update: 2006-05-23

'''Greek''': el.po

translated: 44 ( '''2%''')

fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)

Date of last update: 2001-12-28

'''Spanish''': es.po

translated: 2125 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)

Date of last update: 2006-05-25

'''Spanish/Mexico''': es_MX.po

translated: 337 ( '''15%''')

fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)

Date of last update: 2004-04-05

'''Estonian''': et.po

translated: 9 ( '''0%''')

fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)

Date of last update: 2000-04-08

'''Basque''': eu.po

translated: 1548 ( '''72%''')

fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)

Date of last update: 2006-03-16

'''French''': fr.po

translated: 2126 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)

Date of last update: 2006-05-27

'''Irish''': ga.po

translated: 14 ( '''0%''')

fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)

Date of last update: 2000-08-24

'''Galician''': gl.po

translated: 82 ( '''3%''')

fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)

Date of last update: 2001-11-10

'''Hungarian''': hu.po

translated: 1564 ( '''73%''')

fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)

Date of last update: 2006-05-29

'''Italian''': it.po

translated: 2008 ( '''93%''')

fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)

Date of last update: 2006-05-15

'''Japanese''': ja.po

translated: 1294 ( '''60%''')

fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)

Date of last update: 2005-11-16

'''Korean''': ko.po

translated: 180 ( '''8%''')

fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)

Date of last update: 2006-04-10

'''Lithuanian''': lt.po

translated: 1774 ( '''82%''')

fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)

Date of last update: 2006-05-02

'''mk.po'''

translated: 0 ( '''0%''')

fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)

Date of last update: 2003-06-15

'''Norwegian/bokmål dialect''': nb.po

translated: 144 ( '''6%''')

fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)

Date of last update: 2003-01-25

'''Dutch: nl.po'''

translated: 1484 ( '''69%''')

fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)

Date of last update: 2005-11-07

'''Norwegian/Nynorsk''': nn.po

translated: 1376 ( '''64%''')

fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)

Date of last update: 2005-07-14

'''Punjabi''': pa.po

translated: 912 ( '''42%''')

fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)

Date of last update: 2005-09-11

'''Polish''': pl.po

translated: 1503 ( '''70%''')

fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)

Date of last update: 2005-10-29

'''Portuguese''': pt.po

translated: 183 ( '''8%''')

fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)

Date of last update: 2003-07-28

'''Portuguese/Brazillian''': pt_BR.po

translated: 1546 ( '''72%''')

fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)

Date of last update: 2006-04-27

'''Russian''': ru.po

translated: 1542 ( '''71%''')

fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)

Date of last update: 2005-11-08

'''Slovak''': sk.po

translated: 845 ( '''39%''')

fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)

Date of last update: 2005-02-13

'''Slovenian''': sl.po

translated: 2055 ( '''95%''')

fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)

Date of last update: 2006-05-12

'''Serbian''': sr.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Serbian/Latine''': sr@Latn.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Swedish''': sv.po

translated: 410 ( '''19%''')

fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)

Date of last update: 2005-10-08

'''Turkish''': tr.po

translated: 907 ( '''42%''')

fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)

Date of last update: 2005-11-26

'''Ukrainian''': uk.po

translated: 1518 ( '''70%''')

fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)

Date of last update: 2005-10-21

'''Chinese/Simplified''': zh_CN.po

translated: 2134 ( '''99%''')

fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)

Date of last update: 2006-05-28

'''Chinese/Traditional''': zh_TW.po

translated: 1550 ( '''72 %''')

fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)

Date of last update: 2006-03-24

== Tutorials ==

* Basic: ca, de, en, es, fr, ja, nn, ru, sl
* Shapes: ca, en, es, fr, ja, sl
* Advanced: ca, en, es, fr, ja, sl
* Tracing: ca, de, en, es, fr, sl
* Calligraphy: ca, en, es, fr, sl
* Elements of design: en, es, fr, sl
* Tips and tricks: de, en, es, fr, sl

== Keys (shortcuts) ==
Already available in svn :
* en
* fr
* sl

== Windows installer ==

Already available in svn :
* czech.nsh
* english.nsh
* french.nsh
* german.nsh
* italian.nsh
* spanish.nsh

== Wiki translation ==

== Website ==

== News ==

ReleaseAnnounce044

2006-06-03T09:26:19Z

Cornelius: initial edit - ideas for interresting features of 0.44

This is concept of Release Announcement for 0.44 version

List of interresting new features and improvements:
*Outline mode (+Speeeeeeeeeeeeeeeeed improvements)
*Docked swatches
*Layers dialog + layers improvements
*Improvements in calligraphic pen
*Improvements in node editing (Sculpting nodes)
*Improved SVG compliance - added <switch> tag
*Text bar

TestPage

2006-06-01T07:13:28Z

Cornelius: /* Templates */

= Introduction =
== Community based, user oriented ==
The translations of the various documents focusing on Inkscape rely on the work of volunteers.
Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes.
It is very important not to forget that Inkscape is an open source, community based and user oriented 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.

== Guidelines/workflow ==

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

== Best practices ==

Best case for a good translation : translate from English to your mother tongue.

Test the behavior of the interface before starting translation

= Translatable content =

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

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.

== User interface ==

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

See section [[#Interface_Translation]] for information on PO files.

== Tutorials ==

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.

See section [[#Tutorial_Translation]] for information on translating tutorials.

== Windows installer ==

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.

== Templates ==
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.
* 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).
* 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)
* Upload default.xx.svg to the patch tracker.

== Release notes ==
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape

- give a general overview of the possibilities of the software to potential users

- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

== News displayed on Inkscape web site ==

== Web pages ==
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.

== Others ==
Templates (translation and localization)
Text files found in the inkscape directory
...

= Interface Translation =

== Introduction to PO file format ==

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.

#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
#: gedit/dialogs/program-location-dialog.glade2.h:2
msgid "Set program location..."
msgstr "Ställ in programplats..."

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.

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:

* 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.
* 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.

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.

== Get the PO file for your language ==

Download the .po file for your language from here:

http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/

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].

Create your own language file by copying the inkscape.pot file that gets generated when you run make in the codebase.

1. "./autogen.sh"
2. "./configure"
3. enter the "po" directory: "cd po"
4. generate the current PO template: "intltool-update --pot"

To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough),

1. update your local copy of Inkscape in the usual way: "svn update"
2. merge your existing translations into the new POT file (inkscape.pot):

"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"

Then you just need to complete the translations in the PO file that was
created in step 6.

If you want to update ALL .po files in po/, cd there and run:

make update-po

== Tools for translators ==

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.

* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)
* kbabel (http://i18n.kde.org/tools/kbabel/)
* gtranslator (http://gtranslator.sourceforge.net/)
* poEdit (http://poedit.sourceforge.net/)
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.

And last but not least, gettext utils.

== Submit finished work ==

Upload your work via the [[SourceForge]] patch tracker:

http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308

(Check the Upload checkbox and add your file or patch.)

Additionally, you may send a message to Inskcape's translators mailing list.

== A few important things to remember ==

* 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.
* 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).
* 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.

== Review ==
This is the start of a list of places to get translation reviews done. So far:
http://www.linux.it/tp/

== Verification ==
Before submitting your file in the patch tracker, please make sure it is valid:
* Make sure the file is encoded in UTF-8
* 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
* 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

== Locale Testing ==
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):

LANG=es_MX LANGUAGE=es_MX ls -z
ls: opción inválida -- z
Pruebe `ls --help' para más información.

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:

LANG=es_ES LANGUAGE=es_MX ls -z
ls: invalid option -- z
Try `ls --help' for more information.

== Programmers ==
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.

= Tutorial Translation =

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:

http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/

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.

* 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.

* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.

* Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.

* 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.

* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.

* 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.

* 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.

==Tools==
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html
* Transolution - http://transolution.python-hosting.com/

===Transforming XML into PO files===
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.

xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).

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.

<pre>
## use this at the very beginning, when there is no translation at all:
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml

## use this when there is a *.de.xml, but you want a de.po:
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml

## xml2po is not happy when this directory doesn't exist:
mkdir .tmp.basic

## use this when the tutorial-basic.xml has been updated and you
## want the new stuff in your de.po:
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml

## use this to create a tutorial-basic.de.xml from your de.po (ScislaC
## will use this file to create the final tutorial SVG file)
## WARNING: Unfortunately, this doesn't put localized screenshot
## file names into the xml file!
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml

</pre>

= Keyboard and mouse translation =

= Wiki and web site =
== Translation of web site ==
# There are two ways of getting files that you need to translate website:
## 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.
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.
# 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.
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.
=== Translating news and status ===
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Status =

== Interface translation (po files) ==

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)

Total number of PO files: 38
Total number of strings to translate: 2142

'''Amharic''': am.po

translated: 77 ( '''3%''')

fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)

Date of last update: 2003-02-01

'''Azerbaijani/Turkic''': az.po

translated: 63 ( '''2%''')

fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)

Date of last update: 2001-12-04

'''Belarusian''': be.po

translated: 158 ( '''7%''')

fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)

Date of last update: 2003-07-20

'''Catalan''': ca.po

translated: 2039 ( '''95%''')

fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)

Date of last update: 2006-05-08

'''Czech''': cs.po

translated: 2096 ( '''97%''')

fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)

Date of last update: 2006-05-22

'''Danish''': da.po

translated: 100 ( '''4%''')

fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)

Date of last update: 2002-01-15

'''German''': de.po

translated: 2116 ( '''98%''')

fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)

Date of last update: 2006-05-23

'''Greek''': el.po

translated: 44 ( '''2%''')

fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)

Date of last update: 2001-12-28

'''Spanish''': es.po

translated: 2125 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)

Date of last update: 2006-05-25

'''Spanish/Mexico''': es_MX.po

translated: 337 ( '''15%''')

fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)

Date of last update: 2004-04-05

'''Estonian''': et.po

translated: 9 ( '''0%''')

fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)

Date of last update: 2000-04-08

'''Basque''': eu.po

translated: 1548 ( '''72%''')

fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)

Date of last update: 2006-03-16

'''French''': fr.po

translated: 2126 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)

Date of last update: 2006-05-27

'''Irish''': ga.po

translated: 14 ( '''0%''')

fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)

Date of last update: 2000-08-24

'''Galician''': gl.po

translated: 82 ( '''3%''')

fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)

Date of last update: 2001-11-10

'''Hungarian''': hu.po

translated: 1564 ( '''73%''')

fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)

Date of last update: 2006-05-29

'''Italian''': it.po

translated: 2008 ( '''93%''')

fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)

Date of last update: 2006-05-15

'''Japanese''': ja.po

translated: 1294 ( '''60%''')

fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)

Date of last update: 2005-11-16

'''Korean''': ko.po

translated: 180 ( '''8%''')

fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)

Date of last update: 2006-04-10

'''Lithuanian''': lt.po

translated: 1774 ( '''82%''')

fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)

Date of last update: 2006-05-02

'''mk.po'''

translated: 0 ( '''0%''')

fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)

Date of last update: 2003-06-15

'''Norwegian/bokmål dialect''': nb.po

translated: 144 ( '''6%''')

fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)

Date of last update: 2003-01-25

'''Dutch: nl.po'''

translated: 1484 ( '''69%''')

fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)

Date of last update: 2005-11-07

'''Norwegian/Nynorsk''': nn.po

translated: 1376 ( '''64%''')

fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)

Date of last update: 2005-07-14

'''Punjabi''': pa.po

translated: 912 ( '''42%''')

fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)

Date of last update: 2005-09-11

'''Polish''': pl.po

translated: 1503 ( '''70%''')

fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)

Date of last update: 2005-10-29

'''Portuguese''': pt.po

translated: 183 ( '''8%''')

fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)

Date of last update: 2003-07-28

'''Portuguese/Brazillian''': pt_BR.po

translated: 1546 ( '''72%''')

fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)

Date of last update: 2006-04-27

'''Russian''': ru.po

translated: 1542 ( '''71%''')

fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)

Date of last update: 2005-11-08

'''Slovak''': sk.po

translated: 845 ( '''39%''')

fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)

Date of last update: 2005-02-13

'''Slovenian''': sl.po

translated: 2055 ( '''95%''')

fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)

Date of last update: 2006-05-12

'''Serbian''': sr.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Serbian/Latine''': sr@Latn.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Swedish''': sv.po

translated: 410 ( '''19%''')

fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)

Date of last update: 2005-10-08

'''Turkish''': tr.po

translated: 907 ( '''42%''')

fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)

Date of last update: 2005-11-26

'''Ukrainian''': uk.po

translated: 1518 ( '''70%''')

fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)

Date of last update: 2005-10-21

'''Chinese/Simplified''': zh_CN.po

translated: 2134 ( '''99%''')

fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)

Date of last update: 2006-05-28

'''Chinese/Traditional''': zh_TW.po

translated: 1550 ( '''72 %''')

fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)

Date of last update: 2006-03-24

== Tutorials ==

* Basic: ca, de, en, es, fr, ja, nn, ru, sl
* Shapes: ca, en, es, fr, ja, sl
* Advanced: ca, en, es, fr, ja, sl
* Tracing: ca, de, en, es, fr, sl
* Calligraphy: ca, en, es, fr, sl
* Elements of design: en, es, fr, sl
* Tips and tricks: de, en, es, fr, sl

== Keys (shortcuts) ==
Already available in svn :
* en
* fr
* sl

== Windows installer ==

Already available in svn :
* czech.nsh
* english.nsh
* german.nsh
* italian.nsh

== Wiki translation ==

== Website ==

== News ==

TestPage

2006-05-31T19:24:29Z

Cornelius: /* Templates */

= Introduction =
== Community based, user oriented ==
The translations of the various documents focusing on Inkscape rely on the work of volunteers.
Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes.
It is very important not to forget that Inkscape is an open source, community based and user oriented 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.

== Guidelines/workflow ==

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

== Best practices ==

Best case for a good translation : translate from English to your mother tongue.

Test the behavior of the interface before starting translation

= Translatable content =

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

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.

== User interface ==

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

See section [[#Interface_Translation]] for information on PO files.

== Tutorials ==

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.

See section [[#Tutorial_Translation]] for information on translating tutorials.

== Windows installer ==

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.

== Templates ==
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.
* 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/templates/ directory on Linux, or C:\Program Files\Inkscape\share\templates\ directory on MS Windows(tm).
* 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)
* Upload default.xx.svg to the patch tracker.

== Release notes ==
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape

- give a general overview of the possibilities of the software to potential users

- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

== News displayed on Inkscape web site ==

== Web pages ==
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.

== Others ==
Templates (translation and localization)
Text files found in the inkscape directory
...

= Interface Translation =

== Introduction to PO file format ==

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.

#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
#: gedit/dialogs/program-location-dialog.glade2.h:2
msgid "Set program location..."
msgstr "Ställ in programplats..."

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.

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:

* 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.
* 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.

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.

== Get the PO file for your language ==

Download the .po file for your language from here:

http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/

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].

Create your own language file by copying the inkscape.pot file that gets generated when you run make in the codebase.

1. "./autogen.sh"
2. "./configure"
3. enter the "po" directory: "cd po"
4. generate the current PO template: "intltool-update --pot"

To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough),

1. update your local copy of Inkscape in the usual way: "svn update"
2. merge your existing translations into the new POT file (inkscape.pot):

"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"

Then you just need to complete the translations in the PO file that was
created in step 6.

If you want to update ALL .po files in po/, cd there and run:

make update-po

== Tools for translators ==

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.

* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)
* kbabel (http://i18n.kde.org/tools/kbabel/)
* gtranslator (http://gtranslator.sourceforge.net/)
* poEdit (http://poedit.sourceforge.net/)
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.

And last but not least, gettext utils.

== Submit finished work ==

Upload your work via the [[SourceForge]] patch tracker:

http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308

(Check the Upload checkbox and add your file or patch.)

Additionally, you may send a message to Inskcape's translators mailing list.

== A few important things to remember ==

* 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.
* 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).
* 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.

== Review ==
This is the start of a list of places to get translation reviews done. So far:
http://www.linux.it/tp/

== Verification ==
Before submitting your file in the patch tracker, please make sure it is valid:
* Make sure the file is encoded in UTF-8
* 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
* 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

== Locale Testing ==
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):

LANG=es_MX LANGUAGE=es_MX ls -z
ls: opción inválida -- z
Pruebe `ls --help' para más información.

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:

LANG=es_ES LANGUAGE=es_MX ls -z
ls: invalid option -- z
Try `ls --help' for more information.

== Programmers ==
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.

= Tutorial Translation =

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:

http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/

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.

* 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.

* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.

* Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.

* 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.

* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.

* 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.

* 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.

==Tools==
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html
* Transolution - http://transolution.python-hosting.com/

===Transforming XML into PO files===
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.

xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).

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.

<pre>
## use this at the very beginning, when there is no translation at all:
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml

## use this when there is a *.de.xml, but you want a de.po:
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml

## xml2po is not happy when this directory doesn't exist:
mkdir .tmp.basic

## use this when the tutorial-basic.xml has been updated and you
## want the new stuff in your de.po:
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml

## use this to create a tutorial-basic.de.xml from your de.po (ScislaC
## will use this file to create the final tutorial SVG file)
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml

</pre>

= Keyboard and mouse translation =

= Wiki and web site =
== Translation of web site ==
# There are two ways of getting files that you need to translate website:
## 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.
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.
# 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.
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.
=== Translating news and status ===
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Status =

== Interface translation (po files) ==

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)

Total number of PO files: 38
Total number of strings to translate: 2142

'''Amharic''': am.po

translated: 77 ( '''3%''')

fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)

Date of last update: 2003-02-01

'''Azerbaijani/Turkic''': az.po

translated: 63 ( '''2%''')

fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)

Date of last update: 2001-12-04

'''Belarusian''': be.po

translated: 158 ( '''7%''')

fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)

Date of last update: 2003-07-20

'''Catalan''': ca.po

translated: 2039 ( '''95%''')

fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)

Date of last update: 2006-05-08

'''Czech''': cs.po

translated: 2096 ( '''97%''')

fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)

Date of last update: 2006-05-22

'''Danish''': da.po

translated: 100 ( '''4%''')

fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)

Date of last update: 2002-01-15

'''German''': de.po

translated: 2116 ( '''98%''')

fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)

Date of last update: 2006-05-23

'''Greek''': el.po

translated: 44 ( '''2%''')

fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)

Date of last update: 2001-12-28

'''Spanish''': es.po

translated: 2125 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)

Date of last update: 2006-05-25

'''Spanish/Mexico''': es_MX.po

translated: 337 ( '''15%''')

fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)

Date of last update: 2004-04-05

'''Estonian''': et.po

translated: 9 ( '''0%''')

fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)

Date of last update: 2000-04-08

'''Basque''': eu.po

translated: 1548 ( '''72%''')

fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)

Date of last update: 2006-03-16

'''French''': fr.po

translated: 2126 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)

Date of last update: 2006-05-27

'''Irish''': ga.po

translated: 14 ( '''0%''')

fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)

Date of last update: 2000-08-24

'''Galician''': gl.po

translated: 82 ( '''3%''')

fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)

Date of last update: 2001-11-10

'''Hungarian''': hu.po

translated: 1564 ( '''73%''')

fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)

Date of last update: 2006-05-29

'''Italian''': it.po

translated: 2008 ( '''93%''')

fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)

Date of last update: 2006-05-15

'''Japanese''': ja.po

translated: 1294 ( '''60%''')

fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)

Date of last update: 2005-11-16

'''Korean''': ko.po

translated: 180 ( '''8%''')

fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)

Date of last update: 2006-04-10

'''Lithuanian''': lt.po

translated: 1774 ( '''82%''')

fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)

Date of last update: 2006-05-02

'''mk.po'''

translated: 0 ( '''0%''')

fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)

Date of last update: 2003-06-15

'''Norwegian/bokmål dialect''': nb.po

translated: 144 ( '''6%''')

fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)

Date of last update: 2003-01-25

'''Dutch: nl.po'''

translated: 1484 ( '''69%''')

fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)

Date of last update: 2005-11-07

'''Norwegian/Nynorsk''': nn.po

translated: 1376 ( '''64%''')

fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)

Date of last update: 2005-07-14

'''Punjabi''': pa.po

translated: 912 ( '''42%''')

fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)

Date of last update: 2005-09-11

'''Polish''': pl.po

translated: 1503 ( '''70%''')

fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)

Date of last update: 2005-10-29

'''Portuguese''': pt.po

translated: 183 ( '''8%''')

fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)

Date of last update: 2003-07-28

'''Portuguese/Brazillian''': pt_BR.po

translated: 1546 ( '''72%''')

fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)

Date of last update: 2006-04-27

'''Russian''': ru.po

translated: 1542 ( '''71%''')

fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)

Date of last update: 2005-11-08

'''Slovak''': sk.po

translated: 845 ( '''39%''')

fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)

Date of last update: 2005-02-13

'''Slovenian''': sl.po

translated: 2055 ( '''95%''')

fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)

Date of last update: 2006-05-12

'''Serbian''': sr.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Serbian/Latine''': sr@Latn.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Swedish''': sv.po

translated: 410 ( '''19%''')

fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)

Date of last update: 2005-10-08

'''Turkish''': tr.po

translated: 907 ( '''42%''')

fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)

Date of last update: 2005-11-26

'''Ukrainian''': uk.po

translated: 1518 ( '''70%''')

fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)

Date of last update: 2005-10-21

'''Chinese/Simplified''': zh_CN.po

translated: 2134 ( '''99%''')

fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)

Date of last update: 2006-05-28

'''Chinese/Traditional''': zh_TW.po

translated: 1550 ( '''72 %''')

fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)

Date of last update: 2006-03-24

== Tutorials ==

* Basic: ca, de, en, es, fr, ja, nn, ru, sl
* Shapes: ca, en, es, fr, ja, sl
* Advanced: ca, en, es, fr, ja, sl
* Tracing: ca, de, en, es, fr, sl
* Calligraphy: ca, en, es, fr, sl
* Elements of design: en, es, fr, sl
* Tips and tricks: de, en, es, fr, sl

== Keys (shortcuts) ==
Already available in svn :
* en
* fr
* sl

== Windows installer ==

Already available in svn :
* czech.nsh
* english.nsh
* german.nsh
* italian.nsh

== Wiki translation ==

== Website ==

== News ==

TestPage

2006-05-31T19:20:05Z

Cornelius: /* Templates */ Update what is translatable in template

= Introduction =
== Community based, user oriented ==
The translations of the various documents focusing on Inkscape rely on the work of volunteers.
Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes.
It is very important not to forget that Inkscape is an open source, community based and user oriented 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.

== Guidelines/workflow ==

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

== Best practices ==

Best case for a good translation : translate from English to your mother tongue.

Test the behavior of the interface before starting translation

= Translatable content =

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

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.

== User interface ==

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

See section [[#Interface_Translation]] for information on PO files.

== Tutorials ==

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.

See section [[#Tutorial_Translation]] for information on translating tutorials.

== Windows installer ==

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.

== Templates ==
In the template are translatable several items; for example the name of default layer, size of the document(A4/Letter or another)...
# 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/templates/ directory on Linux, or C:\Program Files\Inkscape\share\templates\ directory on MS Windows(tm).
# 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)
# Upload default.xx.svg to the patch tracker.

== Release notes ==
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape

- give a general overview of the possibilities of the software to potential users

- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

== News displayed on Inkscape web site ==

== Web pages ==
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.

== Others ==
Templates (translation and localization)
Text files found in the inkscape directory
...

= Interface Translation =

== Introduction to PO file format ==

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.

#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
#: gedit/dialogs/program-location-dialog.glade2.h:2
msgid "Set program location..."
msgstr "Ställ in programplats..."

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.

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:

* 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.
* 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.

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.

== Get the PO file for your language ==

Download the .po file for your language from here:

http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/

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].

Create your own language file by copying the inkscape.pot file that gets generated when you run make in the codebase.

1. "./autogen.sh"
2. "./configure"
3. enter the "po" directory: "cd po"
4. generate the current PO template: "intltool-update --pot"

To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough),

1. update your local copy of Inkscape in the usual way: "svn update"
2. merge your existing translations into the new POT file (inkscape.pot):

"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"

Then you just need to complete the translations in the PO file that was
created in step 6.

If you want to update ALL .po files in po/, cd there and run:

make update-po

== Tools for translators ==

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.

* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)
* kbabel (http://i18n.kde.org/tools/kbabel/)
* gtranslator (http://gtranslator.sourceforge.net/)
* poEdit (http://poedit.sourceforge.net/)
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.

And last but not least, gettext utils.

== Submit finished work ==

Upload your work via the [[SourceForge]] patch tracker:

http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308

(Check the Upload checkbox and add your file or patch.)

Additionally, you may send a message to Inskcape's translators mailing list.

== A few important things to remember ==

* 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.
* 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).
* 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.

== Review ==
This is the start of a list of places to get translation reviews done. So far:
http://www.linux.it/tp/

== Verification ==
Before submitting your file in the patch tracker, please make sure it is valid:
* Make sure the file is encoded in UTF-8
* 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
* 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

== Locale Testing ==
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):

LANG=es_MX LANGUAGE=es_MX ls -z
ls: opción inválida -- z
Pruebe `ls --help' para más información.

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:

LANG=es_ES LANGUAGE=es_MX ls -z
ls: invalid option -- z
Try `ls --help' for more information.

== Programmers ==
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.

= Tutorial Translation =

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:

http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/

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.

* 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.

* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.

* Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.

* 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.

* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.

* 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.

* 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.

==Tools==
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html
* Transolution - http://transolution.python-hosting.com/

===Transforming XML into PO files===
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.

xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).

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.

<pre>
## use this at the very beginning, when there is no translation at all:
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml

## use this when there is a *.de.xml, but you want a de.po:
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml

## xml2po is not happy when this directory doesn't exist:
mkdir .tmp.basic

## use this when the tutorial-basic.xml has been updated and you
## want the new stuff in your de.po:
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml

## use this to create a tutorial-basic.de.xml from your de.po (ScislaC
## will use this file to create the final tutorial SVG file)
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml

</pre>

= Keyboard and mouse translation =

= Wiki and web site =
== Translation of web site ==
# There are two ways of getting files that you need to translate website:
## 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.
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.
# 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.
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.
=== Translating news and status ===
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Status =

== Interface translation (po files) ==

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)

Total number of PO files: 38
Total number of strings to translate: 2142

'''Amharic''': am.po

translated: 77 ( '''3%''')

fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)

Date of last update: 2003-02-01

'''Azerbaijani/Turkic''': az.po

translated: 63 ( '''2%''')

fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)

Date of last update: 2001-12-04

'''Belarusian''': be.po

translated: 158 ( '''7%''')

fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)

Date of last update: 2003-07-20

'''Catalan''': ca.po

translated: 2039 ( '''95%''')

fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)

Date of last update: 2006-05-08

'''Czech''': cs.po

translated: 2096 ( '''97%''')

fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)

Date of last update: 2006-05-22

'''Danish''': da.po

translated: 100 ( '''4%''')

fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)

Date of last update: 2002-01-15

'''German''': de.po

translated: 2116 ( '''98%''')

fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)

Date of last update: 2006-05-23

'''Greek''': el.po

translated: 44 ( '''2%''')

fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)

Date of last update: 2001-12-28

'''Spanish''': es.po

translated: 2125 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)

Date of last update: 2006-05-25

'''Spanish/Mexico''': es_MX.po

translated: 337 ( '''15%''')

fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)

Date of last update: 2004-04-05

'''Estonian''': et.po

translated: 9 ( '''0%''')

fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)

Date of last update: 2000-04-08

'''Basque''': eu.po

translated: 1548 ( '''72%''')

fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)

Date of last update: 2006-03-16

'''French''': fr.po

translated: 2126 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)

Date of last update: 2006-05-27

'''Irish''': ga.po

translated: 14 ( '''0%''')

fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)

Date of last update: 2000-08-24

'''Galician''': gl.po

translated: 82 ( '''3%''')

fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)

Date of last update: 2001-11-10

'''Hungarian''': hu.po

translated: 1564 ( '''73%''')

fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)

Date of last update: 2006-05-29

'''Italian''': it.po

translated: 2008 ( '''93%''')

fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)

Date of last update: 2006-05-15

'''Japanese''': ja.po

translated: 1294 ( '''60%''')

fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)

Date of last update: 2005-11-16

'''Korean''': ko.po

translated: 180 ( '''8%''')

fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)

Date of last update: 2006-04-10

'''Lithuanian''': lt.po

translated: 1774 ( '''82%''')

fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)

Date of last update: 2006-05-02

'''mk.po'''

translated: 0 ( '''0%''')

fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)

Date of last update: 2003-06-15

'''Norwegian/bokmål dialect''': nb.po

translated: 144 ( '''6%''')

fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)

Date of last update: 2003-01-25

'''Dutch: nl.po'''

translated: 1484 ( '''69%''')

fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)

Date of last update: 2005-11-07

'''Norwegian/Nynorsk''': nn.po

translated: 1376 ( '''64%''')

fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)

Date of last update: 2005-07-14

'''Punjabi''': pa.po

translated: 912 ( '''42%''')

fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)

Date of last update: 2005-09-11

'''Polish''': pl.po

translated: 1503 ( '''70%''')

fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)

Date of last update: 2005-10-29

'''Portuguese''': pt.po

translated: 183 ( '''8%''')

fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)

Date of last update: 2003-07-28

'''Portuguese/Brazillian''': pt_BR.po

translated: 1546 ( '''72%''')

fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)

Date of last update: 2006-04-27

'''Russian''': ru.po

translated: 1542 ( '''71%''')

fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)

Date of last update: 2005-11-08

'''Slovak''': sk.po

translated: 845 ( '''39%''')

fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)

Date of last update: 2005-02-13

'''Slovenian''': sl.po

translated: 2055 ( '''95%''')

fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)

Date of last update: 2006-05-12

'''Serbian''': sr.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Serbian/Latine''': sr@Latn.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Swedish''': sv.po

translated: 410 ( '''19%''')

fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)

Date of last update: 2005-10-08

'''Turkish''': tr.po

translated: 907 ( '''42%''')

fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)

Date of last update: 2005-11-26

'''Ukrainian''': uk.po

translated: 1518 ( '''70%''')

fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)

Date of last update: 2005-10-21

'''Chinese/Simplified''': zh_CN.po

translated: 2134 ( '''99%''')

fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)

Date of last update: 2006-05-28

'''Chinese/Traditional''': zh_TW.po

translated: 1550 ( '''72 %''')

fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)

Date of last update: 2006-03-24

== Tutorials ==

* Basic: ca, de, en, es, fr, ja, nn, ru, sl
* Shapes: ca, en, es, fr, ja, sl
* Advanced: ca, en, es, fr, ja, sl
* Tracing: ca, de, en, es, fr, sl
* Calligraphy: ca, en, es, fr, sl
* Elements of design: en, es, fr, sl
* Tips and tricks: de, en, es, fr, sl

== Keys (shortcuts) ==
Already available in svn :
* en
* fr
* sl

== Windows installer ==

Already available in svn :
* czech.nsh
* english.nsh
* german.nsh
* italian.nsh

== Wiki translation ==

== Website ==

== News ==

TestPage

2006-05-31T18:56:15Z

Cornelius: /* Translation of web site */ svn checkout of web module update

= Introduction =
== Community based, user oriented ==
The translations of the various documents focusing on Inkscape rely on the work of volunteers.
Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes.
It is very important not to forget that Inkscape is an open source, community based and user oriented 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.

== Guidelines/workflow ==

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

== Best practices ==

Best case for a good translation : translate from English to your mother tongue.

Test the behavior of the interface before starting translation

= Translatable content =

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

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.

== User interface ==

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

See section [[#Interface_Translation]] for information on PO files.

== Tutorials ==

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.

See section [[#Tutorial_Translation]] for information on translating tutorials.

== Windows installer ==

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.

== Templates ==

== Release notes ==
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape

- give a general overview of the possibilities of the software to potential users

- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

== News displayed on Inkscape web site ==

== Web pages ==
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.

== Others ==
Templates (translation and localization)
Text files found in the inkscape directory
...

= Interface Translation =

== Introduction to PO file format ==

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.

#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
#: gedit/dialogs/program-location-dialog.glade2.h:2
msgid "Set program location..."
msgstr "Ställ in programplats..."

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.

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:

* 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.
* 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.

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.

== Get the PO file for your language ==

Download the .po file for your language from here:

http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/

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].

Create your own language file by copying the inkscape.pot file that gets generated when you run make in the codebase.

1. "./autogen.sh"
2. "./configure"
3. enter the "po" directory: "cd po"
4. generate the current PO template: "intltool-update --pot"

To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough),

1. update your local copy of Inkscape in the usual way: "svn update"
2. merge your existing translations into the new POT file (inkscape.pot):

"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"

Then you just need to complete the translations in the PO file that was
created in step 6.

If you want to update ALL .po files in po/, cd there and run:

make update-po

== Tools for translators ==

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.

* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)
* kbabel (http://i18n.kde.org/tools/kbabel/)
* gtranslator (http://gtranslator.sourceforge.net/)
* poEdit (http://poedit.sourceforge.net/)
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.

And last but not least, gettext utils.

== Submit finished work ==

Upload your work via the [[SourceForge]] patch tracker:

http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308

(Check the Upload checkbox and add your file or patch.)

Additionally, you may send a message to Inskcape's translators mailing list.

== A few important things to remember ==

* 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.
* 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).
* 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.

== Review ==
This is the start of a list of places to get translation reviews done. So far:
http://www.linux.it/tp/

== Verification ==
Before submitting your file in the patch tracker, please make sure it is valid:
* Make sure the file is encoded in UTF-8
* 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
* 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

== Locale Testing ==
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):

LANG=es_MX LANGUAGE=es_MX ls -z
ls: opción inválida -- z
Pruebe `ls --help' para más información.

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:

LANG=es_ES LANGUAGE=es_MX ls -z
ls: invalid option -- z
Try `ls --help' for more information.

== Programmers ==
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.

= Tutorial Translation =

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:

http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/

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.

* 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.

* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.

* Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.

* 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.

* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.

* 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.

* 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.

==Tools==
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html
* Transolution - http://transolution.python-hosting.com/

===Transforming XML into PO files===
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.

xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).

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.

<pre>
## use this at the very beginning, when there is no translation at all:
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml

## use this when there is a *.de.xml, but you want a de.po:
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml

## xml2po is not happy when this directory doesn't exist:
mkdir .tmp.basic

## use this when the tutorial-basic.xml has been updated and you
## want the new stuff in your de.po:
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml

## use this to create a tutorial-basic.de.xml from your de.po (ScislaC
## will use this file to create the final tutorial SVG file)
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml

</pre>

= Keyboard and mouse translation =

= Wiki and web site =
== Translation of web site ==
# There are two ways of getting files that you need to translate website:
## 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.
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.
# 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.
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.
=== Translating news and status ===
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Status =

== Interface translation (po files) ==

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)

Total number of PO files: 38
Total number of strings to translate: 2142

'''Amharic''': am.po

translated: 77 ( '''3%''')

fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)

Date of last update: 2003-02-01

'''Azerbaijani/Turkic''': az.po

translated: 63 ( '''2%''')

fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)

Date of last update: 2001-12-04

'''Belarusian''': be.po

translated: 158 ( '''7%''')

fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)

Date of last update: 2003-07-20

'''Catalan''': ca.po

translated: 2039 ( '''95%''')

fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)

Date of last update: 2006-05-08

'''Czech''': cs.po

translated: 2096 ( '''97%''')

fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)

Date of last update: 2006-05-22

'''Danish''': da.po

translated: 100 ( '''4%''')

fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)

Date of last update: 2002-01-15

'''German''': de.po

translated: 2116 ( '''98%''')

fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)

Date of last update: 2006-05-23

'''Greek''': el.po

translated: 44 ( '''2%''')

fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)

Date of last update: 2001-12-28

'''Spanish''': es.po

translated: 2125 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)

Date of last update: 2006-05-25

'''Spanish/Mexico''': es_MX.po

translated: 337 ( '''15%''')

fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)

Date of last update: 2004-04-05

'''Estonian''': et.po

translated: 9 ( '''0%''')

fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)

Date of last update: 2000-04-08

'''Basque''': eu.po

translated: 1548 ( '''72%''')

fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)

Date of last update: 2006-03-16

'''French''': fr.po

translated: 2126 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)

Date of last update: 2006-05-27

'''Irish''': ga.po

translated: 14 ( '''0%''')

fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)

Date of last update: 2000-08-24

'''Galician''': gl.po

translated: 82 ( '''3%''')

fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)

Date of last update: 2001-11-10

'''Hungarian''': hu.po

translated: 1564 ( '''73%''')

fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)

Date of last update: 2006-05-29

'''Italian''': it.po

translated: 2008 ( '''93%''')

fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)

Date of last update: 2006-05-15

'''Japanese''': ja.po

translated: 1294 ( '''60%''')

fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)

Date of last update: 2005-11-16

'''Korean''': ko.po

translated: 180 ( '''8%''')

fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)

Date of last update: 2006-04-10

'''Lithuanian''': lt.po

translated: 1774 ( '''82%''')

fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)

Date of last update: 2006-05-02

'''mk.po'''

translated: 0 ( '''0%''')

fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)

Date of last update: 2003-06-15

'''Norwegian/bokmål dialect''': nb.po

translated: 144 ( '''6%''')

fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)

Date of last update: 2003-01-25

'''Dutch: nl.po'''

translated: 1484 ( '''69%''')

fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)

Date of last update: 2005-11-07

'''Norwegian/Nynorsk''': nn.po

translated: 1376 ( '''64%''')

fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)

Date of last update: 2005-07-14

'''Punjabi''': pa.po

translated: 912 ( '''42%''')

fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)

Date of last update: 2005-09-11

'''Polish''': pl.po

translated: 1503 ( '''70%''')

fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)

Date of last update: 2005-10-29

'''Portuguese''': pt.po

translated: 183 ( '''8%''')

fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)

Date of last update: 2003-07-28

'''Portuguese/Brazillian''': pt_BR.po

translated: 1546 ( '''72%''')

fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)

Date of last update: 2006-04-27

'''Russian''': ru.po

translated: 1542 ( '''71%''')

fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)

Date of last update: 2005-11-08

'''Slovak''': sk.po

translated: 845 ( '''39%''')

fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)

Date of last update: 2005-02-13

'''Slovenian''': sl.po

translated: 2055 ( '''95%''')

fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)

Date of last update: 2006-05-12

'''Serbian''': sr.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Serbian/Latine''': sr@Latn.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Swedish''': sv.po

translated: 410 ( '''19%''')

fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)

Date of last update: 2005-10-08

'''Turkish''': tr.po

translated: 907 ( '''42%''')

fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)

Date of last update: 2005-11-26

'''Ukrainian''': uk.po

translated: 1518 ( '''70%''')

fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)

Date of last update: 2005-10-21

'''Chinese/Simplified''': zh_CN.po

translated: 2134 ( '''99%''')

fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)

Date of last update: 2006-05-28

'''Chinese/Traditional''': zh_TW.po

translated: 1550 ( '''72 %''')

fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)

Date of last update: 2006-03-24

== Tutorials ==

* Basic: ca, de, en, es, fr, ja, nn, ru, sl
* Shapes: ca, en, es, fr, ja, sl
* Advanced: ca, en, es, fr, ja, sl
* Tracing: ca, de, en, es, fr, sl
* Calligraphy: ca, en, es, fr, sl
* Elements of design: en, es, fr, sl
* Tips and tricks: de, en, es, fr, sl

== Keys (shortcuts) ==
Already available in svn :
* en
* fr
* sl

== Windows installer ==

Already available in svn :
* czech.nsh
* english.nsh
* german.nsh
* italian.nsh

== Wiki translation ==

== Website ==

== News ==

TestPage

2006-05-31T14:44:18Z

Cornelius: /* Translation of web site */ Update of links

= Introduction =
== Community based, user oriented ==
The translations of the various documents focusing on Inkscape rely on the work of volunteers.
Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes.
It is very important not to forget that Inkscape is an open source, community based and user oriented 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.

== Guidelines/workflow ==

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

== Best practices ==

Best case for a good translation : translate from English to your mother tongue.

Test the behavior of the interface before starting translation

= Translatable content =

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

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.

== User interface ==

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

See section [[#Interface_Translation]] for information on PO files.

== Tutorials ==

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.

See section [[#Tutorial_Translation]] for information on translating tutorials.

== Windows installer ==

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.

== Templates ==

== Release notes ==
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape

- give a general overview of the possibilities of the software to potential users

- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

== News displayed on Inkscape web site ==

== Web pages ==
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.

== Others ==
Templates (translation and localization)
Text files found in the inkscape directory
...

= Interface Translation =

== Introduction to PO file format ==

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.

#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
#: gedit/dialogs/program-location-dialog.glade2.h:2
msgid "Set program location..."
msgstr "Ställ in programplats..."

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.

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:

* 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.
* 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.

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.

== Get the PO file for your language ==

Download the .po file for your language from here:

http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/

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].

Create your own language file by copying the inkscape.pot file that gets generated when you run make in the codebase.

1. "./autogen.sh"
2. "./configure"
3. enter the "po" directory: "cd po"
4. generate the current PO template: "intltool-update --pot"

To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough),

1. update your local copy of Inkscape in the usual way: "svn update"
2. merge your existing translations into the new POT file (inkscape.pot):

"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"

Then you just need to complete the translations in the PO file that was
created in step 6.

If you want to update ALL .po files in po/, cd there and run:

make update-po

== Tools for translators ==

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.

* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)
* kbabel (http://i18n.kde.org/tools/kbabel/)
* gtranslator (http://gtranslator.sourceforge.net/)
* poEdit (http://poedit.sourceforge.net/)
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.

And last but not least, gettext utils.

== Submit finished work ==

Upload your work via the [[SourceForge]] patch tracker:

http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308

(Check the Upload checkbox and add your file or patch.)

Additionally, you may send a message to Inskcape's translators mailing list.

== A few important things to remember ==

* 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.
* 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).
* 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.

== Review ==
This is the start of a list of places to get translation reviews done. So far:
http://www.linux.it/tp/

== Verification ==
Before submitting your file in the patch tracker, please make sure it is valid:
* Make sure the file is encoded in UTF-8
* 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
* 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

== Locale Testing ==
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):

LANG=es_MX LANGUAGE=es_MX ls -z
ls: opción inválida -- z
Pruebe `ls --help' para más información.

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:

LANG=es_ES LANGUAGE=es_MX ls -z
ls: invalid option -- z
Try `ls --help' for more information.

== Programmers ==
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.

= Tutorial Translation =

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:

http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/

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.

* 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.

* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.

* Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.

* 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.

* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.

* 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.

* 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.

==Tools==
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html
* Transolution - http://transolution.python-hosting.com/

===Transforming XML into PO files===
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.

xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).

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.

<pre>
## use this at the very beginning, when there is no translation at all:
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml

## use this when there is a *.de.xml, but you want a de.po:
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml

## xml2po is not happy when this directory doesn't exist:
mkdir .tmp.basic

## use this when the tutorial-basic.xml has been updated and you
## want the new stuff in your de.po:
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml

## use this to create a tutorial-basic.de.xml from your de.po (ScislaC
## will use this file to create the final tutorial SVG file)
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml

</pre>

= Keyboard and mouse translation =

= Wiki and web site =
== Translation of web site ==
# There are two ways of getting files that you need to translate website:
## Checkout actual svn version of inkscape_web module ( [http://inkscape.org/svn.php Working with SVN] ). The URL of svn repository is https://svn.sourceforge.net/svnroot/inkscape/inkscape_web/trunk
## OR Use [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/ online browser of subversion repository] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [http://sourceforge.net/tracker/?group_id=93438&atid=604308 patch tracker] at Sourceforge and mark it as a translation.
# 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.
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.
=== Translating news and status ===
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Status =

== Interface translation (po files) ==

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)

Total number of PO files: 38
Total number of strings to translate: 2142

'''Amharic''': am.po

translated: 77 ( '''3%''')

fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)

Date of last update: 2003-02-01

'''Azerbaijani/Turkic''': az.po

translated: 63 ( '''2%''')

fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)

Date of last update: 2001-12-04

'''Belarusian''': be.po

translated: 158 ( '''7%''')

fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)

Date of last update: 2003-07-20

'''Catalan''': ca.po

translated: 2039 ( '''95%''')

fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)

Date of last update: 2006-05-08

'''Czech''': cs.po

translated: 2096 ( '''97%''')

fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)

Date of last update: 2006-05-22

'''Danish''': da.po

translated: 100 ( '''4%''')

fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)

Date of last update: 2002-01-15

'''German''': de.po

translated: 2116 ( '''98%''')

fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)

Date of last update: 2006-05-23

'''Greek''': el.po

translated: 44 ( '''2%''')

fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)

Date of last update: 2001-12-28

'''Spanish''': es.po

translated: 2125 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)

Date of last update: 2006-05-25

'''Spanish/Mexico''': es_MX.po

translated: 337 ( '''15%''')

fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)

Date of last update: 2004-04-05

'''Estonian''': et.po

translated: 9 ( '''0%''')

fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)

Date of last update: 2000-04-08

'''Basque''': eu.po

translated: 1548 ( '''72%''')

fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)

Date of last update: 2006-03-16

'''French''': fr.po

translated: 2126 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)

Date of last update: 2006-05-27

'''Irish''': ga.po

translated: 14 ( '''0%''')

fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)

Date of last update: 2000-08-24

'''Galician''': gl.po

translated: 82 ( '''3%''')

fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)

Date of last update: 2001-11-10

'''Hungarian''': hu.po

translated: 1564 ( '''73%''')

fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)

Date of last update: 2006-05-29

'''Italian''': it.po

translated: 2008 ( '''93%''')

fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)

Date of last update: 2006-05-15

'''Japanese''': ja.po

translated: 1294 ( '''60%''')

fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)

Date of last update: 2005-11-16

'''Korean''': ko.po

translated: 180 ( '''8%''')

fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)

Date of last update: 2006-04-10

'''Lithuanian''': lt.po

translated: 1774 ( '''82%''')

fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)

Date of last update: 2006-05-02

'''mk.po'''

translated: 0 ( '''0%''')

fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)

Date of last update: 2003-06-15

'''Norwegian/bokmål dialect''': nb.po

translated: 144 ( '''6%''')

fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)

Date of last update: 2003-01-25

'''Dutch: nl.po'''

translated: 1484 ( '''69%''')

fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)

Date of last update: 2005-11-07

'''Norwegian/Nynorsk''': nn.po

translated: 1376 ( '''64%''')

fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)

Date of last update: 2005-07-14

'''Punjabi''': pa.po

translated: 912 ( '''42%''')

fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)

Date of last update: 2005-09-11

'''Polish''': pl.po

translated: 1503 ( '''70%''')

fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)

Date of last update: 2005-10-29

'''Portuguese''': pt.po

translated: 183 ( '''8%''')

fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)

Date of last update: 2003-07-28

'''Portuguese/Brazillian''': pt_BR.po

translated: 1546 ( '''72%''')

fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)

Date of last update: 2006-04-27

'''Russian''': ru.po

translated: 1542 ( '''71%''')

fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)

Date of last update: 2005-11-08

'''Slovak''': sk.po

translated: 845 ( '''39%''')

fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)

Date of last update: 2005-02-13

'''Slovenian''': sl.po

translated: 2055 ( '''95%''')

fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)

Date of last update: 2006-05-12

'''Serbian''': sr.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Serbian/Latine''': sr@Latn.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Swedish''': sv.po

translated: 410 ( '''19%''')

fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)

Date of last update: 2005-10-08

'''Turkish''': tr.po

translated: 907 ( '''42%''')

fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)

Date of last update: 2005-11-26

'''Ukrainian''': uk.po

translated: 1518 ( '''70%''')

fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)

Date of last update: 2005-10-21

'''Chinese/Simplified''': zh_CN.po

translated: 2134 ( '''99%''')

fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)

Date of last update: 2006-05-28

'''Chinese/Traditional''': zh_TW.po

translated: 1550 ( '''72 %''')

fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)

Date of last update: 2006-03-24

== Tutorials ==

* Basic: ca, de, en, es, fr, ja, nn, ru, sl
* Shapes: ca, en, es, fr, ja, sl
* Advanced: ca, en, es, fr, ja, sl
* Tracing: ca, de, en, es, fr, sl
* Calligraphy: ca, en, es, fr, sl
* Elements of design: en, es, fr, sl
* Tips and tricks: de, en, es, fr, sl

== Keys (shortcuts) ==
Already available in svn :
* en
* fr
* sl

== Windows installer ==

Already available in svn :
* czech.nsh
* english.nsh
* german.nsh
* italian.nsh

== Wiki translation ==

== Website ==

== News ==

TestPage

2006-05-31T14:42:08Z

Cornelius: /* Wiki and web site */ Initial version of text for web site translation

= Introduction =
== Community based, user oriented ==
The translations of the various documents focusing on Inkscape rely on the work of volunteers.
Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes.
It is very important not to forget that Inkscape is an open source, community based and user oriented 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.

== Guidelines/workflow ==

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

== Best practices ==

Best case for a good translation : translate from English to your mother tongue.

Test the behavior of the interface before starting translation

= Translatable content =

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

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.

== User interface ==

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

See section [[#Interface_Translation]] for information on PO files.

== Tutorials ==

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.

See section [[#Tutorial_Translation]] for information on translating tutorials.

== Windows installer ==

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.

== Templates ==

== Release notes ==
Translating [http://wiki.inkscape.org/wiki/index.php/Release_Notes release notes] helps giving a lot of visibility to Inkscape

- give a general overview of the possibilities of the software to potential users

- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

== News displayed on Inkscape web site ==

== Web pages ==
English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.

== Others ==
Templates (translation and localization)
Text files found in the inkscape directory
...

= Interface Translation =

== Introduction to PO file format ==

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.

#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
#: gedit/dialogs/program-location-dialog.glade2.h:2
msgid "Set program location..."
msgstr "Ställ in programplats..."

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.

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:

* 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.
* 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.

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.

== Get the PO file for your language ==

Download the .po file for your language from here:

http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/

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].

Create your own language file by copying the inkscape.pot file that gets generated when you run make in the codebase.

1. "./autogen.sh"
2. "./configure"
3. enter the "po" directory: "cd po"
4. generate the current PO template: "intltool-update --pot"

To make an absolutely up-to-date translation (in case the PO file in SVN is not up-to-date enough),

1. update your local copy of Inkscape in the usual way: "svn update"
2. merge your existing translations into the new POT file (inkscape.pot):

"msgmerge your_latest_PO_file inkscape.pot > new_PO_file"

Then you just need to complete the translations in the PO file that was
created in step 6.

If you want to update ALL .po files in po/, cd there and run:

make update-po

== Tools for translators ==

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.

* emacs' po-mode (contained in the gettext distribution; the version in po-utils is old)
* kbabel (http://i18n.kde.org/tools/kbabel/)
* gtranslator (http://gtranslator.sourceforge.net/)
* poEdit (http://poedit.sourceforge.net/)
* GEdit (installed on GNOME desktops) has a syntax highlight mode for PO file syntax.

And last but not least, gettext utils.

== Submit finished work ==

Upload your work via the [[SourceForge]] patch tracker:

http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308

(Check the Upload checkbox and add your file or patch.)

Additionally, you may send a message to Inskcape's translators mailing list.

== A few important things to remember ==

* 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.
* 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).
* 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.

== Review ==
This is the start of a list of places to get translation reviews done. So far:
http://www.linux.it/tp/

== Verification ==
Before submitting your file in the patch tracker, please make sure it is valid:
* Make sure the file is encoded in UTF-8
* 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
* 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

== Locale Testing ==
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):

LANG=es_MX LANGUAGE=es_MX ls -z
ls: opción inválida -- z
Pruebe `ls --help' para más información.

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:

LANG=es_ES LANGUAGE=es_MX ls -z
ls: invalid option -- z
Try `ls --help' for more information.

== Programmers ==
Please make sure you use [http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150 dgettext] for any pluralized strings.

= Tutorial Translation =

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:

http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/

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.

* 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.

* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.

* Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.

* 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.

* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed.

* 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.

* 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.

==Tools==
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html
* Transolution - http://transolution.python-hosting.com/

===Transforming XML into PO files===
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.

xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).

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.

<pre>
## use this at the very beginning, when there is no translation at all:
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml

## use this when there is a *.de.xml, but you want a de.po:
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml

## xml2po is not happy when this directory doesn't exist:
mkdir .tmp.basic

## use this when the tutorial-basic.xml has been updated and you
## want the new stuff in your de.po:
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml

## use this to create a tutorial-basic.de.xml from your de.po (ScislaC
## will use this file to create the final tutorial SVG file)
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml

</pre>

= Keyboard and mouse translation =

= Wiki and web site =
== Translation of web site ==
# There are two ways of getting files that you need to translate website:
## Checkout actual svn version of inkscape_web module ( [Working with SVN http://inkscape.org/svn.php] ). The URL of svn repository is: https://svn.sourceforge.net/svnroot/inkscape/inkscape_web/trunk
## OR Use [online browser of subversion repository http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape_web/trunk/] and download files manually.
## Files you probably want to translate are:
##* includes/localized.inc (file contains string to translate menu)
##* index-en.inc (main page of inkscape.org)
##* discussion-en.inc
##* download-en.inc
##* mailing-lists-en.inc
##* report-bugs-en.inc
##* submit2webmaster-en.inc
##* submit2webmaster-en-form.inc
##* svn-en.inc
# 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...).
# Now you can start your translation. Files are simple text files with HTML tags and in UTF-8 encoding.
# If you have the file translated and really want to submit it, read it once more and correct errors ;)
# Submit the file to the [patch tracker http://sourceforge.net/tracker/?group_id=93438&atid=604308] at Sourceforge and mark it as a translation.
# 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.
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.
=== Translating news and status ===
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:
<pre>
/news
- en
\- 2005
- 2006
\- 04
- 05
\- 001.inc
- 002.inc
...
- de
- fr
</pre>
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.
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.

= Status =

== Interface translation (po files) ==

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)

Total number of PO files: 38
Total number of strings to translate: 2142

'''Amharic''': am.po

translated: 77 ( '''3%''')

fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)

Date of last update: 2003-02-01

'''Azerbaijani/Turkic''': az.po

translated: 63 ( '''2%''')

fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)

Date of last update: 2001-12-04

'''Belarusian''': be.po

translated: 158 ( '''7%''')

fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)

Date of last update: 2003-07-20

'''Catalan''': ca.po

translated: 2039 ( '''95%''')

fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)

Date of last update: 2006-05-08

'''Czech''': cs.po

translated: 2096 ( '''97%''')

fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)

Date of last update: 2006-05-22

'''Danish''': da.po

translated: 100 ( '''4%''')

fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)

Date of last update: 2002-01-15

'''German''': de.po

translated: 2116 ( '''98%''')

fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)

Date of last update: 2006-05-23

'''Greek''': el.po

translated: 44 ( '''2%''')

fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)

Date of last update: 2001-12-28

'''Spanish''': es.po

translated: 2125 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)

Date of last update: 2006-05-25

'''Spanish/Mexico''': es_MX.po

translated: 337 ( '''15%''')

fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)

Date of last update: 2004-04-05

'''Estonian''': et.po

translated: 9 ( '''0%''')

fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)

Date of last update: 2000-04-08

'''Basque''': eu.po

translated: 1548 ( '''72%''')

fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)

Date of last update: 2006-03-16

'''French''': fr.po

translated: 2126 ( '''99%''')

fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)

Date of last update: 2006-05-27

'''Irish''': ga.po

translated: 14 ( '''0%''')

fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)

Date of last update: 2000-08-24

'''Galician''': gl.po

translated: 82 ( '''3%''')

fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)

Date of last update: 2001-11-10

'''Hungarian''': hu.po

translated: 1564 ( '''73%''')

fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)

Date of last update: 2006-05-29

'''Italian''': it.po

translated: 2008 ( '''93%''')

fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)

Date of last update: 2006-05-15

'''Japanese''': ja.po

translated: 1294 ( '''60%''')

fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)

Date of last update: 2005-11-16

'''Korean''': ko.po

translated: 180 ( '''8%''')

fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)

Date of last update: 2006-04-10

'''Lithuanian''': lt.po

translated: 1774 ( '''82%''')

fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)

Date of last update: 2006-05-02

'''mk.po'''

translated: 0 ( '''0%''')

fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)

Date of last update: 2003-06-15

'''Norwegian/bokmål dialect''': nb.po

translated: 144 ( '''6%''')

fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)

Date of last update: 2003-01-25

'''Dutch: nl.po'''

translated: 1484 ( '''69%''')

fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)

Date of last update: 2005-11-07

'''Norwegian/Nynorsk''': nn.po

translated: 1376 ( '''64%''')

fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)

Date of last update: 2005-07-14

'''Punjabi''': pa.po

translated: 912 ( '''42%''')

fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)

Date of last update: 2005-09-11

'''Polish''': pl.po

translated: 1503 ( '''70%''')

fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)

Date of last update: 2005-10-29

'''Portuguese''': pt.po

translated: 183 ( '''8%''')

fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)

Date of last update: 2003-07-28

'''Portuguese/Brazillian''': pt_BR.po

translated: 1546 ( '''72%''')

fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)

Date of last update: 2006-04-27

'''Russian''': ru.po

translated: 1542 ( '''71%''')

fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)

Date of last update: 2005-11-08

'''Slovak''': sk.po

translated: 845 ( '''39%''')

fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)

Date of last update: 2005-02-13

'''Slovenian''': sl.po

translated: 2055 ( '''95%''')

fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)

Date of last update: 2006-05-12

'''Serbian''': sr.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Serbian/Latine''': sr@Latn.po

translated: 1359 ( '''63%''')

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08

'''Swedish''': sv.po

translated: 410 ( '''19%''')

fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)

Date of last update: 2005-10-08

'''Turkish''': tr.po

translated: 907 ( '''42%''')

fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)

Date of last update: 2005-11-26

'''Ukrainian''': uk.po

translated: 1518 ( '''70%''')

fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)

Date of last update: 2005-10-21

'''Chinese/Simplified''': zh_CN.po

translated: 2134 ( '''99%''')

fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)

Date of last update: 2006-05-28

'''Chinese/Traditional''': zh_TW.po

translated: 1550 ( '''72 %''')

fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)

Date of last update: 2006-03-24

== Tutorials ==

* Basic: ca, de, en, es, fr, ja, nn, ru, sl
* Shapes: ca, en, es, fr, ja, sl
* Advanced: ca, en, es, fr, ja, sl
* Tracing: ca, de, en, es, fr, sl
* Calligraphy: ca, en, es, fr, sl
* Elements of design: en, es, fr, sl
* Tips and tricks: de, en, es, fr, sl

== Keys (shortcuts) ==
Already available in svn :
* en
* fr
* sl

== Windows installer ==

Already available in svn :
* czech.nsh
* english.nsh
* german.nsh
* italian.nsh

== Wiki translation ==

== Website ==

== News ==

Inkscape

2006-02-09T16:37:59Z

Cornelius: Remove a huge amount of spam. Used version from 21:24, 23 January 2006 (by Tom)

This is a freeform area for Inkscape development and discussion.
Curious about [[WikiSyntax]]?
<table cellspacing="11" width="100%"><tr valign="top">
<td style="width:33%;background-color: #EFFBFF; padding:.5em; border: 1px solid #BFEEFF">
=== About Inkscape ===
* [http://www.inkscape.org/ Inkscape Homepage]
* [[AboutInkscape]]
* [[InkscapeFeatures]]
* [[FAQ]] - Frequently Asked Questions
* [[ProjectInfo]]
* [http://inkscape.org/cgi-bin/wiki.pl?SupportedOperatingSystems Supported Operating Systems]
* [[Tools]] - Supporting Tools and Applications
* [[Galleries]]
* [[ArticlesAndPresentations]]
* [[TestimonialComments]]
* [[InkscapePopularity]]
* [[ContactInfo]] our heroes

</td><td style="width:33%;;background-color: #[[FFF1EF]]; padding:.5em; border: 1px solid #[[FFC7BF]];margin:.5em">
=== User Documentation ===
* [[InkscapeTerminology]]
* [[UserManual]]
* [http://inkscape.org/doc/basic/tutorial-basic.html Tutorial:Basic]
* [[InkscapeSVG]] vs. Plain SVG
* [[GettingExtensionsWorking]]
* [[GettingEffectsWorking]]
* [[WhatEffectsDo]]
* [[UsingTheConnectorTool]]
* [[Installing Fonts as a User]]

* [[ReleaseNotes]] for 0.44 and past
* [[PressRelease]] for 0.43 and past
* [[ArticleIntroducingInkscape0_40|Introducing Inkscape 0.40]]

* [[InkscapeTipWiki]]
* [[OtherProjects]] (outside links)
</td><td style="width:33%;background-color: #FFFAEF; padding:.5em; border: 1px solid #[[FFE9BF]]; margin:.5em">

=== Help Inkscape Without Coding ===

* [[PrintingConsensusPoll]]
* [[HelpWanted]]
* [[CreatingDists]]: how to build packages
* [[WebsiteEditing]]
* [[WritingNews]]
* [[UpdatingTrackerItems]]
* [[TutorialIdeas]]

* [[TestingInkscape]]

</td></tr></table><table cellspacing="0" width="100%" style="background-color: #FFFAEF; border-width:0em .5em; border-style:solid; border-color:white"><tr valign="top" style="padding:11px 0em 0em 11px">
<th colspan="2" align="left" style="padding:.5em 0em 0em .5em">
=== Developer Documentation ===
</th></tr><tr valign="top" align="left"><td style="width:50%;padding:.5em">
==== General ====
* [[DeveloperManual]]
* [[CompilingInkscape]]
* [[WorkingWithSVN]]
* [[HandlingPreferences]]: creating and using preference values
* [[AddSPObject]]: how to add a new SPObject type
* [[ReprListeners]]: responding to XML doc changes
* [[ErrorsAndWarnings]]: how to deal with reporting errors, warnings, and other messages
* [[DebuggingTips]]: random tips to help debug problems

* [[DeveloperTitles]]: terms for various roles in Inkscape
* [[InkscapeJanitors]]: small tasks that need doing
* [http://livarot.sourceforge.net/ Livarot]: for boolean ops

</td><td style="width:50%;padding:.5em">
==== Development Discussion ====
* [[Roadmap]]: the main todo list
* [[NewFeatureProposals]]
* [[ExtensionArchitectureProposals]]
* [[Coding Style|Coding Style Discussion]]
* [[FileTypes]]
* [[Icons]] (Application + Interface)
* [[ApplicationIcons]] ( more application + interface )
* [[InkscapeColor]]
* [[PrintingSubsystem]]
* [[SVG Competitors Plan]] - MS WVG vs SVG, etc
* [[SVG Tiny Compliance]]
* [[SVG Test Suite Compliance]] - [[W3C]] full test suite
* [[CSS Support]]
* [[OpenVG]] Standard (draft)
* [[OpenDocument proposal]]
* [[Googles Summer of Code]]

</td></tr><tr valign="top" align="left"><td style="width:50%;padding:.5em">
==== User Interface Discussion ====
* [[TranslationInformation]]
* [[AccessibleGraphics]]
* [[ObjectManager]]
* [[DialogsReorganization]]
* [[DialogReplacement]]
* [[ModalInterfaces]]
* [[TextUsability]]: text tool /dialog dialog
* [[KeyboardShortcutsToDo]]
** [[KeyboardProfiles]]: how you can help
* [[StatusbarAPI]]
* [[Animation-(Timeline)]]
* [[Free Desktop Graphic Suite]]

</td><td style="width:50%;padding:.5em">
==== Rearchitecture Discussion ====
* [[SubsystemRearchitecture]]
* [[CPlusPlus]]: Convert to C++
* [[Pangoification]]: replace font rendering subsystem
* [[GtkMMification]]: replace C boilerplate with gtkmm objects
* [[PathRepresentation]]
* [[Cairoification]]
* [[ScribusInteroperability]]

</td></tr></table>
----
* [[WikiAttic]]: pages that are no longer relevant but kept for historical value

__NOTOC__

CzechTerminology

2005-08-04T08:50:25Z

Cornelius: changes in UI description translation

This is a beginning of an Inkscape glossary. Please respect it and contribute to it if you work on Inkscape UI. If you are doing translations, please create and link below a similar glossary for your language.

* RussianTerminology
* FrenchTerminology

------
Poznámka: toto je velmi raná verze překladu, bude doplněna a budou v ní prováděny změny.
== Obecné ==

* '''Uzel''': bod na ''křivce'', který můžete přesunovat. Pokud použijete nástroj pro úpravu uzlů, pak je zobrazen jako šedý (pokud není vybrán) nebo modrý (když je vybrán) čtvereček na křivce. ''Tvary'' uzly nemají; mají ''handle''. Uzel může mít také jeden nebo dva ''handle'' - jsou to malé kružnice spojené s uzlem a upravují se jimi bezierovy tangenty.

* '''Handle''': 1) one of two points around a ''node'', displayed (for selected nodes) as a circle connected with its node by a line (node handles); 2) the arrows around the selected object in selector (scale handles, rotation handles); 3) points on a ''shape'' that can be dragged by node tool to edit the shape, displayed as small white diamonds (shape handles); 4) the things that you drag on canvas to set the placement, direction, and size of a gradient or pattern (gradient handles, pattern handles). (Internally this is called a '''Knot''', but this is a deprecated term in user documentation.)

* '''Křivka''': objekt, který má ''uzly'', ale nemá ''ovládací prvky'' (při použití nástroje pro úpravu uzlů). Mapříklad se jedná o čáru vytvořenou nástrojem pro kreslení od ruky.

* '''Live Shape''': an object that does not display ''nodes'' but may have ''controls''. An example is a circle or star. A live shape can be converted to ''path'' by Convert to Path command.

* '''Stroke''': a visible outline of a ''shape'' or ''path''. Not the same as ''path''; a path may or may not have a stroke. If the stroke is present, it can be converted to path by Convert Stroke to Path command.

** '''Stroke shape''' (''to be implemented''): the dependency of the stroke width on distance along the stroke. Currently only constant-width strokes are supported.

** '''Stroke pattern''' (''to be implemented''): the representation of a stroke as a sequence of arbitrary objects positioned along the path.

* '''Object''': an independent editable thing on the canvas. May be a ''path'', a ''shape'', a text object, a group, etc.

== Uživatelské rozhranní ==

* '''Okno dokumentu''': the window with a Canvas, Menu, Commands bar, etc. Note that the same instance of the program may have several document windows. Some dialog are referred to as "windows" therefore it is important to distinguish between them and the Document window.

** '''Menu''', bar at the top.

** '''Commands bar''', beneath the Menu, with buttons for commands like New, Open, ... Note that this one will likely be broken into many smaller toolbars, each covering one topic, so the user will be able to switch them on/off and rearrange. So this name is temporary.

** '''Tool Controls bar''', beneath the Commands bar. Has the controls for the currently active tool. Note the capitalization. One should not refer to it as the "Tool bar," nor is it a "Tool" edition of the "controls" variety of "bar". It's proper name should be "Tool Controls" bar.

** '''Nástroje''', along the left side
*** '''Nástroj pro výběr''', nebo jednodušeji '''Selektor'''
*** '''Nátroj pro úpravu uzlů'''
*** '''Nástroj pro přiblížení a nebo oddálení obrázku''' (Lupa)
*** '''Nástroj pro tvorbu obdélníků'''
*** '''Nástroj pro tvorbu elips'''
*** '''Nástroj pro tvorbu hvězd'''
*** '''Nástroj pro tvorbu spirál'''
*** '''Nástro Tužka''': pro zachování konzistence, prosím, neodkazujte na tento nástroj jako na ''Nástroj pro kreslení od ruky''. Je lepší použít termín ''Tužka (kreslení od ruky)''.
*** '''Nástroj Pero''': pro zachování konzistence, prosím, neodkazujte na tento nástroj jako na ''Nástroj pro tvorbu bezierovych křivek'' nebo ''Bezier (pen) Tool''. Je lepší použít termín ''Nástroj Pero (Bezier)''.
*** '''Nástroj pro tvorbu kaligafických křivek'''
*** '''Nástroj pro tvorbu textu'''
*** '''Nástroj pro tvorbu barevných přechodů'''
*** '''Nástroj pro získání barvy''' (Kapátko)

** '''Plátno''', hlavni oblast, s volitelným ohraničením '''pravítky''' a '''posuvníky'''

** '''Stavový řádek''', podél spodní strany okna

== ZASTARALÉ A VYŘAZENÉ TERMÍNY ==

Tyto jsou použitelné pouze uvnitř kódu, nikdy je nepoužívejte v dokumentaci.
* knot (this may be a "handle", "control", "node" etc as seen by the user)
* item (use "object")
* desktop (use "canvas" or "document window" depending on context)
* event contexts (they are known to users as "tools")