Translation

From Synfig Studio :: Documentation
Revision as of 12:50, 20 May 2016 by Jay (Talk | contribs) (Add Serbian language to the list)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Navigation Navigation:  <<Writer Documentation>>


Getting Started

To translate you just need to create a page with the same English original name adding / and two-letter code corresponding to your language as a suffix. For example, Russian translation for Doc:Getting_Started page is Doc:Getting_Started/ru and Spanish translation is Doc:Getting_Started/es. (for how to add pages have a look at the first page of the writer doc.

List of supported languages:

  • ar Arabic
  • bg Bulgarian
  • br Breton
  • ca Catalan
  • cz Czech
  • de German
  • dk Danish (Denmark)
  • en English
  • es Spanish
  • fa Farsi
  • fi Finnish
  • fr French
  • id Bahasa Indonesia
  • it Italian
  • ja Japanese
  • ko Korean
  • nl Dutch
  • pl Polish
  • pt Portuguese
  • ro Romanian
  • ru Russian
  • sr Serbian
  • sv Swedish
  • tr Turkey
  • zh-cn Simplified Chinese
  • zh-tw Traditional Chinese

If your language code is not recognized correctly, please submit a request to this forum thread.

Hint: Adding new language requires editing two templates: Template:Languages and Template:Languages/ThisPageTranslatedIn, see also : Meta:How_to_add_support_for_new_language

Handling Links

When translating text in the page body please don't change links - just leave them pointing to the English pages. The wiki software will automatically bring readers to the corresponding translation if a translation exists. You might want to use the alternative text if the English version just links to the page without alternative text!

Handling Changes

Please don't forget to update your translations as the original English page changes. Don't add your own stuff to translated page - add it to English first.

Formal Or Informal?

If the language you are translating to allows for formal and informal ways of talking to the reader, we prefer informal over formal.


Navigation Navigation:  <<Writer Documentation>>