apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe Jr." <wr...@rowe-clan.net>
Subject Re: Q to unix filesystem developers
Date Fri, 15 Apr 2011 01:27:57 GMT
On 4/14/2011 8:04 PM, Branko Čibej wrote:
> On 15.04.2011 01:24, William A. Rowe Jr. wrote:
>> On 4/14/2011 6:00 PM, Jonathan Leffler wrote:
>>> Given that the second byte is in the range 0x40..0x7E (second para), and / is
0x2F, there
>>> shouldn't be a problem with Shift-JIS.  That's not to say there isn't another
>>> where there isn't a problem, but I don't think it is Shift-JIS and possibly not
any of the
>>> main Japanese codesets.
>> Looking at the references to the EUC and Big5 encodings, it seems similarly safe
>> assume 20-3F are always the expected ASCII representations, while 0x40-0x7E seem
>> Thanks for this research, it saved me a ton of headaches!
> This is what I remember from my messy days, too. Path handling would be
> a nightmare othewise, it's bad enough for poor Windows lusers that \
> gets displayed as ¥ :)

Ok, stupid question; is ¥ the pathname delimiter, for real?  I don't think I have
a working shift-jis environment set up.

View raw message