XLIFF allows you to natively define the size of your translation units in any locale. The size limit is defined at segment level, which means that any existing sub-segments rely on the same meta information attached to that segment. This means, if a segment has subsegments (segment 13, 13-1, 13-2, 13-3) they all share the same context or segment properties.
In any case, the information on text length constraints is always passed over to the Editor so you can apply with confidence your QA checks and have the problematic segments highlighted. You will always be able to verify the text length constraints in the main sub-segment, listed without index (segment 13 in the example above). However, if you are working offline you may not have visibility of the limitations applied to subsegments so you will need to process your files twice, with different text extraction profiles:
- Profile 1: (parse file not to create subsegments). You could have the maxwidth property applied to the group of all sentences contained in the segment. This profile will have the subsegmentation based on SRX or linebreaks disabled as shown below (the highlighted part in yellow may vary depending on your files).
Translators will be able to do their best attempt in the translation to respect the maxwidth for whole the segment.
- Profile 2: (parse the file as usual). You will use this alternative profile with the translated XLIFF, using the regular segmentation rule, making sure you also extract the translations if any (see option available under the content section of the parser). Since the translated file is bilingual, the segmentation rules will apply for both languages. This means, you will automatically generate the subsegments from this file and the last checks can easily be done in Wordbee with the existing QA profile to ensure consistency.
To verify the information passed as maximum text length check the related article How do I pass over the text length constraints contained in my XLIFF files?