Community
Participate
Working Groups
Build ID: N/A Steps To Reproduce: Hello everyone, We are now translating some of help files in Japanese. We want to integrate them into the language pack. More information: Previous Japanese language pack for 3.1 and 3.2 included translated help files.
Mori-san, could you please attach a help file to this bug so we can discuss the best way to integrate it with Babel ? This enhancement sounds like a good idea to me.
Created attachment 123469 [details] partially translated help files of WTP and Mylyn Antoine-san, Thank you for your comment. I put a sample in some html files. This sample is partially translated, and now still under translation. And we are considering about the final format of it; html files, compiled help file, jar file, etc. We also appriciate your proposal.
Mori-san, here is a first suggestion. You should package the help files in a separate fragments following the rules described in this article: http://www.eclipse.org/articles/Article-Speak-The-Local-Language/article.html Particularly referring to the structure this image shows: http://www.eclipse.org/articles/Article-Speak-The-Local-Language/images/figure001.png I think Babel could offer a repository that would contain translations of files. And we would do the packaging and distribution work ourselves. For now you would need to do the work of hosting the translated files and build the fragments. I am asking the AC in a separate bug.
Antoine-san, Thank you for your suggestion. I had some discussion with Japan working gourp members. And we accept your proposal. According to our current plan, we will finish the tranlation and review of help files at the end of March. We will be very happy if the repository would be ready in a short time.
(In reply to comment #4) > Antoine-san, > Thank you for your suggestion. I had some discussion with Japan working gourp > members. And we accept your proposal. Thanks for accepting it. However at this point we are unsure as to the best solution to adopt, and it is likely we won't have a solution by March. If you look at the ongoing discussion on the bug 211806, and the one I spawned with the AC: 262124, we have come to know that a technology that would work for translating help files would be to use something that is already in use at Aptana. I contacted the Aptana team and it seems there might be a patent problem to consider: http://dev.eclipse.org/mhonarc/lists/babel-dev/msg00633.html http://dev.eclipse.org/mhonarc/lists/babel-dev/msg00634.html http://dev.eclipse.org/mhonarc/lists/babel-dev/msg00635.html We are going to discuss this in depth with Aptana and the Eclipse Foundation; then we will come back to you. Of course you are welcome to dial in the call, however I believe this is the middle of the night for you, so I will try to keep you in the loop through this bug instead. Others alternatives exist if you want to achieve doing something by March. I suggest you host the help files on a public source repository: github.com, sourceforge, etc. And that you build your scripts to do the proper packaging of the help fragments.
At this time we have no solution for this. The workaround I indicated before sounds like the best way to go yet.
Created attachment 138081 [details] help fragment sample candidate version of Web Tools Platform (WTP) help fragments
We (Japan Working Group) are translating some help files, and built the fragments. As a example, I attached the candidate version of Web Tools Platform (WTP) help fragments.(Comment #7) We would like to contribute translated help files in this way, is it acceptable one or not? It is just "candidate" version, because # 277256 (Copyright description in help file) and # 277257 ("Translation history file" in case of Large Contribution) are not resolved yet. But I deployed it to my development environment, translated sentences are displayed normally.
Created attachment 146348 [details] Japanized help files of WTP and Mylyn
I put a set of Japanised help files of WTP and Mylyn. We added 2 types of contributors' information 1) Contributor's name in each html file 2) "BabelTranslationHistory.html" in each fragment(jar file) Please check them, and if necessary handle them to IP group.
IPZilla CQ submitted: http://dev.eclipse.org/ipzilla/show_bug.cgi?id=3538
Mori-san, the Eclipse Foundation IP team would like to understand what, if any, mechanism the Japan Working Group has in place regarding those performing the translations and/or translations which are contributed to the working group. Are these help files all translated from scratch by translators from NEC Soft? Any of the translated files contributed by other companies in the Japan Working Group? Is there a URL for the Japan Working Group site so that the IP team can find more info about the JWG? Thanks!
> Are these help files all translated from scratch by translators from NEC Soft? Yes. About WTP and Mylyn, NEC Soft tranlated them from scratch.
Thanks to JWG for the contribution. The submission has been approved.
The building of the help files is different from the properties files. I will assign this to myself to finish the process.
I've finished integrating the translated help files of WTP and Mylyn for Ganymede. They are currently in the RC1 folder at the test build site: http://build.eclipse.org/technology/babel/babel_language_packs/RC1/BabelLanguagePack-tools.mylyn-doc-ja_3.4.0.v20091017043401.zip http://build.eclipse.org/technology/babel/babel_language_packs/RC1/BabelLanguagePack-webtools.sourceediting-doc-ja_3.4.0.v20091017043401.zip http://build.eclipse.org/technology/babel/babel_language_packs/RC1/BabelLanguagePack-webtools-doc-ja_3.4.0.v20091017043401.zip I did the test myself and all help files were properly displayed. If no furthur problem is found, we will promote them and make them available from the Babel download page soon.
Thank you kit-san. I also will test it.
A few japanese member tested them. The help of WTP worked well. But Mylyn did not worked with Ganymede nor Galileo. Now we are investigating the repro condition. Kit-san, please let us know your test condition.
Language packs should work for specific level of code plugins because the strings or help files may be modified in the newer versions of the plugins. If we don't set a host fragment version range the language packs should work for, the translations may not match the English text. However, if you don't think the Mylyn help files were changed much between versions, I can remove the host fragment tolerance range. Then the Mylyn language pack will work for Ganymede or Europa. Try this new language pack: http://build.eclipse.org/technology/babel/babel_language_packs/RC1/BabelLanguagePack-tools.mylyn-doc-ja_3.4.0.v20091017043401b.zip
Kit-san, Ganymede SR1 includes Mylyn3.0. But our Mylyn help is based on Mylyn 3.1, because Mylyn help was updated drastically after Ganymede SR1. Therefore we would like to propose Ganymede users to update Mylyn to 3.1. Do you have any good idea to inform it to users, for example by build name or some other way?
Created attachment 150818 [details] About Eclipse SDK Features There are multiple releases of Mylyn, and each release of Mylyn works in multiple releases of Eclipse. We have to be specific on what release of Mylyn that this Mylyn language pack is for. Users can find out their release of Mylyn installed by going to "Help>About Eclipse SDK" pulldown menu and click on "Feature Details" button. (See screen capture)
