Comments on: What happened to two localizations on the day of Firefox 3.5′s release

By: Bill

Bill — Mon, 27 Jul 2009 00:48:04 +0000

I am totally giving up on your so0ftware. I hate IE, and do not like Opra, so I guess I either develop my own or search for something new.

By: Philippe

Philippe — Fri, 24 Jul 2009 13:05:21 +0000

@RK : yes it works, but I think that for the two first lines, it threats the ” (and the inversed ones) as entities (likes the "es; that appears further).

By: RQ

RQ — Fri, 24 Jul 2009 07:32:51 +0000

Doh, my reply targets Philippe’s comment, actually.

By: RQ

RQ — Fri, 24 Jul 2009 07:30:13 +0000

This doesn’t seem to work very well. See http://frenchmozilla.fr/glossaire/lt/entite for example.

By: seth bindernagel

seth bindernagel — Thu, 23 Jul 2009 22:13:55 +0000

Gordon: Thanks for the comment. We’ll keep an eye out for that.

By: gordon

gordon — Thu, 23 Jul 2009 21:33:11 +0000

This isn’t the first time this has happened for the mk locale. It has had issues with invalid rdf files. The ko locale is another culprit. Please also make sure to check for valid RDF when doing automation.

By: Philippe

Philippe — Thu, 23 Jul 2009 09:01:02 +0000

For localizers who already want to test for misspelling entities in their localization, there is :

http://frenchmozilla.fr/glossaire/fr/entite

which search for difference between your locale and en-US entities name in their localisation.

(Replace fr with your short locale code).

By: Simon

Simon — Thu, 23 Jul 2009 03:29:10 +0000

(Never mind… missed the comment about test automation)

By: Simon

Simon — Thu, 23 Jul 2009 03:20:06 +0000

For simple cases such as unresolvable entities, shouldn’t there be automated processes for validating localizations, perhaps as part of packaging a release? It wouldn’t catch minor embarrassments like spelling errors, but would certainly catch anything that results in an invalid page…