Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial localization support #205

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Jonathan-Rosewood
Copy link
Contributor

These changes were made to start collecting information about possible problems with the ArmA localization system.

@Barbolani77
Copy link
Contributor

Question, the system accepts dynamic text? Reason: I have seen text with "Maru" and it should change to "Petros" depending on the edition. That may happen in several situations.

@Jonathan-Rosewood
Copy link
Contributor Author

Jonathan-Rosewood commented Nov 24, 2018

@Jonathan-Rosewood
Copy link
Contributor Author

You can do nested formatting.
For example, we have the strings - "Hello my name is Maru" and "Greetings from Maru".
Where the name may be one of several options that must also be translated into other languages.
For example, such as - "Maru" and "Petros".
To do this, we make the main lines with a name marker - "Hello my name is %1" and "Greetings from %1". And separate translation lines for names - "Maru" and "Petros".
When using, we format the main string by substituting the translated name as an argument.

hint format [ localize "str_antistasi_greetings", localize "str_antistasi_name_maru" ];
// Result if locale is English: hint format [ "Greetings from %1", "Maru" ];
// Result if locale is Russian: hint format [ "Приветствие от %1", "Мару" ];

@Barbolani77
Copy link
Contributor

ok, will start to work with this structure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants