[Escalated to WPML Developers team] Word calculation with ATE's new Big Segments

3) This comes from the same root cause: CRLF. it seems they are removed and for some reason they are changed by "segmenting" the result into small texts since ATE sees it as one big and long string. it's probably a parser issue.

I just got word from our devs that CRLF is not compatible since some third party libraries and parsers have this as a restriction. they mentioned, however they would treat this case as a feature request and try to see how and if they could implement this for the future.

4) The translation memory is handled by segment so if you have a segment "this is a segment" and you changed it to "this is a new segment" then it would be treated as a new segment. With bigger segments you could indeed end up spending more credits for these small typos (in exchange, you'd have a better quality translation). You can turn "bigger segments" off from the gear icon on the top right part of the editor.

5) I don't think it will be shown as a WPML setting, but it's a good idea so I'll send it to our devs as a possible improvement.

6) They are independent by organization so if the websites aren't sharing credits and translation memory then they are going to be treated separately and that means that you'd have to disable the bigger segments, if you wished to do so on all of them.

Each sentence in the translation ends with a <br> so each sentence is on it's own line.

yes, this is a collateral of that CRLF. see, the CRLF is actually "kept" but the HTML parser, for some reason interprets it super weirdly and the editor DOES remove it, or well, it kind of "moves" it.

when the parser is ran again to transform the content from ATE into the XLIFF, it re-adds it but it sort of segments the content which is at this point a HUGE string, into "mini segments". all this because it doesn't know how to correctly interprets these CRLF.

This is not seen as a bug at this moment only because we do not support CRLF, thus any outcome that comes with it, but it's seen as a feature request which our devs are considering. If it gets accepted, it will probably take a long time before it's implemented because it seems like something "easy" but it requires a LOT of changes in libraries, including the third party ones we use where we do not have much power over.

There isn't much to do here but to either use "small segments", for now which seems like a suitable solution given that you do not want to use bigger segments at all (or at least not for now or not in this project) or disable this new configuration which can both be done in the settings, set in the gear icon on the editor.

hm, you're totally right and i think i couldn't recreate it before because i either had a segment that was not "big" enough OR i had any HTML marker there.

now this is definitely a bug, you're right, and was already sent to our devs.

I'll leave this ticket open but in a different status so i can update you as soon as we have more info on this.

Regards.