Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
moz2po changes
2 views
Skip to first unread message
Dwayne Bailey
Mar 19, 2014, 9:26:25 AM3/19/14
to dev-l10n
Hi,
For languages using *moz2po* on your own and not on Pootle you will want to
use the latest version from git master as this covers the accesskeys
changes plus some bugfixes.
See https://github.com/translate/translate
Notable changes:
1. .properties accesskeys are merged as we do with DTD files. Your
strings will go fuzzy so you might want to do this as an isolated step so
that you can easily review these.
2. Better choice on en-US accesskey based on case. This leads to some
changes in English source which will make your translations fuzzy.
3. & and other entities are now rendered as normal text in PO and
escaped in reverse. Again your strings will go fuzzy. Let us know if
we're still missing some entities.
Accesskeys that are still not merged fall into these cases:
- No entity named .label so we are unable to guess what entity stores
the label text
- Broken .label e.g. .label2, .label3 or similar
- Label text entity is named something else other then .label e.g.
.button
Some of the above are bugs which should be fixed in the en-US source, so if
you feel like chasing these down please do as they'll improve the lives of
all other translators. If you think the bug is on the toolkit side, let us
know and we'll fix it.
--
Dwayne
*Translate*
+27 12 460 1095 (work)
For languages using *moz2po* on your own and not on Pootle you will want to
use the latest version from git master as this covers the accesskeys
changes plus some bugfixes.
See https://github.com/translate/translate
Notable changes:
1. .properties accesskeys are merged as we do with DTD files. Your
strings will go fuzzy so you might want to do this as an isolated step so
that you can easily review these.
2. Better choice on en-US accesskey based on case. This leads to some
changes in English source which will make your translations fuzzy.
3. & and other entities are now rendered as normal text in PO and
escaped in reverse. Again your strings will go fuzzy. Let us know if
we're still missing some entities.
Accesskeys that are still not merged fall into these cases:
- No entity named .label so we are unable to guess what entity stores
the label text
- Broken .label e.g. .label2, .label3 or similar
- Label text entity is named something else other then .label e.g.
.button
Some of the above are bugs which should be fixed in the en-US source, so if
you feel like chasing these down please do as they'll improve the lives of
all other translators. If you think the bug is on the toolkit side, let us
know and we'll fix it.
--
Dwayne
*Translate*
+27 12 460 1095 (work)
Axel Hecht
Mar 19, 2014, 9:55:04 AM3/19/14
to
On 3/19/14, 2:26 PM, Dwayne Bailey wrote:
> Accesskeys that are still not merged fall into these cases:
>
> - No entity named .label so we are unable to guess what entity stores
> the label text
> - Broken .label e.g. .label2, .label3 or similar
> - Label text entity is named something else other then .label e.g.
> .button
>
> Some of the above are bugs which should be fixed in the en-US source, so if
> you feel like chasing these down please do as they'll improve the lives of
> all other translators. If you think the bug is on the toolkit side, let us
> know and we'll fix it.
Just a word of caution, changing these would fix things for the people
> Accesskeys that are still not merged fall into these cases:
>
> - No entity named .label so we are unable to guess what entity stores
> the label text
> - Broken .label e.g. .label2, .label3 or similar
> - Label text entity is named something else other then .label e.g.
> .button
>
> Some of the above are bugs which should be fixed in the en-US source, so if
> you feel like chasing these down please do as they'll improve the lives of
> all other translators. If you think the bug is on the toolkit side, let us
> know and we'll fix it.
working on the other side of translate toolkit, but break things for the
people that don't.
We should go about this on a case by case basis.
Axel
0 new messages