bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#31807: 27.0; `info-apropos' bad name or bad matching


From: Eli Zaretskii
Subject: bug#31807: 27.0; `info-apropos' bad name or bad matching
Date: Thu, 14 Jun 2018 16:29:00 +0300

> Date: Tue, 12 Jun 2018 16:59:19 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> 
> This is the scary text I saw, FWIW:
> 
> These default coding systems were tried to encode text
> in the buffer 'aaaaa.txt':
>   (undecided-unix (768 . 8216) (771 . 8217)) (iso-latin-1-unix (768
>   . 8216) (771 . 8217))
> However, each of them encountered characters it couldn't encode:
>   undecided-unix cannot encode these: ' '
>   iso-latin-1-unix cannot encode these: ' '
> 
> Click on a character (or switch to this window by 'C-x o'
> and select the characters by RET) to jump to the place it appears,
> where 'C-u C-x =' will give information about it.
> 
> Select one of the safe coding systems listed below,
> or cancel the writing with C-g and edit the buffer
>    to remove or modify the problematic characters,
> or specify any other coding system (and risk losing
>    the problematic characters).
> 
>   gb2312 shift_jis iso-2022-jp big5 utf-8 euc-kr euc-jis-2004 euc-jp
>   euc-tw windows-1256 windows-1258 cp874 iso-2022-jp-2004 windows-1255
>   cp869 windows-1253 iso-8859-7 adobe-standard-encoding macintosh
>   windows-1257 windows-1254 windows-1252 windows-1250 windows-1251
>   koi8-t gb18030 gbk big5-hkscs hz-gb-2312 utf-7 utf-16
>   utf-16be-with-signature utf-16le-with-signature utf-16be utf-16le
>   iso-2022-7bit utf-8-auto utf-8-with-signature eucjp-ms utf-8-hfs
>   georgian-academy georgian-ps korean-cp949 japanese-shift-jis-2004
>   japanese-iso-7bit-1978-irv japanese-cp932 pt154
>   cyrillic-alternativnyj utf-7-imap utf-8-emacs prefer-utf-8

What's so scary about it?  It clearly identifies the problematic
characters, offers clickable buttons to go to each of them, and
explains the problem.  It should probably suggest UTF-8 as the first
alternative, but other than that I see no problem in this dialog.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]