Fichiers De Localisation
Skedar Lokalizimi
ملفات الترجمة
Supported
localization files
Flutter ARB files
CSV files
INI files
i18next JSON files
Key-Value JSON files
JSON files
Gettext PO and POT files
Java Properties files
NET resources (RESX, RESW)
Qt Linguist TS files
Apple Strings files
Apple Xcstrings files
iOS XLIFF files
XLIFF 1.2 files
Angular XLIFF files
Angular XMB files
Angular XTB files
Rise 360 XLIFF files
Excel XLS and XLSX files
Android XML files
YAML files
Sample file
View file
Download
/*Please don't change the name of the application*/
"app.name" = "TODO List";
/*Fuzzy*/
"app.login.text" = "Enter your credentials below to login";
"app.login.message.success" = "Login successful !\nWelcome back %s !";
"app.login.message.error" = "Make sure you've entered the correct username and password";
"app.login.password.forget" = "I forgot my password";
"app.login.password.reset" = "Enter your address in the field below. A new password will be sent to your inbox.";
"app.register.text" = "Sign up for free! No credit card required!";
"app.register.message.success" = "Thank you for signing up !\nPlease check your email address to activate your account.";
"app.register.message.error" = "We were unable to sign you up.\nPlease correct the marked fields.";
"app.menu.terms" = "Terms and conditions";
/*form_label*/
"app.login.label" = "Username";
"app.users.active" = "Just one user online";
/*form_label*/
"app.login.pass" = "Password";
.strings files
What are iOS strings files
The standard strings file format consists of one or more key-value pairs along with optional comments. The key and value in a given pair are strings of text enclosed in double quotation marks, separated by an equal sign, and terminated by a semicolon. Although the inclusion of comments is optional, they do provide a useful way to communicate contextual information to the translator about how each string is used.
Good to know
- To work with POEditor, .strings files need to be encoded in UTF-8, like the rest of our supported formats, although Apple recommends UTF-16.
- Comments are marked with /* .... */
- Terms take their comments from above. If there are comments after the term, on the same line, the comment will be taken by the next term.
- There are no plurals (only term – translation pairs), context and reference.