Re: Mule-UCS and the Euro sign.

Ar an t-ochtú lá de mí Eanair, scríobh Steve Youngs: Yeah--it bombed out last night, but didn’t seem to give a message to that effect. Checking it out again seems to have fixed it. The issue is that unicode-basic-translation-charset-order-list is initialised at compile time, based on the character sets that exist in the compiling XEmacs, and is never updated to reflect new character sets. So if latin-iso8859-15 _is_ loaded, no translation rule is ever put in place. One way to work around this would be to write a function that recalculates that list and reloads all the Mule UCS code that depended on it, and have, for example, (eval-after-load "latin-unity-latin7" `(mucs-recalculate-translation-charsets)) for the files that we’re aware create character sets. A stumbling block with this, though, is that the files mapping the Mule characters to the UCS in lisp have been moved into the etc/ hierarchy of the package, and thus won�t be available to Lisp in the packaged Mule-UCS. Would changing this back be a problem, Stephen? -- “Ah come on now Ted, a Volkswagen with a mind of its own, driving all over the place and going mad, if that’s not scary I don’t know what is.”