[lubuntu-devel] Testing Lubuntu Alternate i386 version 20160727

[Nio Wiklund]

Hi again,

I think this is a problem of the encoding of the characters. UTF-8 uses 
'two character' encodings for certain characters, and you can set the 
encoding for some software (for example editors, word processors, 
terminal windows).

Example: In 'xfce-terminal' there is

Edit - Settings - the Advanced tab

where you can set the encoding.

I hope this can give you a clue where to look for a solution. Use a 
tool, that you can control, even if it is not the standard tool for Lubuntu.

Best regards
Nio

Den 2016-07-27 kl. 23:50, skrev Ian Bruntlett:
> Hi Nio,
>
> On 27 July 2016 at 21:39, Nio Wiklund <nio.wiklund at gmail.com
> <mailto:nio.wiklund at gmail.com>> wrote:
>
>     Thanks for this test report Ian,
>
> No problem.
>
>     Please add and submit it as a test result at the qa testing tracker
>     too :-) It helps our release manager and also other testers to
>     identify what is tested, and what stills needs to be tested.
>
>     The report at the testing tracker can be very brief.
>
> I believe it is some kind of keyboard handling bug. Not sure as I am not
> familiar with the subsystems involved.
>
> Simply go into emacs/some editor on a system and type this into a file
> called hello.txt
> "Hello World"
>
>
> On my Lenovo T420 laptop (which is working OK), running Ubuntu 16.04
> LTS, this happens:-
>
> $ cat hello.txt
> "Hello World"
>
> $ od -A x -t x1z -v hello.txt
> 000000 22 48 65 6c 6c 6f 20 57 6f 72 6c 64 22 0a        >"Hello World".<
> 00000e
>
> The first character, 0x22, is the ASCII character for double quotes. So
> far, so good.
>
>
> I did the same as above, but on the 32-bit Netbook.
>
> First thing I did was create the "Hello World" text file on the Netbook
> and I got this:-
> ¨Hello World¨
>
> Then I did a hexdump of that file (using the od command as before) and
> got this:-
> ian at hawking:~$ cat hello.txt
> ¨Hello World¨
>
> ian at hawking:~$ od -A x -t x1z -v hello.txt
> 000000 c2 a8 48 65 6c 6c 6f 20 57 6f 72 6c 64 c2 a8 0a  >..Hello World...<
>
> It appears that the 32-bit test system is putting two characters - 0xc2
> and 0xa8 where it should be putting one - 0x22
>
>
> BW,
>
>
> Ian
>
> --
> -- ACCU - Professionalism in programming - http://www.accu.org
> -- My writing - https://sites.google.com/site/ianbruntlett/
> -- Free Software page -
> https://sites.google.com/site/ianbruntlett/home/free-software
>