Translate Chatty to main page

Parts of Chatty can be translated into different languages, and you can help!

Getting started

Join the localization project and tell me the account name you used so I can approve it. The best way is via #localization on Discord, but you can also send a mail. If the language you want to work on hasn't been added yet, tell me.

Remember that you can also join languages that have already been completely translated, since future Chatty updates will likely also require more or updated translations. This is especially true now, since still not all GUI parts have been added for localization yet.

Note that not everything can be translated yet, and the help pages probably won't be at all, since it would be too much work to keep updated. My goal for now is to make the basic functions of the program more comfortable to use for people who don't speak English as their first language.

Translation Guidelines

• You don't have to translate everything. If there is no good translation for something, just keep it in English (this especially applies if the English term is commonly used in that language and better fitting).
• Strings that aren't translated will automatically fallback to English, so please don't just copy the English strings to fill translations, unless the English string is the translation (see previous point).
• If you're translating a term specific to Twitch or Streaming, try to use the "official" translation from the Twitch website.
• Try to be consistent within each language, for example check other translations for already used terms.
• Try to replicate things like strings ending with a colon (e.g. Language:) or HTML codes.
• In some cases (like button labels) it can be important that the translated text is not too long, so it may be necessary to rephrase things.
• Translations that are marked as Fuzzy should be reviewed again, usually because the original string has changed and the translation may have to be updated. You can filter and order by Fuzzy strings. If you are satisfied that the translation is correct, you can remove the Fuzzy flag.

Questions / Discussion

• The comments for a specific translation item sometimes give additional hints about the string and can be used for basic discussion.
• Another (probably better) place to discuss things is #localization on Discord.

Replacements

Something like {0} in a string is replaced with a certain value, for example in Join #{0} the {0} is replaced with the stream name (e.g. resulting in Join #joshimuz).

Replacements use the MessageFormat class, you can read that documentation if you're interested, although mostly it's enough to just stick close to the template. One important thing is that any single quotes need to be escaped with a single quote (e.g. Can''t join ''{0}'').

The more advanced choice pattern is commonly used for plurals: Join {0,choice,1#|1<{0} }{0,choice,1#channel|1<channels}. In this example there are two separate choice patterns ({0,choice,<choices>}), both using the first parameter (0), which contains the number of channels:

• The first one {0,choice,1#|1<{0} } outputs the number and a space ({0} ) only if it's greater than one.
• In the second one the choices are "1#channel" and "1<channels", meaning if the parameter is 1 it will be replaced with "channel", if it's 1 or greater it will be replaced with "channels" (the plural). In this case the number should never be 0, so that's not a consideration.

After Translation

Translations are commited to the repository by myself, since the files have to be converted into the format I want (e.g. proper structure and order of items). The process is mostly automated. It also adds the names of contributors to each language at the top of the file (if you want to be excluded from that or want to appear with a different name, let me know).

Other

Changes of the original English strings have to be done via GitHub (the normal way via Pull Requests).