Wordbee supports the XLIFF 2 features described in the OASIS specification.
...
The second option permits to save back changed or new comments back to the translated XLIFF.
HTML content
Optionally choose tick this option to interpret texts as HTML content and apply an HTML filter:
...
NOTE: Document comments are not saved back to the file. Saving back is available for comments attached to segments only.
When this option is ticked the system will NOT sub-segment the text at HTML breaking tags (eg: <p>, <div>.......etc.). Only tick if XLIFF already contains translations and the translated HTML does not well match the source HTML: For example, if the source contains two <div> tags whereas the translation contains just one.
Please take into consideration that there are two prerequisites that must be achieved so that the aforementioned behavior can take place:
When ticking this option "Split text at HTML breaking tags" in the XLIFF configuration.
1) Please make sure that the XLIFF file that is going to be marked for online translation using this XLIFF config. would contain HTML content.
2) Make sure that you have configured the "Non-breaking tags" first in the HTML configuration that is attached to the XLIFF configuration
Context field
The Wordbee context field is populated with the translation unit ID (<unit id="heading1"..:>).
...