Re: [PATCH pkgs] Texinfo 5.x fixes, etc.

On Fri, May 23, 2014 at 1:29 PM, Aidan Kehoe <[email protected]> wrote:
> The characters on line 4779 that iconv chokes on are all encoded in JISX
> 0208, details from #'split-char as so:
>
> ((japanese-jisx0208 34 49) (japanese-jisx0208 34 81) (japanese-jisx0208 34 113))
>
> Converted to ku/ten (row/column) indexes, these are:
>
> 2 17
> 2 49
> 2 81
>
> Looking at page 814 of Ken Lund’s CJKV Information Processing, second
> edition (2002), these all have no mappings, they are blank spaces. They also
> don’t have mappings in our japanese-jisx0208-1978 character set.
>
> The relevant text in skk.texi is describing how to enter characters by means
> of their ku/ten code (type \ within the japanese-skk input method), and
> indeed, if I type C-u C-\ japanese-skk RET \ RET XEmacs prints that line
> (4779) in the minibuffer, unencodable characters and all.
>
> It’d be reasonable to use replacement characters, something like U+FFFD, for
> them in skk.texi, and iconv and makeinfo shouldn’t choke on those. U+3013 is
> in JISX0208 and is intended for this purpose, as I understand it. To be
> clear, the characters to replace are those after W:, R: and Y:.
>
> I’m not confident that there will be problems with lines 4771 and 4780 of
> skk.texi once line 4779 is fixed. Give it a shot.
>
> I’m also irritated the Unicode coding systems don’t error more cleanly on
> this, I should have noticed and fixed this long ago. Oh well.

Thanks a lot for the solutions, Stephen and Aidan!  If only you had
offered the same advice....

Could the two of you put your heads together and decide what should be
done here?  I'm not competent to judge between the conflicting replies
the two of you gave.  Thank you and regards,
-- 
Jerry James
http://www.jamezone.org/

_______________________________________________
XEmacs-Patches mailing list
[email protected]
http://lists.xemacs.org/mailman/listinfo/xemacs-patches