Bug 798 - add russian IBM866 encoding to luit
Summary: add russian IBM866 encoding to luit
Status: CLOSED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: App/luit (show other bugs)
Version: unspecified
Hardware: All All
: high minor
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 269
  Show dependency tree / graph
 
Reported: 2004-06-23 05:42 UTC by Konstantin Stopani
Modified: 2011-10-15 16:41 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Konstantin Stopani 2004-06-23 05:42:57 UTC 
Excuse me for posting it in bugzilla, but i simply had no time
A little update to xc/programs/luit/charset.c to help luit understand russian
IBM866 encoding

--- charset.c	2004-06-23 14:10:46.000000000 +0400
+++ charset-old.c	2004-06-23 14:13:03.073052936 +0400
@@ -133,7 +133,6 @@
 
     {"KOI8-R", T_128, 0, "koi8-r", 0x80, 0, 0},
     {"KOI8-U", T_128, 0, "koi8-u", 0x80, 0, 0},
-    {"IBM866", T_128, 0, "ibm-cp866", 0x80,0, 0},
     {"KOI8-RU", T_128, 0, "koi8-ru", 0x80, 0, 0},
     {"CP 1252", T_128, 0, "microsoft-cp1252", 0x80, 0, 0},
     {"CP 1251", T_128, 0, "microsoft-cp1251", 0x80, 0, 0},
@@ -411,8 +410,6 @@
     { "ISO8859-16", 0, 2, "ASCII", NULL, "ISO 8859-16", NULL, NULL},
     { "KOI8-R", 0, 2, "ASCII", NULL, "KOI8-R", NULL, NULL},
     { "CP1251", 0, 2, "ASCII", NULL, "CP 1251", NULL, NULL},
-/*    {"IBM866", T_128, 0, "ibm-cp866", 0x80,0, 0}, */
-    { "IBM866", 0, 2, "ASCII", NULL, "IBM866", NULL, NULL},
     { "TCVN", 0, 2, "ASCII", NULL, "TCVN", NULL, NULL},
     { "eucCN", 0, 1, "ASCII", "GB 2312", NULL, NULL, NULL},
     { "GB2312", 0, 1, "ASCII", "GB 2312", NULL, NULL, NULL},
Comment 1 Juliusz Chroboczek 2006-10-31 08:06:49 UTC 
I've added CP 437, 850 and 866 to the encodings vector.  Unlike your patch,
I didn't touch the locale vector, so you'll need to do something like

  luit -gr g2 -g2 cp866

                                               Juliusz

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.