Standard Android internationalization .xml file
Example:
<resources>
<string name="greeting">Hello {name}!</string>
<string name="farewell">Goodbye {name}!</string>
<plurals name="entities_found">
<item quantity="one"<entity found>/item>
<item quantity="other"<entities found>/item>
</plurals>
</resources>

• Only string and plurals data will be translated
• Plurals items must be as shown in the above example
• Other types will not be translated
• Value can be an HTML but must have escaped html tags or url encoded
• Variables are not mandatory, but if you use them, you must indicate both the start and end variable symbols

Standard dotnet .resx file
Example:
<data name="AskName" xml:space="preserve">
<value>What's your first name?</value>
</data>

• Only string data will be translated
• Other types will not be translated
• Value can be an HTML but must have escaped html tags or url encoded
• Variables are not mandatory, but if you use them, you must indicate both the start and end variable symbols

i18n JSON File containing all languages in a single file
Example:
{
"en": {
"greeting": "Hello {name}",
"inner": {
"key1": "ole",
"key2": "ola"
},
"farewell": "Goodbye {name}",
},
"fr": {
}
}

• If item for the target translation language doesn't exists it will be automatically added (eg. fr)
• All nested lever will be translated (eg. key1 and key2)
• Variables are not mandatory, but if you use them, you must indicate both the start and end variable symbols

i18n JSON File containing only one language (each language has its own file)
Example:
{
"greeting": "Hello {name}",
"inner": {
"key1": "ole",
"key2": "ola"
},
"farewell": "Goodbye {name}",
}

• All nested lever will be translated (eg. key1 and key2)
• Variables are not mandatory, but if you use them, you must indicate both the start and end variable symbols

Java Bundle Properties file
Example:
# This is a comment 1
Name=What is your name?
Question=My name is {name}.
Multiline=test multiline 1 \ntest multiline 2 \nlast line
# This is a comment 2
Test=This is a test

• Only string data will be translated
• The text can span multiple lines as shown in the example using \n
• Variables are not mandatory, but if you use them, you must indicate both the start and end variable symbols

Php Po file with original strings and translated strings
Example:
msgid "Hello, world!"
msgstr "Ciao, mondo!"

msgid "Goodbye"
msgstr "Addio"

msgid ""
"line 1 "
"line 2 "
"line 3 "
msgstr ""
"linea 1 "
"linea 2 "
"linea 3 "

• Only string data will be translated
• The text can span multiple lines as shown in the example
• msgid must contain the text that needs to be translated
• msgstr can be blank,empty or text already translated (it will be ignored)
• ScribaCode will translate msgid content and put the tranlsation in msgstr
• Variables are not mandatory, but if you use them, you must indicate both the start and end variable symbols

Php Po file with a key and string content
Example:
msgid "MSG_WELCOME"
msgstr "Benvenuto"

msgid "MSG_GOODBYE"
msgstr "Addio"

msgid "MSG_LONG_TEXT"
msgstr ""
"line 1 "
"line 2 "
"line 3 "

• Only string data will be translated
• The text can span multiple lines as shown in the example
• msgid content will be ignored
• ScribaCode will translate msgstr content and put the tranlsation in msgstr
• Variables are not mandatory, but if you use them, you must indicate both the start and end variable symbols

XCode Localizable.strings
Example:
"greeting" = "Hello {name}";
"farewell" = "Goodbye {name}";

• Only string data will be translated
• Other types will not be translated
• Value can be an HTML but must have escaped html tags or url encoded
• Variables are not mandatory, but if you use them, you must indicate both the start and end variable symbols