OpenType ligatures support in Word 2010

[siggy]

We're testing our OpenType fonts in the new Word 2010 (technical preview). I have set the OpenType Features on the Advanced tab for Font options to use "All" Ligatures and to "Use Contextual Alternates." The font sample in that window shows contextual alternates, but the document itself still does not use contextual alternates. This happens in Windows Vista and Windows 7.

Is this a bug? Is this feature just not functional in the Technical Preview? Is it because our fonts are not  signed with a secure digital certificate?

Thanks!

[Sergey Malkin (Microsoft)]

This should work.

Does this hapen just with your font (on the same text)? You can try Cambria or Gabriola, fonts coming with Office.

Does it happen with all or just some ligatures/alternates? Are your contextual alternates lookups look across word boundaries? Word has known problem of breaking text into smaller runs in unpredictable places, but if your context are fairly simple, you should see shaping ok.

Thanks,
Sergey

[siggy]

Hi Sergey:

None of the contextual alternates were used -- we created several fonts. What alternates should I look for in Cambria or Gabriola? Can you give me an example of a word or phrase that should display contextual alternates in those fonts?

The lookups are within each word. They work fine in Word for Mac 2008.

Thanks!

[Sergey Malkin (Microsoft)]

What script/language/feature tags you are using and what characters you are testing with?

[siggy]

VOLT tags are <latn>/<dflt>/<clig>, using Substitution lookups on glyphs a-z. These fonts also tested successfully in Publisher 2007 using right-to-left text direction.

Thanks!

[siggy]

Follow-up posting on this topic ---

Further testing was needed outside this forum to determine the problem. Word 2010 requires OpenType fonts to have a DSIG for ligatures to work in the font.

For those of you who don't know, a digital signature (DSIG) can only be inserted in a font if you have a current Class 3 code authentication certificate issued by a company such as VeriSign or Comodo.

Microsoft offers a free font-signing tool (the tool only, not the certificate). FontLab Studio also can sign fonts if you have a current certificate to use.

http://www.microsoft.com/typography/developers/dsig/dsig.aspx

Thanks again, Sergey and Simon!

[astype]

"Word 2010 requires OpenType fonts to have a DSIG for ligatures to work in the font. "

I don't think this is the way the things should go. I see a lot of future customers blaming little foundries why the fonts not work like it should.

[Si Daniels (Microsoft)]

Actually I think adding the dsig was a work around to a specific issue in GDI related to it not identifying your fonts as an OpenType font. I don't think dsig is necessary for all fonts.

[Sergey Malkin (Microsoft)]

My current understanding of the issue is that DSIG will be requred for TrueType fonts to shape. OpenType CFF fonts should work fine without it.

And it seems this will still be true for final release of Office2010.

Thanks,
Sergey

[tiro_hudson]

Ugh! So do Word programmers bother to consult with other groups in MS about how to implement things like font support? Or do they just make it up as they go along?

[minorityfonts]

"My current understanding of the issue is that DSIG will be requred for TrueType fonts to shape"

Does this mean Word 2010 won't work with all Arabic and Indic and every other complex-script TT-style OpenType font, unless they incorporate DSIG? Or will features like isol, init, medi, fina, ccmp, rlig, mark, mkmk - and the several Indic features - still work? So far I have not encountered a single complex-script font with a DSIG! Most of the fonts suitable for languages beyond the major world languages are produced by individual users or small companies in obscure countries, none of whom have or are likely to obtain a certificate.

[Sergey Malkin (Microsoft)]

Does this mean Word 2010 won't work with all Arabic and Indic and every other complex-script TT-style OpenType font, unless they incorporate DSIG?

Complex script fonts should work as before. DSIG requirement is for fonts that want to shape "simple" scripts which did not apply OpenType features before, like Latin. Again,this is my understanding of the problem.

Thanks,
Sergey

[Arno Enslin]

And does the DSIG table have to contain a valid digital signature? Or can it just be a bit hex code? As far as I know, you have to pay for the certificate. It would be a shame, if Office 2010 requires fonts with valid digital signatures! It is easy to merge the DSIG table into a font with TTX.

[Tags:]

Jump to: Please select a destination: ----------------------------- News and announcements ----------------------------- => Announcements from the forum’s moderators => News from the font industry ----------------------------- Type design and font technology ----------------------------- => Principles of type design => OpenType Layout feature development => Hinting => Font Formats and OpenType => Web font embedding => Font licensing ===> Electronic EULA Abstract (EEULAA) ----------------------------- Education and collaboration ----------------------------- => Work: Offers => Work: Looking for => Education: Offers => Education: Looking for => Typographic Events and Conferences ----------------------------- FontLab products ----------------------------- => News from FontLab => FontLab Studio ===> FontLab Studio Problems ===> FontLab Studio Tips and Tricks ===> FontLab Studio Wish List ===> FontLab Studio Public Preview => Fontographer ===> Fontographer Problems ===> Fontographer Wish List => TypeTool => AsiaFont Studio => TransType => ScanFont => SigMaker => Other Products ----------------------------- Photofont products ----------------------------- => BitFonter => Photofont WebReady => Photofont Start => Photofont ID => Photofont QX => The Photofont technology ----------------------------- Adobe Type products ----------------------------- => Adobe FDK for OpenType (AFDKO) ----------------------------- Apple Font products ----------------------------- => Apple Font Tools ----------------------------- Microsoft Typography products ----------------------------- => Microsoft Font Validator => Microsoft Visual OpenType Layout Tool (VOLT) => Microsoft Web Embedding Fonts Tool (WEFT) => Microsoft Visual TrueType (VTT) ----------------------------- Other products and Python scripting ----------------------------- => Python scripting => FontTools/TTX => Other font-related tools ----------------------------- Special interest groups ----------------------------- => SBL Fonts ===> SBL Hebrew ===> SBL Greek ===> SBL BibLit ----------------------------- FAQ and TechNotes ----------------------------- => OpenType Layout feature development FAQ and TechNotes => Hinting FAQ and TechNotes => Font Formats and OpenType FAQ and TechNotes => Web font embedding FAQ and TechNotes => Font licensing FAQ and TechNotes => FontLab Studio FAQ and TechNotes => Fontographer FAQ and TechNotes => TypeTool FAQ and TechNotes => AsiaFont Studio FAQ and TechNotes => TransType FAQ and TechNotes => ScanFont FAQ and TechNotes => SigMaker FAQ and TechNotes => BitFonter FAQ and TechNotes => Photofont WebReady FAQ and TechNotes => Photofont Start FAQ and TechNotes => Photofont ID FAQ and TechNotes => Photofont QX FAQ and TechNotes ----------------------------- Archive (MSN Groups) ----------------------------- => Archive: Old FontLab forum ===> Archive: FontLab Tips and Tricks ===> Archive: FontLab Bugs and Problems ===> Archive: FontLab Wish List ===> Archive: FontLab Announcements => Archive: Old Microsoft Font Validator group => Archive: Old Microsoft VOLT group => Archive: Old Microsoft VTT group ===> Archive: VTT Downloads ===> Archive: VTT Support ===> Archive: VTT Suggestions => Archive: Old Microsoft WEFT group ===> Archive: WEFT III ===> Archive: EOT for Email => Archive: Old SBL Fonts group ===> Archive: SBL Hebrew ===> Archive: SBL Greek ----------------------------- Various ----------------------------- => fontlab.com — the FontLab website => forum.fontlab.com — this forum => Other Topics