Re: [translate-pootle] Alternate source language isn't shown on some languages

2010-03-03 Thread F Wolff
Op Wo, 2010-03-03 om 16:19 +0100 skryf Johannes Ahlers:
 Hi all,
 
 I set my alternative source languages to English and French. I found an 
 translation entry in one language where pootle shows both alternate 
 source languages. I checked the same entry (same ID / location) in some 
 other languages. On some the alternative languages are shown on other 
 they are missing. Why aren't they shown always? I check the 
 corresponding xlf-source files, but can't see any helpful differences. 
 The refresh_stats-task is running every night...
 
 Greetings
 
 Johannes Ahlers

Hallo Johannes

Pootle displays them if they are found and translated in the other
language, otherwise it doesn't show anything, just getting out of the
translator's way. If they are fuzzy or untranslated or not there, Pootle
will simply appear as if the alternative language is not selected, but
only for that unit.  Another issue with XLIFF, is that the id attributes
for the units would have to be the same.

Would that explain what you have seen?

Do you update your files outside Pootle? Is that why you run
refreshstats every night?

Keep well
Friedel


--
Recently on my blog:
http://translate.org.za/blogs/friedel/en/content/hunspell-osx-106


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


Re: [translate-pootle] Alternate source language isn't shown on some languages

2010-03-03 Thread Johannes Ahlers
Hi Friedel,

I will discribe the problem on an example:
On each language we have a xlf-file: cashbox/uidictionary.xlf. The first 
trans-unit element has the ID amountDifference.label. If I open this 
entry in Chinese (China) the alternative source languages in French 
and English are shown. If I open this entry in Arabic the alternative 
source languages aren't shown.

Here is the Chinese-file:
?xml version=1.0 encoding=UTF-8?
xliff xmlns=urn:oasis:names:tc:xliff:document:1.2 version=1.2
  file original= source-language=de target-language=zh_CN 
datatype=x-other
body
  trans-unit id=amountDifference.label
source xml:space=preserve xml:lang=deDifferenz/source
target xml:space=preserve /
  /trans-unit
[...]
/body
  /file
/xliff

And here is the Arabic-File:
?xml version=1.0 encoding=UTF-8?
xliff xmlns=urn:oasis:names:tc:xliff:document:1.2 version=1.2
  file original= source-language=en target-language=ar 
datatype=x-other
body
  trans-unit id=amountDifference.label
source xml:space=preserve xml:lang=enDifference/source
target xml:space=preserve /
  /trans-unit
[...]
/body
  /file
/xliff

I found a regularity: We generate our xlif-files with 
target-language-specific source languages. For all languages, where we 
set the source language to German, the alternative source texts are 
shown. For all other languages where we set English as source language 
the alternative sources are missing.

The xliff-files are synchronized with individual language-files 
generated out of our software. This task runs every night and adds, 
removes or updates trans-unit-elements in the xliff-files directly. 
Afterwards the refresh_stats-task is started to speed up pootle's intro 
screen.

Greetings

Johannes

F Wolff schrieb:
 Hallo Johannes

 Pootle displays them if they are found and translated in the other
 language, otherwise it doesn't show anything, just getting out of the
 translator's way. If they are fuzzy or untranslated or not there, Pootle
 will simply appear as if the alternative language is not selected, but
 only for that unit.  Another issue with XLIFF, is that the id attributes
 for the units would have to be the same.

 Would that explain what you have seen?

 Do you update your files outside Pootle? Is that why you run
 refreshstats every night?

 Keep well
 Friedel
   


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


[translate-pootle] Pootle XLIFF problems

2010-03-03 Thread Laurent Marchal
Hi,

I installed pootle to translate XLIFF files. My problem is when I upload 
a fr.xlf file (source=EN, target=FR) that has these entries :

body
trans-unit id=editor.name.serveroptions xml:space=preserve
source xml:lang=enServer Options/source
/trans-unit
trans-unit id=action.label.editmachine xml:space=preserve
source xml:lang=enEdit Machine/source
/trans-unit
/body

After I translated some of the strings in French, when I download the 
file back from Pootle I got :

body
trans-unit id=editor.name.serveroptions xml:space=preserve 
approved=yes
source xml:lang=enOptions Serveur/source
/trans-unit
trans-unit id=action.label.editmachine xml:space=preserve 
approved=yes
source xml:lang=enMachine Edition/source
/trans-unit
/body

As you can see pootle replace the source xml:lang=en with the French 
translation instead of adding a new source xml:lang=fr !
This completely destroys the xliff file !

Thanks.
Laurent.

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle