Re: [l10n-dev] TMs for 3.0

2008-02-14 Thread Clytie Siddall


On 13/02/2008, at 4:23 PM, Jean-Christophe Helary wrote:



On 13 févr. 08, at 14:16, Clytie Siddall wrote:

In response to our requests, the latest version of the Translate  
Toolkit actually has _less_ escaping than the SDF file. It replaces  
the extra escaping when you convert to SDF.


Sure, but the TMX that Rafaella delivered have _no_ escaping  
problems whatsoever.


It is the SDF->PO->TMX conversion that causes the incompatibilities  
that have been previously mentioned. The fact that the current SDF- 
>PO->TMX is "less bad" at delivering  properly escaped (or not)  
files is not really relevant.


Also, the fact that TMX sets have different escape rules depending  
on the converter version defeats the purpose of TMXs... Do we need  
to reconvert megabytes of file sets every time there is a new  
version of TT ?


Hmm, I don't think I explained myself well enough.

The Translate Toolkit now gives us a very clean, escape-free Help  
text. This avoids a lot of errors and rechecking, and makes the text  
look much less intimidating and complex to new translators (or ones  
like me, who have very limited concentration).


This change is a huge help, and provided directly in response to user  
requests. As a user, I really appreciate that kind of support.


I have no problems converting between SDF and PO. My PO editor handles  
XLIFF and TMX conversion natively, so I'm looking forward to dealing  
with the TMX Rafaella has kindly provided (once they stop munging  
Vietnamese characters).


I've found it a very simple matter to update files created by older  
versions of the Toolkit, and, in view of its constant improvement, I  
do not consider those few seconds ill-spent. This version is the only  
time I've had to do anything of the kind. In fact, the constant  
improvement of the Toolkit is generally seamless: the only thing we  
generally have to do when there is a new version of TT is install it.


Which, in my experience, has always been a minute or two well-spent. :)

from Clytie

Vietnamese Free Software Translation Team
http://vnoss.net/dokuwiki/doku.php?id=projects:l10n



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [l10n-dev] TMs for 3.0

2008-02-12 Thread Jean-Christophe Helary


On 13 févr. 08, at 14:16, Clytie Siddall wrote:

In response to our requests, the latest version of the Translate  
Toolkit actually has _less_ escaping than the SDF file. It replaces  
the extra escaping when you convert to SDF.


Sure, but the TMX that Rafaella delivered have _no_ escaping problems  
whatsoever.


It is the SDF->PO->TMX conversion that causes the incompatibilities  
that have been previously mentioned. The fact that the current SDF->PO- 
>TMX is "less bad" at delivering  properly escaped (or not) files is  
not really relevant.


Also, the fact that TMX sets have different escape rules depending on  
the converter version defeats the purpose of TMXs... Do we need to  
reconvert megabytes of file sets every time there is a new version of  
TT ?



Jean-Christophe Helary


http://mac4translators.blogspot.com/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [l10n-dev] TMs for 3.0

2008-02-12 Thread Clytie Siddall


On 08/02/2008, at 11:13 AM, Jean-Christophe Helary wrote:



On 8 févr. 08, at 00:41, F Wolff wrote:

Furthermore, I think it is important to note that these TMX files  
does

not follow the same unescaping rules of the new conversions done by
Translate Toolkit 1.1.  Of course, TMX files corresponding to the new
unescaping rules can be generated from the set of PO files with  
po2tmx

from the Translate Toolkit:
http://translate.sourceforge.net/wiki/toolkit/po2tmx


Because they have been created directly from the SDF files and not  
from the PO files.


The translate toolkit is vastly over escaping strings. If you need a  
reference to see how proper escaping should be done, take a look at  
the PO files from the Debian distribution.


It would be nice if TT could comply with already established rules  
of the "industry" and not re-invent the wheel at each new release.


ps: do you also meant that TMX created with TT 1.1 are not  
compatible with TMX created with previous TT versions ? Why do you  
think you have the right to break our work because you suddenly  
decided to change your specs ?


Whoa, J-C, hold on!

In response to our requests, the latest version of the Translate  
Toolkit actually has _less_ escaping than the SDF file. It replaces  
the extra escaping when you convert to SDF.


All you see after you run oo2po are strings like this:
___
Calculates the amount of  
depreciation for a settlement period as linear amortization. If the  
capital asset is purchased during the settlement period, the  
proportional amount of depreciation is considered.


DatePurchased is the date of acquisition.
___

Very clean.

It's also very simple to convert previous files, if required. I think  
it's all covered in the wiki, but all you need to do is remove the  
extra backslashes.


The Wordforge people are trying to help us simplify and/or improve our  
workflow. Things don't always turn out the way they may want, but they  
work very hard to fix any errors.


Don't shoot the pony carrying the messenger, please. :)

from Clytie

Vietnamese Free Software Translation Team
http://vnoss.net/dokuwiki/doku.php?id=projects:l10n



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [l10n-dev] TMs for 3.0

2008-02-12 Thread Clytie Siddall


On 08/02/2008, at 2:33 AM, Rafaella Braconi wrote:


