It is very easy to end up with different fonts and font sizes in rich text fields across the myriad of RTF fields contained in an IM model. Trouble is that Publisher outputs them in to a generated Word document as-is and the result is a mess that takes quite a bit of manual tidying up work. Between IM and Publisher this needs to be got right. (Just don't loose emphasis (bold, italics, underlining) in the solution.) Personally, I would advocate the use of a markdown language (such as ASCIIDOC) as an alternative to rich text. However, having the means to fix the font and font size when the RTF is output by Publisher into the generated document would be one solution. Alternatively, provide the means to do this in IM, may be with a script, or a Reviewer rule with a fix.
