Changes

In other cases, it's necessary to provide a hint to translators, <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>,

* Localized strings returned from gettext, ngettext, <abbr title="et cetera - Latin phrase meaning 'and so on'">etc. </abbr> are always unicode

See [[Addons_DevelopmentAddons_development#Localization|Addons development]] for more details.

* [[Translation_environment4|Gramps 4.0.x to master (trunk)5.1.x]]

Don't build up a sentence from phrases. Because a sentence is ordered in a particular way in your language does not mean that it is ordered the same way in another. Providing the entire sentence as a single unit allows the translator to make a meaningful translation. Do not concatenate phrases or terms as they will then show up as separate phrases or terms to be translated and the complete sentence may then show up incorrectly, especially in right-to-left languages (Arabic, Hebrew, <abbr title="et cetera - Latin phrase meaning 'and so on'">etc.</abbr>).===Use named %s/%d parameter values===Python provides a powerful mechanism that allows the reordering of %s parameter values in a string. A This has two advantages:# it allows the translator may need an option to rearrange the structure of a sentenceto fit more naturally into the language structure.# it can provide the translator more detail about what the variable refers to. There are two main options allowing you to name the variable being replaced.* The older style applies [https://docs.python.org/3.11/library/stdtypes.html#printf-style-string-formatting the '%' operator]* Python3 introduced a new style with the [https://docs.python.org/3.11/library/stdtypes.html#str.format| string formatting method] Either technique can be used with Gramps for translations, although the ''str.format()'' method is preferred for new code.Whichever you choose, and it may not match is important to ''use named arguments'' when there is more than one %s/%d value into a translation string. Also remember, some languages are using right-to-left text direction.  Most examples on this page use the order you choseolder style - this includes use of the ''print'' statement, which must be replaced by the ''print()'' function in python3. For ==== Using '%' style formatting ====A simple example:

Some languages are using right-to-left text direction==== Using the str. It is important to use named arguments when there is more than one %format() method====Using the str.format method, the example above would be written as print("{male_name:s} was born in {city:s/%d value into a translation string}".format( city = 'Toronto', male_name = 'Joe') )

Plurals are handled differently in various languages. Whilst English or German have a singular and a plural form, other languages like Turkish don't distinguish between plural or singular and there are languages which use different plurals for different numbers, <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g. </abbr>, Polish.

Gramps often displays names of primary objects (''Person, Family, Event, <abbr title="et cetera - Latin phrase meaning 'and so on'">etc .</abbr> ...''), for being consistent on displayed strings (also in english!), there is a ''trans_objclass(objclass_str)'' function on TransUtils module.

See ''the person'' details # or See ''the family, the event, <abbr title="et cetera - Latin phrase meaning 'and so on'">etc.</abbr> ...'' details

<abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g. </abbr>,

so need some extra-testing and customization for some translators. <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, in french

This works because the dummy definition of _() simply returns the string unchanged. And this dummy definition will temporarily override any definition of _() in the built-in builtin namespace (until the del command). Take care, though if you have a previous definition of _() in the local namespace.