Encoding problem with caption string (for %M) and constants (assumes latin1)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| screen |
Unknown
|
Unknown
|
|||
| screen (Debian) |
Confirmed
|
Unknown
|
|||
| screen (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: screen
When using %M in the caption, this should be "Mär" currently in Germany, but it does not get displayed properly (shows up as "Mär").
Also when using "Mär" directly as string in the caption setup, and the .screenrc file is encoded as utf8, it will get displayed wrong.
To work around this second issue, you have to encode the config file in latin1/iso-8859-1.
The first problem (wrong display of %M) remains still, despite of the config file encoding.
It seems that screen itself gets confused between the resolving of %M and the display itself.
REPRODUCE:
1. Add the following to ~/.screenrc:
caption always "%M Mär"
2. Start screen
3. Verify caption line
ProblemType: Bug
Architecture: i386
Date: Mon Mar 1 21:35:09 2010
DistroRelease: Ubuntu 10.04
NonfreeKernelMo
Package: screen 4.0.3-14ubuntu1
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: screen
Uname: Linux 2.6.32-14-generic i686
|
|
#1 |
|
|
#2 |
| Daniel Hahler (blueyed) wrote Encoding problem with caption string (assumes latin1) | #3 |
| Daniel Hahler (blueyed) wrote | #4 |
| summary: |
- Encoding problem with caption string (assumes latin1) + Encoding problem with caption string (for %M) and constants (assumes + latin1) |
| Daniel Hahler (blueyed) wrote | #5 |
| Changed in screen (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in screen (Debian): | |
| status: | Unknown → New |
| Changed in screen (Debian): | |
| status: | New → Confirmed |
At Wed, 15 Oct 2003 14:56:42 -0200,
Leonardo Boiko wrote:
> Japanese characters don't display correctly in screen's ``caption'' if
> using ja_JP.UTF-8 locale.
>
> I tried Portuguese UTF-8 characters and they seem to work fine, as well
> as Japanese EUC-JP characters. The problem is specific with
> ja_JP.UTF-8.
I treid such situation on my environment, like the following:
$ script
$ screen -c foo
-- foo
caption always "テスト"
--
Then I checked the real screen output.
The string "テスト" is the following byte sequences:
e3 83 86 e3 82 b9 e3 83 88
And the follwoing is the output of screen command:
c3 a3 c2 83 c2 86 c3 a3 c2 82 c2 b9 c3 a3 c2 83 c2 88
I don't know why such conversion was occured.
--
NOKUBI Takatsugu
E-mail: <email address hidden>
<email address hidden> / <email address hidden>