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)
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: User story - ETL4ALL
On Wed, 11 Jun 2003 21:10:45 -0400 Andrew C. Oliver [EMAIL PROTECTED] wrote: I hope to add Japan to that list very soon. Ditto: I've made another gateway to post to the case studies for the Japanese. Sincerely, -- Tetsuya ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Excel File Download using JSP
-1 I won't translate the wiki page FAQ. Sincerely, -- Tetsuya ([EMAIL PROTECTED]) -- AIM# tkitahata - On Mon, 21 Jul 2003 22:45:44 -0400 (Subject: Re: Excel File Download using JSP) Andrew C. Oliver [EMAIL PROTECTED] wrote: I think we should move the FAQ all onto the wikiThen you wouldn't have to plan. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Chinese Translation (Re: Cell value encoding)
Xuemin, Greeat!! Very appreciative!! However, I know that you will have a trouble in building the current POI website. (What people in multi-byte chars must undergo...) Anyway, I need more information from you. Could you please give me the info of your environment? (Which tool do you use in editing the xmls? Windows Japanese/Traditional Chinese/ (I forgot) Chinese Edition? Are there any free fonts of chinese? (just my ignorance, sorry)) I think (temporarily) uploading the docs (not xdocs) from Xuemin (built site by Xuemin) directly to daedalus will be the best choice. I am willing to volunteer to do this. Also, I am thinking about the i18n/m17n of the Apache Software Foundation (infrastructure for the translators, etc) and I hope it will be achieved sooner or later. -- Tetsuya ([EMAIL PROTECTED]) P.S. Andrew, Chinese/Korean/Japanese are different from western languages. you can not build the chinese/japanese sites from xdocs in your environment, i guess. I need more wisdom from all over the world! -- On Sat, 2 Aug 2003 20:58:05 +0900 (Subject: Re: Cell value encoding) Xuemin Guan [EMAIL PROTECTED] wrote: Hello, guys, thanks for all the emails. As I am a Chinese native spearker, doing a Chinese version documentation would be a cinch for me. I would like to do it as part of this site, if possible. I can start this straightaway. Any suggestions, hints, or guidlines on documentation are all welcome. Cheers, Xuemin - Original Message - From: Tetsuya Kitahata [EMAIL PROTECTED] To: POI Users List [EMAIL PROTECTED] Sent: Saturday, August 02, 2003 1:54 PM Subject: Re: Cell value encoding Yes, sure. I know that appresso is a japanese company (because my company is also listed up to the Opensource Technology Alliance), however, I am not sure which language you (Mr. Xuemin Guan) often use. I think I can help you in some points. Thank you. -- Tetsuya ([EMAIL PROTECTED]) P.S. Andrew, there are many problems building POI-site in japanese/korean/chinese languages, because the default lacks the those 3 language's fonts. (in the process of the creation of PDF files) On Sat, 02 Aug 2003 00:43:31 -0400 (Subject: Re: Cell value encoding) Andrew C. Oliver [EMAIL PROTECTED] wrote: Sure! If you can write something up just kind of explaining what POI is, how to use it, the character encoding issue, etc that would be awesome. An article or how to, or something like that. We'll publish it here and give you accords. If you want to do it as part of the site, just do it in the xdoc format that all the existing docuemntation is in. Its basically XML. See here: http://cvs.apache.org/viewcvs/jakarta-poi/src/documentation/content/xdocs/ Tetsuya Kitahata can probably give you a few pointers with the encoding and the such. -andy On 8/1/03 11:42 PM, Xuemin Guan [EMAIL PROTECTED] wrote: Hello, Andy, surely I can do this. It is my pleasure if I can contribute a bit to the POI project. Could you please point me a way of how do this? Thanks, Xuemin - Original Message - From: Andrew C. Oliver [EMAIL PROTECTED] To: POI Users List [EMAIL PROTECTED] Sent: Saturday, August 02, 2003 2:17 AM Subject: Re: Cell value encoding Yeah man. Pass the word along BTW. If you can publish any non-english documentation on this it would sure help us out a lot. We can always help with hosting it. Thanks, Andy On 8/1/03 1:12 PM, Xuemin Guan [EMAIL PROTECTED] wrote: Hello, Andy, thanks a lot for the note! Best, Xuemin - Original Message - From: Andrew C. Oliver [EMAIL PROTECTED] To: POI Users List [EMAIL PROTECTED] Sent: Friday, August 01, 2003 10:31 PM Subject: Re: Cell value encoding You did the right thing. The UTF_16 is a misnomer carried from the earliest versions of POI. In 3.0 these will be renamed to EIGHT_BIT_CSET and SIXTEEN_BIT_CSET or something. The first case is useful only for US character sets. The only problem is how to name this concisely and clearly (because there are some eight bit character sets that excel writes in 2 bytes because Excel is a silly format). -Andy On 8/1/03 2:31 AM, Xuemin Guan [EMAIL PROTECTED] wrote: Hello, dear all, I am having some problems dealding with Japanese Characters. I set up a cell value as this: cell.setCellValue(some Japanese characters go here); And I end up with wrong values in the generated XLS file. Then I looked up the POI API and souce code, and did the follow: cell.setEncoding((short)1);//Using UTF_16 cell.setCellValue(some Japanese characters go here); Then it worked fine. But I am not sure if this is the right thing to do. Doesn't the POI/Excel supports something like
Re: How to create MS-Excel which contain Japanese strings encoded in Shift JIS encoding.
I suspect that it would be related to just the default encodings of Solaris (EUC_JP). Have you ever experienced such a transformation? (EUC_JP = Shift_JIS / vice versa) I suspect that it is not related to POI itself. (Not sure. I do not have Solaris environment) Make sure the CodePage, also. -- On Wed, 22 Oct 2003 18:53:48 +0530 Mudit Gupta [EMAIL PROTECTED] wrote: Hi All, We are planning to use POI for creating an XLS file from a J2EE based application. The application server is WebLogic 8.1, OS is Solaris 8. However, the XLS to be created will contain Japanese strings encoded in Shift JIS encoding. After checking the POI API, what we found there is no place where one can specify the encoding of the XLS file to be created. Typically it is done through OutputStreamWriter of java.io. However, the relevant APIs (wb.create(java.io.OutputStream stream))in POI, which can be used to write strings in the XLS file, accepts only OutputStream object. In this situation, can anyone please let us know how POI can be used to create a XLS file with Japanese strings encoded in Shift_JIS ? Regards, Sourav - Tetsuya Kitahata -- Terra-International, Inc. E-mail: [EMAIL PROTECTED] http://www.terra-intl.com/ Apache Software Foundation Committer: http://www.apache.org/~tetsuya/ fingerprint: E420 3713 FAB0 C160 4A1E 6FC5 5846 23D6 80AE BDEA - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
