Ar an chéad lá de mí Bealtaine, scríobh Raymond Toy:
What does "JIT" unicode mean? A quick google search
doesn't enlighten me
since most of the hits refer to xemacs.
JIT here stands for “just-in-time,” as it does elsewhere. The problem was
that the Mule encoding doesn’t have (unused) space for all the Unicode code
points as well as all the Mule code points, so a static mapping from Mule
code points to Unicode code points didn’t work.
A dynamic mapping, with Mule code points allocated at runtime, does work,
and with a bit of re-jigging of the code space, we have 200,000 possible
Unicode points in a given XEmacs session, plenty for normal use. The problem
this provoked initially was consistency from auto-save files from one
invocation to the next, and we addressed that by using the ISO-IR 196 UTf-8
compatible escapes in our ISO-2022-oriented escape-quoted autosave encoding.
The dynamic allocation idea was Mike Fabian’s, and using the ISO-IR 196
escapes for those characters was mine. The net result was we don’t have
quite the pressure towards switching to a Unicode internal encoding that we
had in the first years of this millenium.
‘Iodine deficiency was endemic in parts of the UK until, through what has been
described as “an unplanned and accidental public health triumph”, iodine was
added to cattle feed to improve milk production in the 1930s.’
(EN Pearce, Lancet, June 2011)
XEmacs-Beta mailing list