Why lines break where they do
Here is a complaint we take seriously. A paragraph converts cleanly, every word is correct, and yet it wraps in different places than it did in Publisher. One extra word climbs onto the line above, and everything below it shifts down. In a two column newsletter that can cost you a whole paragraph off the bottom of the page.
Three things decide where a line breaks. Get any one wrong and the text lands somewhere else.
Font metrics
Every letter has a width. Add them up and you know how many words fit. If the engine reads a font's measurements slightly differently than Publisher does, the count comes out different too. We wrote about that last time in when you don't have the font, and the fixes there are the base layer for everything here.
Hyphenation
Publisher does not hyphenate the moment a word runs long. It gives itself an 18 point zone at the right margin first: if the word starts inside that zone, it wraps whole instead of splitting. Our engine now uses the same zone, so words break in the same places, or stay whole in the same places.
Curved text got the same treatment. A word that almost fits on a curved line no longer splits partway through, so "sub-ject" arching over a logo is "subject" again.
The padding inside the frame
Text does not start at the edge of its box. There is a margin inside, and in tables Publisher sets its own. Ours was a guess. Now it is Publisher's, and table cells that land within half a point of Publisher went from under 2 in 100 to 89 in 100.
One honest note: a narrow header cell can still wrap to two lines where Publisher fits one. We are working on it.
More on where text sits: text that sits where Publisher puts it.
If a paragraph wrapped wrong in your file, run it again.