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.

Sign up for GitHub

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

Jump to bottom

Localization: Japanese #1

Open
waydabber opened this issue Aug 27, 2023 · 148 comments
Open

Localization: Japanese #1

waydabber opened this issue Aug 27, 2023 · 148 comments
Assignees
@SakiPapa
Labels
localization ready Included in the stable release

Comments

@waydabber
Copy link
Owner

waydabber commented Aug 27, 2023 •
edited
Loading

Japanese localization, thanks to @SakiPapa

waydabber/BetterDisplay#1343
@waydabber waydabber self-assigned this Aug 27, 2023
@waydabber
Copy link
Owner Author

Screenshot 2023-08-28 at 18 57 01

@waydabber waydabber reopened this Sep 1, 2023
@waydabber waydabber changed the title Add Japanese localization Localization: Japanese Sep 1, 2023
@nyuyuyu
Copy link

nyuyuyu commented Sep 6, 2023

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
Copy link
Owner Author

@nyuyuyu - Thank you!
@SakiPapa - Fyi!

@SakiPapa
Copy link
Contributor

SakiPapa commented Sep 6, 2023

Thank you @nyunyu san.

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

@waydabber
Copy link
Owner Author

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

@waydabber
Copy link
Owner Author

Imported the updated translation for the next app version!

@waydabber
Copy link
Owner Author

Full localization based on v2.0.10:

ja.xcloc.zip

@waydabber
Copy link
Owner Author

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

@SakiPapa
Copy link
Contributor

SakiPapa commented Dec 5, 2023

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

@waydabber
Copy link
Owner Author

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
Copy link
Contributor

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

@waydabber
Copy link
Owner Author

Thank you!

@waydabber
Copy link
Owner Author

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

@SakiPapa
Copy link
Contributor

SakiPapa commented Jan 3, 2024

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

@waydabber
Copy link
Owner Author

Thank you!

@waydabber waydabber transferred this issue from waydabber/BetterDisplay Jan 3, 2024
@waydabber
Copy link
Owner Author

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

@waydabber waydabber removed their assignment Jan 4, 2024
@SakiPapa
Copy link
Contributor

SakiPapa commented Jan 7, 2024

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

@waydabber
Copy link
Owner Author

Thanks @SakiPapa, committed to the main branch!

@SakiPapa
Copy link
Contributor

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

@waydabber
Copy link
Owner Author

Thank you!

@SakiPapa
Copy link
Contributor

Hi,
Updated Japanese localization for 11/19/2024.
ja.xcloc-11192024.zip

I translated "unexposed" refresh rate, as "undiscosed" refresh rate.

@waydabber
Copy link
Owner Author

Thank you @SakiPapa! The translation now stands at an astounding... 99%!

:)

@SakiPapa
Copy link
Contributor

SakiPapa commented Nov 22, 2024 •
edited
Loading

Hi,
Updated Japanese localization for 11/19/2024 23:17 change.
Also includes some minor translation improvements.
ja.xcloc-11192024a.zip

@waydabber
Copy link
Owner Author

Thank you! Just in time to have it addded to the v3.2.0 pre-release that is now available. Japanese now stands at 100% :)

@SakiPapa
Copy link
Contributor

SakiPapa commented Dec 9, 2024

I finally decided to create a branch of BetterDisplay on GitHub.
I've sent you a readme.md PR.
Hopefully I am using GitHub correctly!

@waydabber
Copy link
Owner Author

Nice! :)

@SakiPapa
Copy link
Contributor

I don’t really know what I must do next :-o

@waydabber
Copy link
Owner Author

Whenever there is a change in the repo, you simply need to update your fork, work on it and then add a PR.

