Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
entity reference errors
4 views
Skip to first unread message
Fernando Pereira Silveira
Sep 18, 2012, 12:14:04 PM9/18/12
to
Hi!
I just updated Thunderbird Aurora pt-BR locale, but now I'm getting entity reference errors, which confuses me because the same entity is widely used on the same DTD file.
What are those errors about?
https://l10n.mozilla.org/dashboard/compare?run=248865
I just updated Thunderbird Aurora pt-BR locale, but now I'm getting entity reference errors, which confuses me because the same entity is widely used on the same DTD file.
What are those errors about?
https://l10n.mozilla.org/dashboard/compare?run=248865
flod
Sep 18, 2012, 12:22:22 PM9/18/12
to Mozilla l10n Mailing List
You're using an entity not available in the original en-US string ;-)
http://hg.mozilla.org/comm-central/file/8f1eedc904bb/mail/locales/en-US/chrome/messenger/messenger.dtd#l553
<!ENTITY appmenuButton.label "AppMenu">
http://hg.mozilla.org/comm-central/file/8f1eedc904bb/mail/locales/en-US/chrome/messenger/messenger.dtd#l584
<!ENTITY appmenuButton.tooltip "Displays the Application Menu">
Francesco
http://hg.mozilla.org/comm-central/file/8f1eedc904bb/mail/locales/en-US/chrome/messenger/messenger.dtd#l553
<!ENTITY appmenuButton.label "AppMenu">
http://hg.mozilla.org/comm-central/file/8f1eedc904bb/mail/locales/en-US/chrome/messenger/messenger.dtd#l584
<!ENTITY appmenuButton.tooltip "Displays the Application Menu">
Francesco
Fernando Pereira Silveira
Sep 18, 2012, 1:04:40 PM9/18/12
to
I know that.
What I would like to know is why I can't use it there, since that entity is already used on the same file/context...
Is it mandatory that if some entity is not present on original string I cannot use it on translated string? Even if that entity is used on other strings on the same file?
I already tested it on Thunderbird and it works correctly.
What I would like to know is why I can't use it there, since that entity is already used on the same file/context...
Is it mandatory that if some entity is not present on original string I cannot use it on translated string? Even if that entity is used on other strings on the same file?
I already tested it on Thunderbird and it works correctly.
flod
Sep 18, 2012, 1:34:15 PM9/18/12
to dev-...@lists.mozilla.org
Il 18/09/12 19:04, Fernando Pereira Silveira ha scritto:
ship a build with those inside.
Francesco
> What I would like to know is why I can't use it there, since that entity is already used on the same file/context...
Those are warnings (orange), not errors (red). As far as I know you can
ship a build with those inside.
Francesco
Axel Hecht
Sep 18, 2012, 7:19:16 PM9/18/12
to
As flod noted, they're warnings.
Which means that they may very well be fatal, or OK. It's really hard to
tell in general if an entity is OK to be used as I can't reconstruct the
full context, aka, find out which DTD files are included in all contexts
in which the DTD file is included. Thus, I warn if the entity reference
is not a plain XML entity ref (like &) or not in the en-US string.
I think that's a fair compromise.
I expect both localizers and reviewers to use their best judgement on
those warnings when localizing, signing off, and reviewing sign-offs.
Axel
On 18.09.12 19:04, Fernando Pereira Silveira wrote:
> I know that.
>
> What I would like to know is why I can't use it there, since that entity is already used on the same file/context...
>
> Is it mandatory that if some entity is not present on original string I cannot use it on translated string? Even if that entity is used on other strings on the same file?
>
> I already tested it on Thunderbird and it works correctly.
>
Which means that they may very well be fatal, or OK. It's really hard to
tell in general if an entity is OK to be used as I can't reconstruct the
full context, aka, find out which DTD files are included in all contexts
in which the DTD file is included. Thus, I warn if the entity reference
is not a plain XML entity ref (like &) or not in the en-US string.
I think that's a fair compromise.
I expect both localizers and reviewers to use their best judgement on
those warnings when localizing, signing off, and reviewing sign-offs.
Axel
On 18.09.12 19:04, Fernando Pereira Silveira wrote:
> I know that.
>
> What I would like to know is why I can't use it there, since that entity is already used on the same file/context...
>
> Is it mandatory that if some entity is not present on original string I cannot use it on translated string? Even if that entity is used on other strings on the same file?
>
> I already tested it on Thunderbird and it works correctly.
>
0 new messages