Background of the issue:
I'm testing XLIFF exports while having moved back to CTE, as it's the only way to work WPML with XLIFF files.
So I add my test page for translation and select an option to translate it myself, so that I can further export it to XLIFF.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello,
I'll try to help you while a supporter takes your case.
you can be a translation manager, but to translate yourself you also need to be set as a translator.
It's all done in the same place: WPML > Translation Management > Translators (tab).
You don't have to add yourself as a translation manager because as an Admin you're already one (all admins are automatically translation managers even though you might not see yourself in there). but you need to add yourself as a translator AND set yourself with the correct language pair (say EN > IT) to translate it.
Ok indeed, it solves the issue. Thanks for that explanation.
Sorry, 2 more questions:
1. I gave the account the capacity to export from US english to any languages. I need that to be able to export XLIFF files that way. So this means I need to be a translator to manage files, while a manager can't? This doesn't really make sense to me, since as a manager, I won't translate, but I definitly need to handle the XLIFF files in every directions.
2. Why the XLIFF file I was finally able to export includes (from English to Italian), has all fields filled with the english values? Shouldn't these be empty?
I just checked, it's absolutely not completed on the website.
1) In this case, you will be handling translation jobs, so you are actually translator in WPML system and need to be set as such.
2) Can you explain further, have they included English values as translation in your XLIFF file or? When you open XLIFF file, you should have English values as your default language and empty for translation. Is that not the case for you?
1) In this case, you will be handling translation jobs, so you are actually translator in WPML system and need to be set as such.
> So a "manager" can assign translations to specific translations, but can't export/import XLIFF files? So that, only the translators are entitled to upload these files?
Sorry, it still doesn't make sense to me, at least when working with XLIFFs files. To my understanding, a translator... translates, and shouldn't be involved with file handling or the publication process, since these are rather translation management related.
But anyway, understood, I need to have my admin profile as a translator to handle these takss
2) Can you explain further, have they included English values as translation in your XLIFF file or? When you open XLIFF file, you should have English values as your default language and empty for translation. Is that not the case for you?
Indeed. The page I'm exporting is 0% completed from English to Italian, as of what's shown from the original language. Still, when I export the page as XLIFF, I get a file that has all the English content in both columns (English and Italian). While the Italian one should be empty. I can provide you with the XLIFF file if needed.
I checked, and you are actually right, it seems that it works like that out of the box. It is due memory system we use inside the WPML plugin, so target fields need to be filled.
I have opened a feature request from our side, and have suggested a change in our plugin. I can not guarantee it will be accepted or when.
For now, you will have to delete the 2nd language content and add the correct one while translating.
