Re: [Lynx-dev] Problem displaying gopherspace UTF-8 on ARM (Raspberry Pi)

[Zephaniah E. Loss-Cutler-Hull]

On 01/15/2016 05:38 AM, Axel Beckert wrote:
> Hi,
>
> On Fri, Jan 15, 2016 at 08:30:02AM -0500, Héctor A. Abreu wrote:
>> I run raspi-config from the command line. The output for locale is as 
>> follows:
>>
>> address@hidden:~ $ locale
>> LANG=es_US.UTF-8
>> LANGUAGE=
>> LC_CTYPE="es_US.UTF-8"
>> LC_NUMERIC="es_US.UTF-8"
>> LC_TIME="es_US.UTF-8"
>> LC_COLLATE="es_US.UTF-8"
>> LC_MONETARY="es_US.UTF-8"
>> LC_MESSAGES="es_US.UTF-8"
>> LC_PAPER="es_US.UTF-8"
>> LC_NAME="es_US.UTF-8"
>> LC_ADDRESS="es_US.UTF-8"
>> LC_TELEPHONE="es_US.UTF-8"
>> LC_MEASUREMENT="es_US.UTF-8"
>> LC_IDENTIFICATION="es_US.UTF-8"
>> LC_ALL=
> Thanks. Looks fine to on a first glance.
>
>> The only strange thing I see is "LANGUAGE=" which contrast with my
>> non-ARM Linux boxes (HP Laptop with Lubuntu, AMD with Debian Jessie
>> LXDE), which show "LANGUAGE=es_US:es",
> I must admit that I always forget what's the difference between $LANG
> and $LANGUAGE. One is multivalue and one is with charset or so.
>
>> but I don't know if it has anything to do with the problem because
>> Lynx on Raspberry Pi displays gopher utf-8 correctly for http, but
>> not for gopher.
> That's indeed strange and sounds like an issue in Lynx.

Alright, but HTTP and HTML can both specify the page character set, can
Gopher?

What is the lynx 'Assumed document character set' in the options menu
for both systems?

Regards,
Zephaniah E. Loss-Cutler-Hull.

signature.asc
Description: OpenPGP digital signature