|[eclipse.org-architecture-council] [Bug 262124] New: Create a separate source repository for translations of help files|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=262124 Product/Component: Community / Architecture Council Summary: Create a separate source repository for translations of help files Product: Community Version: unspecified Platform: PC OS/Version: Mac OS X Status: NEW Severity: enhancement Priority: P3 Component: Architecture Council AssignedTo: eclipse.org-architecture-council@xxxxxxxxxxx ReportedBy: antoine@xxxxxxxxxxxxxxx CC: kitlo@xxxxxxxxxx Hi, we at the Babel project have been successful to some extent to internationalize Eclipse. We tackle the translation of plugin projects by parsing the properties files and generating translation fragments. However we haven't been at this point able to handle help files, html files, graphics, xml files, etc that need to be translated as well. Mori-san asked the question and provided a sample of such files as part of bug 261958. I proposed to Mori-san that Babel hosts translations in a source repository. >From there, we would build fragments along with the translated properties files and we would distribute them. I am proposing a different source repository for translations for different reasons. 1. The most controversial reason is that translations by themselves do not contain IP. That is an ongoing debate in the legal team of the Foundation IIRC. So it might not be necessary to run IP checks on that repository. 2. The second reason is that we don't want to give access to committers only. We would rather be flexible as to who can commit, just like the Babel system does. 3. The third reason is that it would be most practical for the Babel team. We would have the tools to reject a translation, branch at will depending of the project changes, etc. -- Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
Back to the top