perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Morrison [Mailing-Lists]" <>
Subject RE: [OT] Character encodings in web pages
Date Fri, 09 May 2003 13:53:32 GMT

How do you get on with '£' signs?  .. I have a very similar problem with
A(umlaut)'s appearing in front of pound signs and various other chars. 

In my case it appears to be to do with LibXML.. You have to be very
careful as I remember not to switch from UTF8 to iso-1859-1 or back to
prevent them from appearing... I haven't had a chance to track down the
latest incarnation of the bug but when I do I can give you a shout?

All I can suggest for now is trying the perl-xml list? This problem
seems to go about a bit?

Soz not to be more helpful :-)


> -----Original Message-----
> From: Steve Hay [] 
> Sent: 09 May 2003 12:59
> To: Dr. Helmut Zeilinger
> Cc:
> Subject: Re: [OT] Character encodings in web pages
> Dr. Helmut Zeilinger wrote:
> > My be it has nothing to do with your problem -  some time 
> ago a work 
> > with XML::Parser and my page (erroniously) gave out some unicode 
> > characters (at least i think so). In that page, all the other 
> > "umlaute" where not shown correctly by the browser (IE 6).
> This sounds like it could be relevant: the page being generated does 
> contain data from XML files too (parsed with XML::LibXML), and you're 
> the second person on this list to make this suggestion, so I tried 
> adding some XML parsed content to the page output by my test program 
> (new version attached).
> Alas, all my a-umlauts still display correctly: one from an XML 
> attribute, one from XML text content, and one from the plain text 
> message file.  No doubt it'll run fine for you too.
> However, some of the content on the page being generated is 
> user input 
> from elsewhere in the application (CGI input from previous 
> pages, data 
> read from plain text files and data parsed from XML files), 
> so it may be 
> the case that my customer's input includes some characters 
> that make the 
> page "break", but when I try it it "works" simply because I have 
> different input that doesn't include any such characters.
> I will look into this more closely.
> If anybody knows of, or finds any, particular characters that 
> cause the 
> a-umlauts to be shown incorrectly I'd be interested to hear.
> Steve

View raw message