yo_soy_tu_padre007 wrote:
1) Why sometimes erase all the word local formats and sometimes does not?
When placing, you can select to either preserve 'local' formatting or remove it. Local formatting is "anything done without using a style", just as it is in InDesign. As Ellis says, check your import settings.
In addition, even if you 'preserve' local formatting, it's very easy to accidentally remove it in InDesign when you apply another style. If common attributes such as bold and italics are not applied through character styles in the original Word document, you should preserve them yourself by doing that in InDesign.
2) Is it a problem using .doc, .docx or .rtf to save text files an import?
Yes, on all three. There is no single format that InDesign works best with. If a Word document causes me trouble, I try the other options until I get not exactly the "best" result, but more accurately a "least bad".
3) Is the problem that you work with .TTF fonts (like Arial, Times, Courier) from word and on ID you use OpenType Fonts?
Not in the least. Actually, you can use TTF fonts as well as OTF fonts with InDesign. The import is totally indifferent of the fonts used -- it doesn't matter what you used in Word, you'll get the same fonts in the imported text. That is, except when it's bitmap fonts, which you cannot use in InDesign, or when the author italicized or bolded text in Word where the actual Bold or Italic font doesn't exist. But even then, InDesign will happily import the text -- it will just have an 'unavailable' font assigned to it, and you'll be notified of that.
4) What is the NON-FAIL way to do an excellent import? from Microsoft Word to ID
I would like to know the answer to that as well. The import filter has problems with tables, footnotes, endnotes, automatic references, and new page codes, for .docx, .rtf, and .doc files.