Localization: Japanese

[waydabber]

Japanese localization, thanks to @SakiPapa

waydabber/BetterDisplay#1343

[waydabber]

[nyuyuyu]

Hi @waydabber

I found a mistake in Japanese translation. Fixed in ja.xcloc.zip

The differences are as follows.

❯ diff -r -u ./ja.xcloc.orig ./ja.xcloc
diff --color=auto -r -u ./ja.xcloc.orig/Localized Contents/ja.xliff ./ja.xcloc/Localized Contents/ja.xliff
--- ./ja.xcloc.orig/Localized Contents/ja.xliff 2023-09-01 22:02:21
+++ ./ja.xcloc/Localized Contents/ja.xliff      2023-09-06 11:31:15
@@ -1616,7 +1616,7 @@
       </trans-unit>
       <trans-unit id="Disable All Protections" xml:space="preserve">
         <source>Disable All Protections</source>
-        <target state="translated">すべてを保護</target>
+        <target state="translated">すべての保護を解除</target>
         <note/>
       </trans-unit>
       <trans-unit id="Disable Auto-Connect" xml:space="preserve">
@@ -2080,7 +2080,7 @@
       </trans-unit>
       <trans-unit id="Enable All Protections" xml:space="preserve">
         <source>Enable All Protections</source>
-        <target state="translated">すべてを保護解除</target>
+        <target state="translated">すべてを保護</target>
         <note/>
       </trans-unit>
       <trans-unit id="Enable Apple display hardware brightness control" xml:space="preserve">

I was confused because in Japanese it means the exact opposite.

[waydabber]

@nyuyuyu - Thank you!
@SakiPapa - Fyi!

[SakiPapa]

Thank you @nyunyu san.

It did indeed mean the opposite. I'm very sorry, but my translation was wrong.

[waydabber]

@SakiPapa - no problem, you did a great job!

[waydabber]

Imported the updated translation for the next app version!

[waydabber]

Full localization based on v2.0.10:

ja.xcloc.zip

[waydabber]

I updated the localization file in the waydabber/BetterDisplay#2165 opening post to reflect the latest v2.1.0 pre-release version.

[SakiPapa]

Localization based on v2.1.1-b25108-pre
ja.xcloc-2.1.1-b25108-pre.zip

[waydabber]

Thank you!

(note: the interim pre-release strings might not be final so it's ok if you don't rush to translate all such interim versions - don't want you to get frustrated! :))

[SakiPapa]

Japanese localization based on BD 2.1.3.
ja.xcloc-2.1.3.zip

[waydabber]

Thank you!

[waydabber]

I uploaded an interim build to the opening post here: waydabber/BetterDisplay#2165

[SakiPapa]

Japanese localization based on BD 2.2.0pre :-)
ja.xcloc-2.2.0pre.zip

[waydabber]

Thank you!

[waydabber]

I made some changes in how you BetterDisplay localization works. Here is the announcement: waydabber/BetterDisplay#2165 (comment)

[SakiPapa]

I updated Japanese localization based on 2.2.0pre 04/01/2024.
ja.xcloc-2.2.0pre-04012024.zip

[waydabber]

Thanks @SakiPapa, committed to the main branch!

[SakiPapa]

I added Japanese localization for 2.2.0 BD released 04/13/2024.
ja.xcloc-2.2.0release.zip

[waydabber]

Thank you!

[waydabber]

Hmm. Are you sure? I see the following untranslated items in the repo:

[SakiPapa]

The cause was probably a broken configuration in the GitHub Desktop App. (Caused by some mistake in my operation) I fetch GitHub DesktopApp then use "Show in Finder" and open the local ja.xcloc file, it is different from the file on GitHub. If I edit this file and add translations, it does not sync with GitHub. So I after fetch again, then the file that does not contain the recently added strings saved locally. When I fetch on the GitHub website, the file in my fork syncs correctly with the original. (It contains untranslated strings. Now, my GitHub Desktop App, I decided to rebuild the repository. It seems to be syncing correctly again. Maybe I should have use “Rebase". 2024年12月29日(日) 8:18 waydabber ***@***.***>:

…

Hmm. Are you sure? I see the following untranslated items in the repo: Screenshot.2024-12-29.at.0.17.20.png (view on web) <https://github.com/user-attachments/assets/a7d16d09-280e-463a-8466-bcc93f732bd0> — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZK5UQYINWDOHBHLLCPX5TD2H4WUXAVCNFSM6AAAAABBLZV3ICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGU2TINBWG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- 杉崎 忠久 Tadahisa Sugisaki ***@***.***>

[SakiPapa]

The GitHub Desktop issue has been resolved, I believe. I've sent a PR to you. 2024年12月29日(日) 8:18 waydabber ***@***.***>:

…

Hmm. Are you sure? I see the following untranslated items in the repo: Screenshot.2024-12-29.at.0.17.20.png (view on web) <https://github.com/user-attachments/assets/a7d16d09-280e-463a-8466-bcc93f732bd0> — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZK5UQYINWDOHBHLLCPX5TD2H4WUXAVCNFSM6AAAAABBLZV3ICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGU2TINBWG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- 杉崎 忠久 Tadahisa Sugisaki ***@***.***>

[SakiPapa]

The word "visual" has many meanings, so it is difficult to apply an appropriate translation. There are no Japanese word of same concept for "visual". I use different Japanese depending on the case.

For the string "Identify Visually" I translate it like "Identify by the way it is displayed". The meaning may be a little difficult to understand what it means.

[waydabber]

This feature just creates a temporary flash on the screen so in a multi-display setup it is easier to pinpoint which display the user is managing. So you can name the feature simply "Identify screen" or "Flash the screen" or something similar. :)

