By committing changes of this sort to base-config and languagechooser at this point *without testing them*, you run the risk of getting a nice errata item for your language for the final sarge release that says "does not work, pick another language". It's stupid, don't do it.
Also, NEVER commit code changes to base-config at this point without talking to me. I have to explain each code change in base-config to the release managers; which is impossible if nobody has explained them to me. People who abuse this privelige will lose commit access to base-config.
(BTW, the branch of base-config you committed your changes to is not one that will ever be released in sarge, so I assume you just broke your language by getting languagechooser and base-config out of sync. One reason you should talk to the maintainer first.)
(Also BTW, you documented your change in the changelog entry for a released version of base-config, which is broken and indicates you don't know what you're doing even if none of the above did.)
I guess this applies to Bulgarian's CP1251 too. Now I see that last changelog entry is for unstable, not UNRELEASED.
It is acceptable for Bulgarian language to revert the CP1251 support in termwrap. Then jfbterm will be used.
Regards, ogi
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
