* how to change file coding system
@ 2005-08-12 8:34 Martin Monsorno
2005-08-12 11:30 ` Eli Zaretskii
[not found] ` <mailman.3519.1123846596.20277.help-gnu-emacs@gnu.org>
0 siblings, 2 replies; 38+ messages in thread
From: Martin Monsorno @ 2005-08-12 8:34 UTC (permalink / raw)
Hi,
I have a c-file which file (the command) claims to be a "UTF-8 Unicode
C program text". Now I want to make it a 8859 file, so in the emacs
buffer visiting it I say:
C-x <RET> f iso-8859-1-unix <RET>
and
C-x C-s
Afterwards, file (the command) says the same as before. Did I miss
something?
--
Martin
^ permalink raw reply [flat|nested] 38+ messages in thread* Re: how to change file coding system 2005-08-12 8:34 how to change file coding system Martin Monsorno @ 2005-08-12 11:30 ` Eli Zaretskii [not found] ` <mailman.3519.1123846596.20277.help-gnu-emacs@gnu.org> 1 sibling, 0 replies; 38+ messages in thread From: Eli Zaretskii @ 2005-08-12 11:30 UTC (permalink / raw) > From: Martin Monsorno <mmonsorno@gmx-gmbh.de> > Date: Fri, 12 Aug 2005 10:34:31 +0200 > > I have a c-file which file (the command) claims to be a "UTF-8 Unicode > C program text". Now I want to make it a 8859 file, so in the emacs > buffer visiting it I say: > C-x <RET> f iso-8859-1-unix <RET> > and > C-x C-s That is the right way. > Afterwards, file (the command) says the same as before. Did I miss > something? Do you have a reason to believe `file' more than you believe Emacs? That is, is it possible that `file' lies? Can you find a character in the file after translation that is not Latin-1, and if you can, what is that character? One possibility is that you have in that file a character whose code is outside the valid range of Latin-1 codepoints. But that's a wild guess, you need to find such a character and type "C-u C-x =" with the cursor on it, to see what it is. ^ permalink raw reply [flat|nested] 38+ messages in thread
[parent not found: <mailman.3519.1123846596.20277.help-gnu-emacs@gnu.org>]
* Re: how to change file coding system [not found] ` <mailman.3519.1123846596.20277.help-gnu-emacs@gnu.org> @ 2005-08-12 12:32 ` Pascal Bourguignon 2005-08-12 15:04 ` Eli Zaretskii 2005-08-12 15:36 ` Peter Dyballa 2005-08-12 13:33 ` Martin Monsorno 1 sibling, 2 replies; 38+ messages in thread From: Pascal Bourguignon @ 2005-08-12 12:32 UTC (permalink / raw) Eli Zaretskii <eliz@gnu.org> writes: > Do you have a reason to believe `file' more than you believe Emacs? > That is, is it possible that `file' lies? Can you find a character in > the file after translation that is not Latin-1, and if you can, what > is that character? It's rather hard. If you include control codes both in the rows 0&1 and 8&9, then Latin-1 uses the whole 256 codes. NUL SOH STX ETX EOT ENQ ACK BEL BS TAB LF VT FF CR SO SI DLE DC1 DC2 DC3 DC4 NAK SYN ETB CAN EM SUB ESC FS GS RS US SP ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~ DEL PAD HOP BPH NBH IND NEL SSA ESA HTS HTJ VTS PLD PLU RI SS2 SS3 DCS PU1 PU2 STS CCH MW SPA EPA SOS SGCI SCI CSI ST OSC PM APC ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « ¬ ® ¯ ° ± ² ³ ´ µ ¶ · ¸ ¹ º » ¼ ½ ¾ ¿ À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï Ð Ñ Ò Ó Ô Õ Ö × Ø Ù Ú Û Ü Ý Þ ß à á â ã ä å æ ç è é ê ë ì í î ï ð ñ ò ó ô õ ö ÷ ø ù ú û ü ý þ ÿ > One possibility is that you have in that file a character whose code > is outside the valid range of Latin-1 codepoints. But that's a wild > guess, you need to find such a character and type "C-u C-x =" with the > cursor on it, to see what it is. Or use: od -t x1 -t c example.c -- __Pascal Bourguignon__ http://www.informatimago.com/ Cats meow out of angst "Thumbs! If only we had thumbs! We could break so much!" ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-12 12:32 ` Pascal Bourguignon @ 2005-08-12 15:04 ` Eli Zaretskii 2005-08-12 15:36 ` Peter Dyballa 1 sibling, 0 replies; 38+ messages in thread From: Eli Zaretskii @ 2005-08-12 15:04 UTC (permalink / raw) > From: Pascal Bourguignon <spam@mouse-potato.com> > Date: Fri, 12 Aug 2005 14:32:53 +0200 > > Eli Zaretskii <eliz@gnu.org> writes: > > Do you have a reason to believe `file' more than you believe Emacs? > > That is, is it possible that `file' lies? Can you find a character in > > the file after translation that is not Latin-1, and if you can, what > > is that character? > > It's rather hard. If you include control codes both in the rows 0&1 > and 8&9, then Latin-1 uses the whole 256 codes. ??? Look at the codes in the file: the range between 0x80 and 0xa0 is not used, it's for control characters that should never appear in a text file. ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-12 12:32 ` Pascal Bourguignon 2005-08-12 15:04 ` Eli Zaretskii @ 2005-08-12 15:36 ` Peter Dyballa 1 sibling, 0 replies; 38+ messages in thread From: Peter Dyballa @ 2005-08-12 15:36 UTC (permalink / raw) Am 12.08.2005 um 14:32 schrieb Pascal Bourguignon: > PAD HOP BPH NBH IND NEL SSA ESA HTS HTJ VTS PLD PLU RI > SS2 SS3 > DCS PU1 PU2 STS CCH MW SPA EPA SOS SGCI SCI CSI ST OSC > PM APC > Pay attention: these are *not* (I repeat: *NOT*) part of Latin-1. They're only 8 bit control codes ... But they are part of Mac Roman, MS Windows, NeXT, KOI8 ... -- Greetings Pete There's no sense in being precise when you don't even know what you're talking about. -- John von Neumann Apple's Mail can sometimes be so funny ... ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system [not found] ` <mailman.3519.1123846596.20277.help-gnu-emacs@gnu.org> 2005-08-12 12:32 ` Pascal Bourguignon @ 2005-08-12 13:33 ` Martin Monsorno 2005-08-12 15:06 ` Eli Zaretskii ` (2 more replies) 1 sibling, 3 replies; 38+ messages in thread From: Martin Monsorno @ 2005-08-12 13:33 UTC (permalink / raw) Eli Zaretskii <eliz@gnu.org> writes: >> From: Martin Monsorno <mmonsorno@gmx-gmbh.de> >> Date: Fri, 12 Aug 2005 10:34:31 +0200 >> >> I have a c-file which file (the command) claims to be a "UTF-8 Unicode >> C program text". Now I want to make it a 8859 file, so in the emacs >> buffer visiting it I say: >> C-x <RET> f iso-8859-1-unix <RET> >> and >> C-x C-s > > That is the right way. > >> Afterwards, file (the command) says the same as before. Did I miss >> something? > > Do you have a reason to believe `file' more than you believe Emacs? Not generally. But as the file is under source control and "cvs diff" shows those many lines containing german umlauts, I suppose that file is working correctly. BTW: the real culprit is eclipse, that converted the file when writing >:( > > That is, is it possible that `file' lies? Can you find a character in > the file after translation that is not Latin-1, and if you can, what > is that character? > � doesn't seem like an 'ü' to me > > One possibility is that you have in that file a character whose code > is outside the valid range of Latin-1 codepoints. But that's a wild > guess, you need to find such a character and type "C-u C-x =" with the > cursor on it, to see what it is. the umlauts are not de-/encoded correctly, don't know whom to blame (however, most of the times it's eclipse). and i also don't know how to handle this problem. -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-12 13:33 ` Martin Monsorno @ 2005-08-12 15:06 ` Eli Zaretskii 2005-08-12 15:52 ` Pascal Bourguignon [not found] ` <mailman.3561.1123859480.20277.help-gnu-emacs@gnu.org> 2 siblings, 0 replies; 38+ messages in thread From: Eli Zaretskii @ 2005-08-12 15:06 UTC (permalink / raw) > From: Martin Monsorno <mmonsorno@gmx-gmbh.de> > Date: Fri, 12 Aug 2005 15:33:22 +0200 > > the umlauts are not de-/encoded correctly, don't know whom to blame Sorry, I don't understand this. Please show the details. ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-12 13:33 ` Martin Monsorno 2005-08-12 15:06 ` Eli Zaretskii @ 2005-08-12 15:52 ` Pascal Bourguignon 2005-08-12 16:33 ` Joe Corneli [not found] ` <mailman.3561.1123859480.20277.help-gnu-emacs@gnu.org> 2 siblings, 1 reply; 38+ messages in thread From: Pascal Bourguignon @ 2005-08-12 15:52 UTC (permalink / raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset=utf-8, Size: 49208 bytes --] Martin Monsorno <mmonsorno@gmx-gmbh.de> writes: > � > > doesn't seem like an 'ü' to me Neither to me. The three bytes I received were ef, bf and bd, displayed as: "LATIN_SMALL_LETTER_I_WITH_DIAERESIS" "INVERTED_QUESTION_MARK" "VULGAR_FRACTION_ONE_HALF" in the iso-8859-1 encoding of the message. If you want to send us unicode character you'd better use utf-8! $ od -t x1 /tmp/a 0000000 ef bf bd 0a 0000004 $ cat /tmp/a # I've got a utf-8 terminal � and this is a unicode "REPLACEMENT_CHARACTER". > the umlauts are not de-/encoded correctly, don't know whom to blame > (however, most of the times it's eclipse). and i also don't know how > to handle this problem. If you were expecting a ü, then it's not utf-8. You have to know what encoding it is exactly. What's sure, is that it's not a ü in any known encoding: $ for encoding in $(iconv -l|sed -e '1,/^$/d' -e /:/d -e s-//--) ; do printf "%24s " "$encoding" ; ch=$( iconv -f $encoding -t utf-8 </tmp/a || echo bad ) ; case "$ch" in *bad) ;; ü) echo "*** GOT ü ***" ;; *) echo "got $ch" ;; esac ; done 437 got ∩â”â•œ 500 got ÕרŽ 500V1 got ÕרŽ 850 got ´â”¢ 851 got ´â”Ξ 852 got ´â”Å» 855 got â„–â”й 856 got ´â”¢ 857 got ´â”¢ 860 got ∩â”â•œ 861 got ∩â”â•œ 862 got ∩â”â•œ 863 got ∩â”â•œ 864 got ﻡ؟ﺵ 865 got ∩â”â•œ 866 got Ñâ”â•œ 866NAV got Ñâ”â•œ 869 got ΄â”Ξ 874 got à¹à¸Ÿà¸ 904 iconv: illegal input sequence at position 0 1026 got ÕרŽ 1046 got Ù؟ﺿ 1047 got Õ×]ÂŽ 8859_1 got � 8859_2 got ÄÅ¼Ë 8859_3 got ïż½ 8859_4 got Ä«Å‹ÅŠ 8859_5 got ÑПР8859_6 iconv: illegal input sequence at position 2 8859_7 got ον 8859_8 iconv: illegal input sequence at position 1 8859_9 got � ANSI_X3.4-1968 iconv: illegal input sequence at position 0 ANSI_X3.4-1986 iconv: illegal input sequence at position 0 ANSI_X3.4 iconv: illegal input sequence at position 0 ANSI_X3.110-1983 got ʼn¿½ ANSI_X3.110 got ʼn¿½ ARABIC iconv: illegal input sequence at position 2 ARABIC7 iconv: illegal input sequence at position 0 ARMSCII-8 got Õ¿Õ§Õ¦ ASCII iconv: illegal input sequence at position 0 ASMO-708 iconv: illegal input sequence at position 2 ASMO_449 iconv: illegal input sequence at position 0 BALTIC got ļæ½ BIG-5 iconv: illegal input sequence at position 2 BIG-FIVE iconv: illegal input sequence at position 2 BIG5-HKSCS iconv: illegal input sequence at position 2 BIG5 iconv: illegal input sequence at position 2 BIG5HKSCS iconv: illegal input sequence at position 2 BIGFIVE iconv: illegal input sequence at position 2 BS_4730 iconv: illegal input sequence at position 0 CA iconv: illegal input sequence at position 0 CN-BIG5 iconv: illegal input sequence at position 2 CN-GB iconv: illegal input sequence at position 2 CN iconv: illegal input sequence at position 0 CP-AR iconv: illegal input sequence at position 0 CP-GR got ΄â”Ξ CP-HU got ∩â”â•œ CP037 got ÕרŽ CP038 iconv: illegal input sequence at position 0 CP273 got ÕרŽ CP274 iconv: illegal input sequence at position 0 CP275 iconv: illegal input sequence at position 0 CP278 got ÕרŽ CP280 got ÕרŽ CP281 iconv: illegal input sequence at position 0 CP282 got ÕרŽ CP284 got Õ×~ÂŽ CP285 got ÕרŽ CP290 iconv: illegal input sequence at position 0 CP297 got Õ×~ÂŽ CP367 iconv: illegal input sequence at position 0 CP420 got ٥هنŽ CP423 got üψφŽ CP424 iconv: illegal input sequence at position 0 CP437 got ∩â”â•œ CP500 got ÕרŽ CP737 got ÎŽâ”â•œ CP775 got ’â”Ä® CP813 got ον CP819 got � CP850 got ´â”¢ CP851 got ´â”Ξ CP852 got ´â”Å» CP855 got â„–â”й CP856 got ´â”¢ CP857 got ´â”¢ CP860 got ∩â”â•œ CP861 got ∩â”â•œ CP862 got ∩â”â•œ CP863 got ∩â”â•œ CP864 got ﻡ؟ﺵ CP865 got ∩â”â•œ CP866 got Ñâ”â•œ CP866NAV got Ñâ”â•œ CP868 iconv: illegal input sequence at position 0 CP869 got ΄â”Ξ CP870 got ÅרŽ CP871 got ÕרŽ CP874 got à¹à¸Ÿà¸ CP875 got ¬ψφŽ CP880 got ЫГЕŽ CP891 iconv: illegal input sequence at position 0 CP903 iconv: illegal input sequence at position 0 CP904 iconv: illegal input sequence at position 0 CP905 got Ä Ã—Â¨ÂŽ CP912 got ÄÅ¼Ë CP915 got ÑПРCP916 iconv: illegal input sequence at position 1 CP918 iconv: illegal input sequence at position 0 CP920 got � CP922 got � CP930 iconv: illegal input sequence at position 0 CP932 iconv: illegal input sequence at position 0 CP933 iconv: illegal input sequence at position 0 CP935 iconv: illegal input sequence at position 0 CP936 iconv: illegal input sequence at position 2 CP937 iconv: illegal input sequence at position 0 CP939 iconv: illegal input sequence at position 0 CP949 iconv: illegal input sequence at position 2 CP950 iconv: illegal input sequence at position 2 CP1004 got � CP1026 got ÕרŽ CP1046 got Ù؟ﺿ CP1047 got Õ×]ÂŽ CP1070 got ÕרŽ CP1079 got Õ×~ÂŽ CP1081 got Õ×~ÂŽ CP1084 got ÕרŽ CP1089 iconv: illegal input sequence at position 2 CP1124 got ÑПРCP1125 got Ñâ”â•œ CP1129 got � CP1132 iconv: illegal input sequence at position 0 CP1133 iconv: illegal input sequence at position 0 CP1160 got ๊ิาŽ CP1161 got à¹à¸Ÿà¸ CP1162 got à¹à¸Ÿà¸ CP1163 got � CP1164 got Æ Ã—Å“ÂŽ CP1250 got ÄÅ¼Ë CP1251 got пїЅ CP1252 got � CP1253 got ον CP1254 got � CP1255 got ן¿½ CP1256 got ï؟½ CP1257 got ļæ½ CP1258 got � CP1361 iconv: illegal input sequence at position 2 CP10007 got пњљ CPIBM861 got ∩â”â•œ CSA7-1 iconv: illegal input sequence at position 0 CSA7-2 iconv: illegal input sequence at position 0 CSASCII iconv: illegal input sequence at position 0 CSA_T500-1983 got ʼn¿½ CSA_T500 got ʼn¿½ CSA_Z243.4-1985-1 iconv: illegal input sequence at position 0 CSA_Z243.4-1985-2 iconv: illegal input sequence at position 0 CSA_Z243.419851 iconv: illegal input sequence at position 0 CSA_Z243.419852 iconv: illegal input sequence at position 0 CSDECMCS got � CSEBCDICATDE iconv: illegal input sequence at position 0 CSEBCDICATDEA iconv: illegal input sequence at position 0 CSEBCDICCAFR iconv: illegal input sequence at position 0 CSEBCDICDKNO iconv: illegal input sequence at position 0 CSEBCDICDKNOA iconv: illegal input sequence at position 0 CSEBCDICES iconv: illegal input sequence at position 0 CSEBCDICESA iconv: illegal input sequence at position 0 CSEBCDICESS iconv: illegal input sequence at position 0 CSEBCDICFISE iconv: illegal input sequence at position 0 CSEBCDICFISEA iconv: illegal input sequence at position 0 CSEBCDICFR iconv: illegal input sequence at position 0 CSEBCDICIT iconv: illegal input sequence at position 0 CSEBCDICPT iconv: illegal input sequence at position 0 CSEBCDICUK iconv: illegal input sequence at position 0 CSEBCDICUS iconv: illegal input sequence at position 0 CSEUCKR iconv: illegal input sequence at position 2 CSEUCPKDFMTJAPANESE iconv: illegal input sequence at position 2 CSGB2312 iconv: illegal input sequence at position 2 CSHPROMAN8 got ÿ¢§ CSIBM037 got ÕרŽ CSIBM038 iconv: illegal input sequence at position 0 CSIBM273 got ÕרŽ CSIBM274 iconv: illegal input sequence at position 0 CSIBM275 iconv: illegal input sequence at position 0 CSIBM277 got ÕרŽ CSIBM278 got ÕרŽ CSIBM280 got ÕרŽ CSIBM281 iconv: illegal input sequence at position 0 CSIBM284 got Õ×~ÂŽ CSIBM285 got ÕרŽ CSIBM290 iconv: illegal input sequence at position 0 CSIBM297 got Õ×~ÂŽ CSIBM420 got ٥هنŽ CSIBM423 got üψφŽ CSIBM424 iconv: illegal input sequence at position 0 CSIBM500 got ÕרŽ CSIBM851 got ´â”Ξ CSIBM855 got â„–â”й CSIBM856 got ´â”¢ CSIBM857 got ´â”¢ CSIBM860 got ∩â”â•œ CSIBM863 got ∩â”â•œ CSIBM864 got ﻡ؟ﺵ CSIBM865 got ∩â”â•œ CSIBM866 got Ñâ”â•œ CSIBM868 iconv: illegal input sequence at position 0 CSIBM869 got ΄â”Ξ CSIBM870 got ÅרŽ CSIBM871 got ÕרŽ CSIBM880 got ЫГЕŽ CSIBM891 iconv: illegal input sequence at position 0 CSIBM903 iconv: illegal input sequence at position 0 CSIBM904 iconv: illegal input sequence at position 0 CSIBM905 got Ä Ã—Â¨ÂŽ CSIBM918 iconv: illegal input sequence at position 0 CSIBM922 got � CSIBM930 iconv: illegal input sequence at position 0 CSIBM932 iconv: illegal input sequence at position 0 CSIBM933 iconv: illegal input sequence at position 0 CSIBM935 iconv: illegal input sequence at position 0 CSIBM937 iconv: illegal input sequence at position 0 CSIBM939 iconv: illegal input sequence at position 0 CSIBM943 iconv: illegal input sequence at position 0 CSIBM1026 got ÕרŽ CSIBM1124 got ÑПРCSIBM1129 got � CSIBM1132 iconv: illegal input sequence at position 0 CSIBM1133 iconv: illegal input sequence at position 0 CSIBM1160 got ๊ิาŽ CSIBM1161 got à¹à¸Ÿà¸ CSIBM1163 got � CSIBM1164 got Æ Ã—Å“ÂŽ CSIBM11621162 got à¹à¸Ÿà¸ CSISO4UNITEDKINGDOM iconv: illegal input sequence at position 0 CSISO10SWEDISH iconv: illegal input sequence at position 0 CSISO11SWEDISHFORNAMES iconv: illegal input sequence at position 0 CSISO14JISC6220RO iconv: illegal input sequence at position 0 CSISO15ITALIAN iconv: illegal input sequence at position 0 CSISO16PORTUGESE iconv: illegal input sequence at position 0 CSISO17SPANISH iconv: illegal input sequence at position 0 CSISO18GREEK7OLD iconv: illegal input sequence at position 0 CSISO19LATINGREEK iconv: illegal input sequence at position 0 CSISO21GERMAN iconv: illegal input sequence at position 0 CSISO25FRENCH iconv: illegal input sequence at position 0 CSISO27LATINGREEK1 iconv: illegal input sequence at position 0 CSISO49INIS iconv: illegal input sequence at position 0 CSISO50INIS8 iconv: illegal input sequence at position 0 CSISO51INISCYRILLIC iconv: illegal input sequence at position 0 CSISO58GB1988 iconv: illegal input sequence at position 0 CSISO60DANISHNORWEGIAN iconv: illegal input sequence at position 0 CSISO60NORWEGIAN1 iconv: illegal input sequence at position 0 CSISO61NORWEGIAN2 iconv: illegal input sequence at position 0 CSISO69FRENCH iconv: illegal input sequence at position 0 CSISO84PORTUGUESE2 iconv: illegal input sequence at position 0 CSISO85SPANISH2 iconv: illegal input sequence at position 0 CSISO86HUNGARIAN iconv: illegal input sequence at position 0 CSISO88GREEK7 iconv: illegal input sequence at position 0 CSISO89ASMO449 iconv: illegal input sequence at position 0 CSISO90 got ʼn¿½ CSISO92JISC62991984B iconv: illegal input sequence at position 0 CSISO99NAPLPS got ʼn¿½ CSISO103T618BIT got ʼn¿½ CSISO111ECMACYRILLIC got ОФ CSISO121CANADIAN1 iconv: illegal input sequence at position 0 CSISO122CANADIAN2 iconv: illegal input sequence at position 0 CSISO139CSN369103 got ÄÅ¼Ë CSISO141JUSIB1002 iconv: illegal input sequence at position 0 CSISO143IECP271 got ‰∃¬ CSISO150 iconv: illegal input sequence at position 0 CSISO150GREEKCCITT iconv: illegal input sequence at position 0 CSISO151CUBA iconv: illegal input sequence at position 0 CSISO153GOST1976874 got ÑПРCSISO646DANISH iconv: illegal input sequence at position 0 CSISO2022CN iconv: illegal input sequence at position 0 CSISO2022JP iconv: illegal input sequence at position 0 CSISO2022JP2 iconv: illegal input sequence at position 0 CSISO2022KR iconv: illegal input sequence at position 0 CSISO2033 iconv: illegal input sequence at position 0 CSISO5427CYRILLIC iconv: illegal input sequence at position 0 CSISO5427CYRILLIC1981 iconv: illegal input sequence at position 0 CSISO5428GREEK iconv: illegal input sequence at position 0 CSISO10367BOX iconv: illegal input sequence at position 0 CSISOLATIN1 got � CSISOLATIN2 got ÄÅ¼Ë CSISOLATIN3 got ïż½ CSISOLATIN4 got Ä«Å‹ÅŠ CSISOLATIN5 got � CSISOLATIN6 got ïŋ― CSISOLATINARABIC iconv: illegal input sequence at position 2 CSISOLATINCYRILLIC got ÑПРCSISOLATINGREEK got ον CSISOLATINHEBREW iconv: illegal input sequence at position 1 CSKOI8R got О©╫ CSKSC5636 iconv: illegal input sequence at position 0 CSMACINTOSH got ÔøΩ CSNATSDANO iconv: illegal input sequence at position 0 CSNATSSEFI iconv: illegal input sequence at position 0 CSN_369103 got ÄÅ¼Ë CSPC8CODEPAGE437 got ∩â”â•œ CSPC775BALTIC got ’â”Ä® CSPC850MULTILINGUAL got ´â”¢ CSPC862LATINHEBREW got ∩â”â•œ CSPCP852 got ´â”Å» CSSHIFTJIS iconv: illegal input sequence at position 0 CSUCS4 iconv: illegal input sequence at position 0 CSUNICODE got 뿯ઽ CUBA iconv: illegal input sequence at position 0 CWI-2 got ∩â”â•œ CWI got ∩â”â•œ CYRILLIC got ÑПРDE iconv: illegal input sequence at position 0 DEC-MCS got � DEC got � DECMCS got � DIN_66003 iconv: illegal input sequence at position 0 DK iconv: illegal input sequence at position 0 DS2089 iconv: illegal input sequence at position 0 DS_2089 iconv: illegal input sequence at position 0 E13B/ iconv: conversion from `E13B/' is not supported EBCDIC-AT-DE-A iconv: illegal input sequence at position 0 EBCDIC-AT-DE iconv: illegal input sequence at position 0 EBCDIC-BE iconv: illegal input sequence at position 0 EBCDIC-BR iconv: illegal input sequence at position 0 EBCDIC-CA-FR iconv: illegal input sequence at position 0 EBCDIC-CP-AR1 got ٥هنŽ EBCDIC-CP-AR2 iconv: illegal input sequence at position 0 EBCDIC-CP-BE got ÕרŽ EBCDIC-CP-CA got ÕרŽ EBCDIC-CP-CH got ÕרŽ EBCDIC-CP-DK got ÕרŽ EBCDIC-CP-ES got Õ×~ÂŽ EBCDIC-CP-FI got ÕרŽ EBCDIC-CP-FR got Õ×~ÂŽ EBCDIC-CP-GB got ÕרŽ EBCDIC-CP-GR got üψφŽ EBCDIC-CP-HE iconv: illegal input sequence at position 0 EBCDIC-CP-IS got ÕרŽ EBCDIC-CP-IT got ÕרŽ EBCDIC-CP-NL got ÕרŽ EBCDIC-CP-NO got ÕרŽ EBCDIC-CP-ROECE got ÅרŽ EBCDIC-CP-SE got ÕרŽ EBCDIC-CP-TR got Ä Ã—Â¨ÂŽ EBCDIC-CP-US got ÕרŽ EBCDIC-CP-WT got ÕרŽ EBCDIC-CP-YU got ÅרŽ EBCDIC-CYRILLIC got ЫГЕŽ EBCDIC-DK-NO-A iconv: illegal input sequence at position 0 EBCDIC-DK-NO iconv: illegal input sequence at position 0 EBCDIC-ES-A iconv: illegal input sequence at position 0 EBCDIC-ES-S iconv: illegal input sequence at position 0 EBCDIC-ES iconv: illegal input sequence at position 0 EBCDIC-FI-SE-A iconv: illegal input sequence at position 0 EBCDIC-FI-SE iconv: illegal input sequence at position 0 EBCDIC-FR iconv: illegal input sequence at position 0 EBCDIC-GREEK got ¬ψφŽ EBCDIC-INT iconv: illegal input sequence at position 0 EBCDIC-INT1 got Õ‗¨Ž EBCDIC-IS-FRISS iconv: illegal input sequence at position 0 EBCDIC-IT iconv: illegal input sequence at position 0 EBCDIC-JP-E iconv: illegal input sequence at position 0 EBCDIC-JP-KANA iconv: illegal input sequence at position 0 EBCDIC-PT iconv: illegal input sequence at position 0 EBCDIC-UK iconv: illegal input sequence at position 0 EBCDIC-US iconv: illegal input sequence at position 0 EBCDICATDE iconv: illegal input sequence at position 0 EBCDICATDEA iconv: illegal input sequence at position 0 EBCDICCAFR iconv: illegal input sequence at position 0 EBCDICDKNO iconv: illegal input sequence at position 0 EBCDICDKNOA iconv: illegal input sequence at position 0 EBCDICES iconv: illegal input sequence at position 0 EBCDICESA iconv: illegal input sequence at position 0 EBCDICESS iconv: illegal input sequence at position 0 EBCDICFISE iconv: illegal input sequence at position 0 EBCDICFISEA iconv: illegal input sequence at position 0 EBCDICFR iconv: illegal input sequence at position 0 EBCDICISFRISS iconv: illegal input sequence at position 0 EBCDICIT iconv: illegal input sequence at position 0 EBCDICPT iconv: illegal input sequence at position 0 EBCDICUK iconv: illegal input sequence at position 0 EBCDICUS iconv: illegal input sequence at position 0 ECMA-114 iconv: illegal input sequence at position 2 ECMA-118 got ον ECMA-128 got � ECMA-CYRILLIC got ОФ ECMACYRILLIC got ОФ ELOT_928 got ον ES iconv: illegal input sequence at position 0 ES2 iconv: illegal input sequence at position 0 EUC-CN iconv: illegal input sequence at position 2 EUC-JISX0213 iconv: illegal input sequence at position 2 EUC-JP iconv: illegal input sequence at position 2 EUC-KR iconv: illegal input sequence at position 2 EUC-TW iconv: illegal input sequence at position 2 EUCCN iconv: illegal input sequence at position 2 EUCJP iconv: illegal input sequence at position 2 EUCKR iconv: illegal input sequence at position 2 EUCTW iconv: illegal input sequence at position 2 FI iconv: illegal input sequence at position 0 FR iconv: illegal input sequence at position 0 GB iconv: illegal input sequence at position 0 GB2312 iconv: illegal input sequence at position 2 GB13000 iconv: illegal input sequence at position 2 GB18030 iconv: illegal input sequence at position 2 GBK iconv: illegal input sequence at position 2 GB_1988-80 iconv: illegal input sequence at position 0 GB_198880 iconv: illegal input sequence at position 0 GEORGIAN-ACADEMY got � GEORGIAN-PS got � GOST_19768-74 got ÑПРGOST_19768 got ÑПРGOST_1976874 got ÑПРGREEK-CCITT iconv: illegal input sequence at position 0 GREEK got ον GREEK7-OLD iconv: illegal input sequence at position 0 GREEK7 iconv: illegal input sequence at position 0 GREEK7OLD iconv: illegal input sequence at position 0 GREEK8 got ον GREEKCCITT iconv: illegal input sequence at position 0 HEBREW iconv: illegal input sequence at position 1 HP-ROMAN8 got ÿ¢§ HPROMAN8 got ÿ¢§ HU iconv: illegal input sequence at position 0 IBM-856 got ´â”¢ IBM-922 got � IBM-930 iconv: illegal input sequence at position 0 IBM-932 iconv: illegal input sequence at position 0 IBM-933 iconv: illegal input sequence at position 0 IBM-935 iconv: illegal input sequence at position 0 IBM-937 iconv: illegal input sequence at position 0 IBM-939 iconv: illegal input sequence at position 0 IBM-943 iconv: illegal input sequence at position 0 IBM-1046 got Ù؟ﺿ IBM-1124 got ÑПРIBM-1129 got � IBM-1132 iconv: illegal input sequence at position 0 IBM-1133 iconv: illegal input sequence at position 0 IBM-1160 got ๊ิาŽ IBM-1161 got à¹à¸Ÿà¸ IBM-1162 got à¹à¸Ÿà¸ IBM-1163 got � IBM-1164 got Æ Ã—Å“ÂŽ IBM037 got ÕרŽ IBM038 iconv: illegal input sequence at position 0 IBM256 got Õ‗¨Ž IBM273 got ÕרŽ IBM274 iconv: illegal input sequence at position 0 IBM275 iconv: illegal input sequence at position 0 IBM277 got ÕרŽ IBM278 got ÕרŽ IBM280 got ÕרŽ IBM281 iconv: illegal input sequence at position 0 IBM284 got Õ×~ÂŽ IBM285 got ÕרŽ IBM290 iconv: illegal input sequence at position 0 IBM297 got Õ×~ÂŽ IBM367 iconv: illegal input sequence at position 0 IBM420 got ٥هنŽ IBM423 got üψφŽ IBM424 iconv: illegal input sequence at position 0 IBM437 got ∩â”â•œ IBM500 got ÕרŽ IBM775 got ’â”Ä® IBM813 got ον IBM819 got � IBM848 got Ñâ”â•œ IBM850 got ´â”¢ IBM851 got ´â”Ξ IBM852 got ´â”Å» IBM855 got â„–â”й IBM856 got ´â”¢ IBM857 got ´â”¢ IBM860 got ∩â”â•œ IBM861 got ∩â”â•œ IBM862 got ∩â”â•œ IBM863 got ∩â”â•œ IBM864 got ﻡ؟ﺵ IBM865 got ∩â”â•œ IBM866 got Ñâ”â•œ IBM866NAV got Ñâ”â•œ IBM868 iconv: illegal input sequence at position 0 IBM869 got ΄â”Ξ IBM870 got ÅרŽ IBM871 got ÕרŽ IBM874 got à¹à¸Ÿà¸ IBM875 got ¬ψφŽ IBM880 got ЫГЕŽ IBM891 iconv: illegal input sequence at position 0 IBM903 iconv: illegal input sequence at position 0 IBM904 iconv: illegal input sequence at position 0 IBM905 got Ä Ã—Â¨ÂŽ IBM912 got ÄÅ¼Ë IBM915 got ÑПРIBM916 iconv: illegal input sequence at position 1 IBM918 iconv: illegal input sequence at position 0 IBM920 got � IBM922 got � IBM930 iconv: illegal input sequence at position 0 IBM932 iconv: illegal input sequence at position 0 IBM933 iconv: illegal input sequence at position 0 IBM935 iconv: illegal input sequence at position 0 IBM937 iconv: illegal input sequence at position 0 IBM939 iconv: illegal input sequence at position 0 IBM943 iconv: illegal input sequence at position 0 IBM1004 got � IBM1026 got ÕרŽ IBM1046 got Ù؟ﺿ IBM1047 got Õ×]ÂŽ IBM1089 iconv: illegal input sequence at position 2 IBM1124 got ÑПРIBM1129 got � IBM1132 iconv: illegal input sequence at position 0 IBM1133 iconv: illegal input sequence at position 0 IBM1160 got ๊ิาŽ IBM1161 got à¹à¸Ÿà¸ IBM1162 got à¹à¸Ÿà¸ IBM1163 got � IBM1164 got Æ Ã—Å“ÂŽ IEC_P27-1 got ‰∃¬ IEC_P271 got ‰∃¬ INIS-8 iconv: illegal input sequence at position 0 INIS-CYRILLIC iconv: illegal input sequence at position 0 INIS iconv: illegal input sequence at position 0 INIS8 iconv: illegal input sequence at position 0 INISCYRILLIC iconv: illegal input sequence at position 0 ISIRI-3342 iconv: illegal input sequence at position 0 ISIRI3342 iconv: illegal input sequence at position 0 ISO-2022-CN-EXT iconv: illegal input sequence at position 0 ISO-2022-CN iconv: illegal input sequence at position 0 ISO-2022-JP-2 iconv: illegal input sequence at position 0 ISO-2022-JP-3 iconv: illegal input sequence at position 0 ISO-2022-JP iconv: illegal input sequence at position 0 ISO-2022-KR iconv: illegal input sequence at position 0 ISO-8859-1 got � ISO-8859-2 got ÄÅ¼Ë ISO-8859-3 got ïż½ ISO-8859-4 got Ä«Å‹ÅŠ ISO-8859-5 got ÑПРISO-8859-6 iconv: illegal input sequence at position 2 ISO-8859-7 got ον ISO-8859-8 iconv: illegal input sequence at position 1 ISO-8859-9 got � ISO-8859-10 got ïŋ― ISO-8859-11 got à¹à¸Ÿà¸ ISO-8859-13 got ļæ½ ISO-8859-14 got ïṡẄ ISO-8859-15 got ï¿œ ISO-8859-16 got ïżœ ISO-10646 iconv: illegal input sequence at position 0 ISO-10646/UCS2/ got 뿯ઽ ISO-10646/UCS4/ iconv: illegal input sequence at position 0 ISO-10646/UTF-8/ got � ISO-10646/UTF8/ got � ISO-CELTIC got ïṡẄ ISO-IR-4 iconv: illegal input sequence at position 0 ISO-IR-6 iconv: illegal input sequence at position 0 ISO-IR-8-1 iconv: illegal input sequence at position 0 ISO-IR-9-1 iconv: illegal input sequence at position 0 ISO-IR-10 iconv: illegal input sequence at position 0 ISO-IR-11 iconv: illegal input sequence at position 0 ISO-IR-14 iconv: illegal input sequence at position 0 ISO-IR-15 iconv: illegal input sequence at position 0 ISO-IR-16 iconv: illegal input sequence at position 0 ISO-IR-17 iconv: illegal input sequence at position 0 ISO-IR-18 iconv: illegal input sequence at position 0 ISO-IR-19 iconv: illegal input sequence at position 0 ISO-IR-21 iconv: illegal input sequence at position 0 ISO-IR-25 iconv: illegal input sequence at position 0 ISO-IR-27 iconv: illegal input sequence at position 0 ISO-IR-37 iconv: illegal input sequence at position 0 ISO-IR-49 iconv: illegal input sequence at position 0 ISO-IR-50 iconv: illegal input sequence at position 0 ISO-IR-51 iconv: illegal input sequence at position 0 ISO-IR-54 iconv: illegal input sequence at position 0 ISO-IR-55 iconv: illegal input sequence at position 0 ISO-IR-57 iconv: illegal input sequence at position 0 ISO-IR-60 iconv: illegal input sequence at position 0 ISO-IR-61 iconv: illegal input sequence at position 0 ISO-IR-69 iconv: illegal input sequence at position 0 ISO-IR-84 iconv: illegal input sequence at position 0 ISO-IR-85 iconv: illegal input sequence at position 0 ISO-IR-86 iconv: illegal input sequence at position 0 ISO-IR-88 iconv: illegal input sequence at position 0 ISO-IR-89 iconv: illegal input sequence at position 0 ISO-IR-90 got ʼn¿½ ISO-IR-92 iconv: illegal input sequence at position 0 ISO-IR-98 iconv: illegal input sequence at position 0 ISO-IR-99 got ʼn¿½ ISO-IR-100 got � ISO-IR-101 got ÄÅ¼Ë ISO-IR-103 got ʼn¿½ ISO-IR-109 got ïż½ ISO-IR-110 got Ä«Å‹ÅŠ ISO-IR-111 got ОФ ISO-IR-121 iconv: illegal input sequence at position 0 ISO-IR-122 iconv: illegal input sequence at position 0 ISO-IR-126 got ον ISO-IR-127 iconv: illegal input sequence at position 2 ISO-IR-138 iconv: illegal input sequence at position 1 ISO-IR-139 got ÄÅ¼Ë ISO-IR-141 iconv: illegal input sequence at position 0 ISO-IR-143 got ‰∃¬ ISO-IR-144 got ÑПРISO-IR-148 got � ISO-IR-150 iconv: illegal input sequence at position 0 ISO-IR-151 iconv: illegal input sequence at position 0 ISO-IR-153 got ÑПРISO-IR-155 iconv: illegal input sequence at position 0 ISO-IR-156 got ʼn¿½ ISO-IR-157 got ïŋ― ISO-IR-166 got à¹à¸Ÿà¸ ISO-IR-179 got ļæ½ ISO-IR-193 got � ISO-IR-197 got ïǯʒ ISO-IR-199 got ïṡẄ ISO-IR-203 got ï¿œ ISO-IR-209 got ïǯʒ ISO-IR-226 got ïżœ ISO646-CA iconv: illegal input sequence at position 0 ISO646-CA2 iconv: illegal input sequence at position 0 ISO646-CN iconv: illegal input sequence at position 0 ISO646-CU iconv: illegal input sequence at position 0 ISO646-DE iconv: illegal input sequence at position 0 ISO646-DK iconv: illegal input sequence at position 0 ISO646-ES iconv: illegal input sequence at position 0 ISO646-ES2 iconv: illegal input sequence at position 0 ISO646-FI iconv: illegal input sequence at position 0 ISO646-FR iconv: illegal input sequence at position 0 ISO646-FR1 iconv: illegal input sequence at position 0 ISO646-GB iconv: illegal input sequence at position 0 ISO646-HU iconv: illegal input sequence at position 0 ISO646-IT iconv: illegal input sequence at position 0 ISO646-JP-OCR-B iconv: illegal input sequence at position 0 ISO646-JP iconv: illegal input sequence at position 0 ISO646-KR iconv: illegal input sequence at position 0 ISO646-NO iconv: illegal input sequence at position 0 ISO646-NO2 iconv: illegal input sequence at position 0 ISO646-PT iconv: illegal input sequence at position 0 ISO646-PT2 iconv: illegal input sequence at position 0 ISO646-SE iconv: illegal input sequence at position 0 ISO646-SE2 iconv: illegal input sequence at position 0 ISO646-US iconv: illegal input sequence at position 0 ISO646-YU iconv: illegal input sequence at position 0 ISO2022CN iconv: illegal input sequence at position 0 ISO2022CNEXT iconv: illegal input sequence at position 0 ISO2022JP iconv: illegal input sequence at position 0 ISO2022JP2 iconv: illegal input sequence at position 0 ISO2022KR iconv: illegal input sequence at position 0 ISO6937 got ʼn¿½ ISO8859-1 got � ISO8859-2 got ÄÅ¼Ë ISO8859-3 got ïż½ ISO8859-4 got Ä«Å‹ÅŠ ISO8859-5 got ÑПРISO8859-6 iconv: illegal input sequence at position 2 ISO8859-7 got ον ISO8859-8 iconv: illegal input sequence at position 1 ISO8859-9 got � ISO8859-10 got ïŋ― ISO8859-11 got à¹à¸Ÿà¸ ISO8859-13 got ļæ½ ISO8859-14 got ïṡẄ ISO8859-15 got ï¿œ ISO8859-16 got ïżœ ISO88591 got � ISO88592 got ÄÅ¼Ë ISO88593 got ïż½ ISO88594 got Ä«Å‹ÅŠ ISO88595 got ÑПРISO88596 iconv: illegal input sequence at position 2 ISO88597 got ον ISO88598 iconv: illegal input sequence at position 1 ISO88599 got � ISO885910 got ïŋ― ISO885911 got à¹à¸Ÿà¸ ISO885913 got ļæ½ ISO885914 got ïṡẄ ISO885915 got ï¿œ ISO885916 got ïżœ ISO_2033-1983 iconv: illegal input sequence at position 0 ISO_2033 iconv: illegal input sequence at position 0 ISO_5427-EXT iconv: illegal input sequence at position 0 ISO_5427 iconv: illegal input sequence at position 0 ISO_5427EXT iconv: illegal input sequence at position 0 ISO_5428 iconv: illegal input sequence at position 0 ISO_6937-2 got ʼn¿½ ISO_6937 got ʼn¿½ ISO_8859-1 got � ISO_8859-2 got ÄÅ¼Ë ISO_8859-3 got ïż½ ISO_8859-4 got Ä«Å‹ÅŠ ISO_8859-5 got ÑПРISO_8859-6 iconv: illegal input sequence at position 2 ISO_8859-7 got ον ISO_8859-8 iconv: illegal input sequence at position 1 ISO_8859-9 got � ISO_8859-10 got ïŋ― ISO_8859-14 got ïṡẄ ISO_9036 iconv: illegal input sequence at position 0 ISO_10367-BOX iconv: illegal input sequence at position 0 ISO_10367BOX iconv: illegal input sequence at position 0 ISO_69372 got ʼn¿½ IT iconv: illegal input sequence at position 0 JIS_C6220-1969-RO iconv: illegal input sequence at position 0 JIS_C6229-1984-B iconv: illegal input sequence at position 0 JIS_C62201969RO iconv: illegal input sequence at position 0 JIS_C62291984B iconv: illegal input sequence at position 0 JOHAB iconv: illegal input sequence at position 2 JP-OCR-B iconv: illegal input sequence at position 0 JP iconv: illegal input sequence at position 0 JS iconv: illegal input sequence at position 0 JUS_I.B1.002 iconv: illegal input sequence at position 0 KOI-7 iconv: illegal input sequence at position 0 KOI-8 iconv: illegal input sequence at position 1 KOI8-R got О©╫ KOI8-T iconv: illegal input sequence at position 2 KOI8-U got ÐžÂ©Ò KOI8 iconv: illegal input sequence at position 1 KOI8R got О©╫ KOI8U got ÐžÂ©Ò KSC5636 iconv: illegal input sequence at position 0 L1 got � L2 got ÄÅ¼Ë L3 got ïż½ L4 got Ä«Å‹ÅŠ L5 got � L6 got ïŋ― L7 got ļæ½ L8 got ïṡẄ L10 got ïżœ LATIN-GREEK-1 iconv: illegal input sequence at position 0 LATIN-GREEK iconv: illegal input sequence at position 0 LATIN1 got � LATIN2 got ÄÅ¼Ë LATIN3 got ïż½ LATIN4 got Ä«Å‹ÅŠ LATIN5 got � LATIN6 got ïŋ― LATIN7 got ļæ½ LATIN8 got ïṡẄ LATIN10 got ïżœ LATINGREEK iconv: illegal input sequence at position 0 LATINGREEK1 iconv: illegal input sequence at position 0 MAC-CYRILLIC got пњљ MAC-IS got ÔøΩ MAC-SAMI got Ôøž MAC-UK got пњљ MAC got ÔøΩ MACCYRILLIC got пњљ MACINTOSH got ÔøΩ MACIS got ÔøΩ MACUK got пњљ MACUKRAINIAN got пњљ MS-ANSI got � MS-ARAB got ï؟½ MS-CYRL got пїЅ MS-EE got ÄÅ¼Ë MS-GREEK got ον MS-HEBR got ן¿½ MS-MAC-CYRILLIC got пњљ MS-TURK got � MSCP949 iconv: illegal input sequence at position 2 MSCP1361 iconv: illegal input sequence at position 2 MSMACCYRILLIC got пњљ MSZ_7795.3 iconv: illegal input sequence at position 0 MS_KANJI iconv: illegal input sequence at position 0 NAPLPS got ʼn¿½ NATS-DANO iconv: illegal input sequence at position 0 NATS-SEFI iconv: illegal input sequence at position 0 NATSDANO iconv: illegal input sequence at position 0 NATSSEFI iconv: illegal input sequence at position 0 NC_NC0010 iconv: illegal input sequence at position 0 NC_NC00-10 iconv: illegal input sequence at position 0 NF_Z_62-010 iconv: illegal input sequence at position 0 NF_Z_62-010_(1973) iconv: illegal input sequence at position 0 NF_Z_62-010_1973 iconv: illegal input sequence at position 0 NF_Z_62010 iconv: illegal input sequence at position 0 NF_Z_62010_1973 iconv: illegal input sequence at position 0 NO iconv: illegal input sequence at position 0 NO2 iconv: illegal input sequence at position 0 NS_4551-1 iconv: illegal input sequence at position 0 NS_4551-2 iconv: illegal input sequence at position 0 NS_45511 iconv: illegal input sequence at position 0 NS_45512 iconv: illegal input sequence at position 0 OS2LATIN1 got � OSF00010001 got � OSF00010002 got ÄÅ¼Ë OSF00010003 got ïż½ OSF00010004 got Ä«Å‹ÅŠ OSF00010005 got ÑПРOSF00010006 iconv: illegal input sequence at position 2 OSF00010007 got ον OSF00010008 iconv: illegal input sequence at position 1 OSF00010009 got � OSF0001000A got ïŋ― OSF00010020 iconv: illegal input sequence at position 0 OSF00010100 got 뿯ઽ OSF00010101 got 뿯ઽ OSF00010102 got 뿯ઽ OSF00010104 iconv: illegal input sequence at position 0 OSF00010105 iconv: illegal input sequence at position 0 OSF00010106 iconv: illegal input sequence at position 0 OSF00030010 iconv: illegal input sequence at position 2 OSF0004000A iconv: illegal input sequence at position 2 OSF0005000A iconv: illegal input sequence at position 2 OSF05010001 got � OSF100201A4 got ٥هنŽ OSF100201A8 iconv: illegal input sequence at position 0 OSF100201B5 got ∩â”â•œ OSF100201F4 got ÕרŽ OSF100203B5 iconv: illegal input sequence at position 2 OSF1002011C got Õ×~ÂŽ OSF1002011D got ÕרŽ OSF1002035D got ∩â”â•œ OSF1002035E got ∩â”â•œ OSF1002035F got ∩â”â•œ OSF1002036B got ¬ψφŽ OSF1002037B iconv: illegal input sequence at position 0 OSF10010001 got ÿ¢§ OSF10020025 got ÕרŽ OSF10020111 got ÕרŽ OSF10020115 got ÕרŽ OSF10020116 got ÕרŽ OSF10020118 got ÕרŽ OSF10020122 iconv: illegal input sequence at position 0 OSF10020129 got Õ×~ÂŽ OSF10020352 got ´â”¢ OSF10020354 got ´â”Å» OSF10020357 got â„–â”й OSF10020359 got ´â”¢ OSF10020360 got ﻡ؟ﺵ OSF10020364 iconv: illegal input sequence at position 0 OSF10020365 got ΄â”Ξ OSF10020366 got ÅרŽ OSF10020367 got ÕרŽ OSF10020370 got ЫГЕŽ OSF10020387 iconv: illegal input sequence at position 0 OSF10020388 iconv: illegal input sequence at position 0 OSF10020396 iconv: illegal input sequence at position 0 OSF10020402 got ÕרŽ OSF10020417 got Õ×]ÂŽ PT iconv: illegal input sequence at position 0 PT2 iconv: illegal input sequence at position 0 R8 got ÿ¢§ ROMAN8 got ÿ¢§ RUSCII got Ñâ”â•œ SE iconv: illegal input sequence at position 0 SE2 iconv: illegal input sequence at position 0 SEN_850200_B iconv: illegal input sequence at position 0 SEN_850200_C iconv: illegal input sequence at position 0 SHIFT-JIS iconv: illegal input sequence at position 0 SHIFT_JIS iconv: illegal input sequence at position 0 SHIFT_JISX0213 got é¹ï½½ SJIS iconv: illegal input sequence at position 0 SS636127 iconv: illegal input sequence at position 0 ST_SEV_358-88 got ÑПРT.61-8BIT got ʼn¿½ T.61 got ʼn¿½ T.618BIT got ʼn¿½ TCVN-5712 got ùẴẵ TCVN got ùẴẵ TCVN5712-1 got ùẴẵ TIS-620 got à¹à¸Ÿà¸ TIS620-0 got à¹à¸Ÿà¸ TIS620.2529-1 got à¹à¸Ÿà¸ TIS620.2533-0 got à¹à¸Ÿà¸ TIS620 got à¹à¸Ÿà¸ TS-5881 got � TSCII got ஞà¯à®¨à®£ UCS-2 got 뿯ઽ UCS-2BE got 봊 UCS-2LE got 뿯ઽ UCS-4 iconv: illegal input sequence at position 0 UCS-4BE iconv: illegal input sequence at position 0 UCS-4LE got üŠ¯›¿¯ UCS2 got 뿯ઽ UCS4 iconv: illegal input sequence at position 0 UHC iconv: illegal input sequence at position 2 UJIS iconv: illegal input sequence at position 2 UK iconv: illegal input sequence at position 0 UNICODE got 뿯ઽ UNICODEBIG got 봊 UNICODELITTLE got 뿯ઽ US-ASCII iconv: illegal input sequence at position 0 US iconv: illegal input sequence at position 0 UTF-7 iconv: illegal input sequence at position 0 UTF-8 got � UTF-16 got 뿯ઽ UTF-16BE got 봊 UTF-16LE got 뿯ઽ UTF-32 iconv: illegal input sequence at position 0 UTF-32BE iconv: illegal input sequence at position 0 UTF-32LE iconv: illegal input sequence at position 0 UTF7 iconv: illegal input sequence at position 0 UTF8 got � UTF16 got 뿯ઽ UTF16BE got 봊 UTF16LE got 뿯ઽ UTF32 iconv: illegal input sequence at position 0 UTF32BE iconv: illegal input sequence at position 0 UTF32LE iconv: illegal input sequence at position 0 VISCII got ỉƯơ WCHAR_T got üŠ¯›¿¯ WIN-SAMI-2 got ïž½ WINBALTRIM got ļæ½ WINDOWS-1250 got ÄÅ¼Ë WINDOWS-1251 got пїЅ WINDOWS-1252 got � WINDOWS-1253 got ον WINDOWS-1254 got � WINDOWS-1255 got ן¿½ WINDOWS-1256 got ï؟½ WINDOWS-1257 got ļæ½ WINDOWS-1258 got � WINSAMI2 got ïž½ WS2 got ïž½ YU iconv: illegal input sequence at position 0 -- __Pascal Bourguignon__ http://www.informatimago.com/ Litter box not here. You must have moved it again. I'll poop in the sink. ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-12 15:52 ` Pascal Bourguignon @ 2005-08-12 16:33 ` Joe Corneli 0 siblings, 0 replies; 38+ messages in thread From: Joe Corneli @ 2005-08-12 16:33 UTC (permalink / raw) What's sure, is that it's not a ü in any known encoding: Where's SETI when you need them!? ^ permalink raw reply [flat|nested] 38+ messages in thread
[parent not found: <mailman.3561.1123859480.20277.help-gnu-emacs@gnu.org>]
* Re: how to change file coding system [not found] ` <mailman.3561.1123859480.20277.help-gnu-emacs@gnu.org> @ 2005-08-16 9:22 ` Martin Monsorno 2005-08-16 11:20 ` Peter Dyballa ` (3 more replies) 0 siblings, 4 replies; 38+ messages in thread From: Martin Monsorno @ 2005-08-16 9:22 UTC (permalink / raw) Eli Zaretskii <eliz@gnu.org> writes: > Sorry, I don't understand this. Please show the details. Ok, I did the following: I created 2 identical files, containing the string "überfall": ,---- | monsorno@mmdev ~/work/workspace.c/gmx $ file bla* | bla.eclipse: ISO-8859 text | bla.emacs: ISO-8859 text `---- I then opened "bla.eclipse" with eclipse and saved it again, which lead to this: ,---- | monsorno@mmdev ~/work/workspace.c/gmx $ file bla* | bla.eclipse: UTF-8 Unicode text | bla.emacs: ISO-8859 text `---- Opening "bla.eclipse" with emacs, shows me the string "�berfall". Changing the file encoding with "C-x <RET> f iso-latin-1-unix" and saving leads to: ,---- | monsorno@mmdev ~/work/workspace.c/gmx $ file bla* | bla.eclipse: UTF-8 Unicode text | bla.emacs: ISO-8859 text `---- Somewhere in the middle I got lost. Can anyone help me out? -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-16 9:22 ` Martin Monsorno @ 2005-08-16 11:20 ` Peter Dyballa 2005-08-17 4:07 ` Eli Zaretskii ` (2 subsequent siblings) 3 siblings, 0 replies; 38+ messages in thread From: Peter Dyballa @ 2005-08-16 11:20 UTC (permalink / raw) Cc: help-gnu-emacs Am 16.08.2005 um 11:22 schrieb Martin Monsorno: > ,---- > | monsorno@mmdev ~/work/workspace.c/gmx $ file bla* > | bla.eclipse: UTF-8 Unicode text > | bla.emacs: ISO-8859 text > `---- > > Opening "bla.eclipse" with emacs, shows me the string > "�berfall". Changing the file encoding with "C-x <RET> f > iso-latin-1-unix" and saving leads to: The correct way would have been, once you've opened the file bla.eclipse and Emacs came up showing `-0:´ as start of the mode-line (stating ISO Latin-1 or ISO Latin-15 encoding), C-x <RET> r utf-8-unix <RET>: re-open the file in UTF-8 encoding, to view it in its natural mood. When you now save the file in ISO Latin-1 encoding, having applied C-x <RET> f (set-buffer-file-coding-system), GNU Emacs does the conversion. Instead of C3 BC it writes only FC. The file size will be reduced by one byte. The C-x RET commands *do not* change a buffer's (or a file's) contents, they just put some new skin on the buffer so that your view on the buffer's (i.e. file's) contents is adapted in a certain way: you can see a buffer's (or file's) whatever contents in green, blue, red, yellow, cyan ... utf-8, Mac-Roman, NeXT, koi-r8, euc-jp-unix ... encoding/view. Eclipse might be fooling you. The character `ü´ is encoded in UTF-8 as C3 BC or, translating the two hex codes into ISO Latin-1 (or -15) characters, as: à ³. What you cite in your eMail, � or in HTML �, is *not* UTF-8. -- Greetings Pete "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-16 9:22 ` Martin Monsorno 2005-08-16 11:20 ` Peter Dyballa @ 2005-08-17 4:07 ` Eli Zaretskii [not found] ` <mailman.3911.1124191758.20277.help-gnu-emacs@gnu.org> [not found] ` <mailman.4004.1124251989.20277.help-gnu-emacs@gnu.org> 3 siblings, 0 replies; 38+ messages in thread From: Eli Zaretskii @ 2005-08-17 4:07 UTC (permalink / raw) > From: Martin Monsorno <mmonsorno@gmx-gmbh.de> > Date: Tue, 16 Aug 2005 11:22:28 +0200 > > ,---- > | monsorno@mmdev ~/work/workspace.c/gmx $ file bla* > | bla.eclipse: ISO-8859 text > | bla.emacs: ISO-8859 text > `---- > > I then opened "bla.eclipse" with eclipse and saved it again, which > lead to this: > > ,---- > | monsorno@mmdev ~/work/workspace.c/gmx $ file bla* > | bla.eclipse: UTF-8 Unicode text > | bla.emacs: ISO-8859 text > `---- > > Opening "bla.eclipse" with emacs, shows me the string When you open bla.eclipse with Emacs, did you tell Emacs that it was a UTF-8 encoded file? That is, did you say C-x RET c utf-8 RET C-x C-f bla.eclipse or did you use "C-x C-f" as usual? If the latter, I'm guessing that Emacs thought it was an ISO-8859 encoded file (because it cannot easily distinguish between these 2 encodings), and thus your subsequent C-x RET f had no effect at all. ^ permalink raw reply [flat|nested] 38+ messages in thread
[parent not found: <mailman.3911.1124191758.20277.help-gnu-emacs@gnu.org>]
* Re: how to change file coding system [not found] ` <mailman.3911.1124191758.20277.help-gnu-emacs@gnu.org> @ 2005-08-17 9:20 ` Martin Monsorno 2005-08-17 12:22 ` Martin Monsorno ` (2 more replies) 0 siblings, 3 replies; 38+ messages in thread From: Martin Monsorno @ 2005-08-17 9:20 UTC (permalink / raw) Peter Dyballa <Peter_Dyballa@Web.DE> writes: > Am 16.08.2005 um 11:22 schrieb Martin Monsorno: > >> ,---- >> | monsorno@mmdev ~/work/workspace.c/gmx $ file bla* >> | bla.eclipse: UTF-8 Unicode text >> | bla.emacs: ISO-8859 text >> `---- >> >> Opening "bla.eclipse" with emacs, shows me the string >> "�berfall". Changing the file encoding with "C-x <RET> f >> iso-latin-1-unix" and saving leads to: > > The correct way would have been, once you've opened the file > bla.eclipse and Emacs came up showing `-0:´ as start of the mode-line > (stating ISO Latin-1 or ISO Latin-15 encoding), C-x <RET> r utf-8-unix > <RET>: re-open the file in UTF-8 encoding, to view it in its natural > mood. Hmm, I cannot make something showing off in the modeline, regardless of how I open one of the files (I tried to open bla.eclipse with both iso-8859-1 and utf-8 specified). (describe-variable 'buffer-file-coding-system) says: buffer-file-coding-system's value is raw-text-unix Local in buffer bla.eclipse; global value is mule-utf-8 AND this output is the same with file "bla.emacs", which is a 8859-latin1 file. :-? > When you now save the file in ISO Latin-1 encoding, having applied C-x > <RET> f (set-buffer-file-coding-system), GNU Emacs does the conversion. > Instead of C3 BC it writes only FC. The file size will be reduced by > one byte. To make it just more exciting, I tried something more: 1) Created a file called "bla.created-by-emacs" containing the string "überfall" with emacs. 2) Copied this file to "bla.changed-by-eclipse". 3) Opened this file with eclipse. 4) Saved this file with eclipse. 5) Created a new file with eclipse "bla.created-by-eclipse" containing the same string. 6) ls -l bla* -rw-r--r-- 1 monsorno users 11 17. Aug 11:00 bla.changed-by-eclipse -rw-r--r-- 1 monsorno users 10 17. Aug 10:35 bla.created-by-eclipse -rw-r--r-- 1 monsorno users 9 17. Aug 10:58 bla.created-by-emacs 7) file bla* bla.changed-by-eclipse: UTF-8 Unicode text bla.created-by-eclipse: UTF-8 Unicode text bla.created-by-emacs: ISO-8859 text 8) Visiting bla.changed-by-eclipse with emacs shows "�berfall" 9) Visiting bla.chreated-by-eclipse with emacs shows "überfall" So we now have 3 files containing the "same" string, 2 of them claim to be utf-8, but they use a different encoding (2 or 3 bytes). For all 3 files, when opening the in emacs, buffer-file-coding-system's value is raw-text-unix. Emacs can only display "bla.created-by-emacs" correctly, eclipse can only display "bla.created-by-eclipse" correctly. > The C-x RET commands *do not* change a buffer's (or a file's) contents, > they just put some new skin on the buffer so that your view on the > buffer's (i.e. file's) contents is adapted in a certain way: you can > see a buffer's (or file's) whatever contents in green, blue, red, > yellow, cyan ... utf-8, Mac-Roman, NeXT, koi-r8, euc-jp-unix ... > encoding/view. I think I understood this. But this means that I can change the file-encoding of a file with emacs, doesn't it? > Eclipse might be fooling you. The character `ü´ is encoded in UTF-8 as > C3 BC or, translating the two hex codes into ISO Latin-1 (or -15) > characters, as: à ³. What you cite in your eMail, � or in HTML > �, is *not* UTF-8. Yes, or at least, it does not look like an 'ü' ;-) What I cite in my mails are the strings as emacs shows them to me when loading one of the files. So the question is, /why/ are they not UTF-8? Does eclipse do a wrong latin-1 to utf-8 conversion? -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-17 9:20 ` Martin Monsorno @ 2005-08-17 12:22 ` Martin Monsorno 2005-08-17 19:09 ` Peter Dyballa [not found] ` <mailman.4075.1124306087.20277.help-gnu-emacs@gnu.org> 2 siblings, 0 replies; 38+ messages in thread From: Martin Monsorno @ 2005-08-17 12:22 UTC (permalink / raw) Martin Monsorno <monsorno@gmx.de> writes: > Emacs can only display "bla.created-by-emacs" correctly, eclipse can > only display "bla.created-by-eclipse" correctly. What hurts even more is, that vi can handle both files correctly ... :-/ -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-17 9:20 ` Martin Monsorno 2005-08-17 12:22 ` Martin Monsorno @ 2005-08-17 19:09 ` Peter Dyballa [not found] ` <mailman.4075.1124306087.20277.help-gnu-emacs@gnu.org> 2 siblings, 0 replies; 38+ messages in thread From: Peter Dyballa @ 2005-08-17 19:09 UTC (permalink / raw) Cc: help-gnu-emacs Am 17.08.2005 um 11:20 schrieb Martin Monsorno: > 7) file bla* > bla.changed-by-eclipse: UTF-8 Unicode text > bla.created-by-eclipse: UTF-8 Unicode text > bla.created-by-emacs: ISO-8859 text > 8) Visiting bla.changed-by-eclipse with emacs shows "�berfall" > 9) Visiting bla.chreated-by-eclipse with emacs shows "überfall" > > So we now have 3 files containing the "same" string, 2 of them claim > to be utf-8, but they use a different encoding (2 or 3 bytes). For > all 3 files, when opening the in emacs, buffer-file-coding-system's > value is raw-text-unix. I wouldn't say the files claim to be something -- it's the `file´ programme that says so, according to some rules in `magic´ files. UTF-8 contents usually cannot be distinguished from other contents -- a byte is a byte is a byte. Some UTF-8 files contain a marker by which one can determine, that it's UTF-8. Other markers state that the text is written right to left with a citation left to right. Could be Eclipse writes such a marker ... > >> The C-x RET commands *do not* change a buffer's (or a file's) >> contents, >> they just put some new skin on the buffer so that your view on the >> buffer's (i.e. file's) contents is adapted in a certain way: you can >> see a buffer's (or file's) whatever contents in green, blue, red, >> yellow, cyan ... utf-8, Mac-Roman, NeXT, koi-r8, euc-jp-unix ... >> encoding/view. > > I think I understood this. But this means that I can change the > file-encoding of a file with emacs, doesn't it? Yes. I Usually revert buffer from file with new encoding, C-x RET r <encoding> RET and save the file in that encoding. I'd say it works reliably! > > What I cite in my mails are the strings as emacs shows them to me when > loading one of the files. So the question is, /why/ are they not > UTF-8? Does eclipse do a wrong latin-1 to utf-8 conversion? > I don't know and use Eclipse. Test is with its own documentation -- and some reliably encoded files! -- Mit friedvollen Grüßen Pete "engineer: a mechanism for converting caffeine into designs" ^ permalink raw reply [flat|nested] 38+ messages in thread
[parent not found: <mailman.4075.1124306087.20277.help-gnu-emacs@gnu.org>]
* Re: how to change file coding system [not found] ` <mailman.4075.1124306087.20277.help-gnu-emacs@gnu.org> @ 2005-08-18 8:40 ` Martin Monsorno 2005-08-18 11:37 ` Peter Dyballa [not found] ` <mailman.4171.1124367223.20277.help-gnu-emacs@gnu.org> 0 siblings, 2 replies; 38+ messages in thread From: Martin Monsorno @ 2005-08-18 8:40 UTC (permalink / raw) Peter Dyballa <Peter_Dyballa@Web.DE> writes: >> I think I understood this. But this means that I can change the >> file-encoding of a file with emacs, doesn't it? > > Yes. I Usually revert buffer from file with new encoding, C-x RET r > <encoding> RET and save the file in that encoding. I'd say it works > reliably! (I suppose you mean C-x RET f ...) Lucky guy, my problem is, it doesn't seem to work for me :-( >> What I cite in my mails are the strings as emacs shows them to me when >> loading one of the files. So the question is, /why/ are they not >> UTF-8? Does eclipse do a wrong latin-1 to utf-8 conversion? >> > > I don't know and use Eclipse. Test is with its own documentation -- and > some reliably encoded files! Meanwhile I found out how to specify the encoding of a file in eclipse (prior to loading), which leads to correctly encoded files (latin1 and utf-8). What remains is the problem with emacs and UTF-8 files. -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-18 8:40 ` Martin Monsorno @ 2005-08-18 11:37 ` Peter Dyballa [not found] ` <mailman.4171.1124367223.20277.help-gnu-emacs@gnu.org> 1 sibling, 0 replies; 38+ messages in thread From: Peter Dyballa @ 2005-08-18 11:37 UTC (permalink / raw) Cc: help-gnu-emacs Am 18.08.2005 um 10:40 schrieb Martin Monsorno: > What remains is the problem with emacs and UTF-8 files. > I have GNU Emacs 21.3.50 from CVS in rare use too. It has no problems to open an actual UTF-8 file in UTF-8 or an ISO Latin-1 file in ISO Latin-1. Although it has problems to show most of the >100K glyphs in Unicode, but that's a secondary problem to deal with in elaborate fontsets. Such a header line helps Emacs: ;;; -*- mode: Text; coding: utf-8; -*- (The first three `;´ are three comment characters.) Or such a footer: % % Local Variables: % mode: LaTeX % fill-column: 160 % coding-system: iso-latin-1 % End: % %% (The `%´ introduces a comment in TeX.) And yes, I meant and I wrote C-x RET r. Usually I first view a file's contents and judge then if I need to change the encoding Emacs uses by default. -- Mit friedvollen Grüßen Pete Es gibt 10 Sorten Leute: solche, die binär verstehen, und solche, die es nicht verstehen. ^ permalink raw reply [flat|nested] 38+ messages in thread
[parent not found: <mailman.4171.1124367223.20277.help-gnu-emacs@gnu.org>]
* Re: how to change file coding system [not found] ` <mailman.4171.1124367223.20277.help-gnu-emacs@gnu.org> @ 2005-08-19 10:20 ` Martin Monsorno 2005-08-19 13:24 ` Peter Dyballa [not found] ` <mailman.4307.1124458248.20277.help-gnu-emacs@gnu.org> 0 siblings, 2 replies; 38+ messages in thread From: Martin Monsorno @ 2005-08-19 10:20 UTC (permalink / raw) Peter Dyballa <Peter_Dyballa@Web.DE> writes: > I have GNU Emacs 21.3.50 from CVS in rare use too. You have 21.3.50 from CVS? I have a stable 21.4.1 version! But I tried out 22.0.50 from cvs and: it NEVER does show me an 'ü'. Instead it always displays the code: \374 in the latin-1 file, and \303\274 in the UTF-8 file. Specifying the coding system in the headerline doesn't change anything: buffer-file-coding-system's value remains raw-text-unix. > And yes, I meant and I wrote C-x RET r. Usually I first view a file's > contents and judge then if I need to change the encoding Emacs uses by > default. C-h k C-x RET r is undefined --> C-x RET r is undefined -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-19 10:20 ` Martin Monsorno @ 2005-08-19 13:24 ` Peter Dyballa [not found] ` <mailman.4307.1124458248.20277.help-gnu-emacs@gnu.org> 1 sibling, 0 replies; 38+ messages in thread From: Peter Dyballa @ 2005-08-19 13:24 UTC (permalink / raw) Cc: help-gnu-emacs Am 19.08.2005 um 12:20 schrieb Martin Monsorno: > Peter Dyballa <Peter_Dyballa@Web.DE> writes: > >> I have GNU Emacs 21.3.50 from CVS in rare use too. > > You have 21.3.50 from CVS? I have a stable 21.4.1 version! But I > tried out 22.0.50 from cvs and: it NEVER does show me an 'ü'. > Instead it always displays the code: \374 in the latin-1 file, and > \303\274 in the UTF-8 file. What about a nice fontset? (create-fontset-from-fontset-spec "-adobe-courier-medium-r-*-*-11-*-*-*-*-*-fontset-11pt_adobe_courier" t 'noerror) (set-fontset-font "fontset-11pt_adobe_courier" 'latin-iso8859-1 '("adobe-courier" . "iso8859-1")) (set-fontset-font "fontset-11pt_adobe_courier" 'latin-iso8859-2 '("adobe-courier" . "iso8859-2")) (set-fontset-font "fontset-11pt_adobe_courier" 'latin-iso8859-3 '("adobe-courier" . "iso8859-3")) (set-fontset-font "fontset-11pt_adobe_courier" 'latin-iso8859-4 '("adobe-courier" . "iso8859-4")) (set-fontset-font "fontset-11pt_adobe_courier" 'greek-iso8859-7 '("adobe-couriergr" . "iso8859-7")) (set-fontset-font "fontset-11pt_adobe_courier" 'latin-iso8859-9 '("adobe-courier" . "iso8859-9")) (set-fontset-font "fontset-11pt_adobe_courier" 'latin-iso8859-14 '("adobe-courier" . "iso8859-14")) (set-fontset-font "fontset-11pt_adobe_courier" 'latin-iso8859-15 '("adobe-courier" . "iso8859-15")) (set-fontset-font "fontset-11pt_adobe_courier" 'mule-unicode-0100-24ff '("adobe-courier" . "iso10646-1")) (set-fontset-font "fontset-11pt_adobe_courier" 'mule-unicode-2500-33ff '("adobe-courier" . "iso10646-1")) (set-fontset-font "fontset-11pt_adobe_courier" 'mule-unicode-e000-ffff '("adobe-courier" . "iso10646-1")) (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0370) (decode-char 'ucs #x03cf)) '("courier new" . "iso10646-1")) ; Greek (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x03d0) (decode-char 'ucs #x03ff)) '("lucida sans typewriter" . "iso10646-1")) ; Coptic (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0400) (decode-char 'ucs #x04ff)) '("lucida sans typewriter" . "iso10646-1")) ; Cyrillic (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0500) (decode-char 'ucs #x052f)) '("lucida sans typewriter" . "iso10646-1")) ; Cyrillic Supplement (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0530) (decode-char 'ucs #x058f)) '("aramian unicode" . "iso10646-1")) ; Armenian (sylfaen (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0590) (decode-char 'ucs #x05af)) '("lucida sans typewriter" . "iso10646-1")) ; Hebrew (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x05b0) (decode-char 'ucs #x05ff)) '("courier new" . "iso10646-1")) ; Hebrew (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0600) (decode-char 'ucs #x066f)) '("courier new" . "iso10646-1")) ; Arabic (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0670) (decode-char 'ucs #x06ff)) '("lucida sans typewriter" . "iso10646-1")) ; Arabic (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0700) (decode-char 'ucs #x074f)) '("titus cyberbit basic" . "iso10646-1")) ; Syriac (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0780) (decode-char 'ucs #x07bf)) '("titus cyberbit basic" . "iso10646-1")) ; Thaana (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0900) (decode-char 'ucs #x097f)) '("titus cyberbit basic" . "iso10646-1")) ; Devanagari (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0980) (decode-char 'ucs #x09ff)) '("code2000" . "iso10646-1")) ; Bengali (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0a00) (decode-char 'ucs #x0a7f)) '("code2000" . "iso10646-1")) ; Gurmukhi (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0a80) (decode-char 'ucs #x0aff)) '("code2000" . "iso10646-1")) ; Gujarati (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0b00) (decode-char 'ucs #x0b7f)) '("code2000" . "iso10646-1")) ; Oriya (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0b80) (decode-char 'ucs #x0bff)) '("code2000" . "iso10646-1")) ; Tamil (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0c00) (decode-char 'ucs #x0c7f)) '("code2000" . "iso10646-1")) ; Telugu (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0c80) (decode-char 'ucs #x0cff)) '("code2000" . "iso10646-1")) ; Kannada (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0d00) (decode-char 'ucs #x0d7f)) '("code2000" . "iso10646-1")) ; Malayalam (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0d80) (decode-char 'ucs #x0dff)) '("akshar unicode" . "iso10646-1")) ; Sinhala (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0e00) (decode-char 'ucs #x0e7f)) '("code2000" . "iso10646-1")) ; Thai (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0e80) (decode-char 'ucs #x0eff)) '("code2000" . "iso10646-1")) ; Lao (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x0f00) (decode-char 'ucs #x0fff)) '("xtashi" . "iso10646-1")) ; Tibetan (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1000) (decode-char 'ucs #x109f)) '("code2000" . "iso10646-1")) ; Myanmar (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x10a0) (decode-char 'ucs #x10ff)) '("everson mono unicode" . "iso10646-1")) ; Georgian (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1100) (decode-char 'ucs #x11ff)) '("code2000" . "iso10646-1")) ; Hangul Jamo (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1200) (decode-char 'ucs #x137f)) '("ethiopia jiret" . "iso10646-1")) ; Ethiopic (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x13a0) (decode-char 'ucs #x13ff)) '("everson mono unicode" . "iso10646-1")) ; Cherokee (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1400) (decode-char 'ucs #x167f)) '("everson mono unicode" . "iso10646-1")) ; Canadian Aboriginal Syllabics (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1680) (decode-char 'ucs #x169f)) '("everson mono unicode" . "iso10646-1")) ; Ogham (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x16a0) (decode-char 'ucs #x16ff)) '("everson mono unicode" . "iso10646-1")) ; Runic ; (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1700) (decode-char 'ucs #x171f)) '("code2000" . "iso10646-1")) ; Tagalog ; (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1720) (decode-char 'ucs #x173f)) '("code2000" . "iso10646-1")) ; Hanunoo (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1740) (decode-char 'ucs #x175f)) '("code2000" . "iso10646-1")) ; Buhid ; (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1760) (decode-char 'ucs #x177f)) '("code2000" . "iso10646-1")) ; Tagbanwa (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1780) (decode-char 'ucs #x17ff)) '("code2000" . "iso10646-1")) ; Khmer (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1800) (decode-char 'ucs #x18af)) '("code2000" . "iso10646-1")) ; Mongolian (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1900) (decode-char 'ucs #x194f)) '("code2000" . "iso10646-1")) ; Limbu (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1950) (decode-char 'ucs #x197f)) '("tai le valentinium" . "iso10646-1")) ; Tai Le (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x19e0) (decode-char 'ucs #x19ff)) '("cdt khmer" . "iso10646-1")) ; Khmer Symbols (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1d00) (decode-char 'ucs #x1d7f)) '("everson mono unicode" . "iso10646-1")) ; Phonetic Extensions (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1e00) (decode-char 'ucs #x1eff)) '("courier" . "iso10646-1")) ; Latin Extended Additional (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x1f00) (decode-char 'ucs #x1fff)) '("everson mono unicode" . "iso10646-1")) ; Greek Extended (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2000) (decode-char 'ucs #x206f)) '("everson mono unicode" . "iso10646-1")) ; General Puctuation (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2070) (decode-char 'ucs #x209f)) '("everson mono unicode" . "iso10646-1")) ; Superscripts and Subscripts (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x20a0) (decode-char 'ucs #x20cf)) '("everson mono unicode" . "iso10646-1")) ; Currency Symbols (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x20d0) (decode-char 'ucs #x20ff)) '("everson mono unicode" . "iso10646-1")) ; Combining Marks for Symbols (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2100) (decode-char 'ucs #x214f)) '("everson mono unicode" . "iso10646-1")) ; Letterlike Symbols ; (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2150) (decode-char 'ucs #x218f)) '("courier new" . "iso10646-1")) ; Number Forms (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2190) (decode-char 'ucs #x21ff)) '("code2000" . "iso10646-1")) ; *Arrows (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2200) (decode-char 'ucs #x22ff)) '("code2000" . "iso10646-1")) ; Mathematical Operators (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2300) (decode-char 'ucs #x23ff)) '("code2000" . "iso10646-1")) ; Miscellaneous Technical (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2400) (decode-char 'ucs #x243f)) '("code2000" . "iso10646-1")) ; Control Pictures (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2440) (decode-char 'ucs #x245f)) '("code2000" . "iso10646-1")) ; Optical Character Recognition (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2460) (decode-char 'ucs #x24ff)) '("code2000" . "iso10646-1")) ; Enclosed Alphanumerics (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2500) (decode-char 'ucs #x257f)) '("code2000" . "iso10646-1")) ; Box Drawing (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2580) (decode-char 'ucs #x259f)) '("code2000" . "iso10646-1")) ; Block Elements (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x25a0) (decode-char 'ucs #x25ff)) '("code2000" . "iso10646-1")) ; Geometric Shapes (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2600) (decode-char 'ucs #x26ff)) '("code2000" . "iso10646-1")) ; Miscellaneous Symbols (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2700) (decode-char 'ucs #x27bf)) '("code2000" . "iso10646-1")) ; Dingbats (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x27c0) (decode-char 'ucs #x27ef)) '("code2000" . "iso10646-1")) ; Miscellaneous Math Symbols-A (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x27f0) (decode-char 'ucs #x27ff)) '("code2000" . "iso10646-1")) ; Supplemental Arrows-A (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2800) (decode-char 'ucs #x28ff)) '("code2000" . "iso10646-1")) ; Braille Patterns (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2900) (decode-char 'ucs #x297f)) '("code2000" . "iso10646-1")) ; Supplemental Arrows-B (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2980) (decode-char 'ucs #x29ff)) '("code2000" . "iso10646-1")) ; Miscellaneous Math Symbols-B (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2a00) (decode-char 'ucs #x2aff)) '("code2000" . "iso10646-1")) ; Supplemental Math Operators (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2b00) (decode-char 'ucs #x2bff)) '("code2000" . "iso10646-1")) ; Miscellaneous Symbols and Arrows (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2e80) (decode-char 'ucs #x2eff)) '("code2000" . "iso10646-1")) ; CJK Radicals Supplement (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2f00) (decode-char 'ucs #x2fdf)) '("code2000" . "iso10646-1")) ; Kangxi Radicals (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x2ff0) (decode-char 'ucs #x2fff)) '("code2000" . "iso10646-1")) ; Ideographic Description Characters (set-fontset-font "fontset-11pt_adobe_courier" (cons (decode-char 'ucs #x3000) (decode-char 'ucs #x303f)) '("code2000" . "iso10646-1")) ; CJK Symbols and Punctuation It looks ugly here ... 'though it needs to be continued! > > Specifying the coding system in the headerline doesn't change > anything: buffer-file-coding-system's value remains raw-text-unix. Then you're doing something the wrong way ... At least my experience (>10a) tells me so. This code never failed for me (and I am no politician): -*- coding: iso-8859-15; -*- > >> And yes, I meant and I wrote C-x RET r. Usually I first view a file's >> contents and judge then if I need to change the encoding Emacs uses by >> default. > > C-h k C-x RET r is undefined > --> C-x RET r is undefined > C-h b shows, amongst many others: C-x RET l set-language-environment C-x RET c universal-coding-system-argument C-x RET C-\ set-input-method C-x RET X set-next-selection-coding-system C-x RET x set-selection-coding-system C-x RET p set-buffer-process-coding-system C-x RET k set-keyboard-coding-system C-x RET t set-terminal-coding-system C-x RET F set-file-name-coding-system C-x RET r revert-buffer-with-coding-system C-x RET f set-buffer-file-coding-system BTW: to which value is LC_CTYPE set? LC_ALL? LANG? -- Mit friedvollen Grüßen Pete Hupende Autos beißen nicht. ^ permalink raw reply [flat|nested] 38+ messages in thread
[parent not found: <mailman.4307.1124458248.20277.help-gnu-emacs@gnu.org>]
* Re: how to change file coding system [not found] ` <mailman.4307.1124458248.20277.help-gnu-emacs@gnu.org> @ 2005-08-23 9:20 ` Martin Monsorno 0 siblings, 0 replies; 38+ messages in thread From: Martin Monsorno @ 2005-08-23 9:20 UTC (permalink / raw) Peter Dyballa <Peter_Dyballa@Web.DE> writes: > Am 19.08.2005 um 12:20 schrieb Martin Monsorno: > >> Peter Dyballa <Peter_Dyballa@Web.DE> writes: >> >>> I have GNU Emacs 21.3.50 from CVS in rare use too. >> >> You have 21.3.50 from CVS? I have a stable 21.4.1 version! But I >> tried out 22.0.50 from cvs and: it NEVER does show me an 'ü'. >> Instead it always displays the code: \374 in the latin-1 file, and >> \303\274 in the UTF-8 file. > > What about a nice fontset? > [...] > It looks ugly here ... 'though it needs to be continued! This is about the problem with emacs 22, correct? Could you please send this again as attachement: the line wraps corrupted the code a little. This would be easier to me than fixing it manually. >> Specifying the coding system in the headerline doesn't change >> anything: buffer-file-coding-system's value remains raw-text-unix. > > Then you're doing something the wrong way ... Yes, but what? The value of buffer-file-coding-system stays the same (raw-text-unix), whatever method to load a file I choose. > At least my experience (>10a) tells me so. This code never failed > for me (and I am no politician): > > -*- coding: iso-8859-15; -*- > >> >>> And yes, I meant and I wrote C-x RET r. Usually I first view a file's >>> contents and judge then if I need to change the encoding Emacs uses by >>> default. >> >> C-h k C-x RET r is undefined >> --> C-x RET r is undefined >> > > C-h b shows, amongst many others: > > C-x RET l set-language-environment > C-x RET c universal-coding-system-argument > C-x RET C-\ set-input-method > C-x RET X set-next-selection-coding-system > C-x RET x set-selection-coding-system > C-x RET p set-buffer-process-coding-system > C-x RET k set-keyboard-coding-system > C-x RET t set-terminal-coding-system > C-x RET F set-file-name-coding-system > C-x RET r revert-buffer-with-coding-system > C-x RET f set-buffer-file-coding-system here it is (emacs 21.4.1): C-x RET l set-language-environment C-x RET c universal-coding-system-argument C-x RET C-\ set-input-method C-x RET X set-next-selection-coding-system C-x RET x set-selection-coding-system C-x RET p set-buffer-process-coding-system C-x RET k set-keyboard-coding-system C-x RET t set-terminal-coding-system C-x RET f set-buffer-file-coding-system (describe-function revert-buffer-with-coding-system) --> Debugger entered--Lisp error: (void-variable revert-buffer-with-coding-system) Seems your emacs is better than mine ... > BTW: to which value is LC_CTYPE set? LC_ALL? LANG? monsorno@mmdev ~ $ locale LANG=de_DE.UTF-8 LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE=POSIX LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= Starting emacs with "LANG= emacs" does not change anything. ??? -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
[parent not found: <mailman.4004.1124251989.20277.help-gnu-emacs@gnu.org>]
* Re: how to change file coding system [not found] ` <mailman.4004.1124251989.20277.help-gnu-emacs@gnu.org> @ 2005-08-17 9:26 ` Martin Monsorno 2005-08-17 18:23 ` Eli Zaretskii [not found] ` <mailman.4071.1124303238.20277.help-gnu-emacs@gnu.org> 0 siblings, 2 replies; 38+ messages in thread From: Martin Monsorno @ 2005-08-17 9:26 UTC (permalink / raw) Eli Zaretskii <eliz@gnu.org> writes: > When you open bla.eclipse with Emacs, did you tell Emacs that it was a > UTF-8 encoded file? That is, did you say > > C-x RET c utf-8 RET C-x C-f bla.eclipse > > or did you use "C-x C-f" as usual? If the latter, I'm guessing that > Emacs thought it was an ISO-8859 encoded file (because it cannot > easily distinguish between these 2 encodings), and thus your > subsequent C-x RET f had no effect at all. I tried many ways of opening the file, with no noticable difference. Some details are in my followup to Peter's posting. -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-17 9:26 ` Martin Monsorno @ 2005-08-17 18:23 ` Eli Zaretskii [not found] ` <mailman.4071.1124303238.20277.help-gnu-emacs@gnu.org> 1 sibling, 0 replies; 38+ messages in thread From: Eli Zaretskii @ 2005-08-17 18:23 UTC (permalink / raw) > From: Martin Monsorno <monsorno@gmx.de> > Date: Wed, 17 Aug 2005 11:26:13 +0200 > > > C-x RET c utf-8 RET C-x C-f bla.eclipse > > > > or did you use "C-x C-f" as usual? If the latter, I'm guessing that > > Emacs thought it was an ISO-8859 encoded file (because it cannot > > easily distinguish between these 2 encodings), and thus your > > subsequent C-x RET f had no effect at all. > > I tried many ways of opening the file But none of them is what I suggested... > Some details are in my followup to Peter's posting. But none of that clears up the situation in any way... They are just random trials, nothing more. Please try my suggestions. Alternatively, send the offending file(s) as binary attachments (preferably base64-encoded), and someone will figure out what's wrong. In any case, the fact that Emacs thinks the file is encoded raw-text-unix indicates that there are some bytes in the file that don't belong to ISO-8859. Perhaps that clue will help you solve the problem (you can use hexl-find-file to see the raw bytes in the file). ^ permalink raw reply [flat|nested] 38+ messages in thread
[parent not found: <mailman.4071.1124303238.20277.help-gnu-emacs@gnu.org>]
* Re: how to change file coding system [not found] ` <mailman.4071.1124303238.20277.help-gnu-emacs@gnu.org> @ 2005-08-18 8:05 ` Martin Monsorno 2005-08-19 8:14 ` Eli Zaretskii 2005-08-23 21:23 ` Jason Rumney 0 siblings, 2 replies; 38+ messages in thread From: Martin Monsorno @ 2005-08-18 8:05 UTC (permalink / raw) Eli Zaretskii <eliz@gnu.org> writes: >> I tried many ways of opening the file > > But none of them is what I suggested... Sure! I should have said that I tried many ways /including/ the one suggested by you. When emacs asks me what coding system to use after pressing C-x <RET> c, the default it suggests (in parentheses on the modeline) is "mule-utf-8". After opening it your way, buffer-file-coding-system's value is raw-text-unix, nevertheless. >> Some details are in my followup to Peter's posting. > > But none of that clears up the situation in any way... They are just > random trials, nothing more. > > Please try my suggestions. Alternatively, send the offending file(s) > as binary attachments (preferably base64-encoded), and someone will > figure out what's wrong. I will append the files. As I don't know how to base64-encode it explicitly and well, I will just append also a tar file containing the three files. > In any case, the fact that Emacs thinks the file is encoded > raw-text-unix indicates that there are some bytes in the file that > don't belong to ISO-8859. Perhaps that clue will help you solve the > problem (you can use hexl-find-file to see the raw bytes in the file). Hmm, this only shows me, that file (the command) seems to be correct with it's suggestions. So it seems, emacs is not. -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-18 8:05 ` Martin Monsorno @ 2005-08-19 8:14 ` Eli Zaretskii 2005-08-23 21:23 ` Jason Rumney 1 sibling, 0 replies; 38+ messages in thread From: Eli Zaretskii @ 2005-08-19 8:14 UTC (permalink / raw) > From: Martin Monsorno <monsorno@gmx.de> > Date: Thu, 18 Aug 2005 10:05:42 +0200 > > I will append the files. As I don't know how to base64-encode it > explicitly and well, I will just append also a tar file containing the > three files. Your message arrived here with no attached files. > > In any case, the fact that Emacs thinks the file is encoded > > raw-text-unix indicates that there are some bytes in the file that > > don't belong to ISO-8859. Perhaps that clue will help you solve the > > problem (you can use hexl-find-file to see the raw bytes in the file). > > Hmm, this only shows me, that file (the command) seems to be correct > with it's suggestions. So it seems, emacs is not. No, you misunderstood what I was saying. ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-18 8:05 ` Martin Monsorno 2005-08-19 8:14 ` Eli Zaretskii @ 2005-08-23 21:23 ` Jason Rumney 2005-08-25 7:52 ` Martin Monsorno 1 sibling, 1 reply; 38+ messages in thread From: Jason Rumney @ 2005-08-23 21:23 UTC (permalink / raw) Martin Monsorno <monsorno@gmx.de> writes: > Sure! I should have said that I tried many ways /including/ the one > suggested by you. When emacs asks me what coding system to use after > pressing C-x <RET> c, the default it suggests (in parentheses on the > modeline) is "mule-utf-8". After opening it your way, > buffer-file-coding-system's value is raw-text-unix, nevertheless. In the Options menu, there is a submenu "Mule (Multilingual Environment)". At the bottom of that submenu is "Show All of Mule Status". If you select that, what does the "Multibyte character awareness" under the General Information section near the top say? ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-23 21:23 ` Jason Rumney @ 2005-08-25 7:52 ` Martin Monsorno 2005-08-25 22:18 ` Peter Dyballa ` (2 more replies) 0 siblings, 3 replies; 38+ messages in thread From: Martin Monsorno @ 2005-08-25 7:52 UTC (permalink / raw) jasonr (Jason Rumney) @ f2s.com writes: > Martin Monsorno <monsorno@gmx.de> writes: > >> Sure! I should have said that I tried many ways /including/ the one >> suggested by you. When emacs asks me what coding system to use after >> pressing C-x <RET> c, the default it suggests (in parentheses on the >> modeline) is "mule-utf-8". After opening it your way, >> buffer-file-coding-system's value is raw-text-unix, nevertheless. > > In the Options menu, there is a submenu "Mule (Multilingual > Environment)". At the bottom of that submenu is "Show All of Mule Status". > > If you select that, what does the "Multibyte character awareness" > under the General Information section near the top say? it says: ,---- | Multibyte characters awareness: | default: nil | current-buffer: nil | | Current language environment: UTF-8 `---- doesn't sound too well, does it? -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-25 7:52 ` Martin Monsorno @ 2005-08-25 22:18 ` Peter Dyballa [not found] ` <mailman.5086.1125044809.20277.help-gnu-emacs@gnu.org> 2005-08-29 0:51 ` Jason Rumney 2 siblings, 0 replies; 38+ messages in thread From: Peter Dyballa @ 2005-08-25 22:18 UTC (permalink / raw) Cc: help-gnu-emacs Am 25.08.2005 um 09:52 schrieb Martin Monsorno: > | Current language environment: UTF-8 > There is nowhere in this world a language ``UTF-8´´, even Esperanto is ``Esperanto´´. Try it again with German and do yourself a favour and set LC_ALL to an UTF-8 value! Then check the multibyte awareness again! -- Mit friedvollen Grüßen Pete "Give a man a fish, and you've fed him for a day. Teach him to fish, and you've depleted the lake." ^ permalink raw reply [flat|nested] 38+ messages in thread
[parent not found: <mailman.5086.1125044809.20277.help-gnu-emacs@gnu.org>]
* Re: how to change file coding system [not found] ` <mailman.5086.1125044809.20277.help-gnu-emacs@gnu.org> @ 2005-08-26 9:52 ` Martin Monsorno 2005-08-26 10:48 ` Peter Dyballa 2005-08-26 9:59 ` Reiner Steib 1 sibling, 1 reply; 38+ messages in thread From: Martin Monsorno @ 2005-08-26 9:52 UTC (permalink / raw) Peter Dyballa <Peter_Dyballa@Web.DE> writes: > Am 25.08.2005 um 09:52 schrieb Martin Monsorno: > >> | Current language environment: UTF-8 >> > > There is nowhere in this world a language ``UTF-8´´, even Esperanto is > ``Esperanto´´. Try it again with German and do yourself a favour and > set LC_ALL to an UTF-8 value! Then check the multibyte awareness again! Well, you can choose "UTF-8" from the "Set Language Environment"? (while I'm sure that there are even less UTF-8 speakers than there are esperanto speakers). Anyway, choosing "German" from the list makes the info screen showing "German" as language environment, but nothing else changes. locale says: ,---- | monsorno@mmdev ~ $ locale | LANG=de_DE.utf8 | LC_CTYPE="de_DE.utf8" | LC_NUMERIC="de_DE.utf8" | LC_TIME="de_DE.utf8" | LC_COLLATE="de_DE.utf8" | LC_MONETARY="de_DE.utf8" | LC_MESSAGES="de_DE.utf8" | LC_PAPER="de_DE.utf8" | LC_NAME="de_DE.utf8" | LC_ADDRESS="de_DE.utf8" | LC_TELEPHONE="de_DE.utf8" | LC_MEASUREMENT="de_DE.utf8" | LC_IDENTIFICATION="de_DE.utf8" | LC_ALL=de_DE.utf8 `---- I played around with de_DE.UTF-8, posix and leaving the value blank (LANG and LC_ALL): no difference! Emacs always prints the same info about multibyte character awareness and language environment. It seems to me my emacs installation is /not/ capable of handling multibyte characters, right? So what to do? -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-26 9:52 ` Martin Monsorno @ 2005-08-26 10:48 ` Peter Dyballa 2005-08-26 18:12 ` Kevin Rodgers 0 siblings, 1 reply; 38+ messages in thread From: Peter Dyballa @ 2005-08-26 10:48 UTC (permalink / raw) Cc: help-gnu-emacs Am 26.08.2005 um 11:52 schrieb Martin Monsorno: > locale says: I don't know what this command ``locale´´ is doing, what I recommend and what is documented in GNU Emacs is the use of environment variables. Those are set in Bourne Shell alikes (sh, bash, ksh, zsh) à la: LANG=de_DE.UTF-8 export LANG and in csh alikes (csh, tcsh, zsh) à la: set LANG=de_DE.UTF-8 > > It seems to me my emacs installation is /not/ capable of handling > multibyte characters, right? So what to do? > Check what the difference between the info from locale and an environment variable in a shell is! Check, if necessary, whether GNU Emacs understands the values returned from locale! If all fails: get yourself GNU Emacs 22 from CVS or GNU Emacs 23 from a not working server? If Miles Bader or any other from the Unicode Emacs team is reading: how can the source be accessed nowadays? -- Mit friedvollen Grüßen Pete "Specifications are for the weak and timid!" ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-26 10:48 ` Peter Dyballa @ 2005-08-26 18:12 ` Kevin Rodgers 2005-08-26 18:56 ` Peter Dyballa 0 siblings, 1 reply; 38+ messages in thread From: Kevin Rodgers @ 2005-08-26 18:12 UTC (permalink / raw) Peter Dyballa wrote: > and in csh alikes (csh, tcsh, zsh) ? la: > > set LANG=de_DE.UTF-8 I think you mean: setenv LANG de_DE.UTF-8 -- Kevin Rodgers ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-26 18:12 ` Kevin Rodgers @ 2005-08-26 18:56 ` Peter Dyballa 0 siblings, 0 replies; 38+ messages in thread From: Peter Dyballa @ 2005-08-26 18:56 UTC (permalink / raw) Cc: help-gnu-emacs Am 26.08.2005 um 20:12 schrieb Kevin Rodgers: > > and in csh alikes (csh, tcsh, zsh) ? la: > > > > set LANG=de_DE.UTF-8 > > I think you mean: > > setenv LANG de_DE.UTF-8 > Oh yes! You're right -- setenv is the correct syntax. I think I need some holidays ... -- Greetings ~ O Pete ~~_\\_/% ~ O o ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system [not found] ` <mailman.5086.1125044809.20277.help-gnu-emacs@gnu.org> 2005-08-26 9:52 ` Martin Monsorno @ 2005-08-26 9:59 ` Reiner Steib 1 sibling, 0 replies; 38+ messages in thread From: Reiner Steib @ 2005-08-26 9:59 UTC (permalink / raw) On Fri, Aug 26 2005, Peter Dyballa wrote: > Am 25.08.2005 um 09:52 schrieb Martin Monsorno: > >> | Current language environment: UTF-8 >> > > There is nowhere in this world a language ``UTF-8´´, even Esperanto is > ``Esperanto´´. But it's a valid language environment in Emacs. > Try it again with German and do yourself a favour and set LC_ALL to > an UTF-8 value! Then check the multibyte awareness again! I don't think LANG and LC_* affect the multibyte awareness of Emacs, CMIIW. LC_ALL is almost never a good idea, except for testing. Maybe Martin has set EMACS_UNIBYTE or is using --unibyte? (I didn't read the whole thread. Sorry, if I'm missing something.) Bye, Reiner. -- ,,, (o o) ---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/ ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-25 7:52 ` Martin Monsorno 2005-08-25 22:18 ` Peter Dyballa [not found] ` <mailman.5086.1125044809.20277.help-gnu-emacs@gnu.org> @ 2005-08-29 0:51 ` Jason Rumney 2005-08-31 8:46 ` Martin Monsorno 2 siblings, 1 reply; 38+ messages in thread From: Jason Rumney @ 2005-08-29 0:51 UTC (permalink / raw) Martin Monsorno <monsorno@gmx.de> writes: > it says: > > ,---- > | Multibyte characters awareness: > | default: nil > | current-buffer: nil There's your problem. Check your environment for a variable EMACS_UNIBYTE. Check the way you are starting Emacs, do you have a script or alias that is actually running "emacs --unibyte" instead? Lastly, check your .emacs. I don't remember exactly how to switch Emacs into unibyte mode from there, nor if it is still even possible for more than just current-buffer, but it probably involves either the string unibyte, or multibyte in the name of the variable or function. ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-29 0:51 ` Jason Rumney @ 2005-08-31 8:46 ` Martin Monsorno 2005-08-31 9:18 ` Martin Monsorno 2005-08-31 9:55 ` Reiner Steib 0 siblings, 2 replies; 38+ messages in thread From: Martin Monsorno @ 2005-08-31 8:46 UTC (permalink / raw) jasonr (Jason Rumney) @ f2s.com writes: > Martin Monsorno <monsorno@gmx.de> writes: > >> it says: >> >> ,---- >> | Multibyte characters awareness: >> | default: nil >> | current-buffer: nil > > There's your problem. Check your environment for a variable > EMACS_UNIBYTE. > Check the way you are starting Emacs, do you have a script or alias > that is actually running "emacs --unibyte" instead? > Lastly, check your .emacs. I don't remember exactly how to switch > Emacs into unibyte mode from there, nor if it is still even possible > for more than just current-buffer, but it probably involves either > the string unibyte, or multibyte in the name of the variable or > function. Well, I didn't find anything that seems to be directly involved with this unibyte mode stuff, /but/ while searching around I found the rather harmless sounding function "standard-display-european", that I inserted im my .emacs some time ago (must be long long ago), because it fixed the display of german umlauts. The function doc says: ,---- | Enabling European character display with this command noninteractively | from Lisp code also selects Latin-1 as the language environment, and | selects unibyte mode for all Emacs buffers (both existing buffers and | those created subsequently). This provides increased compatibility | for users who call this function in `.emacs'. `---- After switchin this off, everything now works absolutely perfect. Umlauts are displayed correctly in latin-1 and utf-8 files and the encoding is displayed in the lower left corner of emacs. Thanks to you all for helping me to clear this issue! PS: I promise I will start emacs with "emacs --no-init-file" when registering strange things like these from now on! I promise I will start emacs with "emacs --no-init-file" when registering strange things like these from now on! I promise I will start emacs with "emacs --no-init-file" when registering strange things like these from now on! ... -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-31 8:46 ` Martin Monsorno @ 2005-08-31 9:18 ` Martin Monsorno 2005-08-31 9:56 ` Reiner Steib 2005-08-31 9:55 ` Reiner Steib 1 sibling, 1 reply; 38+ messages in thread From: Martin Monsorno @ 2005-08-31 9:18 UTC (permalink / raw) Damn! Deactivating standard-display-european fixes the display of files with a correctly recognized encoding. /But/ what is broken now is the display of Gnus imap folders with umlauts in their names. (I suppose this was the reason for activating this in my .emacs) Any ideas? Is this a Gnus issue? -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-31 9:18 ` Martin Monsorno @ 2005-08-31 9:56 ` Reiner Steib 2005-09-08 15:21 ` Martin Monsorno 0 siblings, 1 reply; 38+ messages in thread From: Reiner Steib @ 2005-08-31 9:56 UTC (permalink / raw) On Wed, Aug 31 2005, Martin Monsorno wrote: > Damn! Deactivating standard-display-european fixes the display of > files with a correctly recognized encoding. /But/ what is broken now > is the display of Gnus imap folders with umlauts in their names. (I > suppose this was the reason for activating this in my .emacs) > > Any ideas? Is this a Gnus issue? Please report the problem (with more details) to ding@gnus.org. Bye, Reiner. -- ,,, (o o) ---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/ ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-31 9:56 ` Reiner Steib @ 2005-09-08 15:21 ` Martin Monsorno 0 siblings, 0 replies; 38+ messages in thread From: Martin Monsorno @ 2005-09-08 15:21 UTC (permalink / raw) Reiner Steib <reinersteib+from-uce@imap.cc> writes: > Please report the problem (with more details) to ding@gnus.org. Done. Hope it helps. Thank you. -- Martin ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: how to change file coding system 2005-08-31 8:46 ` Martin Monsorno 2005-08-31 9:18 ` Martin Monsorno @ 2005-08-31 9:55 ` Reiner Steib 1 sibling, 0 replies; 38+ messages in thread From: Reiner Steib @ 2005-08-31 9:55 UTC (permalink / raw) On Wed, Aug 31 2005, Martin Monsorno wrote: > Well, I didn't find anything that seems to be directly involved with > this unibyte mode stuff, /but/ while searching around I found the > rather harmless sounding function "standard-display-european", that I > inserted im my .emacs some time ago (must be long long ago), because > it fixed the display of german umlauts. The function doc says: [...] "This function is semi-obsolete". One year ago, Richard agreed to remove switching to unibyte mode from `standard-display-european', see <URL:http://thread.gmane.org/gmane.emacs.gnus.general/58308>. But apparently nobody actually made the change. Bye, Reiner. -- ,,, (o o) ---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/ ^ permalink raw reply [flat|nested] 38+ messages in thread
end of thread, other threads:[~2005-09-08 15:21 UTC | newest]
Thread overview: 38+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-12 8:34 how to change file coding system Martin Monsorno
2005-08-12 11:30 ` Eli Zaretskii
[not found] ` <mailman.3519.1123846596.20277.help-gnu-emacs@gnu.org>
2005-08-12 12:32 ` Pascal Bourguignon
2005-08-12 15:04 ` Eli Zaretskii
2005-08-12 15:36 ` Peter Dyballa
2005-08-12 13:33 ` Martin Monsorno
2005-08-12 15:06 ` Eli Zaretskii
2005-08-12 15:52 ` Pascal Bourguignon
2005-08-12 16:33 ` Joe Corneli
[not found] ` <mailman.3561.1123859480.20277.help-gnu-emacs@gnu.org>
2005-08-16 9:22 ` Martin Monsorno
2005-08-16 11:20 ` Peter Dyballa
2005-08-17 4:07 ` Eli Zaretskii
[not found] ` <mailman.3911.1124191758.20277.help-gnu-emacs@gnu.org>
2005-08-17 9:20 ` Martin Monsorno
2005-08-17 12:22 ` Martin Monsorno
2005-08-17 19:09 ` Peter Dyballa
[not found] ` <mailman.4075.1124306087.20277.help-gnu-emacs@gnu.org>
2005-08-18 8:40 ` Martin Monsorno
2005-08-18 11:37 ` Peter Dyballa
[not found] ` <mailman.4171.1124367223.20277.help-gnu-emacs@gnu.org>
2005-08-19 10:20 ` Martin Monsorno
2005-08-19 13:24 ` Peter Dyballa
[not found] ` <mailman.4307.1124458248.20277.help-gnu-emacs@gnu.org>
2005-08-23 9:20 ` Martin Monsorno
[not found] ` <mailman.4004.1124251989.20277.help-gnu-emacs@gnu.org>
2005-08-17 9:26 ` Martin Monsorno
2005-08-17 18:23 ` Eli Zaretskii
[not found] ` <mailman.4071.1124303238.20277.help-gnu-emacs@gnu.org>
2005-08-18 8:05 ` Martin Monsorno
2005-08-19 8:14 ` Eli Zaretskii
2005-08-23 21:23 ` Jason Rumney
2005-08-25 7:52 ` Martin Monsorno
2005-08-25 22:18 ` Peter Dyballa
[not found] ` <mailman.5086.1125044809.20277.help-gnu-emacs@gnu.org>
2005-08-26 9:52 ` Martin Monsorno
2005-08-26 10:48 ` Peter Dyballa
2005-08-26 18:12 ` Kevin Rodgers
2005-08-26 18:56 ` Peter Dyballa
2005-08-26 9:59 ` Reiner Steib
2005-08-29 0:51 ` Jason Rumney
2005-08-31 8:46 ` Martin Monsorno
2005-08-31 9:18 ` Martin Monsorno
2005-08-31 9:56 ` Reiner Steib
2005-09-08 15:21 ` Martin Monsorno
2005-08-31 9:55 ` Reiner Steib
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).