TestPage

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

1. Contact to a local translation group, to get support and help on your language. Rather than working alone, you should work with an experienced translation team for your language. Thus you will benefit from their knowledge, as well as being able to communicate with them on your own mother tongue. Moreover, translation teams use to have style guidelines and a standarized vocabulary for technical terms that you should be aware of. There may be many communities working on translations for your own language, but a good start point is subscribing to your local GNOME translation team or KDE translation team.
2. Subscribe to 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.
3. Get files for your language. If you only want to translate the interface messages, you can get the files from 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 here. See section #Translatable_content for which files you have to modify to translate each part of Inkscape.
4. 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 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.
5. 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 [InterfaceTranslation] page for detailed information on the PO files.

Tutorials

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.

See [Document Translation] page for detailed 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

The man pages consist in a standard user documentation, available from the command line on Unix systems simply type "man inkscape" from the prompt of a command window).

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

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

Release notes

Translating 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).

Web pages, News and Wiki

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.

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

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

Others

Text files found in the inkscape directory ...

Status

See this [dedicated page]