OpenType Glyphs

Hi, I have a problem with my Glyphs in Pages. They show in Special Characters, but they don't actually end up on a page. What's up with that?? What can I do?
Thanks,
Marc

A little warning message comes up at the bottom saying that this is a glyph variant, but it doesn't say how to get around this. I just want a way to get certain ligatures that happen to be glyph variants. Any ideas?
TrueType simple does not support substitution (for reshaping, reordering). In other words, no glyph variants, only simple one character to one glyph shaping in the CMAP Character Map. Apple's extensions to TrueType (marketed as GX, TrueType 2, Apple Advanced Typography) and Microsoft's extensions to TrueType (marketed as TrueType Open, OpenType) support glyph variants (for reshaping, reordering).
Apple introduced a hack for direct drawing of glyph variants in the Apple Glyph Access Protocol for SFNT-housed font data (TrueType simple, AAT, OT). The hack lets you open the Glyph Catalogue in the Character Palette, insert your cursor in your copy, and click a GID Glyph Identifier or click Insert with Font for a glyph variant that is not drawn by a character code in the CMAP; glyphs drawn from characters in the CMAP have UTF16 and UTF8 short character identifiers as well as a GID.
One would like to think that Apple's text group correctly inserted both the character information and the imageable composition, but Apple's text group inserts REPLACEMENT CHARACTER (UTF16 FFFD, UTF8 EF BF BD) instead of decomposing the Glyph Identifier into the input of character information and then inserting the input of character information. So, using the Glyph Catalogue chaotifies the input of character information.
Adobe and Microsoft have a somewhat similar problem. In developing TrueType Open and OpenType, it was decided that application software should be able to override the drawing intents (feature selectors, rendering intents) defined in the intelligent font model. Since font software creators want to guarantee that font software customers can draw the glyphs they have paid for, Adobe and Heidelberg went on to provide PUA Private Use Area drawing for glyph variants.
This mess has been elevated to standards tracks as well as to the European Federation of National Institutions for Language which reports to Members States and to the Commission.
/hh
Reference:
http://developer.apple.com/mac/library/technotes/tn2002/tn2079.html

Similar Messages

Weird Symbols in my Text! Help! (Unicode?)

