Re: [gopher] gopher++ (gopher1) protocol
> > Something along those lines, even though not necessarily gopher++: on
> > gopher://gopher.teply.info/1/test
> > i've put up a very simple UTF-8 test menu. Mainly it was out of curiosity
> > whether or not it'll work in any way.
>
> I tested that before with my own test files, but since you published a
> nice full set here are my results with the above URL:
>
> Client LC_CTYPE Test 1 Test 2 Test 3 Test 4
> ==============================================================
> FF 3.5 UTF-8 OK Fail OK OK
> FF 3.5 IS0-8859-1 OK Fail OK Fail
>
> Overbite UTF-8 OK OK OK OK
> Overbite ISO-8859-1 Fail Fail OK OK
>
> Lynx 2.8.8 UTF-8 OK Fail OK Fail
> Lynx 2.8.7 ISO-8859-1 Fail Fail OK Fail
>
> gopher 3.0.13 UTF-8 Fail OK OK Fail
> gopher 3.0.13 ISO-8859-1 Fail OK OK Fail
>
>
> ... and the above results are exactly why I suggested server charset
> transcoding... I actually expected Overbite to Just Work(tm), but it
> seems that it only works when the local charset is UTF-8. Also, it's
> possible to make Lynx almost work by changing some charset options - the
> above stuff is run with pretty much default settings.
That doesn't make sense. Isn't UTF-8 a superset of ISO-8859-1? I'm happy
that Overbite did the best, but I'm distressed it failed two of the
ISO-8859-1 tests.
--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@floodgap.com
-- If you live in a country run by committee, be on the committee. -- G. Summer
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/gopher-project
Reply to: