Caolan McNamara

A mockup I’m played around with that tries to support the normal mortal case of just selecting the right locale, but supporting the apparently common situation of
a) wanting just the UI in US English which leads people to effectively set LANG=en_US and then fighting their applications one at a time to get them to not use Letter paper, not use a baffling date format, getting . vs , in numbers, inches vs cm, and so on
b) wanting dates in ISO format
and at the least letting you know up-front the effect your settings will have on applications.

e.g. X wants everything to be standard German

e.g. X wants UI in English because X finds that more comfortable but normally X will be writing in German and using metric, wants the normal German formatting rules to apply for numbers and currency, except for dates because X wants to use the ISO date format to avoid cross-cultural cockups on dates like the 6th of April and the 4th of June.

What maps to what

callcatcher results for DEV300_m55 now show rdbmaker and basctl as unused method free. Overall unused methods drops to 949. (desktop +1)

DEV300_m54 callcatcher results show a modest -8 to 959 unused methods though sw sneaks in a new unused method.

So even if only one section in MS Word is protected against changes, then Word disables the ability to track-changes or add comments globally for *ALL* sections. Unfortunately the Table of Contents in OOo is by default a read-only element, because editing it is a bad thing to to as your changes will be blown away the next time the toc is automatically updated. So…

OOo->export to .doc->read-only OOo toc becomes a word toc in a readonly section->word refuses to insert comments anywhere in the doc, even though you can manually edit the rest of the sections in word.

Sigh, *drums fingers*. Basically it’s bustage in word isn’t it, but still a problem. No bug in OOo. Changing the OOo default to make TOCs editable would “fix” it, but suboptimal. Not exporting readonly sections as such is wrong as well.

Clearly, hacking the special case of exporting a TOC that is set to read-only to output an editable section is broken too, but might be the best solution.