[waydabber]

But I am not seeing a PR. :)

[waydabber]

But no worries, I just downloaded it from your fork directly.

[SakiPapa]

I was changing translation for "Identify Visually" as "Identify screen", and merging. Just I sent PR.

[waydabber]

Got it, thank you! :)

[SakiPapa]

It seemed that my PR was too late about "Identify Visually" so I send PR again, sorry (^_^)

[waydabber]

Thanks. I updated the latest internal pre-release with the translation!

[SakiPapa]

Hi,
On the key "%1$@ This license is currently active on %2$lld installations.",
the placeholder "%2$lld" is the times(number) of installations ?

[waydabber]

Yes. This text looks like this. The first one is just the placeholder for an icon.

[waydabber]

Hi @SakiPapa - added some new texts still. Will soon do a full release in case you want to bump up the translation to 100% before that! Thank you! :)

[SakiPapa]

Hi,

The following strings,

"right bottom" and "bottom right"
"right top" and "top right"
"left bottom" and "bottom left"
"left top" and "top left"

What is the difference between them?

[waydabber]

Hi there,

these are for the Shortcuts App Intents variant of the "moveTo" CLI feature that moves a display relative to an other display. Right bottom will result in the display moved to the right side of the display, aligning the bottoms. Bottom right will move a display to the bottom of an other specified display, aligning their right side. If I remember correctly. But it's going to be difficult for the user to understand this and will need to experiment with it a bit and I don't think this will be an often used feature, so the best might be to simply translate as is, not explaining it too much. :)

[waydabber]

[SakiPapa]

Hmmm

In English, “up” and “down” are written before “left” and “right”.
So Apple uses
“top right”.
but not use
“right top”.
(Note: Apple uses “right top middle” or “right top front” and so on.)

In Japanese, “left" and "right” is written before “up" and "down”. This is a rather rigid custom.
So, most Japanese should feel
"右上" (right-top) is correct but
"上右" (top-right) is incorrect strings.

It is interesting these opposite order between in Japanese and English. This may be because Japanese is a TTB (top to bottom) language, not LTR. (^_^) <--like this emoji.

I'ill consider for a while if another expression is possible :-)

[waydabber]

From grammatical standpoint "right top" does not sound right at all - the naming here actually simply followed the naming of an internal enum indicating "align right, then anchor at the top corners" (or the other way around, can't remember exactly lol - during testing it was counterintuitive even for me). Since this is a rather obscure feature, I would not worry much about it, the main point is that it should follow some kind of logic (which it does) and should be distinct in the list (which is) and the user will try which one is the best. :)

[SakiPapa]

I've decided to translate "top right" as "上-右" (top-right) also "right top" as "右-上" (right-top).

Thank you for your kind information.

Also I may have found a misspeled word in the key,

"Change the conneciton state of ${displayEntity} to ${onOff}."
conneciton --> connection

(^_^)v

One more question.
What is "TODO" ?
Is there any "TODO Display" hardware, or it means "display todo lists"?
Please let me know. m(-_-)m

[waydabber]

Sorry, the "TODO" thing was just some unfinished code. Not there anymore. :)

[SakiPapa]

#98 Update localization
Translated new strings.
Update localization.
Removed unnecessary spaces for separation.

[waydabber]

Thank you! 🎉

[waydabber]

Thanks, fixed the typo (connection)!

[SakiPapa]

Abt the key

"Turn Picture in Picture configuration ${streamId} for ${displayEntity} to ${onOff}."

May I translate the strings as,

"Turn Picture in Picture for ${displayEntity} with PinP configuration ${streamId} to ${onOff}."

?

[waydabber]

Yes, that is fine, thank you!

[SakiPapa]

Thank you.
PR update localization for new strings.

[waydabber]

Thank you!

[waydabber]

Hmm. Where? :)