So, InDesign has decided to change certain character combos into weird characters. When I copy them out, they show up right in every other program - but they print and export wrong (otherwise I wouldn't care too much).
il = S with a v mark on top (I don't even know how to make it with the keyboard, or what it's called.)
io = Ú
There may be more that I haven't come across yet.
It's done this before, but I don't remember how I fixed it. It had something to do with changing to or from some kind of Unicode, I think.
Working in Snow Leopard, CS6 with Cloud.
Thanks! -T
EDIT: It doesn't do it in certain boxes, but I have no idea why some and not others.
EDIT 2: FIXED! Yay for corrupt fonts! (/sarcasm) Deactivating and then reactivating the trouble fonts fixed the problem.
It's still an InDesign bug though, since it DOESN'T affect any of my other programs. Omg. That was not cool to happen on deadline.

Glad you could get it to work again! Nothing like a good deadline to encounter such problems.
Here is a bit of background information:
A font consists of 'regular' characters (which you can type in from a keyboard; those are indeed Unicode characters), 'special' characters (ligatures, Real Small Caps, Oldstyle numbering, etc., which typically are not valid Unicode characters), and a list of commands which say "if these two character go in, replace them by this single other one instead". That list of commands specifies OpenType ligatures -- and it doesn't really work on characters, but on glyphs instead. A 'character' has a Unicode value, but a 'glyph' may not have one -- it's just an index in the list of all individual drawings in the font, specifying the nth glyph in there.
When all's well, this is not something you'd ordinarily notice. InDesign keeps a list of all fonts, and of all characters and glyphs in all of these fonts, and its OpenType Glyph relations (which, as you may deduce, are only valid for the font they appear in -- some fonts have more "glyphs" than others, and the Glyph Order varies wildly from one font to another, as you can see in the Glyphs Panel when sorted on "GID" (= "Glyph ID")).
What happened with your system is that presumably InDesign got the list of 'glyphs' from one file, but OpenType features from another file, with the exact same font name! So the perfectly normal operation "if you see glyph number 15 followed by glyph number 31, replace it with glyph number 65", meaning for that one font "replace "f" followed by "i" with the glyph "ﬁ"", got confused and instead came to mean "replace "i" followed by "l" with "Š"" (its proper name is "S Caron", with the Caron being this V accent).
So possibly you had more than one version of the same full font name installed (not the file name, but the internal full font name; "Times New Roman Italic", for example). One of the tricks to check this is to select this weirded-up text and disable Automatic Ligatures. If you see it revert to readable text, then this was the issue.
It's also possible something inside your system got confused -- InDesign, written by Adobe, accessed loads and loads of Extra Tricks in fonts that your typical other software doesn't care, or even know, about. That's why mishaps of this kind are typically picked up first by InDesign.
The Find Font dialog is your friend in tackling this issue. You can inspect the file paths of the troublesome fonts, and see if there is anything out of order; for example, you might suddenly see an unexpected file path. A tell-tale sign of Double Font Syndrome is when you physically remove that font file out of InDesign's view, and you can still see it works in InDesign -- but now with another file path in the Find Font dialog. At that point you only have to decide which one of the two was the "correct" font file ...

Disappearing panel content in CS3

InDesign CS3, Mac Pro 3GHz, OS X 10.5.2, 16 gig of Ram, plenty of HD space.
In my workspace I have my most-used panels grouped, i.e. Character-Paragraph-OpenType-Glyphs constitute one group and Swatches-Stroke-Layers-Pages constitute another.
Occasionally when I switch from one of the tabs in a group to another by clicking on the wanted tab (such as switching from Pages to Layers), the content of the selected panel will not be there. The tab is there with its name but the entire panel is blank. Restarting InDesign fixes this problem -- until the next time.
This is a problem that needs to be fixed.
I had this problem under OS 10.5.1 and hoped it would be fixed with the 10.5.2 update but it wasn't. I've read one or two posts which didn't describe this exact problem but are slightly similar and suggest it is a corrupted Prefs file. Having to replace it and rebuild my Prefs is worse than just restarting.
Has anyone else encountered this?

Same problem here, but more serious. My pages palette and color palette is blank whatever I do. Restart do not solve the problem, neither removing some of the prefs files (found a solution for CS that don't work in CS3 - adress: http://kb.adobe.com/selfservice/viewContent.do?externalId=330533).
Obviously this is an old problem that have been hanging around since CS and Adobe haven't fixed it yet. It's about time they find a solution for this problem.
I have this CS3 installed on an old G4 running 10.4.11.

Fraction replacement

Im not sure if I need a scripted solution but probably better to ask here first… So here goes… I have a catalogue coming up for this years updating and the client wants a few changes one of which is an increase of point size nothing drastic… Its all done with styles so some oversetting to handle not a problem. Where I could do with some guidance is fractions… The job as is was converted from Quark 2 years ago and done using postscript font… What I would like to do is swap this in favor of opentype… That should go OK I hope… While I am able to adjust my character styles it is not working with the fractions ( in Q there was a make fraction that did a 50% size and base line shift ) What Im looking for is to find all fractions down to 1/8's and replace with opentype glyphs… does this sound doable? Anyone already been there done it? Will I need script or will the GREP F&C in the GUI do this? TVM

It shouldn't take more than 7 find and replaces to do that. No need for GREP even...
FWIW, Dan Rodney has a script which does proper fractions:
http://www.danrodney.com/scripts/properfraction.html
Harbs

OpenType font won't work in PDF created from PM 7.0.1a file

Per my client's request, I had to purchase a lovely new OpenType font, AJenson Pro, for a book project I'm paging using PageMaker 7.0.1a in Windows XP. First it wouldn't print on my postscript HP laser printer, but downloading an updated printer driver from the HP web site easily fixed that problem. But I have done everything I can think of and I can't get the new font to appear in a .pdf created using Acrobat Distiller 5.0.5, which came bundled with PageMaker.
The font shows up in the finished .pdf as boxes with X marks in them instead of letters! I'm not trying to use anything but standard characters (no glyphs, etc.) in the font. I've been using PageMaker and creating .pdf files in Acrobat Distiller 5.0 for years and have had no problems until I got this new font. Adobe Type Manager shows that it is installed and it looks great on the screen.
I purchased the entire AJenson Pro font family from MyFonts.com, so I have bold, bold ital, etc. Their technical support couldn't suggest anything I hadn't already tried.
I'm planning on upgrading my PageMaker to InDesign soon, but I'll need a new computer to meet the minimum system requirements so I've been putting it off. I'm afraid to even download the free 30-day trial on my older computer. Any suggestions on how to get this OpenType font to work in a .pdf created using PM 7.0.1a and Acrobat Distiller 5.0, or do I have to upgrade to InDesign right away? I need to be able to create a .pdf so I can e-mail proofs to my client and eventually to send the finished book to a commercial printer. Thanks!

I have had this same problem myself with most Open Type fonts. It's very irritating, because it seems like most of the new fonts are being issued exclusively in Open Type.
I have developed a work-around, which you can attempt at your own risk.
Purchase the software FontCreator (I use FontCreator 5.6 Home Edition). It's not very expensive.
Open the problem font in FontCreator, and save it with a different name. In the process of saving it, the font will be converted to a TrueType font. Install the new version of the font. In my experience, you can then successfully use the font in Pagemaker, and convert it to a pdf.
This is not a perfect solution because there will be a *very* slight diminishment in the crispness of the lines of the font -- but this is only visible when the font is magnified to something like 6400% in Acrobat. It is not visible to the naked eye, or at least not to my naked eye.

Export to PDF in CS4 does not include TrueType glyphs

I created a Indesign CS4 document with Times (a Mac OS system font), inserted some glyphs such as 1/2 or 1/4, and exported it as a PDF. The glyphs however are not rendered properly - they appear as boxes.
If I print the file to my printer or print to a PDF, the qlyphs are included. Opentype fonts seem to be OK. I've also confirmed in Acrobat, that I can use the touch up tool to add the glyphs again, but clearly, this is not a desirable solution. This is not a problem in either Illustrator or Photoshop. This is also not a problem with Indesign CS3 which I still have on my system.
I think this started just after the Indesign Update 6.0.1 update, though I can't be certain.
Any ideas?

Same problem - but thanks for the idea. It's curious that when I use the touch text tool to change the properties, Acrobat "knows" the correct characters. I can select the characters, change the font, change it back to the original font and all is OK. I though Acrobat used some Illustrator libraries to do the touch up, but i I open the PDF in Illustrator, the bad characters get rendered as object - not text.
I guess it's time find a way to easily avoid the dfonts. Problem is dfonts show up as TrueType in the font selection menu. The only way I know to see for sure that it is a dfont is to look at its extension in finder.
I'm not real keen on using dfonts - I was archiving some old InDesign files as PDFs when I ran across the problem. It's kind of a pain to have to chase the font types/conversions through so many layers. Sigh.

Only western European glyphs appear in PDF export

Our application uses the .NET report viewer component to display reports that may contain any Unicode characters. When this report is exported (via the .NET report viewer) only western European and Arabic glyphs are displayed in the PDF file. Glyphs from other languages (Chinese, Japanese, Korean, Bengali, Malayalam, etc..) are rendered as empty boxes.
If this report is exported to any other format all of the glyphs can be displayed. The system where the report is viewed, exported, and where the exported report is viewed has the East Asian fonts and complex scripting installed. We can reproduce this on an XP SP3 machine and a Windows 2008 Server machine (these are the only systems we have tried).
If the report is exported to an excel document, and then the excel document is saved as a PDF then all glyphs can be rendered in the excel-generated PDF.
Looking at the PDF properties in Adobe Reader I see that the PDF generated by the Crystal Reports viewer contains only the font we specified in the report (Tahoma), while the excel-generated PDF includes several of the fonts to which the Tahoma OpenType font is linked.
This problem was observed using the Crystal Reports 2008 SP2 runtime.
How can we get the PDF export to include the linked fonts needed to render the non-western European glyphs?

The source of this problem is embedded fonts in PDF documents. The font we chose did not include all of the glyphs used by the report. Windows can be configured with linked and fallback fonts that can provide glyphs when a character is not included in a font, but PDF documents only use the glyphs embedded in them.
The solution was to use a different font. When our software generates a report it will first replace all of the fonts in the report with the font MS Shell Dlg2 is configured to use. This font always contains English glyphs and glyphs for the language of the operating system, which almost always contains all the characters in the report.

PDF/A Conversion Err :CIDset in subset font is incomplete & Character references .notdef glyphs

I was trying to convert some PDF documents to PDF/A-3b. Using Acrobat XI Pro on a Windows Vista PC, the conversion proceeded fine, but I noticed the size of the converted file increased from 1.91 Mb to 16.8 Mb (See spage usage audits below). I expected some increase in size due to the font embedding and such, but did not expect such a big jump. On Auditing the space usage, I noticed that the converted file had no embedded fonts, but the vast majority of space was being consumed by images. Turns out the "Convert to PDF/A-3b" profile in Preflight settings were set to convert all pages to images, if the regular conversion failed. I edited the profile to not do so, but fail on an error. This time when I passed the document through a "Convert to PDF/A-3b" pre-flight, it failed with the following errors.
CIDset in subset font is incomplete (font contains glyphs that are not listed). It appears to be referring to the Arial and TimesNewRoman fonts.
Character references .notdef glyph
How do I fix these errors? For the CIDset error, I noticed some folks in the InDesign forums mentioning you can locate the missing glyphs and then replace the fonts with other fonts in which these glyphs are present. I am wondering if this is the issue here and something similar can be done in Acrobat. As for the .notdef glyphs, I couldn't find anything. Any help would be much appreciated.
Thanks,
Ron
Note:
If I edit the conversion preflight profile to allow replacing the pages with images on regular conversion errors, the conversion goes through fine, but as shown below, there is a huge jump in size, which I would like to avoid. I have about 2GB worth of documents, and the conversion ends up using over 8 GB of space.
Regular PDF
Archival Ready PDF (PDF/A-3b)

What software are you using to do OCR?
Is there a way you can adjust what font is being used by the OCR software or use a different software for OCR? This is not a standard OpenType font or one the can be mapped to Unicode.
I'm not sure exactly how OCR software places fonts in PDFs. Does it show up in the PDF Properties under Fonts? If so, what is the name of the Font.
When you examine the Tagged text in the Tags Panel, if you open up a tag and look at the content does it make sense or is it nonsense (gobbledygook)?
While OCR text is not visible to the end user directly, it can be selected using the text tool and it is recognized by Acrobat for tagging purposes. The Assistive Technology, e.g., screen reader. will be reading from this text. So if it is not understandable you do not have an accessible file.
You would probably obtain better results using the Acrobat OCR feature, preferably on a Windows machine. It's been a while since I've exchanged files between Mac and Windows, and I wouldn't trust that the encodings would be the same without testing it.

[SOLVED] VIM not displaying many glyphs

I'm struggling to get the full glyph set to display in VIM. Particularly missed are the mathematical super- and sub-script. I've worked on the problem and tried various fixes for displaying UTF-8 characters without success.
(Code block bad form? Ok T. IMHO. There's that type of post where the OP doesn't know why something isn't working and they quote a dump truck of details, even though they're not sure what's relevant and what isn't. And the longer the quote, the harder it is to figure out what they're doing wrong. I didn't want to be that guy. I was hiding the verbosity, in the event my font problems are simpler than I've made it.)
1) Applied settings from these WIKI pages:
Fonts
Xterm
2) Apps I've installed
$ pacman -Qs font
local/dina-font 2.92-4
A monospace bitmap font, primarily aimed at programmers
local/fontconfig 2.11.1-1
A library for configuring and customizing font access
local/fontsproto 2.1.3-1
X11 font extension wire protocol
local/freetype2 2.5.3-2
TrueType font rendering library
local/gsfonts 1.0.7pre44-4
Standard Ghostscript Type1 fonts from URW
local/libfontenc 1.1.2-1
X11 font encoding library
local/libotf 0.9.13-2
OpenType Font library
local/libxfont 1.4.7-3
X11 font rasterisation library
local/libxft 2.3.2-1
FreeType-based font drawing library for X
local/t1lib 5.1.2-5
Library for generating character- and string-glyphs from Adobe Type 1 fonts
local/tamsyn-font 1.10-1
A monospaced bitmap font for the console and X11
local/terminus-font 4.39-1
Monospace bitmap font (for X11 and console)
local/ttf-bitstream-vera 1.10-10
Bitstream vera fonts
local/ttf-droid 20121017-3
General-purpose fonts released by Google as part of Android
local/xorg-bdftopcf 1.0.4-2 (xorg xorg-apps)
Convert X font from Bitmap Distribution Format to Portable Compiled Format
local/xorg-font-util 1.3.0-2 (xorg-fonts xorg)
X.Org font utilities
local/xorg-font-utils 7.6-4
Transitional package depending on xorg font utilities
local/xorg-fonts-100dpi 1.0.1-5 (xorg)
X.org 100dpi fonts
local/xorg-fonts-alias 1.0.3-1
X.org font alias files
local/xorg-fonts-encodings 1.0.4-4 (xorg-fonts xorg)
X.org font encoding files
local/xorg-fonts-misc 1.0.1-3
X.org misc fonts
local/xorg-fonts-type1 7.4-3
X.org Type1 fonts
local/xorg-mkfontdir 1.0.7-2 (xorg xorg-apps)
Create an index of X font files in a directory
local/xorg-mkfontscale 1.1.1-1 (xorg-apps xorg)
Create an index of scalable font files for X
3) A forum search found some common issues:
unicode symbols not working in my terminal
$ localectl
System Locale: LANG=en_US.UTF-8
LC_COLLATE=C
VC Keymap: US
X11 Layout: n/a
$ locale -a
C
en_US.utf8
POSIX
$ echo $TERM
xterm-256color
4) ~/.Xresources
! wiki.archlinux.org/.../Xterm
xterm*termName: xterm-256color
xterm*locale: true
xterm*saveLines: 4096
xterm*bellIsUrgent: false
xterm*VT100.geometry: 80x25
xterm*faceName: Droid:style=Regular:size=12
xterm*dynamicColors: true
xterm*utf8: 2
xterm*toolBar: false
5) ~/.xinitrc
# X11 Fonts
xset +fp /usr/share/fonts
Last edited by xtian (2014-07-27 14:43:23)

