We are using Translation Manager in a project to handle the translations. The setup is 1->1 translation for two different nodes (swedish to english). Running Umbraco 7.12.3.
The problem we now have is that the tables we have in RTE-fields doesn't come with the export...
Is this a known error or are we missing something..? I tried updating to latest TranslationManager-version but that didn't help either...
You could Try exporting with the Split HTML option on/off see if that makes any difference.
but if you have a sample of the HTML in the RTE with a table - I can have a look and see if i can get to the bottom of why its happening and see if we can fix it.
EDIT: Yeah turning of splitting helps.
What does that setting even really do? Does it help with anything really in the translation process? Whats the benefit and disadvantages with it?
so headings, paragraphs, lists and tables (when it works). this makes it easier for the translators to just concentrate on the text and not worry about the formatting.
the reality is most translation tools cope with the formatting, but we have the option in translation manager if people need it done as source.
Now, can I change that settings when we have translations out at translation company? I'm assuming no since that would be rather weird to match the data back.
the merging process that happens on import is the same for things that have or haven't been split - so it doesn't really matter to Translation Manager if it was split or not, it should all come back together.
Table dissappears in XLIFF export...?
Hello
We are using Translation Manager in a project to handle the translations. The setup is 1->1 translation for two different nodes (swedish to english). Running Umbraco 7.12.3.
The problem we now have is that the tables we have in RTE-fields doesn't come with the export...
Is this a known error or are we missing something..? I tried updating to latest TranslationManager-version but that didn't help either...
Hi,
tables should be exported, :(
You could Try exporting with the Split HTML option on/off see if that makes any difference.
but if you have a sample of the HTML in the RTE with a table - I can have a look and see if i can get to the bottom of why its happening and see if we can fix it.
Kevin
Thanks for a quick answer. I'll try turning splitting off.
In the meantime, this is whats in the RTE: https://pastebin.com/C5NCsCF3
EDIT: Yeah turning of splitting helps. What does that setting even really do? Does it help with anything really in the translation process? Whats the benefit and disadvantages with it?
Hi
Splitting splits HTML in to parts,
so headings, paragraphs, lists and tables (when it works). this makes it easier for the translators to just concentrate on the text and not worry about the formatting.
the reality is most translation tools cope with the formatting, but we have the option in translation manager if people need it done as source.
Alright, thanks for the answer.
Now, can I change that settings when we have translations out at translation company? I'm assuming no since that would be rather weird to match the data back.
yes, you can :)
the merging process that happens on import is the same for things that have or haven't been split - so it doesn't really matter to Translation Manager if it was split or not, it should all come back together.
Kevin
Alright thanks :)
Let me know when you've looked at the markup and if you need more help recreating the issue!
Hi
Just to say, we have added extra support for the table splitting in v2.3.0 - (just released) http://jumoo.localhost/translate/releases/2.3.0/
So in theory the table and any custom attributes/classes on the elements should now be preserved when the xliff is created.
Kevin
is working on a reply...