Re: non standard path characters
- From: Tijs <tijs_news@xxxxxxxxxxxxxxx>
- Date: Thu, 31 May 2007 14:41:14 +0200
Robin Becker wrote:
A kind user reports having problems running the reportlab tests because
his path has non-ascii characters in it eg
.....\Mes documents\Mes Téléchargements\Firefox\...
somewhere in the tests we look at the path and then try and convert to
utf8 for display in pdf.
Is there a standard way to do these path string conversions?
Paths appear to come from all sorts of places and given the increasing use
of zip file packaging it doesn't seem appropriate to rely on the current
platform as a single choice for the default encoding.
Zip files contain a bit flag for the character encoding (cp430 or utf-8),
see the ZipInfo object in module zipfile and the link (on that page) to the
file format description.
But I think some zip programs just put the path in the zipfile, encoded in
the local code page, in which case you have no way of knowing.
--
Regards,
Tijs
.
- Follow-Ups:
- Re: non standard path characters
- From: Robin Becker
- Re: non standard path characters
- References:
- non standard path characters
- From: Robin Becker
- non standard path characters
- Prev by Date: Re: file reading by record separator (not line by line)
- Next by Date: pexpect/termios error: Inappropriate ioctl for device
- Previous by thread: Re: non standard path characters
- Next by thread: Re: non standard path characters
- Index(es):