3 answers
- 10-1
Hi Bert,
I believe you of course
- yet I can not help you without getting the package to check, what the issue is. Something must be wrong / unexpected, since others are using the translator package on a regular basis.
I would propose that we look into this, once you start working with us in some time from now.
Would that work for you?
best
Marc
Add your comment... - 10-1
Hi Marc,
I just overwrote the xlf in the exported .zip with the xlf generated by Studio (in workfiles folder). All other files in the Import .zip are the same as in the export zip, I also use the same folder structure, Since I cannot attach a file here, you have to believe me
Add your comment... - 10-1
Hi Bert,
from my understanding you did it right and it should work.
Since it did not work we would need to look at the import package, as something is probably unexpected in it.
Maybe the xliff files are not in the same folder structure as in the package, that you exported?
best
Marc
Add your comment...
I exported a translator package and translated it in Studio. Then I copied the XLF file back into the exported ZIP (overwriting the language). When I then use "Re-Import Package," Translate5 reports that the target segments are empty. However, when I look at the XLF file in a text editor, all segments are translated. Am I doing something wrong?
Example for 1 TU
<trans-unit id="NFDBB2FA9-tu7" xml:space="preserve">
<source xml:lang="de-DE"><bpt id="1" ctype="x-link;color:467886;underline:single;"><hyperlink1></bpt>Der ultimative Leitfaden zu ChatGPT Codex für den Alltag<ept id="1"></hyperlink1></ept></source>
<target state="translated" xml:lang="en-GB"><bpt id="1" ctype="x-link;color:467886;underline:single;"><hyperlink1></bpt>The ultimate guide to ChatGPT Codex for everyday use<ept id="1"></hyperlink1></ept></target>
</trans-unit>