Re: HashInURI

On 2010/11/29 8:52, Noah Mendelsohn wrote:
> It looks like it's being served as UTF-8 over the Web, but displays
> right when changed to ISO-8859-1, which may be what you're getting as
> default for local files.

Yes or no. The document internally has
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
so that's what comes into force locally.

Probably the best thing to do is to convert the document to UTF-8 (also 
changing the above line), and then update/republish it.

Another alternative is to ask sysreq to change the encoding it's served 
with (but that would be a step back).

Regards,   Martin.


> It seems to have to do with those &nbsp;'s, but
> I'm not quite sure why.
>
> Noah
>
> On 11/28/2010 6:40 PM, ashok malhotra wrote:
>> Hmmm ... I'm on Windows and I get the same problem on IE, Firefox and
>> Opera
>> when I download
>> the file from the Web. The local copy displays fine.
>> All the best, Ashok
>>
>> On 11/28/2010 2:02 PM, Scott Penrose wrote:
>>> Hi Ashok,
>>>
>>> Small encoding problem on that page:
>>>
>>> On 29/11/2010, at 7:02 AM, ashok malhotra wrote:
>>>
>>>> I just checked inhttp://www.w3.org/2001/tag/2010/11/HashInURI
>>>> This is a combination of Raman's hash-in-url writeup and my earlier
>>>> writeup on
>>>> Client-side Storage. Please review and comment.
>>>> --
>>>> All the best, Ashok
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> That was on Safari on Mac OS X.
>>>>
>>>> Otherwise looks good.
>>>>
>>>> Scott
>>>>
>>>>
>>>> Scott
>>>>
>
>

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp

Received on Monday, 29 November 2010 09:11:27 UTC