Linux fonts are a muddle. Consoles can only display 256 characters, maybe 512. You simply cannot display many texts in a console. To navigate through the font mess in X, you need some familiarity with fontconfig. Xft uses fontconfig to select fonts. Fontconfig documentation is not user-friendly.
Droid is a family of fonts. My installation of the Droid family includes 27 different fonts. The command fc-list will list fonts matching a pattern. I usually filter the output by piping through grep. To list the Droid fonts, file name first followed by the fontconfig name, I use:
$ fc-list | grep Droid
Your fc-match results for Droid are from fontconfig doing its best to give you a readable display. Fontconfig cannot find a matching font for the name 'Droid', so it falls back to a "safe" font, 'Bitstream Vera Sans'.
XTerm or UXTerm or URxvt
I have my locale correctly configured, I think. I do not see any real advantage for uxterm over xterm. In my X resources, I include the lines,
xterm*termName: xterm-256color
XTerm*locale: true
For good glyph coverage with xterm, I have found 'DejaVu Sans Mono' to be among the better fonts. If I truly need utf8 coverage, I use urxvt. Urxvt allows one to use a ladder of fonts. If the character is not found in the first font listed, urxvt will search through the other listed fonts until it finds a glyph that can be displayed.
urxvt*font: xft:DejaVu Sans Mono:style=Book:antialias=false:size=8, \
xft:WenQuanYi Bitmap Song:size=8, \
xft:FreeSerif:style=Regular, \
xft:unifont:style=Medium:antialias=false
Here's a screenshot with three xterms using Droid, DejaVu Sans Mono, and Liberation Mono, plus one urxvt using the fonts in the code above. They all show the same portion of Markus Kuhn's utf8 test text.

