Tiny bug in handling of app-defaults?

[Stephen J. Turnbull]

Aidan Kehoe writes:

 > These are localisation-specific files that are managed by the packages, and
 > renaming them in the packages (and making the change you suggest in
 > device-x.c) would break things for 21.4 and 21.5. 

Well, no, they're not.  They're in site-packages, which means we won't
be breaking XEmacs of any version (assuming Leif has all xemacs+mule
SUMO packages installed).  As long as we aren't distributing such
files, a change won't break XEmacs.

Since they exist, presumably they break user code (which I consider
worse, if this feature is advertised).  I suggest finding out what
code and negotiating with the user(s).

But you know this stuff better than me, Aidan.  Am I missing something?

 > However, it is an open question to me how much we should expect the
 > localisation to be portable from 21.4 to 21.5 and vice-versa.

I agree in principle, but it doesn't take a Weatherman to know which
way the wind blows.  If, as several people have advocated, we are
going to try to release the current code base *soon* more or less
*as-is*, then we need 21.6 to be as portable as possible from 21.4
because it has so few user-visible improvements (IMO, Mule on
Windows counts +1, usable Unicode coding systems counts +1, and Xft
counts +1 = 3).