Validate .dtd and .properties files
Tim Chien (MozTW)
I was wondering if there are any tools available to validate syntax of
DTD or properties files?
Without them, the only way to spot an error is browse through UIs and
look for yellow screen of death.
Googled but got no useful result. Any ideas?
I think one of the localization files triggered a zh-TW-only bug in
Thunderbird, but I couldn't find it.
BR,
Tim
Axel Hecht
compare-locales does some checking, and I think the translate toolkit
does some other checks. The toolchain of the japanese team does yet
another set of checks, as does what the French and what the Portugal
teams have.
YSOD usually sounds like an xml parsing error, which are really hard to
find in general. There's no real DTD parsing logic out there that I
found, so anything we have is based on "best effort"-writing an XML
parser on your own. Even if you get that right, you're not using the
same code path, and if expat+contentsink had bugs, our checks had to
reproduce those.
Not mentioning that with the cross-referenced entity references between
various parts of our code, it's non-trivial to actually distinguish
errors from just odd differences.
Axel
Anas Husseini
Perhaps moz2po tool can help. It can spot a syntax error IIRC and
isn't able to convert to a po file in that case.
HTH
Anas
On Wed, Mar 3, 2010 at 5:22 PM, Tim Chien (MozTW)
<timd...@mail.moztw.org> wrote:
> Dears,
>
> I was wondering if there are any tools available to validate syntax of
> DTD or properties files?
> Without them, the only way to spot an error is browse through UIs and
> look for yellow screen of death.
>
> Googled but got no useful result. Any ideas?
>
> I think one of the localization files triggered a zh-TW-only bug in
> Thunderbird, but I couldn't find it.
>
> BR,
>
>
> Tim
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
>
--
Experience is something you don't get until just after you need it.