Why are there many more glyphs available in Illustrator CS4 than Indesign CS4?

I am in the process of converting a document from Illustrator to InDesign.
Many of the glyphs and ligatures in Illustrator aren't available in Indesign for the same font, Bickham Script Pro.
I checked that all of the opentype settings between the two programs are the same.
I'm currently using suitcase, but I've tried installing font explorer and I get the same problem.
I'm out of ideas... any suggestions?

Since you have not received a reply here, I would suggest posting in the InDesign forum:
http://forums.adobe.com/community/indesign/indesign_general?view=discussions

Need Emergency Help! - Why don't my Illustrator CS6 Glyphs work?

They just do not work; I have tried using them every way I can think of and they will not work!
I have deadlines and feel completely frantic...cannot find an answer anywhere!

I'm using Illustrator CS6 v16.0.4 on Mac OSX 10.9.1. The font is Kohinoor Devanagiri, an opentype font. When I double click on the desired glyph from the glyphs panel, it doesn't insert the actual glyph but instead inserts the conjunct consonants that combine to create that glyph. Previously, I was able to insert this using Illustrator CS5, but after having upgraded to CS6, I'm having this issue.
See attached screenshot - the highlighted glyph in the glyphs panel is not the open appearing in the document, but its the individual characters that combine to create that, that appears. The opentype panel doesn't allow me to change anything as it appears grayed out when I select the text in the document.
What could be the issue?

