Complete.Org: Mailing Lists: Archives: gopher: August 2008:
[gopher] Re: Multilingual Gopher Support (was Re: Gopherness)
Home

[gopher] Re: Multilingual Gopher Support (was Re: Gopherness)

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Multilingual Gopher Support (was Re: Gopherness)
From: Cameron Kaiser <spectre@xxxxxxxxxxxx>
Date: Wed, 13 Aug 2008 18:15:55 -0700 (PDT)
Reply-to: gopher@xxxxxxxxxxxx

> > More testing results are welcome as well as sample text and menus in
> > other languages and encodings.
> 
> Roman, I have tested your pages as well, albeit with different
> results, which can be seen, along with further tests, on my test
> server (I've also included screenshots of each result, just so we know
> exactly what's being output by the client):
> 
> gopher://gopher.hughguiney.com/1/utf8/
> 
> The text files both worked in every scenario. The menus, however, only
> worked with UTF-8 in Firefox using the Mozilla core Gopher handler
> (rather than Overbite). The character sets in all other scenarios are
> misinterpreted. Manually changing them with View > Character Encoding
> > ... to the right ones made no difference, because the source code is
> automatically escaped as Unicode internally before it reaches the
> browser. In the case of Mozilla core, this is a percent-encoded
> result, a la URIs (%20 etc). In the case of Overbite, this is a
> numeric character reference, a la HTML (&#32; etc).

Are you running the most recent Overbite (build 1409)? I think you've
hit the character encoding bug Mate reported and I fixed.

-- 
------------------------------------ personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@xxxxxxxxxxxx
-- Do you think I could buy back my introduction to you? -- Groucho Marx ------



[Prev in Thread] Current Thread [Next in Thread]