I realized a few days ago that the .sdf (at least for the fr project)
for the coming 2.3 contains weird stuff without much of an
explaination as to how to differenciate the different parts.
1) in some places the target part is made of what would be a "fuzzy"
in PO, but without specific notification of the fuzzy character
2) in some places it seemingly contains exact matches
3) in some other places it contains the source English string
In the case where the fuzzy is present, the reference links are
sometimes totally different. Which means that besides for the actual
editing of the translation, it is also necessary to edit the links.
I wonder about the utility of such a mechanism especially since there
is no way to differenciate between the 3 patterns in the .sdf itself.
It seems to me it would have been faster to _not_ insert fuzzies at
all and to provide a complete TMX of the existing OOo contents instead.
Right now, if one wants to create a TMX out of the .sdf files (either
with the Translate toolkit or with Hearstome translation suite, I
suppose there are other ways though), it is impossible to have the
source strings corresponding to the fuzzy target and thus the
matching in a TMX suppotirting CAT tool will not be of much use.
Is there still a way to get SUN to provide the l10n teams with TMX of
the existing contents, similarly to what we can get through the
SunGloss system ?
(FYI, the NetBeans team is provided with TMX and that greatly
enhances the localization process.)
Jean-Christophe Helary
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
