On Mon, May 04, 2015 at 06:43:42PM -0300, Jamenson Ferreira Espindula de
Almeida Melo wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>
>
> Jaboatão dos Guararapes, PE, Brazil, 04 de maio de 2015.
>
>
> - ------------------------------
> - ------------------------------
>
>
> Subject: caracter display problems in Virtual Terminals F1-F6
Ah. Almost certainly NOT related to your video driver.
>
>
> - ------------------------------
> - ------------------------------
>
> So, the problem is that some caracters was not being displayed correctly
> in the six Virtual Terminals (F1-F6).
>
> Take a look on some exemples below:
>
>
> output of the command <cp -v teste1.txt teste5.txt>:
>
> “teste1.txt” -> “teste5.txt”
>
>
> output of the command <cp -v screenlog.0 ~/>:
> “screenlog.0” -> “/home/jamenson/screenlog.0”
>
>
> output of the command <mv -v teste* ~/>:
> “teste1.txt” -> “/home/jamenson/teste1.txt”
> “teste2.txt” -> “/home/jamenson/teste2.txt”
> “teste3.txt” -> “/home/jamenson/teste3.txt”
> “teste4.txt” -> “/home/jamenson/teste4.txt”
> “teste5.txt” -> “/home/jamenson/teste5.txt”
>
>
> output of the command <rm -v ~/teste*>:
> removido “/home/jamenson/teste1.txt”
> removido “/home/jamenson/teste2.txt”
> removido “/home/jamenson/teste3.txt”
> removido “/home/jamenson/teste4.txt”
> removido “/home/jamenson/teste5.txt”
>
For me, everything looks fine, but after reading your next paragraph
again: You are not seeing double-quotes around the filenames, instead
you are seeing a þ ("thorn") ?
Does the system where you are sending / replying to mail show the
same problem when you look at the testeN.txt and removido lines in
your mail and in this reply ? If so, the word in brackets at the
end of the last paragraph is 'thorn', an anglo-saxon and icelandic
letter.
https://pt.wikipedia.org/wiki/Thorn_%28letra%29
>
> - ------------------------------
> - ------------------------------
>
>
> Here in my six Virtual Terminals (F1-F6), instead of a " (ASCII code 034),
> the sistem is generating a þ caracter (ASCII code 254). I also realized
> that
> in Emulated Virtual Terminals in Debian GNU/Linux 8 (Jessy) - inside the X
> Server -
> the problem does not arise.
>
> I just mentioned Debian GNU/Linux 8 (Jessy) here because they migrated
> recently from
> SysV to systemd init scheme, so I thing it is a relevant comparison.
>
I'm not particularly familiar with systemd, but on the one occasion
I tried it, I was using a UTF-8 locale (and a font which had a
unicode map). Looking at 7.6, this is handled in /etc/vconsole.conf
and mostly controlled by the FONT variable.
Every modern distro uses UTF-8, not old legacy iso-8859-X variants,
and I do not see any overrides in section 7.6 of the systemd-7.6
book. So, I guess you are already using a UTF-8 locale.
But which FONT are you using ?
The handling of fonts for the console and for X is completely
different. In the console, at least for those of us who use the kbd
package (debian doesn't), you pick a font from those in
/usr/share/consolefonts.
Some of those are old pre-unicode, so choose a font which has a
.psfu. part within its name. If you are using an 8x16 font, which
is usually the BIOS default, and if your console comes up with white
text on a black background, I suggest that you could try temporarily
changing to LatGrkCyr-8x16 - the example in that book leads me to
believe that the .psfu.gz part should not be specified.
If your terminal comes up as black on white, that font might not be
pleasant (thin characters on a bright background). If so,
LatArCyrHeb-16 might let you see what is going on.
If you can get those to work at all, even if the
double-quotes-are-wrong problem still exists, please run
'showconsolefont'. You may in any case want to use that to find out
which of the available fonts you prefer, along with 'setfont' to try
different fonts in that TTY. Do the double quotes and portuguese
accented letters display correctly in any of those fonts ?
And if the double quotes ARE still wrong, please tell us which
locale settings you are using : pt_BR should already be a UTF-8
locale. AH! in current glibc the pt_BR options are:
pt_BR
pt_BR.iso88591
pt_BR.utf8
Are you using the iso88591 version ? If so, you might have problems
with any existing non-ASCII text.
>
> - ------------------------------
>
> Adicionaly, the caracter ã if not being displayed.
>
> As most of you already had notice, here in Brazil and there in
> Portugal we must use the ã caracter due to orthografic rules
> requirements.
>
Of course, that is what Unicode and UTF-8 are for. I normally reply
to mail from a term within X, where a lot more characters can be
displayed (the console is limited to 256 or 512), and I have
settings for most of the latin accented letters, so I can type
a with acute á
a with circumflex â
a with tilde ã
a with grave à
c with cedilla ç
plus a lot of others which will not be relevant to your current
problem. And I can read all of them when using UTF-8.
BUT - in UTF-8 these are all multi-byte characters (two bytes for
these) - for a portuguese explanation try
https://pt.wikipedia.org/wiki/UTF-8
but tihat looks rather minimal, the English explanation at
https://en.wikipedia.org/wiki/UTF-8
has a lot more detail, particularly the Codepage layout table which
shows how and when the characters use 2, 3, and 4 bytes.
>
> - ------------------------------
> - ------------------------------
>
>
> To solve such a problems, the mentioned configuration is mandatory,
> at least by now, especially:
>
> # CONFIG_DRM_I915 is not set
[ snipped - this is nothing to do with the kernel configuration ]
>
> I hope be clarified the goal of this post.
>
>
> Best regards.
>
I think you clarified it. Please do not 'top post' - we prefer you
to reply the way I am doing : responses to particular items in the
mail got after the items to which they relate,
https://en.wikipedia.org/wiki/Posting_style#Top-posting -
unfortunately, that page is not available in portuguese.
ĸen
--
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
