Community
Participate
Working Groups
Relating to the Bug 277256 (Copyright description in help file), we have one more issue. Is it useful to provide "translation history file" in case of Large Contribution ? In case of Large Contribution (contributing all help files of the plugin ), we think it's very helpful that there is a document what has modification history (who is the original contributer, who translated, who modified, and so on). example of description; ------------------------------------------------------------------- This document is the Japanese version of help files for Mylyn 2.3. 2000 : Contributed by IBM Corporation and others. 2000, 2007 : Translated by NEC Soft. 2008 : Modified by FUJITSU LIMITED. ------------------------------------------------------------------- Written in japanese (if japanese lang pack), in french (if french lang pack), etc. It's important what is the suitable file that includes above descriptions. Which is better, type A or type B ? (or any another solutions ?) Type A; Add descriptions to the file already exists, such as about.html, plugin.xml, plugin.properties, and so on. Type B; Create a NEW file (for example, plugin_folder_1.0.0/nl/ja/readme.html)
I'm investigating the best option to handle this.
Obata-san, I don't want to modify the existing as about.html, plugin.xml, plugin.properties files. "readme" also has a special meaning for software products (like some last minute notes that didn't make into the documentation). How about creating a new file called "BabelTranslationHistory.html" at the root of the doc plugin? When we build the language pack for the doc plugin, we will place the "BabelTranslationHistory.html" file for each language into the "nl/<locale>" directory in the doc plugin. For example: "org.eclipse.platform.doc.user.nl_ja/nl/ja/BabelTranslationHistory.html" Is that acceptable to you?
Kit-san, thank you for your reply. I think that is the best solution. I'm going to create a new file called "BabelTranslationHistory.html" in Japanese and build a plugin of the translated help files. If there's no objections, I think this Bug's STATUS may be changed to "RESOLVED".
Problem resolved
