XEmacs cannot display U+FFFD (REPLACEMENT CHARACTER) correctly
Aidan Kehoe
kehoea at parhasard.net
Thu Jul 26 08:53:22 EDT 2007
Ar an ceathrú lá is fiche de mí Iúil, scríobh Mike FABIAN:
> Aidan Kehoe <kehoea at parhasard.net> さんは書きました:
>
> > [...] Okay, for the sake of round-trip compatibility (especially with a
> > future Unicode-oriented XEmacs), we should map those 7 characters
> > either to a private-use area (and one outside of the BMP) or an area
> > outside of Unicode. Do you have any objections to the following
> > mapping?
> >
> > 0xA15A => U+FA15A
> > 0xA1C3 => U+FA1C3
> > 0xA1C5 => U+FA1C5
> > 0xA1FE => U+FA1FE
> > 0xA240 => U+FA240
> > 0xA2CC => U+FA2CC
> > 0xA2CE => U+FA2CE
>
> Looks fine.
>
> To make sure that this really works I tried the attached patch
> and it does work indeed.
Ok. As I understand it, we need to state explicitly in the file that we’ve
modified it, if we’re to distribute it.
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
More information about the XEmacs-Beta
mailing list