aMule Forum
English => Translations (i18n) => Topic started by: aikishugyo on November 18, 2007, 04:31:04 AM
-
Hi,
I've volunteered myself to do a Japanese translation of the app strings, and man pages for amule. I don't know of a Japanese donkey/mule client for linux but I suppose there is one somewhere. However, since majority of Japanese users are Windows users, they don't have a problem with finding a local-language client---still, for the minority that likes open source software, I hope my efforts will make a difference. Considering that amule is cross-platform, I really hope the country with the most broadband service in the world at present (in hot competition with Korea IIRC) will make more use of amule, and maybe even attract developers.
After reading the Translation HOWTO http://www.amule.org/wiki/index.php/Translations (http://www.amule.org/wiki/index.php/Translations), and looking at the current status of translations http://www.amule.org/translations (http://www.amule.org/translations), I am confused by two things (I will continue looking through the forums of course):
1) what is amule.pot on the latter page (bottom link) for? From the former page (advanced section) I get the impression it is the same as source_strings.po
2) will the translation be for current (2.1.3) or only for the next (2.2.0) amule? In other words, will linux distros get the benefit of new translations pretty soon, or only with a new version of amule?
Sorry for dumb questions, if I find answers in the forums I will update.
Cheers,
Gernot
-
Hi Gernot,
Thank you a lot for your efforts! We appreciate this a lot.
The wiki-page is outdated. You'll find a ja.po file in the translation page very soon. (I one or two hours), which you may use for your translation.
The translation will only be for the next aMule, but we hope to release it soon...at least I hope so, since Kry is back again and should be able to continue his work.
kind regards
-
Got it! Thanks. I've emailed you a first attempt at editing the .po file (with Emacs), and hope the file encoding (UTF-8), and the header lines (one changed) are correct.
I'm afraid kBabel isn't letting me enter from my GNOME UIM---I suspect I'll sort this out tomorrow when I check to see how the equivalent KDE UIM is installed. Then I hope to be able to use kBabel.
And gtranslator simply crashes as soon as I try to do some work.
One more question, since the Wiki is out of date: can I still do tests of some sort on the .po files, or must I compile the entire source of aMule? Sorry, it is hard for me to tell which information on the boards is currently relevant.
Thanks,
G.
-
Please attach translations to the forum and don't send them to me. In case I'm away for a couple of days others can see the new translation as well and can commit it.
Your translation is fine for me, I'll commit it and you'll find a first version in tomorrows tarball or in one or two hours at the translation page.
Sorry, it is hard for me to tell which information on the boards is currently relevant.
I'm sorry about this, but our wiki was overrun by spam and is still closed.
Edit: I test translations by compiling with ./configure --disable-monolithic && make
-
Please attach translations to the forum and don't send them to me. In case I'm away for a couple of days others can see the new translation as well and can commit it.
Undertood, and thanks for the help. I attach the file below.
-
Hello, I attach a new version of the translation done on the weekend, about 50 strings done, and more on the way. But I have some questions---as I have trouble inputting Japanese with kBabel, and gtranslator crashes (still getting poedit to run with Japanese) I am using emacs for this task. Very simple, except I have to guess the format occasionally. Usually text is one line, which then ends up like this:
#: src/BaseClient.cpp:1873
msgid "Requested:"
msgstr "<Japanese term here>"
Very easy. But sometimes there is the confusing construction below, multiline:
#: src/BaseClient.cpp:1875
#, c-format
msgid ""
"Filestats for all sessions: Accepted %d of %d requests, %s transferred\n"
msgstr ""
Does that mean I have to add another line as follows, leaving the first one blank:
#: src/BaseClient.cpp:1875
#, c-format
msgid ""
"Filestats for all sessions: Accepted %d of %d requests, %s transferred\n"
msgstr ""
"<Japanese text goes here>"
Second, while doing the translation of the .po file, I notice that of course as yet there is no src/Preferences.cpp line for Japanese, similar to the below:
#: src/Preferences.cpp:619
msgid "Italian (Swiss)"
msgstr ""
Please advise.
Regards, Gernot
-
Thank you for the update.
Regarding your question: I think so as the other translations use the same format with an empty string in the first and the translation in the second line.
kind regards
-
Thanks!
Right, here's the next installment attached (179 strings done). I put another question in my edited post above regarding addition of Japanese to the preferences.
And another one---consistency in the strings:
a) folder=directory?
b) Url=URL?
Cheers,
Gernot
-
Thanks a lot, I actually forgot to add Japanese to the preferences as well - it will be there tomorrow 3:30am UTC+1 ;)
Consistency - I'm afraid we have no guidelines and everyone just writes it as one wants. I don't think that's so much of an issue for folder and directory as they are synonyms, but URL as an abbreviation should be in capital letters...mh, I'll have a look at it.
-
I feel a fear of losing my work coming on :-) What do I do to get the updated version without losing my translations? Can I safely follow the procedure outlined in the Wiki if I download a new amule.po from CVS?
-
Just download the translation from the translation page (http://www.amule.org/translations) and continue the work with this file. This way you won't loose anything.
-
Right, here is the next Japanese installment: 235 strings done so far.
-
Thank you, I've uploaded the updated translation.
-
I'm uploading another translation. Note: It seems that "Gui" and "Ed2k" are also not consistently spelled.
Cheers,
G.
-
Thank you, I've updated the translation. Could you please file a bug report at http://bugs.amule.org about these inconsitencies? I'll try to check this, but no promises.
-
Done bug report! I found several grammar and spelling mistakes also. It is really trivial to repair this in the amule.pot file. Hope I can simply upload a corrected version...
Here is a new Japanese translation. over 460 strings done now. Now that you've added Japanese preferences, I'll be able to compile it myself and check how it turns out (I was wondering before why my compilation wasn't producing Japanese options even though I had modified the pot directory Makefile and so on.)
BTW, is it okay to delete attachments to previous mails? The old ja.po files are not necessary anymore right?
Cheers,
G.
-
Hi aikishugyo,
amule.pot will be generated of the source code, so any changes will be lost once something changed in the source. But if you give me this file, I might change all the stuff in the source and the GUI. Thanks a lot for your effort!
I don't think it is necessary to delete the old attachments, but feel free to do so, if you want to. It's all in version control anyway.
Thanks for the update, you forgot a "\ņ" in your translated text, but I've fixed this.
P.S. You can see one screenshot of aMule in Japanese here (http://forum.amule.org/index.php?topic=13842.msg73207#msg73207).
-
Hi again,
amule.pot will be generated of the source code, so any changes will be lost once something changed in the source. But if you give me this file, I might change all the stuff in the source and the GUI. Thanks a lot for your effort!
No worries. I'll start a new thread on that once I've done, got a couple hundred more messages to look at though, one or two more evenings needed.
Thanks for the update, you forgot a "\n" in your translated text, but I've fixed this.
Oops, sorry about that.
P.S. You can see one screenshot of aMule in Japanese here.
Well, that looks very nice indeed, I am impressed! Nice skin too... I'll have to take a closer look at many of th translations, since it's not always clear how to translate for the final context from the original English in the .po file. Also, because of the Japanese use of the clumsy katakana syllabary (full-width, compared to the half-width ASCII and other Western characters) to transcribe Western words rather than using a few number of Kanji (pictographs), a lot of the messages can get unreasonably long for the given space provided. Frustrating!
Here the next batch, over 640 messages translated.
Cheers, Gernot
-
Hi Gernot,
does this still make sense? msgid "Command `%s' with pid `%d' has finished with status code `%d'."
msgstr "`%s' がステータスコード PID `%d' のコマンド `%d' で終了しました。"
Unfortunately the order of the arguments seems to be important here, so I changed the part with the %s with the term with the PID to preserve the order.
I've committed the update, if a change is needed for the above, I suggest fixing this with the next update on your side.
kind regards
-
does this still make sense? msgid "Command `%s' with pid `%d' has finished with status code `%d'."
msgstr "`%s' がステータスコード PID `%d' のコマンド `%d' で終了しました。"
Unfortunately the order of the arguments seems to be important here, so I changed the part with the %s with the term with the PID to preserve the order.
I've committed the update, if a change is needed for the above, I suggest fixing this with the next update on your side.
Oops, I'll make a note of that issue, thanks. Unfortunately, Korean and Japanese, which share a common grammar, are the reverse of English (and Chinese, whose grammar is similar to Western languages).
Here the next version, over 800 strings now translated, and a few spelling errors fixed in the English (I figured this would be good to do at short notice).
One thing about rates: in Japanese "N kB/s" becomes effectively "/s N kB". While it may not be critical to change the english everywhere, it should be noted that most Japanese are most certainly not fluent in reading English, especially technical English. Many of the messages that have an argument are separated from the message containing the unit and both will, if such translation is applied correctly, need to be modified. For the moment I've marked just the unit message in such cases.
Regards, Gernot
-
Adding a further update, over 900 messages translated now. I'll have to test extensively eventually, but I prefer to get as much out the door first.
-
Hi Gernot,
First of all, I found the solution for the word order problem.
msgid "Command `%s' with pid `%d' has finished with status code `%d'."
msgstr "PID `%2$d' のコマンド `%1$s' がステータスコード `%3$d' で終了しました。"
(Please review this particular string in the translation, I hope it is correct like this.)
I hope this helps you to improve the translation and make it more natural for Japanese.
Then I've committed the updated, thanks a lot for your work.
kind regards
-
First of all, I found the solution for the word order problem.
msgid "Command `%s' with pid `%d' has finished with status code `%d'."
msgstr "PID `%2$d' のコマンド `%1$s' がステータスコード `%3$d' で終了しました。"
Hello! Thanks, that does appear to be correct for Japanese usage. Before I continue, and change other strings, can I use this syntax in all cases now (even, if for example, there is only one variable)?
-
You can, but in the case of only one variable it doesn't make much sense to change the order, does it? This only serves to change the order of arguments.
To clarify this:
printf("%s %s %s", "one", "two", "three"); -> Output "one two three" (original order)
printf("%3$s %1$s %2$s", "one", "two", "three"); -> Output "three one two" (changed order i.e. use the third argument at the first placeholder, the first at the second placeholder and the second argument at the third)
-
To clarify this:
printf("%s %s %s", "one", "two", "three"); -> Output "one two three" (original order)
printf("%3$s %1$s %2$s", "one", "two", "three"); -> Output "three one two" (changed order i.e. use the third argument at the first placeholder, the first at the second placeholder and the second argument at the third)
Thanks, yes, got it (note: your post has an error: 3 2 1 -> 3 1 2). I'm attaching the next set, over 1000 translated strings. One question:
#: src/muuli_wdr.cpp:799
msgid "Packages saved by I.C.H. :"
msgstr "I.C.H.に助かったパケット："
Is that right, or should that be "Packets saved by I.C.H.:"?
Thanks, Gernot
-
Thanks for the update, committed.
It should be packets saved by I.C.H., at least this is how the variable's called. Could you please add this to your list of corrections and language inconsistencies?
-
OK, noted. Here is the next instalment of the Japanese translation, up to 1100+ strings. I see about 26 disappeared from the total. Good! :-)
Regards, Gernot
-
We were probably talking too much...;) No, these were debug output strings which are only directed at us and shouldn't be translated at all, because we don't understand debug messages in Japanese or Mandarin. ;)
Thanks for the updated translation, I've committed it.
-
Heh! Indeed.... heck, I don't understand them either ;D
Here the next instalment, over 1270 strings done now.
Quick question: what's the best format for 'error' notes? An edited version of the main English .pot file, or it's diff file, or some other format easier to discuss on the forums? I don't see many people liking the idea of line numbers, or verbatim copies from the .po file. I don't think it's much fun either, way too easy to lose track of things :P My notes are on paper at the moment... questions too, mind you, since I can't always tell from the English what the precise meaning should be.
Regards, Gernot
-
Sorry for the delay in committing the update and thanks.
Well, I would like to know what's wrong and where it's wrong, i.e. file and line number. So I would suggest something like:
amule.cpp:123 "This stirng is wrong."
correction: "This string is correct."
I'll try to help you with any questions, provided I know what the English versions means...;)
-
OK, I can do that. However, not right away... it may only be possible after Christmas ::)
Here is the first complete Japanese translation. I'm well aware that the translation job is never done, that there will always be catching up to do in step with development, and that in many many cases I have to improve/shorten/reword the strings to fit the context. I'll be trying to test the Japanese language-enabled aMule in parallel with an English language aMule to compare. This could take some time, unfortunately. I'm open to any suggestions, and I'll see what the Chinese language translators have done in comparison too.
In case I don't get a chance, Merry Christmas/Happy holidays to everyone here!
Best regards,
Gernot
-
Um... Hi wuischke, did you miss my post here? I see you replied to many other language posts since Christmas. I'm keen to start on the error checking with a full ja.po. Thanks!
-
I'm sorry I oversaw your update, thanks for pointing this out. I've committed it now.
There were some little problems, but only one might be critical. Have a look at line 6959 in the updated translation and see if it looks ok to you. (You had the %i.%i.%i string twice in your translation.)
-
There were some little problems, but only one might be critical. Have a look at line 6959 in the updated translation and see if it looks ok to you. (You had the %i.%i.%i string twice in your translation.)
Hi, had a look. Yes, probably pasted i incorrectly instead of li at some point. Sorry.
l.45 is a double line Japanese string, I shortened it by 2 chars, maybe it will fit one line?
l.117 is also a double line. I shortened by 4 chars, maybe it will fit in one line?
I also saw that some Japanese strings are two lines even though they are shorter than the original English lines. Why is that? It confuses me a bit...
New ja.po attached (4 strings translated, a few modified). Ah, "quote" reply doesn't do it for me. I'll attach file to a "reply" post.
OK, I'll be concentrating on compiling the errors I perceived in the English strings from now on.
Cheers!
-
New ja.po attached here.
-
Thank you, committed.
-
Hello, just updated the ja.po file. Sorry, busy with work and all, will list found errors as promised as I find time. :-[
Regards, Gernot
-
Hi Gernot,
thanks for the update, I've committed it.
Don't worry about being busy, there's a very simple rule in aMule development: real life > aMule
But, of course, I'm looking forward to seeing what you've found in our string database...
kind regards
-
Hi. I tried to make translations look more natural...
-
Thank you for your work. Would you be so kind to have a look at the fuzzy and missing strings, too?
-
Sure. An updated version is here.
-
Thanks a lot, the update has been committed!
One thing:
#: src/ExternalConnector.cpp:185
#, c-format
msgid ""
"\n"
"All commands are case insensitive.\n"
"Type '%s <command>' to get detailed info on <command>.\n"
msgstr ""
"\n"
"すべてのコマンドは大文字と小文字を区別します。\n"
"'help %s <コマンド>'を入力することで<コマンド>の詳細の情報が表示されます。\n"
Can you please confirm that the "%s" is at the correct position? Unfortunately I don't speak Japanese and just put it next to the word I understood...
-
Oh sorry, it's a mistake of mine.
The correction is :
#: src/ExternalConnector.cpp:185
#, c-format
msgid ""
"\n"
"All commands are case insensitive.\n"
"Type '%s <command>' to get detailed info on <command>.\n"
msgstr ""
"\n"
"すべてのコマンドは大文字と小文字を区別しません。\n"
"'%s <コマンド>'を入力すると<コマンド>の詳細情報が表示されます。\n"
-
Thank you, corrected. :)
-
Hello all, back again after a hiatus caused by the wedding preparations and the aftermath, whew.....
Baketz, many thanks for improving the translations, as you probably noticed I spent most of the effort getting the strings translated without checking what the stuff actually meant in practice. Never got time to run the Japanese version next to an English one to compare where what appears. I'm looking forward to trying out the 2.2.1 and seeing how the Japanese looks. I'll look into this forum regularly and submit improvements where I can. I'll be more than happy if you correct whatever I submit ;D
Cheers, Gernot
-
I'm glad you're back, congratulations to your marriage!
We've started a first effort to improve the quality of the English strings (thanks to greek (http://forum.amule.org/index.php?action=profile;u=10937)), too, if you want to support us, please contact me.
-
I has been 4 years, much has happened (none of it particularly bad!), and I am back to help with an updated Japanese translation.
-
Nice to see you again! Welcome back to translating unmeaningful and uninteresting strings :)