Diff for "Translations/Guide"

Not logged in - Log In / Register

Differences between revisions 1 and 2
Revision 1 as of 2009-01-18 03:19:42
Size: 932
Editor: 78
Comment:
Revision 2 as of 2009-01-18 03:37:07
Size: 2681
Editor: 78
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
= Variable names = After reading this guide please find the guide specific to your language into the [[Translations/GuidesList | list of translation guides for all languages]].
Line 13: Line 13:
= Context text = = What should not be translated ==
== Data placeholders and variable names ==
in many development languages, a developer can insert data into a string by using a placeholder such as %s or %d. You may also see more complex variations, such as %(variablename)s, $name or ${name}. Copy these variables and placeholders exactly as you see, placing them in whichever part of the string makes most sense in the target language. If you're in doubt, ask another translator for advice.


== Formatting tags ==
Formatting: you may see HTML, such as <strong>, used to format text in a string. Copy these tags exactly as you find them and apply them to the relevant part of the text, remembering to close the tags as appropriate. You may also see other tags, such as XML, and should treat them the same way.


== Context text ==

== Program parameters ==

== Constants ==

 * GTK

 * GCONF
Line 17: Line 35:
different development languages and frameworks use different ways to signify which key within a string should be used as a keyboard shortcut. Very often, if you see an underscore (e.g. Save _As) or ampersand (e.g. Print previe&w) at the beginning or within a word, it may well be a keyboard shortcut. Ensuring you have a unique shortcut for each function is important and you should, at the very least, view the software in action and draw up a list of the shortcuts you plan to use before you start translating. You should place the underscore, ampersand or whichever other control character directly in front of the letter you want to use as the shortcut.
Line 19: Line 39:
= When you could change variables order =

= Rosetta specific =

Launchpad Help > Translations > General Translation Guide

Overview

This guides contains information about what strings should be translated and what not, what are plurar forms and other general things about working with Launchapad Translations (Rosetta).

You are free to translate this guide and include it into your language specific guide, otherwise please make sure your language guide contains a reference to the general guide.

After reading this guide please find the guide specific to your language into the list of translation guides for all languages.

= What should not be translated ==

Data placeholders and variable names

in many development languages, a developer can insert data into a string by using a placeholder such as %s or %d. You may also see more complex variations, such as %(variablename)s, $name or ${name}. Copy these variables and placeholders exactly as you see, placing them in whichever part of the string makes most sense in the target language. If you're in doubt, ask another translator for advice.

Formatting tags

Formatting: you may see HTML, such as <strong>, used to format text in a string. Copy these tags exactly as you find them and apply them to the relevant part of the text, remembering to close the tags as appropriate. You may also see other tags, such as XML, and should treat them the same way.

Context text

Program parameters

Constants

  • GTK
  • GCONF

Menu accelerators / shortcuts

different development languages and frameworks use different ways to signify which key within a string should be used as a keyboard shortcut. Very often, if you see an underscore (e.g. Save _As) or ampersand (e.g. Print previe&w) at the beginning or within a word, it may well be a keyboard shortcut. Ensuring you have a unique shortcut for each function is important and you should, at the very least, view the software in action and draw up a list of the shortcuts you plan to use before you start translating. You should place the underscore, ampersand or whichever other control character directly in front of the letter you want to use as the shortcut.

Plural forms

When you could change variables order

Rosetta specific

< Launchpad Translators group

All language translations Guides list >

Translations/Guide (last edited 2018-10-26 11:00:37 by cjwatson)