But for me getting zips is perfectly fine (in fact it's a bit easier) - however you having a fork and working on that might be beneficial for you as it can help you track changes and update your fork even as you work. But use this only if it really helps you - if you feel it just complicates your life, simply attach zip files. :) Either way, I am really grateful for your translations! :)

@SakiPapa
Copy link
Contributor

Hi, I had to resolve a conflict with GitHub Desktop last night (;o;)
I think I have solved the problem (^^);

Time for you is precious because you have to develop software and solve user support so on at the same time. I would prefer to choose a method that requires less effort on your part if possible. However, I would like to try to use GiHub for a while. This way would be better if more than one person is involved in the Japanese localization in future (^_^)

@waydabber
Copy link
Owner Author

Of course. GitHub is fine and is indeed better for collaboration.

@waydabber
Copy link
Owner Author

Also, make sure you update your fork from the upstream to make sure you are working on the latest localization! :)

@SakiPapa
Copy link
Contributor

Sure, thnaks a lot --- Arigatou gozaimasu!

@SakiPapa
Copy link
Contributor

I've added localization (with some corrections).
Also updated the description in README.md.

May my deeds are right :)

@SakiPapa
Copy link
Contributor

SakiPapa commented Dec 28, 2024 •
edited
Loading

I am attaching a translation from yesterday's main ja.xcloc. I believe there are no missing strings.

Some words for previous translations I'd corrected for these couple of days will have been lost. That will be checked after this. I have the file locally.

ja.xcloc-12272024.zip

Also, I discarded comments from my fork to solve the conflict.
I click "Sync fork" my "BetterDisplay-localization" fork, now it is seems in sync with the main.
I will Sync fork again after you post the ja.xcloc I sent you. Or should I upload the ja.xcloc to my fork and PR it?

Sorry for the inconvenience.

@SakiPapa
Copy link
Contributor

I'm sorry but the ja.xcloc file you recovered seems no new strings you added recently...may be 11 strings.
What is the safest way to recover (merge) lost strings?

The lost 11 strings are followings

"%@ Certain displays are set to hide the menu bar icon, which may override this setting."

"By default the app orders display first, then virtual screens, alphabetically. By providing an ordering string, you can redefine the data which serves as the basis of the alphabetical order and mix the virtual screen among the displays as well."

"Click Here To Allow Sleep"

"Enabling this option removes the menu bar icon when only this and other similarly marked displays are present. Use this setting when you don't need any of the app's features for this display and want to free up menu bar space."

"Hide menu bar icon when no other displays are present"

"Ignore for built-in display auto-disconnect"

"Prevent Sleep While Connected"

"This applies both to physically connecting an external display and using the app to reconnect one. However, the app will not reconnect the built-in display if you allow all displays to be disconnected!"

"Use %@ as menu icon when the app is preventing display sleep"

"Use an alternate icon when the app is configured to prevent display sleep."

"When enabled, this display will not trigger the disconnection of the built-in display when it is set to disconnect upon the connection of an external display."

@waydabber
Copy link
Owner Author

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

Screenshot 2024-12-29 at 0 17 20

@SakiPapa
Copy link
Contributor

SakiPapa commented Dec 29, 2024 via email

@SakiPapa
Copy link
Contributor

SakiPapa commented Dec 29, 2024 via email

@SakiPapa
Copy link
Contributor

SakiPapa commented Dec 29, 2024 •
edited
Loading

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
Copy link
Owner Author

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
Copy link
Owner Author

But I am not seeing a PR. :)

@waydabber
Copy link
Owner Author

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

@SakiPapa
Copy link
Contributor

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

@waydabber
Copy link
Owner Author

Got it, thank you! :)

@SakiPapa
Copy link
Contributor

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

@waydabber
Copy link
Owner Author

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

@SakiPapa
Copy link
Contributor

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
Copy link
Owner Author

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

Screenshot 2025-01-14 at 11 14 35

@waydabber
Copy link
Owner Author

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! :)

@waydabber waydabber added the ready Included in the stable release label Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SakiPapa SakiPapa

Labels
localization ready Included in the stable release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@waydabber @SakiPapa @nyuyuyu