Crénage fautif en Adobe MinionPro avec glyphes localisés

Bonjour,
J'utilise Adobe MinionPro inclus en Adobe Acrobat Reader v. 9.4 sur Ubuntu 10.10. D'abord je voudrais remercier Adobe d'avoir rendu gratuiciel cette merveilleuse police (d'autant plus qu'elle supporte plein de fonctions OpenType! ). Donc passons à l'OpenType, justement. Avec TexWorks 0.2.3 marchant en dessus de TexLive 2010 je compose des documents en format XeLaTex. Quand je travaille avec les variantes localisées en serbe (activées à travers la fonction OpenType locl) je me trouve face à un cas de crénage fautif particulièrement évident. Il se manifeste à l'occasion de la rencontre des caractères u+0423 (CYRILLIC CAPITAL LETTER U) et u+0431 (CYRILLIC SMALL LETTER BE). Comme vous aller voir dans la pièce jointe le problème ne se vérifie qu'en cas de glyphe localisé serbe, le glyphe standard russe ne présentant pas de problèmes de crénage.
Je vous remercie à l'avance de votre collaboration.

Je viens de poster ma demande dans le forum anglais de Typographie Adobe: est-il raisonnable de s'attendre à ce qu'une version patchée de MinionPro 2004 soit rendue disponible pour le téléchargement? Cela m'intéresse car chez la Wikipédia Serbe nous voudrions profiter des fonctions OpenType supportées par le nouveau navigateur sortant bientôt Firefox 4 pour visualiser correctement les glyphes serbes sur écran, ce support manquant jusqu'à aujourd'hui. MinionPro serait sans aucune doute la police à choisir pour la modalité "version imprimable" si seulement il n'y avait ce fâcheux défaut-ci.
P.S.
Au cas où vous connaitriez le serbe, voilà la discussion chez la Wikipédia serbe à propos des glyphes localisés.
Bien plus probable que vous connaissiez l'anglais, donc voilà la discussion chez le forum anglais Typographie d'Adobe.

