jDiction Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

jDiction 2.2.0 released. http://jdiction.org/downloads

Author Topic: XLIFF import problem  (Read 8339 times)

marcel

  • Newbie
  • *
  • Posts: 3
    • View Profile
XLIFF import problem
« on: March 12, 2015, 09:13:19 pm »
I have just installed diction 1.4.1 on a joomla 3.4 website. "Manual" translation works fine. However, I need to translate the website with a CAT tool using the xliff export. They xliff export works fine but when I try to import the translated xliff file I get 0 translations imported. They same happens when exporting and importing a csv file.
I'd be very glad if you could help me with that.
Thanks in advance!
Logged

Harald Leithner

  • Administrator
  • Hero Member
  • *****
  • Posts: 1684
    • View Profile
Re: XLIFF import problem
« Reply #1 on: March 13, 2015, 08:43:47 am »
I will check that later
Logged
Joomla! 5.0 Release Manager
Vote at JED

marcel

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: XLIFF import problem
« Reply #2 on: March 13, 2015, 09:27:34 am »
Thanks in advance.
Logged

marcel

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: XLIFF import problem
« Reply #3 on: March 17, 2015, 08:57:48 am »
Hi Harald,
Did you already find out about that mistake/behaviour? I have to localize a Joomla 3.4 website into four languages soon and would really like to use jDiction as it is the only Joomla plugin (that I know) that supports XLIFF/CSV export and import for using professional CAT tools in the translation process (which is essential for me).
Thanks in advance!
Best regards,
Marcel
Logged

Mark

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: XLIFF import problem
« Reply #4 on: March 17, 2015, 11:07:00 am »
Hi both,

I have the same problem here. I have a dutch website and created two languages NL and EN. Exported the NL to XLIFF and had that translated. Now when i try to import the EN translation it says 0 translations found...

Attached you can find the translated XLIFF file, maybe something is wrong with that?

Joomla 2.5.19 & JDiction 1.3.2

Grtz, Mark
Logged

Harald Leithner

  • Administrator
  • Hero Member
  • *****
  • Posts: 1684
    • View Profile
Re: XLIFF import problem
« Reply #5 on: March 17, 2015, 06:42:06 pm »
I'm a little bit short on time I will check if I get to fix it this week
Logged
Joomla! 5.0 Release Manager
Vote at JED

Harald Leithner

  • Administrator
  • Hero Member
  • *****
  • Posts: 1684
    • View Profile
Re: XLIFF import problem
« Reply #6 on: March 18, 2015, 01:24:05 pm »
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: [Select]
<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[<p>123</p>]]></source>
<target state='translated'><![CDATA[<p>hhh</p>]]></target>
</trans-unit>
</body>
</file>
</xliff>
maybe your translation tool don't change this value. Could you check the source file
Logged
Joomla! 5.0 Release Manager
Vote at JED

Mark

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: XLIFF import problem
« Reply #7 on: March 18, 2015, 04:32:42 pm »
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: [Select]
<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[<p>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.</p>
<p>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.</p>]]></source>
<target state='translated'><![CDATA[<p>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.</p>
<p>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.</p>]]></target>
</trans-unit>
</body>
</file>
</xliff>
NOT WORKING:
Code: [Select]
<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[<p>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.</p>]]></source>
<target state='translated'><![CDATA[<p> 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. </p>]]></target>
</trans-unit>
</body>
</file>
</xliff>
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?
Logged

Mark

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: XLIFF import problem
« Reply #8 on: March 23, 2015, 12:30:26 pm »
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
Logged

Harald Leithner

  • Administrator
  • Hero Member
  • *****
  • Posts: 1684
    • View Profile
Re: XLIFF import problem
« Reply #9 on: March 23, 2015, 12:40:10 pm »
I think I have found the problem, the files have to be UTF8 encoded.

After I converted the notworking part it worked for me.
Logged
Joomla! 5.0 Release Manager
Vote at JED

Harald Leithner

  • Administrator
  • Hero Member
  • *****
  • Posts: 1684
    • View Profile
Re: XLIFF import problem
« Reply #10 on: March 24, 2015, 08:44:51 pm »
Did this fix it?
Logged
Joomla! 5.0 Release Manager
Vote at JED

Mark

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: XLIFF import problem
« Reply #11 on: March 24, 2015, 10:10:14 pm »
Hi Harald, i tried it today and i came a lot further. The trick was to save the file in UTF8 format. But still a lot of translations didn't import, did probably has to do with the file itself.

Thank you for your help!

Grt,
Mark
Logged

Harald Leithner

  • Administrator
  • Hero Member
  • *****
  • Posts: 1684
    • View Profile
Re: XLIFF import problem
« Reply #12 on: March 25, 2015, 08:15:09 am »
Could you show me what translation didn't worked?
Logged
Joomla! 5.0 Release Manager
Vote at JED