qemu-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] ASCII and/or Unicode for ncurses


From: Narcis Garcia
Subject: Re: [Qemu-discuss] ASCII and/or Unicode for ncurses
Date: Thu, 2 Feb 2017 10:29:06 +0100

Matching now both $LANG and $LANGUAGE in all cases, with same result.

GRUB shows different characters too (curses versus SDL) such as arrows:
Use the ^ and ┴ keys to select which entry is highlighted.


El 02/02/17 a les 08:39, Vincenzo Romano ha escrit:
> It is most likely a mismatch among the VM, the host and you terminal locale.
> 
> So,
> 
> 1. check the values of $LANG and $LANGUAGE on both host and guest (use
> the command "locale")
> 
> 2. check the translation/locale of your terminal emulator
> 
> 3. do the same on you possible ssh/telnet client if you are not on the host.
> 
> 
> Il 01 feb 2017 20:13, "Narcis Garcia" <address@hidden> ha scritto:
>>
>> For Qemu 2.0.x ASCII lines too.
>> For Qemu 2.5.0 I've seen this only for non-english characters, such as
>> french ç, spanish ñ, etc.
>>
>>
>> El 01/02/17 a les 19:27, Vincenzo Romano ha escrit:
>>> Which characters?
>>>
>>> Il 01 feb 2017 18:58, "Narcis Garcia" <address@hidden
>>> <mailto:address@hidden>> ha scritto:
>>>
>>>     Okay, solved for the keyboard part of the question, still not for the
>>>     characters representation.
>>>
>>>     Thanks.
>>>
>>>
>>>     El 01/02/17 a les 18:15, Vincenzo Romano ha escrit:
>>>     > Which characters don't match?
>>>     > Have you tried the proper -k option?
>>>     > --
>>>     > Vincenzo Romano - NotOrAnd.IT
>>>     > Information Technologies
>>>     > --
>>>     > NON QVIETIS MARIBVS NAVTA PERITVS
>>>     >
>>>     >
>>>     > 2017-02-01 18:08 GMT+01:00 Narcis Garcia <address@hidden
>>>     <mailto:address@hidden>>:
>>>     >> I don't know if it's a SeaBIOS problem but, when I use -ncurses
>>>     (tried
>>>     >> with Qemu 2.5.0 and Qemu 2.0.0), only letters and numbers match from
>>>     >> keyboard to guest, and not all ASCII characters are well represented.
>>>     >>
>>>     >> Is there some configuration or workaround to not having these
>>>     key&char
>>>     >> problems?
>>>     >>
>>>     >> Thanks.
>>>     >>
>>>     >
>>>
>>
> 



reply via email to

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