-
Notifications
You must be signed in to change notification settings - Fork 8
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.
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
Japanese language resources #424
Comments
Oh, thank you, I’ve just had a nap under a big blackout, and woke up to appliances turning on. |
P.S. These are default settings, and suitable for your deed. |
Sorry, I don't understand. Is "Translate with original" some kind of tool? |
It’s going to be some kind of tool, under Tools menu, that will help to preserve what you have already done. I’m writing it, you forced me. Maybe tonight. |
@coolvitto If you translated more, use Tools → Translate with → Another uorig. Default settings are probably enough, except priority: you may have edited some string. I modified locale.xml, and in those places where I’m sure I removed comment.
e{1} is version name like “e12.1” (emoji 12.1). You may leave as is, or find some ideograph, IDK. |
*.utran actually carries the original someone actually translated. *.uorig does not, that’s why I said: save original. |
@coolvitto What’s going on now? |
Is there anything I can do for you? |
|
I’m working on other feature of UTranslator — “mark as bad”. I wanted to roll out first L10n’s, and did not finish this feature, as there were no languages I don’t know. Now I’ll have. When I finish, I’ll release 0.4. |
ja.uorig has already been sent. Place "en.uorig" and "ja.uorig" in the uorig folder. |
@coolvitto You have already translated something more. To port your job, use Tools → Translate with → Another *.uorig. |
Repeating for the third time.
|
@coolvitto
|
UTranslator 0.4 with “Mark as bad” released. You use 100% and HiDPI is not for you, but I replaced pixel images with SVG. |
Updated to 0.4. However, will the ja.uorig I attached previously not work? |
No, you should create using File/New (or take from my repo, I already created) ja.UTRAN. |
Of course, it’ll be a translation, but… empty (0 translated of almost 2000), and you should port your work using “Translate → Another *.uorig”. |
Hmm, I'm not good at English so I can't understand it well. Do you mean open ja.utran in 0.4 and save it as ja(1).utran for example? |
I invented this approach to L10n for myself, but it proved the best for translating a living program that’s released frequently. |
The common approach is Gettext, and it’s suitable for living program, and cool for unofficial translations, but suitable for short strings only. |
Ok, I understand. |
What is general operation? |
Do you mind finding and replacing apostrophes to U+2019? Are there programmer’s apostrophes just by coincidence or intentionally because of trobles? |
Rjng Rejang: same |
I wrote L10n of punctuation.
Which are Japanese counterparts? |
For now I took: fullwidth colon FF1A + space 20; ideo comma 3001; fullwidth semicolon FF1B; fullwidth parentheses FF08/09. |
Repeat question: is italic OK in Japanese, or disable it specially for Japanese? |
Happy New Year!!
I'm back.
It looks like you've updated to v2.9.4.
Thank you for your hard work.
I can't open the "Japanese language resources" thread on Github.
I've confirmed many of the issues through email, but I have a full-time job starting tomorrow, so it may be difficult to address all of the issues.
> is italic OK in Japanese, or disable it specially for Japanese?
When you want to emphasize something in Japanese, you can use italics. As for font decoration, you don't need to pay special attention to Japanese, so I think it's fine to use it the same as other languages.
…________________________________
差出人: Mercury13 ***@***.***>
送信日時: 2025年1月5日 7:30
宛先: Mercury13/unicodia ***@***.***>
CC: coolvitto ***@***.***>; Mention ***@***.***>
件名: Re: [Mercury13/unicodia] Japanese language resources (Issue #424)
Repeat question: is italic OK in Japanese, or disable it specially for Japanese?
—
Reply to this email directly, view it on GitHub<#424 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGH4IK4YVPSV7F5F2XXIWCD2JBOIRAVCNFSM6AAAAABSWKODZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZRGQZDQMBWGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Of course, do it as slow as you wish. I added a little more strings. |
If you update *.utran, I addressed some of the issues there. But I cannot address all, of course. |
I’m working on L10n task for Unicode 17. Approvals are incomplete, and maybe there’ll be more blocks. |
@coolvitto Could you do some translation? Even two strings a week is OK. |
I’m waiting for January meeting. Probably they’ll release U17 alpha. |
I'm currently busy with other work, so I'll help with the translation when I have some free time. |
Anyway, I made a task for you in advance. Everything I know about U17 is already in language resources. |
@coolvitto As you see, translation to Chinese failed because of accident at the other side. |
Although it is not complete, I have created a Japanese language file.
I would be happy if you could add it to the app.
Japanese_Resources.zip
Best regards,
by coolvitto
The text was updated successfully, but these errors were encountered: