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 setting up the encoding using Shift_JS, ISO-8859-1 > > >>>>> these stuff? Or I only have a choice between > > >>>>> ENCODING_COMPRESSED_UNICODE and or ENCODING_UTF_16? > > >>>>> And the thing I did was just right? > > >>>>> > > >>>>> Any hint will be highly appreciated. > > >>>>> > > >>>>> Best, > > >>>>> > > >>>>> Xuemin > > > ----------------------------------------------------- > Tetsuya Kitahata -- Terra-International, Inc. > E-mail: [EMAIL PROTECTED] > http://www.terra-intl.com/ > (Apache Jakarta Translation, Japanese) > http://jakarta.terra-intl.com/ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > Mailing List: http://jakarta.apache.org/site/mail2.html#poi > The Apache Jakarta Poi Project: http://jakarta.apache.org/poi/ > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] Mailing List: http://jakarta.apache.org/site/mail2.html#poi The Apache Jakarta Poi Project: http://jakarta.apache.org/poi/
