Difference between revisions of "Babel / Development Status Meetings / 2009-09-28"

From Eclipsepedia

Jump to: navigation, search
m (New page: === Attendees === {| border="1" |- | Kit |   |- | Denis |   |- | Gabe |   |- | Antoine |   |- | Nigel |   |- | Jeff |   |- | Margaret |   |} ==...)
 
m (Topics)
Line 27: Line 27:
 
=== Topics  ===
 
=== Topics  ===
  
*Babel Release - post 0.7
+
*{{bug|283734}} Documentation Best Practices
**focus on packaging and polishing works for the translation server, message editor, and other tools
+
**I'm starting to look in more details on how to build translated doc files.
**We need more time to finish the code and test. Re-target to SR2.
+
**Looks like the idea gears more towards developers / doc writers, recommending to signle source the doc files at a wiki.
*Translation assistance tools
+
**There are tools to help convert HTML doc files to wiki format. However, as with any conversion process, some minor manual clean up are needed after the conversion.
**Mori-san: A set of translation assistance tools version 1.0 is available on SourceForge. JP as a name of "Benten" project. By the way, almost all source codes are written in EPL, and we intend to donate them to Babel. But we have recognized a few license issues for the donation. I would like to discuss this point.
+
**Our current thought of extracting the HTML doc files from repositories, translate, convert to wiki format and publish may not work very well.
**Can the tool co-exist in both SourceForge and Eclipse Foundation? Anyone knows how to proceed?
+
**Wiki conversion tools are not perfect yet. The minor manual clean up may be a problem.
*CQs
+
**If a HTML doc file is translated into 34 languages, each translate has to decide on how the author wants the contents to be layout and displayed if the tag is not automatically converted.
**{{bug|261958}} Language pack should integrate the translated help; Japanese help files for WTP and Mylyn attached; CQ 3533 submitted; CQ not approved yet
+
**HTML doc files also reference image files in the doc plugin.
**{{bug|289014}} BIRT 2.5.0 Translation for 6 languages in group 1; CQ 3533 submitted; CQ not approved yet
+
**We have to have the English HTML doc files and image files in place at the wiki first. Otherwise, the translated doc files cannot reference the image files.
*Eclipse Community Forums
+
**To sum up, we probably have to wait till some projects are following these Best Practices and hosting their doc files at the wiki first. Then we will work on the translation process of the wiki doc files.
**Denis, do we have to do anything?
+
*{{bug|290004}}
+
**Babel Language Pack for eclipse in French - jars not available
+
**Denis, can you check to see if it's a server problem?
+
*{{bug|261958}}
+
**CQ not approved yet, but I started to create a langauge pack to include the doc translations
+
**Tried to use the Babel Language Pack Build Tool; encountered a few problems; opened bugs; assigned to Tod
+
**I created the language pack manually; was able to see the WTP doc in Japanese
+
**However, WTP included UI plugins and doc plugins into one feature
+
**I can either see WTP doc in Japanese and UI strings in English, or WTP doc in English and UI strings in Japanese
+
**We have to build both UI plugins and doc plugins together
+
**Hacked the UI plugins and doc plugins together; a langauge pack including the WTP doc in Japanese is ready
+
**Need longer term solution
+
[[Image:WTP translations.png]]
+
 
[[Category:Babel]]
 
[[Category:Babel]]

Revision as of 12:25, 28 September 2009

Attendees

Kit  
Denis  
Gabe  
Antoine  
Nigel  
Jeff  
Margaret  

Topics

  • bug 283734 Documentation Best Practices
    • I'm starting to look in more details on how to build translated doc files.
    • Looks like the idea gears more towards developers / doc writers, recommending to signle source the doc files at a wiki.
    • There are tools to help convert HTML doc files to wiki format. However, as with any conversion process, some minor manual clean up are needed after the conversion.
    • Our current thought of extracting the HTML doc files from repositories, translate, convert to wiki format and publish may not work very well.
    • Wiki conversion tools are not perfect yet. The minor manual clean up may be a problem.
    • If a HTML doc file is translated into 34 languages, each translate has to decide on how the author wants the contents to be layout and displayed if the tag is not automatically converted.
    • HTML doc files also reference image files in the doc plugin.
    • We have to have the English HTML doc files and image files in place at the wiki first. Otherwise, the translated doc files cannot reference the image files.
    • To sum up, we probably have to wait till some projects are following these Best Practices and hosting their doc files at the wiki first. Then we will work on the translation process of the wiki doc files.