Re: Unicode and OpenType Fonts
- From: "S N" <uandme72@xxxxxxxxxxx>
- Date: Sat, 6 Mar 2010 16:53:00 +0530
When I am working on Vista (which is Unicode compliant) , atleast then I must be able to ensure that the font is Unicode.
"Character" <Char@xxxxxxxxxxxxxxxxx> wrote in message news:YJqkn.12658$Bs1.8646@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
S N wrote:.By unicode compliant I am referring to the standard characters which are used out of a particular font in such a way that the document is displayed correctly on any system.
Kindly clarify how to confirm if the font I am using to write the document is unicode or not.
You can never GUARANTEE that a document will display 'correctly' (meaning, I assume, that it appears exactly as it looked on the creator's system). It's more important that applications (including browsers) be unicode compliant than fonts.
This page from the Unicode consortium explains it:
http://unicode.org/faq/font_keyboard.html
If both parties have the same application, the same font, the same level of language support, and maybe even the same operating environment, then it should appear correctly. It doesn't matter what the font's level of Unicode support is. Note that the same operating environment even extends to printers, printer drivers, and display devices and settings.
There is no set of 'standard characters'. NO font supports all the possible characters, particularly when you get to ideographic languages.
= Character
"Character" <Char@xxxxxxxxxxxxxxxxx> wrote in message news:h4bkn.31767$Up1.19375@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
S N wrote:
Are all OpenType Fonts Unicode compliant? Or is it the other way around- All unicode fonts are opentype?
Neither. They are completely independent.
How do we check if a particular font is unicode compliant or not?
Depends on what you mean by 'unicode compliant'.
In some fonts all of the glyphs are unicoded. That does not mean that they have the CORRECT unicodes - where 'correct' means that that the character represented by the glyph has an appropriate name, that name corresponds to the unicode, and it's the right shape for that character.
In some fonts, many glyphs are not unicoded at all. At least hrough Windows Vista, those glyphs couldn't be seen with such utilities as Character Map, and couldn't be used in MS applications. They COULD be seen and used in most Adobe applications.
It's complicated!
- Character
- References:
- Unicode and OpenType Fonts
- From: S N
- Re: Unicode and OpenType Fonts
- From: Character
- Re: Unicode and OpenType Fonts
- From: S N
- Re: Unicode and OpenType Fonts
- From: Character
- Unicode and OpenType Fonts
- Prev by Date: Re: Unicode and OpenType Fonts
- Next by Date: Re: Unicode and OpenType Fonts
- Previous by thread: Re: Unicode and OpenType Fonts
- Next by thread: Re: Unicode and OpenType Fonts
- Index(es):
Relevant Pages
|