|
Developing OpenType Fonts
for Gujarati Script:
Appendices
Features are encoded according to both a designated script and language system.
Currently most shaping engine implementations only support the "default"
language system for each script. However, font developers may want to build
language specific features which are supported in other applications and will be
supported in future Microsoft OpenType implementations.
NOTE: It is strongly recommended to include the "dflt"
language tag in all OpenType fonts because it defines the basic script handling
for a font. The "dflt" language system is used as the default if no other
language specific features are defined, or if the application does not support that
particular language. If the "dflt" tag is not present for the script being
used, the font may not work in some applications.
The following table lists the registered tag names for script and language systems.
Note for new Indic shaping implementation “guj2” is used (old-behavior
implementations used “gujr”).
|
Registered tags for the Gujarati script
|
Registered tags for Gujarati language systems
|
|
Script tag
|
Script
|
Language system tag
|
Language
|
|
"gjr2"
|
Gujarati
|
"dflt"
|
*default script handling
|
|
|
|
"GUJ "
|
Gujarati
|
Note: both the script and language tags are case sensitive (script tags should be
lowercase, language tags are all caps) and must contain four characters (ie. you
must add a space to the three character language tags).
introduction | shaping engine
| features | appendices
|