It contains an additional hyphen.

Thanks for the reply and thanks for this tool.

need to check in on the shebang stuff, I thought that easy_install would do that for me.

Comments in DTDs are fine, unless you have counter examples. The #expand thing is a bug that I just WONTFIXed because we don’t use it anymore at least in firefox and thunderbird. File a bug on suite? On the main toolkit apps, it was just an indication that the URL shouldn’t be in l10n in the first place.

Regarding en-US.dic, this is gonna hit you in other places, too, suite doesn’t have a filter.py, file a bug on suite again, http://mxr.mozilla.org/mozilla/source/browser/locales/filter.py is the equivalent.

I’m not sure if I should really enhance my comparison stuff for all kinds of editor cruft.

The merge isn’t intended to play nice for now, it’s intended to be a build time workaround. If it breaks when you try to make it edit in-place or not is something that I don’t know.

It added a “#expand” alone on the end of a file that started with such command and broke the build.

By the way, I’m using with “suite” as the application.

Well…

would help a lot if the shebang were “/usr/bin/env python” instead of “python”, since the latter won’t work on most unix systems.

Also, would be nice for Linux users if the script ignored files ending on “~” or hidden files:
– file names ending with “~” are temporary files for some editors, as emacs. CVS also add files with names ending on “.~1.1.~” (where this 1.1 stands for the version of the file).
– file names starting with “.#” or starting with “.” and ending with “.swp” are swap files of some widely used text editors, as emacs and vim.
– some people may use some versioning system on their files and usually the directory is hidden (starts with a dot).

It told me to add and localize “en-US.dic”.

It doesn’t like comments on DTDs.

Is it possible to use the locale directory as destine of the merge command?
I, for instance, use git and would be fairly easy to revert anything.