Localization: English (UK)

[waydabber]

This is the localization thread for UK English localization. :)

[PuzzledUser]

Go for it. Now I'm apprehensive at the transcription from my previous dumb approach.

[waydabber]

Here is a localizable file.

en-GB.xcloc.zip

You can either use XCode (simpler) or right click and "Show package contents" and edit the en-GB.xliff file using Notepad.

You should simply add a new target state="translated" line to each translation unit with the translation. Here is an example:

Original:

      <trans-unit id="Color Depth" xml:space="preserve">
        <source>Color Depth</source>
        <note/>
      </trans-unit>

With translation:

      <trans-unit id="Color Depth" xml:space="preserve">
        <source>Color Depth</source>
        <target state="translated">Colour Depth</target>
        <note/>
      </trans-unit>

Note the new <target state="translated">Colour Depth</target> line.

Let me know if you need any help! :)

[PuzzledUser]

Noob: I'm scratting around looking for the original of the about 119KB original Localizable.xcstrings file (that I used in waydabber/BetterDisplay#2165 (comment)) so I can run a diff on it to discover my previous edits. I've poked around various packages and can't find it. My Friday afternoon job has thus stalled.

If you're still with me, where might I find that file, so I don't have to read all the strings again to find my previous dumb changes?

[waydabber]

You probably got it from here:

https://github.com/waydabber/BetterDisplay-localization/tree/main/BetterDisplay%20Localizations/en.xcloc/Source%20Contents/BetterDisplay/Localizable

But it might have been a different version, you can click on the History button to see earlier revisions.

[PuzzledUser]

OK, I used a bash script to parse my diff and edit the XML. I noticed one anomaly in that this trans-unit and source didn't match:

      <trans-unit id="Set as Favorite %lld%@" xml:space="preserve">
        <source>Set as Favorite %1$lld%2$@</source>
  <target state="translated">Set as Favourite %1$lld%2$@</target>
        <note/>
      </trans-unit>

I found 118 translations (i.e. one seemed to escape me in the process).

en-GB.xliff.zip
diff.txt

[waydabber]

Thank you, I'll add this to the next build! :)

[waydabber]

Hi everyone! 👋

I’ve added an “AI assisted” tag to this localization. This means that if no community update is made for the latest strings, AI may be used to help keep the translation up to date.

This can only apply this in cases where:

• AI can translate effectively from English to the target language, and/or
• the language has a large global user base and a strong online presence (which often improves AI translation quality).

Still, AI translations are never perfect, and your contributions make all the difference. AI is no substitute for human insight—so your contributions are always welcome and valued! Also, whenever you see something AI-generated, feel free to review and improve it — you can always check the changes with a GitHub diff.

Thanks a lot for your help and for being part of the project!

[PuzzledUser]

waydabber/BetterDisplay#2165 (reply in thread) I guess you will pop another localizable file: en-GB.xcloc.zip in here in due course.

[waydabber]

It is available in the repo here, but also here it is:

en-GB.xcloc.zip

Please note that as things went on, from time to time I updated the GB localization, simply replacing things like "color" to "colour" or where it felt like British people would say something differently... 😄 But I might have gotten it wrong at some places or maybe there is a need for some deeper changes here and there, so you might want to quickly check existing items as well. :)

[PuzzledUser]

Am I missing something new in the structure (since Aug 2024)? Now there are 2107 trans-unit elements, of which 2023 already have target state="translated". Mostly they contain the same string (which seems inefficient and awkward to see what needs attention).

I see strings such as Outdated License are some of the few without translations. Now I understand your generous approach. waydabber/BetterDisplay#4549

I've reviewed the 84 lonely trans-unit elements without current translations and added 7 new ones.

en-GB.xliff.zip

[waydabber]

Thank you! Yes, repeating the strings feels somewhat inefficient but without this Xcode will complain about the incomplete translation and there is no way to mark something not to be translated on a per language level.