We should patch that in core - we can do it with an "if $] > 5.007" I think.
----- Original Message ----- From: "brian wheeler" <[EMAIL PROTECTED]> To: "BRIAN DAVID WHEELER" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, August 01, 2002 8:47 PM Subject: Re: non-english letter problems > On Thu, 2002-08-01 at 13:14, brian wheeler wrote: > > I forgot to mention this and it might be a wee bit important. In > > addition to upgrading axkit to 1.6, we upgraded to Perl 5.8.0...I wonder > > if it is munching the data... > > > > Brian > > > > It was perl 5.8.0. A coworker of mine noticed that when we pipe .asp or > .cgi files through AxKit everything was fine...it was just broken on > static content. Upon further inspection, things written to AxKit's > cache were in the native encoding, and not utf-8. When the cache was > delivered, the binary contents were sent and the data was encoded wrong > for the browser. The 'easy' fix for this was to make sure that perl 5.8 > didn't change the encoding for the cache output in AxKit. At line 114 > in AxKit::Cache, I inserted this line: > > binmode($fh,":utf8"); > > And everything started working as expected. > > Brian > > > > > > > On Thu, 2002-08-01 at 12:20, brian wheeler wrote: > > > On Thu, 2002-08-01 at 06:45, Robin Berjon wrote: > > > > On Thursday 01 August 2002 00:42, brian wheeler wrote: > > > > > We have a series of documents which are in Spanish. The ñ entity > > > > > is used quite a bit and everything seems to parse ok. However, when the > > > > > data gets to the client, all they get is a square (or on my linux box, a > > > > > question mark). I did a manual request via telnet and when the data > > > > > comes back, the ntildes are just fine. The header returned is: > > > > > > > > > > HTTP/1.1 200 OK > > > > > Date: Wed, 31 Jul 2002 22:37:46 GMT > > > > > Server: Apache/1.3.26 (Unix) AxKit/1.6 mod_perl/1.27 > > > > > Content-Type: text/html; charset=UTF-8 > > > > > > > > Did you serve content in UTF-8 previously? Have you tried to save the output > > > > and run it through a parser to see if it's valid? Note that to display UTF-8 > > > > you need a font that supports the characters you want to see. Note also that > > > > Netscape 4 will most likely break on UTF-8 (but then I guess no one in his > > > > right mind is still using that thing). > > > > > > > > > > Yeah, we are still serving it on our production site (which runs 1.4). > > > > > > http://icpac.indiana.edu/publications/#espanol > > > > > > is a page with tildes and accents, etc. One of our development copies > > > of the same page can be found by prepending 'bdwheele.' to the host name > > > of the url above. The development copy is running 1.6. > > > > > > I'm seeing this on galeon 1.2.0 (a mozilla derivitive) and others have > > > seen it on opera and internet explorer. > > > > > > When I do the same request (via telnet) to the production version, the > > > ntildes don't come out right...they appear as two bytes...which they > > > should when in utf-8. > > > > > > Brian > > > > > > > > > > -- > > > > Robin Berjon <[EMAIL PROTECTED]> > > > > There are things that are so serious that you can only joke about > > > > them. > > > > -- Heisenberg > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
