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>
Also in RFC 2396: For original character sequences that contain non-ASCII characters, however, the situation is more difficult. Internet protocols that transmit octet sequences intended to represent character sequences are expected to provide some way of identifying the charset used, if there might be more than one [RFC2277]. However, there is currently no provision within the generic URI syntax to accomplish this identification. An individual URI scheme may require a single charset, define a default charset, or provide a way to indicate the charset used. I suppose that anything not ASCII is unsafe. Best Regards, Paulo Soares > -----Original Message----- > From: Leonard Rosenthol [SMTP:[EMAIL PROTECTED]] > Sent: Monday, April 29, 2002 18:37 > To: Paulo Soares; 'B J'; [EMAIL PROTECTED] > Subject: RE: [iText-questions] How to specify link with japanese > chars. > > At 6:18 PM +0100 4/29/02, Paulo Soares wrote: > >URLs can be coded in UTF-8 but I don't think that it will work for files. > > > > I haven't looked at the relevant parts of the iText source, > but the filename is stored in the PDF as a "string", which means it > must either be in "PDF Encoding" (aka slightly modified ISO-8859-1) > OR in Unicode. > > > 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
