W3C home > Mailing lists > Public > public-iri@w3.org > July 2011

Re: How browsers display IRI's with mixed encodings

From: Leif H Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Wed, 27 Jul 2011 22:21:51 +0300
To: duerst@it.aoyama.ac.jp
Cc: chris@lookout.net, public-iri@w3.org
Message-ID: <2154559782.996272511@xn--mlform-iua.no>
Martin J. Dürst 27/7/'11,  13:40 

>> But an author which -today- inserts %FC is likely to do a mistake - or
>> at least make a bad choice, no?
> If the author has no (or limited) control over the server (i.e. because 
> the link points to another Web site), then the author has to use 
> whatever will make that link work. If that other Web site uses %FC, then 
> that's what has to go into the link. That's neither a mistake nor a bad 
> choice by the author.



> <detour>
> With mod_fileiri, you can have your cake and eat it too, if you get all 
> the settings right. I.e. you can keep the file names locally the way you 
> always have (e.g. D\xFCrst, I'm using 0xHH notation to express that 
> these are real bytes), but accept D%C3%BCrst externally (i.e. pretend 
> you're using UTF-8), and on top of that also accept D%FCrst but 
> externally redirect in to  D%C3%BCrst (and then internally back to 
> D%FCrst). But you have to be careful to get the settings right, so it 
> may not be something the average server administrator wants to do.
> </detour>

Does it handle conversion from normalised UTF-8 to e.g. Mac filesystem UTF-8 too?
Leif H Silli 
Received on Wednesday, 27 July 2011 20:54:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:14:42 UTC