🚀 go-pugleaf

I would also add that unless the folks on the PC that are doing the editing are making stylistic changes and are just editing some content, then they don't actually need the fonts. I've done tests with this and because the font type is embedded in the document it will stay there unless changed on a large level. This is of course worthless for copy-fitting, but it can work if they just need to change a word in a deck that's using a font that they don't have and can't get in OTF of PS for the PC.

As for the Word issue, if you set your default Word font to say... Adobe Caslon and do all your work in that with an OTF fontset, then any changes brought in the an InDesign or InCopy document should come through. I say should because I've found flat-out weird issues where the stylistic formatting will get lost upon import. But overall, doing this should preserve formatting and stylist changes across platforms. The only two issues you'll run in to are when outside documents come in that have whacked out formatting by some freelancer who thinks they know better and that will have to get taken out. Also, when you import a Word document, you'll get a "Normal" style sheet in the document which comes in from Word (at least that's what I remember it being called) and this will have have to be scrapped as soon as possible.

Both OTF and Word to InCopy to InDesign back to InCopy for edits workflow are you best, albeit pricey friends. Also, with InCopy CS2, you can dump out an RTF file if you need to go back to Word for any reason.

Hope all that helps. Feel free to email me if you have any other questions.

-michael
www.hudin.net <http://www.hudin.net>