| View previous topic :: View next topic |
| Author |
Message |
tarenruof
Agent
Joined: Mar 29, 2009
Posts: 13
|
 Posted: Sun Mar 29, 2009 2:13 pm Post subject: Zapf Dingbats font displays as Arial |
|
| Even with Zapf Dinbats font selected, caracters are displayed on screen as Arial. |
|
| Back to top |
|
 |
yoxi
Cipher
Joined: Sep 07, 2004
Posts: 1799
Location: Dawlish, Devon
|
| Posted: Sun Mar 29, 2009 3:06 pm Post subject: |
|
I can replicate this behaviour in NEoOffice v3 intel 10.5.6 - seems to be deep font substitution going on as even in the dropdown list, it's in Arial (or something).
- padmavyuha |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Sun Mar 29, 2009 3:52 pm Post subject: Re: Zapf Dingbats font displays as Arial |
|
| tarenruof wrote: | | Even with Zapf Dinbats font selected, caracters are displayed on screen as Arial. |
This is normal. Zapf Dingbats has no glyphs that match any Western European characters. For example, Zapf Dingbats has no glyphs for any character between A - Z or a - z or 0 - 9 so when you type such characters, Mac OS X tells NeoOffice that Zapf Dingbats cannot render that character. So, NeoOffice uses a font that can render those characters. That font is called the "fallback font". In your case, the fallback font is Arial.
If you are trying to enter Zapf Dingbat symbols instead of characters, Apple has an article that explains how to enter special, non-character symbols at the following URL:
http://support.apple.com/kb/HT1518
Do the steps in Apple's article allow you to enter Zapf Dingbat symbols.
Edit: If you are used to using Microsoft Word because while, Microsoft Word will use a proprietary mechanism to map characters to non-standard glyph numbers when a symbol font is used, NeoOffice conforms to the behavior that Apple applications such as TextEdit use and do font replacement if a match glyph is not available for the character that you typed.
Edit 2: Replace the URL with the correct URL from Smokey's post
Patrick
Last edited by pluby on Sun Mar 29, 2009 7:44 pm; edited 1 time in total |
|
| Back to top |
|
|
sardisson
Town Crier
Joined: Feb 01, 2004
Posts: 4588
|
| Posted: Sun Mar 29, 2009 7:34 pm Post subject: |
|
Er, I think Patrick meant to point you to this document (though Apple made it hard enough to find  ).
If you want to use the keyboard and continue to "type" the dingbat characters as non-Unicode apps do, you need a special keyboard layout. I have the old Apple keyboard layouts to support this here.
Smokey
_________________
"[...] whether the duck drinks hot chocolate or coffee is irrelevant." -- ovvldc and sardisson in the NeoWiki |
|
| Back to top |
|
|
PGAGA
Captain
Joined: Jan 22, 2009
Posts: 50
|
| Posted: Mon Mar 30, 2009 9:51 am Post subject: |
|
March 30 2009
This is one of the differences between NO and OOo. With OOo choosing Zapf Dingbat with Insert>Special Character switches to gliffs automatically and permits insertion of Dingbats. With NO one has to select Dingbats when one switches to Zapf Dingbat before one can insert the Dingbats.
I am assuming that the NO method is conformity to OS X rather than a failure of OOo code implentation.
Phil |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Mon Mar 30, 2009 10:06 am Post subject: |
|
| PGAGA wrote: | | I am assuming that the NO method is conformity to OS X rather than a failure of OOo code implentation. |
This is correct. The OpenOffice.org Aqua code tries to emulate the Microsoft Office behavior (which is really a Windows behavior). In contrast, NeoOffice has for several years now followed the behavior in the Apple's applications.
Patrick |
|
| Back to top |
|
|
|