On Glyph palette name shows as unassigned

Hey guys, I've added some glyphs to one or our existing fonts and on the glyphs palette in InDesign CS3 that glyph's name shows as "unassigned" when I mouse over the glyph.
Typically I use the Adobe glyph list (http://www.adobe.com/devnet-archive/opentype/archives/glyphlist.txt) to name my glyphs, but this particular glyph isn't in that list.
Does anyone know whether the "unassigned" just means that InDesign doesn't recognize it because it's not in Adobe's list?
Thanks!

Hi Steve,
Sorry, I some how managed to miss your post! Thanks for taking interest.
We develop and maintain fonts for a couple of clients and they recently came up with some new Old English stuff that just isn't anywhere.
Ken

Opentype features problem

Hi,
I am having some difficulty with getting two Opentype layout features to
work in Indesign 1.5 and Photoshop 6. The liga feature works perfectly, but
dlig and clig don't (though they preview correctly in Fontlab 4.5.1). I have
generated the font as a CFF-flavoured OTF font using either Macintosh,
Windows ANSI or FL's standard encoding but the problem remains. Yet all the
glyphs are available under Indesign's "insert character" dialog box. When I
opened the generated font in Fontlab, the features work as expected. Putting
all the lookups in the liga feature didn't solve the problem either (and
every glyph has a Unicode number attached to it). Do the alternate glyphs
need to be named according to their Unicode index?
I am using MacOS 9.2 with ATM Deluxe 4.6.1.
Regards,
David Philpott
Feature files:
feature clig{ # Contextual Ligatures
# Latin
sub T h by Thlig;
sub T T by TTlig;
sub T E by TElig;
sub C O by CO;
sub C I by CI;
sub L A by LA;
} clig;
feature dlig{ # Discretionary Ligatures
# Latin
sub c t by ct;
sub s t by st;
sub g i by gi;
sub g n by gn;
sub g r by gt;
sub g t by gt;
sub g y by gy;
sub t i by ti;
sub t r by tr;
sub t t by tt;
sub t u by tu;
sub t y by ty;
} dlig;

