"This is still occuring in FrameMaker 11 and Windows 7. So we can put it down to stupid Microsoft and IT tricks."