|Extension||.pot / .po|
|Resources||GNU Gettext Documentation|
Smartling also supports the msgctxt parameter that allows you to have Smartling capture a string as a variant. When a gettext string includes msgctxt metadata it will be created as variant using the value of msgctxt.
msgctxt "Home Page Menu Navigation"
msgctxt "Home Address Label"
Will result in two strings for translation, both with the value "Home". The translators can choose to to make the translation the same or not. The value of msgctxt displays to translators in the Translation Interface and the Smartling Dashboard. See the Help Center for more on translation variants.
Smartling includes comments in gettext files as instructions for translators. Comments follow the gettext standard. Only Extracted comments (beginning with
#. ) are displayed to translators as instructions:
#. This is an instruction that is included in the file above a string.
#. This is also an instruction that will be presented to translators.
msgid "Original source string."
Native Gettext Placeholder formats
In addition to Smartling's Placeholder Format directives, Smartling supports Gettext's native method of declaring placeholder format using flags (comment lines beginning with
#,). Flags affect only the entry they are part of. The following native Gettext placeholder types are supported:
Smartling automatically formats Gettext strings with HTML. No integration is required. HTML parsing can be turned on in order to create smaller source strings. Adding the
smartling.string_format directive with value
html turns on HTML parsing. If this directive is present in the file Smartling explicitly parses all subsequent strings as HTML. With HTML parsing on, strings will be created based on HTML block elements. Strings that have no HTML are captured as normal. This directive is completely optional.
If you include a plural-forms header in a original uploaded file, Smartling will return the locale specific plural-forms header in the translated file.
For example if an English source file contains the following header:
"Plural-Forms: nplurals=2; plural=n == 1 ? 0 : 1;\n"
A Russian translation file will contain:
"Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n"
Note: Smartling supports the CLDR standards for plurals. For some languages, Gettext plural support differs from the CLDR standards. For example, CLDR allows four plural forms for Polish: one; few; many and other, while Gettext only supports one; few; and many. Smartling will allow translations for all four CLDR plural forms, but when downloading translated Gettext files, only those supported by Gettext will be included.
Note: When using file/get to download Gettext files from Smartling, the parameter
includeOriginalStrings=false ensures that if no translations are available, Smartling returns an empty string. If the parameter is set to true, Smartling returns the original string.
# smartling.[directive_name] = [value]
The directive must be a single comment on one line, and there should not be any inline trailing symbols after the directive. Directives apply to all strings that follow them. Directives can be changed throughout the file
|Values:||1. Custom regular expression (pcre)
2. NONE - disable custom placeholders
|Description:||Used to define a custom placeholder format for strings in the file. See Placeholders in Resource Files for more information.|
Any characters surrounded by square brackets will be treated as a placeholder.
|Description:||Used to specify a standard placeholder format. See Placeholders in Resource Files for more information.|
Specifies iOS-style placeholders for the file.
|Values:||int - Accepted values are 0-100|
|Description:||Sets the percentage by which original strings are inflated when downloading pseudo translations. If this directive is not set, pseudo translations are 30 percent longer than the original strings.|
Downloaded pseudo translations will increase the length of original strings by 80 percent.
sltrans- (since Parser v3)
|Description:||Use this directive to enable or disable processing of translation strings in the file. You must turn translation back on after the strings you want to exclude.|
Strings below this directive will be captured as strings but excluded from translation
Strings below this directive will be translated