I don't think it's caused by the segmentation rules (then you would get the same weird segmentation in e.g. Word files too, not only in InDesign), but by the structure of the InDesign source.
Try to open the IDML source in text editor and see what exactly in the XML...

Okay, it's not .... but periods with NBSPs and periods with normal spaces in between. In this case, the first three periods are separated by NBSPs, the last period is preceeded by a normal space

In Studio (I merged the segments manually):

Daniel

Unknown said:

periods with NBSPs and periods with normal spaces in between. In this case, the first three periods are separated by NBSPs, the last period is preceeded by a normal space

...which is, BTW, typographically wrong ;-)
There should be ellipsis, not three periods (nota bene separated by non-breaking spaces!).

So... all in all it's just about the old "garbage in, garbage out" rule - if there is a mess in the input, you can't really expect a proper and good result.

Thanks.

I'll have to do a few tests on this... see at which stage this can still be corrected, e.g. CleanUp Task or pre-process the icml files...

Evzen Polenka

I agree they should use the ellipsis, but I have no or little influence on this. CleanUp Task only comes in after segmentation is done, so that alone can't fix this.

I would only pre-process these files if there was no alternative whatsoever.

So here is my solution:

• Change the "full stop" segmentation rule settings so that instead of the default "\s", the after break regex is "\s(?!\.)" That prevents segmentation if a full stop is followed by a space which is followed by a full stop. (And hopefully there is not other fallout...)
• Then CleanUp Task comes in (can be automated, I like that) and replaces "\.\s\.\s\." with an ellipsis.

Thank you again for your input.

Daniel