Dear Community, 

We handle a lot of e-learning content from Articulate suite of products. Unfortunately, embedded HTML tags are represented as <g> tags, all of which become inline tags in SDLXLIFF. I understand the parser behavior is based on the specification of <g> elements in XLIFF format defined here.

http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#Specs_Elem

Would it be possible to handle <g> tags more intelligently by paying attention to ctype attribute values within <g> tags, which basically specifies HTML element names?

Below are some example of <p>, <strong>, <span> tags in prepped SDLXLIFF, where a lack handling of <p> tags as structural tags makes segmentation less than ideal, and a lack of formatting and unclear tag pair matching could results in inaccurate translation.

Thanks for considering!

Thanks,

Naoko