but no real explanations or solutions were presented.
The explanation was given,though for solutions... it's another subject.
Word is using 'faux' italic and 'faux' bold, that is electronic bolding and italics, as if there were no true italics and bold typefaces. This is done by in-line commands for each. InDesign is explicit in using true bold and italic typefaces.
Thus the result.
(One program's simplistic approach to word processing, becomes another's problem).
Using styles in Word (well defined) with proper equivalents in InDesign would help, if that was the case...
George
Dave
InDesign will only let you use real fonts if they exist. If they don't then you'll see what you're seeing. The bold and italic encoding is still there and will spring into life if you change the font to something that has bold and italic variants.
Dave
You made my point by immediately having to name a font.
Ivo,
After you import to ID, is the font still Arial or has it changed to something else?
Dave
"The bold and italic encoding is still there and will spring into life if you change the font to something that has bold and italic variants". Again, I don't know what you mean. Fonts under Windows may be style linked; that is, the designer may specify that if the user chooses Garamond and then bolds it they will get Garamond Semibold, or they may decide to link it so that bolding Garamond gives you Garamond Bold. But however they are linked, the variant font styles have to be installed, and each variant has its own file (if it's TrueType or OpenType) or files (if it's Type 1). As George says, some apps will fake bold and itals if the actual font isn't installed, but these faux fonts are not to be recommended.
Under Windows, apps do not show the variant linked styles as a separate font (as Macs do). Some apps, like InDesign or FrameMaker, will show you the font and the styles installed in two adjoining dialogues, but that is not quite the same thing (although to all intents and purposes it is). Font styles that are not linked will show up as separate fonts (eg, Arial Black or Arial Narrow). When using Windows, you simply have to know what fonts you have installed and you have to know what apps will fake fonts so that you don't run into problems, but if you're using ID I really think you should have that basic level of understanding of font issues anyway.
Ivo
Can you apply the fonts in ID? That is, is it simply a question of importing the file with local formatting intact? Or can you not use the fonts at all?
Dominic
Dominic
What I meant was that ivo was discussing bold and italic without reference to font. He mentioned Arial in his Word documents but didn't say what he was getting in InDesign (he since has). If the font was being converted to something on input that doesn't have bold and italic then that would explain the behavior he was observing.
We seem to have moved on.
It sounds as though Ivo is now able to assign bold and italic in Indesign but still not able to import them in a Word document.
This is mysterious. While there are some problems in this area (usually caused by a failure to understand faux fonts but sometimes caused by not understanding the frailty of local styling when applying paragraph styles after import), I've never heard of a case where bold and italics were lost in the way that Ivo is describing.
Possibily the problem has to do with duplicate fonts. InDesign might have its own Arial installed in one of the Adobe font folders and that is interacting with the one that Ivo knows about and which Word is using in such a fashion as to cause this problem.
Dave
--Mike Nitabach
Unfortunately, the two people who've taken most interest in your thread are Dominic who doesn't do Word imports and me who does them on a Mac.
It seems you've encountered a weird bug with a particular version of Word on a particular OS.
I note from your topic intro that you don't mention which update of ID 2 you're using. If less than 2.0.2, I recommend updating to it.
Dave
Pity they aren't better known.
Also - use of "Style area width" in so-called Normal view. I have
introduced many people to this and it certainly seems to help in getting
Word users to understand a bit more about what they are doing. Mind,
most of them hate Normal view!
Rod