XLIFF import problem

English > General Questions

<< < (2/3) > >>

Harald Leithner:
I'm a little bit short on time I will check if I get to fix it this week

Harald Leithner:
Ok, now I got time to test it and it worked for csv and xlf....

What I have done was to install Joomla, install jdiction, create a article, export jdiction with 'com_content' filter, changed it by hand, imported it and checked if the translation was there...

So csv should work.

On XLF you have to check if the translation tool set the target-tag to "translated".

Here is the example:

--- Code: ---<xliff version='1.2' xmlns='urn:oasis:names:tc:xliff:document:1.2'>
<file original='84e82d5cfbf593a3e66580e648a70a09' source-language='en-GB' target-language='de-DE' datatype='htmlbody' product-name='jDiction' product-version='1.4.1'>
<body>
<trans-unit id='1.com_content.article.edit.title'>
<source><![CDATA[123]]></source>
<target state='translated'><![CDATA[ggg]]></target>
</trans-unit>
<trans-unit id='1.com_content.article.edit.introtext'>
<source><![CDATA[123]]></source>
<target state='translated'><![CDATA[hhh]]></target>
</trans-unit>
</body>
</file>
</xliff>
--- End code ---

maybe your translation tool don't change this value. Could you check the source file

Mark:
Hi Harald,

Thanks for your reply. I've been puzzling for hours now and trying to import little segments of the XLF file. I corrected the target state to 'translated' but still no go :(

I have a working and non-working file:

WORKING:

--- Code: ---<xliff version='1.2' xmlns='urn:oasis:names:tc:xliff:document:1.2'>
<file original='903065ad874cfe4abc2d7cdc6db41d4e' source-language='nl-NL' target-language='en-GB' datatype='htmlbody' product-name='jDiction' product-version='1.3.2'>
<body>
<trans-unit id='2.com_content.article.edit.title'>
<source><![CDATA[Profiel]]></source>
<target state='translated'><![CDATA[Profile]]></target>
</trans-unit>
<trans-unit id='2.com_content.article.edit.introtext'>
<source><![CDATA[MediLingua is volledig gespecialiseerd in het vertalen en redigeren van medische informatie. U kunt bij ons terecht met alle mogelijke medische teksten, van bijsluiters bij geneesmiddelen tot medische software en van gebruiksaanwijzingen en verpakkingsteksten bij operatie-instrumenten tot handleidingen bij medische apparatuur.
Vertalen is onze belangrijkste activiteit. Daarnaast houden we ons bezig met het schrijven, redigeren, controleren en testen van medische teksten. Alle projecten worden centraal ondersteund en geleid vanuit ons kantoor in Leiden.]]></source>
<target state='translated'><![CDATA[MediLingua specialises exclusively in the translation and editing of medical information. You can come to us with any medical text, whether it is patient information leaflets, medical software, instructions for use and packaging texts or manuals for medical equipment.
Translation is our core activity but alongside this we handle writing, editing, reviewing and the testing of medical texts. All projects are centrally managed from our office in Leiden.]]></target>
</trans-unit>
</body>
</file>
</xliff>
--- End code ---

NOT WORKING:

--- Code: ---<xliff version='1.2' xmlns='urn:oasis:names:tc:xliff:document:1.2'>
<file original='815252e5635669a53692aae01ed07418' source-language='nl-NL' target-language='en-GB' datatype='htmlbody' product-name='jDiction' product-version='1.3.2'>
<body>
<trans-unit id='1.com_content.article.edit.title'>
<source><![CDATA[Welkom]]></source>
<target state='translated'><![CDATA[Welcome]]></target>
</trans-unit>
<trans-unit id='1.com_content.article.edit.introtext'>
<source><![CDATA[MediLingua is al sinds 1996 de specialist in farmaceutische, (bio)medische en medisch-technische vertalingen. Onze bewuste specialisatie en de daarbij opgedane kennis onderscheiden ons van andere vertaalbureaus. Wij leveren niet zomaar een vertaling af, maar denken met u mee om tot het beste eindresultaat te komen.]]></source>
<target state='translated'><![CDATA[ MediLingua is one of the leading specialists for pharmaceutical, (bio) medical and medical technology translations. This deliberate specialisation and the knowledge we have acquired through our specific focus are what makes us different from other translation companies. We’ve been doing medical work from 1996, longer than most companies. It is not so much that we simply provide a translation but with our background and experience, we are able to understand your needs so that, together, we can help you achieve the best end result. ]]></target>
</trans-unit>
</body>
</file>
</xliff>
--- End code ---

I can't find a difference between the two, do you have any idea?! The only thing i can't check is if the original attribute in the file element is correct. Can i check this somewhere in the Joomla database or is it generated by jDiction itself? Is it used in any way?

Mark:
Hi Harald, do you have time to look at my import problem? I have to do 7 languages, so I really hope to get this thing working. Otherwise it would be a lot of copy/pasting for me :(

Mark

Harald Leithner:
I think I have found the problem, the files have to be UTF8 encoded.

After I converted the notworking part it worked for me.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version