Hello all, I'm a Japanese iText user. I will be glad if the follwings are a clue as to the solution of the problem of Japanese chars.
I do not know if iText will produce PdfString object represented by hexadecimal strings which must be enclosed within angle brackets < and >. So, I tried to make a change to a line in a pdf source which is generated by iText. Changed result is as follows: /F <8341 2f 8343 2e 70 64 66> Spaces in angle brackets are meaningless for PDF Viewer. I put them just for making it easy to visually recognize each characters. So, even if there are no spaces, you can get the same result. Codes in angle brackets are Shift-JIS code which is a major encoding for Japanese characters. "<8341 2f 8343 2e 70 64 66>" represents a relative path. Each Shift-JIS code represents as follows; 8341 -> Japanese Katakana "a" (30a2 in Unicode) 2f ---> slash (represents directory) 8343 -> Japanese Katakana "i" (30a4 in Unicode) 2e ---> period 70 ---> p 64 ---> d 66 ---> f This link will work both on Japanese Winodews and Japanese Mac OS with Japanese Acrobat. Regards, KuMi > The problem here is how are these multi-byte interpreted. What is the > encoding? I tried to create a link to a directory with a chinese name in my > computer with Acrobat 4 and it just put a "?" for the chinese name. Maybe it > works with the japanese Acrobat, or maybe not. > > Best Regards, > Paulo Soares > >> -----Original Message----- >> From: Leonard Rosenthol [SMTP:[EMAIL PROTECTED]] >> Sent: Tuesday, April 30, 2002 14:17 >> To: Paulo Soares; 'B J'; [EMAIL PROTECTED] >> Subject: RE: [iText-questions] How to specify link with japanese >> chars. >> >> At 10:49 AM +0100 4/30/02, Paulo Soares wrote: >>> According to the PDF specs: >>> <start quote> >>> The URL must adhere to the character-encoding requirements specified in >>> RFC 1738. Because 7-bit U.S. ASCII is a strict subset of PDFDocEncoding, >>> this >>> value may also be considered to be in that encoding. >>> <end quote> >> >> I agree with that, concerning URL's - that wasn't my point. >> >> I was talking about filenames - which CAN contain multi-byte >> characters. In fact the PDF spec (v1.3, section 3.10.1) contains an >> entire subsection about "Multiple-Byte strings in file specification". >> >> >> Leonard >> -- >> -------------------------------------------------------------------------- >> - >> Leonard Rosenthol >> <mailto:[EMAIL PROTECTED]> >> Chief Technical Officer <http://www.pdfsages.com> >> PDF Sages, Inc. 215-629-3700 (voice) > > _______________________________________________ > iText-questions mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/itext-questions > _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ iText-questions mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/itext-questions
