M
Michal_Macura
Version: 2008
Operating System: Mac OS X 10.6 (Snow Leopard)
Processor: Intel
In a blank document (as well as in documents created elsewhere) with Cambria as the default font for Body the following happens:
1) Times New Roman always overrides the default font for normal text immediately when I create a new document. So when I start writing, I write in Times New Roman instead of the default font, i.e. Cambria.
2) Selecting other fonts does not work (neither from the Formatting Palette, nor from anywhere else) - the font for typing always goes back to Times New Roman immediately (I even tried disabling Times New Roman in Font Book - without success). The only way I am able to actually change font for text is to type something in Times New Roman, then select what I typed and change the font manually for the selection. However, even when I do that and continue writing on the same line, the font immediately goes back to Times New Roman.
I am sure this must be a bug in the recent version or something caused by incompatibility with Snow Leopard. I would appreciate any help I can get.
Operating System: Mac OS X 10.6 (Snow Leopard)
Processor: Intel
In a blank document (as well as in documents created elsewhere) with Cambria as the default font for Body the following happens:
1) Times New Roman always overrides the default font for normal text immediately when I create a new document. So when I start writing, I write in Times New Roman instead of the default font, i.e. Cambria.
2) Selecting other fonts does not work (neither from the Formatting Palette, nor from anywhere else) - the font for typing always goes back to Times New Roman immediately (I even tried disabling Times New Roman in Font Book - without success). The only way I am able to actually change font for text is to type something in Times New Roman, then select what I typed and change the font manually for the selection. However, even when I do that and continue writing on the same line, the font immediately goes back to Times New Roman.
I am sure this must be a bug in the recent version or something caused by incompatibility with Snow Leopard. I would appreciate any help I can get.