diff --git a/localization.html b/localization.html index 826ca8c..4b304ad 100644 --- a/localization.html +++ b/localization.html @@ -83,6 +83,15 @@ font-style: italic; background-color: #FFFF77; } + dl { + margin-left: 10px; + } + .cond { + background-color: lime; + } + .repl { + background-color: yellow; + } @@ -110,7 +119,7 @@
  • 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 be consistent within each language, for example check other strings 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.
    • @@ -122,20 +131,43 @@
  • 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

    +

    Something like {0} in a string means it is replaced with the number 0 parameter. It should say in a comment what it gets replaced with (although most of the time it's clear from context already).

    -

    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}'').

    +
    +
    Example: Join #{0}
    +
    When {0} is joshimuz turns into Join #joshimuz
    +
    -

    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:

    - +

    Replacements use the MessageFormat class. Mostly it's enough to just stick close to the template.

    + +

    Important: Any single quote (') in a string that contains a replacement needs to be escaped with a single quote (e.g. Can''t join ''{0}'').

    + +

    Choice

    +

    The more advanced {0,choice,<choices>} pattern is used to decide between two strings depending on the value in the number 0 parameter. This is commonly used to decide between a singular and plural form.

    + +
    +
    Example: Join {0,choice,1#channel|1<{0} channels}
    +
    +
    When {0} is 1 turns into Join channel
    +
    When {0} is 2 turns into Join 2 channels
    +
    When {0} is 30 turns into Join 30 channels
    +
    + +
    +
    Example: {0} {0,choice,1#Hour|1<Hours}
    +
    When {0} is 1 turns into 1 Hour
    +
    When {0} is 2 turns into 2 Hours
    +

    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).

    +

    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.

    + +

    Note: The names of contributors to each language (as registered on POEditor) are added to the top of the language 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).