Thank you for your reply. Regards, David > From: "Thomas Phinney" <[email protected]> > Newsgroups: adobe.opentype.developers.fdk > Date: Sat, 22 Feb 2003 15:40:22 -0800 > Subject: Re: Opentype features problem > > The problem is simply that InDesign 1.x and Photoshop 6 (and 7) do not support > those features. InDesign 2.0 does support these features, however. > > To find out more about what features are supported by which application > versions, read Adobe's User Guide for OpenType, which can be downloaded from > <a href=http://www.adobe.com/type/opentype> > > Regards, > > T

MinionPro v. 2004 and Serbian glyphs for Wikipedia

At the Serbian Wikipedia we are thinking about an OpenType solution to correctly display Serbian glyphs instead of the standard/Russian ones. We are scanning the Web for fonts containing Serbian glyphs and I personally think MinionPro should be our choice. But the 2004 version (the one included with Adobe Reader) displays an annoying kerning flaw whenever the characters u+0423 CYRILLIC CAPITAL LETTER U and u+0431 CYRILLIC SMALL LETTER BE meet each other. I don't know how to insert a .pdf here in order to make you understand better the matter, so I limit myself to tell you that CYRILLIC SMALL LETTER BE anomalously collides with CYRILLIC CAPITAL LETTER U. Please notice that the kerning flaw only happens with the localized Serbian form, never with the standard Russian one.
Now, people told me I can manually fix the kerning, but that is definitely not the solution for usage in Wikipedia where as less user interaction as possible is required. People also told me that there is a kind of new technology for embedding the font that enables on screen visualization without actual installation, but this too is inappropriate for Wikipedia because people are expected to print articles and possibly to store them.
So, I am not asking you to release the 2010 version as freeware, but could you just patch the 2004 version and make it available for download?
Thank you in advance for your collaboration.
P.S.
Just in case you knew Serbian here is the link for the topic: http://sr.wikipedia.org/wiki/%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D0%B5%D0%B4%D0%B8%D1%98%D0%B0: %D0%A2%D1%80%D0%B3/%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D0%BE%D0%BB%D0%B8%D1%82%D0%B8%D0%BA%D0%B 0#.D0.A1.D1.80.D0.BF.D1.81.D0.BA.D0.B8_.D0.B3.D0.BB.D0.B8.D1.84.D0.BE.D0.B2.D0.B8_.D0.BD.D 0.B0_.D0.92.D0.B8.D0.BA.D0.B8.D0.BF.D0.B5.D0.B4.D0.B8.D1.98.D0.B8

This seems to indicate that the term +glyph variant+ is as much political as technical.
Access to Arial Unicode MS Devanagari is blocked because if it were not, apps might use it and display garbage instead the correct Devanagari they produce when using Apple's font.
This might not matter if Devanagari MT worked in Word 2008. To get round this problem, I've downloaded a free font, which works fine in Word.
What font is that? No Unicode font will display correct Devanagari in Word for Mac, although that might not be obvious if you do not know how to read this script.
http://m10lmac.blogspot.com/2007/04/pitfalls-of-working-with-complex.html
Regarding the other point about Adobe Garamond Expert, yes, this is a Type 1 font I bought about 10 years ago. As you suggest, I'll explore this issue further on the MS forums. I did install FontForge, as you suggest, and created a new font with clean oldstyle glyphs. However, once again, Word did not recognize this font in either otf or ttf format, even though other applications did.
Check to make sure you have both the font suitcase and the outline printer fonts installed for AGE.
I'm puzzled that Word would not recognize the .ttf/.otf fonts you made.

OpenType Glyphs

Similar Messages

Maybe you are looking for