Translation (JP)
Hi, All. I am a newer of this project, living in Japan. Wandering the Jakarta Project Web Site, I've luckily found this project. I am using XLS file format a lot because my clients want to. I wondered how to contribute to this project, and I noticed that the translation is the best way for me. # Also, translation is the best way to know more about these # kind of projects, I am sure. G I am trying to translate the documents into Japanese right now. (experimental: http://www.terra-intl.com/jakarta/poi/ ) Of course, I am doing the translation on xdocs at the same time. (Also, I am trying for some other projects in Jakarta) In Japanese standard Windows environment, Shift_JIS code is popular, however, I think using UTF-8 for docs is preferable. What do you think? Thanks a lot. -- Tetsuya Kitahata [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Translation (JP)
On Sat, 2002-07-06 at 17:07, Tetsuya Kitahata wrote: Hi, All. I am a newer of this project, living in Japan. Wandering the Jakarta Project Web Site, I've luckily found this project. I am using XLS file format a lot because my clients want to. Excellent. If you get the opportunity please contribute a Case Study: http://jakarta.apache.org/poi/casestudies.html I wondered how to contribute to this project, and I noticed that the translation is the best way for me. # Also, translation is the best way to know more about these # kind of projects, I am sure. G I am trying to translate the documents into Japanese right now. (experimental: http://www.terra-intl.com/jakarta/poi/ ) Of course, I am doing the translation on xdocs at the same time. (Also, I am trying for some other projects in Jakarta) I think thats great. I cannot comment of course on the quality of the translation (Still working on Spanish and German, one day I'll try Japanese but one can only learn so much in a given time period), but I'm very pleased! In Japanese standard Windows environment, Shift_JIS code is popular, however, I think using UTF-8 for docs is preferable. What do you think? UTF-8 or 16 is the general standard. Due to the nature of this project, we should assume that the user may be using non-windows environments as well. (I hail from a Linux box) If you can post a zip file into bugzilla with the translated xdocs in the same directory format as the Spanish translation, I'll incorporate this into the POI build and get it up on the site. Chances are this will encourage others to assist you in this (by submitting patches) and accelerate the process for you. Just a thought One thing I'd really like to do is incorporate language into the docs. Meaning section title=Some Section name=Some Section language=default !-- english -- p Blablabla /p /section section title=Japanese translation name=Some Section language=jp p !-- japanese characters here -- /p /section This would help keep things up to date. Especially if the XSL transformation process put placeholders where there were untranslated sections. Unfortunately, my XSL/Centipede skills have not progressed to the point where I can do this. Thanks a lot. No thanks required, I should instead thank you! This is an outstanding development. I'll link to it shortly. -Andy -- Tetsuya Kitahata [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- http://www.superlinksoftware.com - software solutions for business http://jakarta.apache.org/poi - Excel/Word/OLE 2 Compound Document in Java http://krysalis.sourceforge.net/centipede - the best build/project structure a guy/gal could have! - Make Ant simple on complex Projects! The avalanche has already started. It is too late for the pebbles to vote. -Ambassador Kosh -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Translation (JP)
Hi, Andrew, I am very glad to your prompt reply. UTF-8 or 16 is the general standard. Due to the nature of this project, we should assume that the user may be using non-windows environments as well. (I hail from a Linux box) In xdocs files (.xml files), the encoding is not UTF-8 but ISO-8859-1... In my thought (Japanese Translation Version) xdocs files should be encoded by Shift_JIS (This is Windows Standard) and docs files generated by xdocs files should be encoded by UTF-8. # Still there're a few text editors which can deal with the UTF-8 # format (I have and can, but..). HTML side, of course UTF-8 is O.K. This can be done by modifying build.xml (using Velocity/Anakia + ANT) or velocity.properties, I think. # I've done the same thing for other projects. For the time being, I'd like to do the translation on my web. However, I am thinking of the translation of xdocs also for easy transfer to http://jakarta.apache.org/poi/trans/jp/ .. or somewhere. If you can post a zip file into bugzilla with the translated xdocs in the same directory format as the Spanish translation, I'll incorporate this into the POI build and get it up on the site. Chances are this will encourage others to assist you in this (by submitting patches) and accelerate the process for you. Thanks a lot. One thing I'd really like to do is incorporate language into the docs. Meaning I think this will be great. However, current xdocs files should be changed in some way (especially ISO-8859-1 part). No thanks required, I should instead thank you! This is an outstanding development. I'll link to it shortly. Right. I'd like to hurry up the translation G. - Tetsuya -- Tetsuya Kitahata [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Translation (JP)
On Sat, 2002-07-06 at 18:50, Tetsuya Kitahata wrote: Hi, Andrew, I am very glad to your prompt reply. UTF-8 or 16 is the general standard. Due to the nature of this project, we should assume that the user may be using non-windows environments as well. (I hail from a Linux box) In xdocs files (.xml files), the encoding is not UTF-8 but ISO-8859-1... Thats not a serious issue to change. In my thought (Japanese Translation Version) xdocs files should be encoded by Shift_JIS (This is Windows Standard) and docs files generated by xdocs files should be encoded by UTF-8. # Still there're a few text editors which can deal with the UTF-8 # format (I have and can, but..). HTML side, of course UTF-8 is O.K. I'm not sure I agree. One of the principles behind POI is that its multi-platform. I for one don't have a Windows box. (I run Excel on Linux via CrossOver Office distro of WINE from www.codeweavers.com). If this is an open multi-platform standard than thats fine. This can be done by modifying build.xml (using Velocity/Anakia + ANT) or velocity.properties, I think. # I've done the same thing for other projects. POI uses Centipede instead of Velocity/Anakia. See http://www.krysalis.org/centipede for details For the time being, I'd like to do the translation on my web. However, I am thinking of the translation of xdocs also for easy transfer to http://jakarta.apache.org/poi/trans/jp/ .. or somewhere. Thats too bad, I think it would be nice to have collaboration on this effort. If you can post a zip file into bugzilla with the translated xdocs in the same directory format as the Spanish translation, I'll incorporate this into the POI build and get it up on the site. Chances are this will encourage others to assist you in this (by submitting patches) and accelerate the process for you. Thanks a lot. One thing I'd really like to do is incorporate language into the docs. Meaning I think this will be great. However, current xdocs files should be changed in some way (especially ISO-8859-1 part). I've no objection really. How do we go about that exactly? No thanks required, I should instead thank you! This is an outstanding development. I'll link to it shortly. Right. I'd like to hurry up the translation G. Well I think the best way to do that is to enable others to contribute. By incorporating the translation into the project, you make it so that: 1. everyone who downloads new releases of POI will get the updated documentation. 2. Exposure. 3. everyone can submit patches to the CVS repository and have them incorporated. Otherwise, you have to do all the work yourself which maybe is okay with you, but I suspect it will take longer. -Andy - Tetsuya -- Tetsuya Kitahata [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- http://www.superlinksoftware.com - software solutions for business http://jakarta.apache.org/poi - Excel/Word/OLE 2 Compound Document in Java http://krysalis.sourceforge.net/centipede - the best build/project structure a guy/gal could have! - Make Ant simple on complex Projects! The avalanche has already started. It is too late for the pebbles to vote. -Ambassador Kosh -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