I had a _very_ quick look at some of them, and it seems that the Help
file for zh-CN and the Vietnamese UI and help file has some encoding
problems. All the others that I tried (mostly UI files) seemed ok. (I
didn't try all of them.)



It would be great to get feedback from the Chinese and Vietnamese  
team regarding the encoding issue...


:(

Very messy. It can't be proper UTF-8.

As far as I can tell without reading through the entire file, the  
upper- and lower-case versions of two characters in particular are  
displayed incorrectly:


Unicode letter  description in the TMX

U+0111  đ   crossed-d   0x00C4�
U+0110  Đ   crossed-D   0x00C4�
U+0103  ă   a breve 0x00C4�
U+0102  Ă   A breve 0x00C4�

I have no idea why. :(

What tools did you use, Rafaella, to produce the TMX?

from Clytie

Vietnamese Free Software Translation Team
http://vnoss.net/dokuwiki/doku.php?id=projects:l10n



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [l10n-dev] TMs for 3.0

2008-02-07 Thread Jean-Christophe Helary


On 8 févr. 08, at 00:41, F Wolff wrote:


Furthermore, I think it is important to note that these TMX files does
not follow the same unescaping rules of the new conversions done by
Translate Toolkit 1.1.  Of course, TMX files corresponding to the new
unescaping rules can be generated from the set of PO files with po2tmx
from the Translate Toolkit:
http://translate.sourceforge.net/wiki/toolkit/po2tmx


Because they have been created directly from the SDF files and not  
from the PO files.


The translate toolkit is vastly over escaping strings. If you need a  
reference to see how proper escaping should be done, take a look at  
the PO files from the Debian distribution.


It would be nice if TT could comply with already established rules of  
the "industry" and not re-invent the wheel at each new release.


ps: do you also meant that TMX created with TT 1.1 are not compatible  
with TMX created with previous TT versions ? Why do you think you have  
the right to break our work because you suddenly decided to change  
your specs ?


Jean-Christophe Helary


http://mac4translators.blogspot.com/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [l10n-dev] TMs for 3.0

2008-02-07 Thread Rafaella Braconi

Hi Friedel,

first of all thank you for your verifying the files. Please see my 
comments below:



I had a _very_ quick look at some of them, and it seems that the Help
file for zh-CN and the Vietnamese UI and help file has some encoding
problems. All the others that I tried (mostly UI files) seemed ok. (I
didn't try all of them.)
  


It would be great to get feedback from the Chinese and Vietnamese team 
regarding the encoding issue...

Furthermore, I think it is important to note that these TMX files does
not follow the same unescaping rules of the new conversions done by
Translate Toolkit 1.1.  Of course, TMX files corresponding to the new
unescaping rules can be generated from the set of PO files with po2tmx
from the Translate Toolkit:
http://translate.sourceforge.net/wiki/toolkit/po2tmx
  

Thank you for bringing this up.

Hopefully there are solutions for all preferred working methods.
  

+1

Rafaella

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [l10n-dev] TMs for 3.0

2008-02-07 Thread F Wolff
Op Donderdag 2008-02-07 skryf Rafaella Braconi:
> Dear All,
> 
> please find the latest tmx (based on the 2.4 release) at : 
> http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/tmx24/
> 
> Great thanks to Frank and Ivo!
> 
> Rafaella
> 

I had a _very_ quick look at some of them, and it seems that the Help
file for zh-CN and the Vietnamese UI and help file has some encoding
problems. All the others that I tried (mostly UI files) seemed ok. (I
didn't try all of them.)

Can you perhaps have a look at these files at least? Perhaps some
validation against the others would be a good idea to make sure they are
ok? I simply ran pocount over the files to see how big they are, and the
parser complained because of incorrect UTF-8 data in the Vietnamese
files. The zh-CN file just _looks_ wrong. For example:


Example:


示0x00E4��:


(the two characters before the colon is "U+FFFD REPLACEMENT CHARACTER"
with notes:
used to replace an incoming character whose value is unknown or
unrepresentable in Unicode

So I guess something went wrong somewhere.


Furthermore, I think it is important to note that these TMX files does
not follow the same unescaping rules of the new conversions done by
Translate Toolkit 1.1.  Of course, TMX files corresponding to the new
unescaping rules can be generated from the set of PO files with po2tmx
from the Translate Toolkit:
http://translate.sourceforge.net/wiki/toolkit/po2tmx

Hopefully there are solutions for all preferred working methods.

Keep well

Friedel




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [l10n-dev] TMs for 3.0

2008-02-07 Thread Rafaella Braconi

Dear All,

please find the latest tmx (based on the 2.4 release) at : 
http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/tmx24/


Great thanks to Frank and Ivo!

Rafaella

Paolo Pozzan wrote:

Hello everybody,

Is it possible to obtain updated Translation Memories?
They are very useful when working offline with .po files.

Thanks!
Paolo

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[l10n-dev] TMs for 3.0

2008-02-03 Thread Paolo Pozzan
Hello everybody,

Is it possible to obtain updated Translation Memories?
They are very useful when working offline with .po files.

Thanks!
Paolo

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]