All articles 1259

I am trying to generate diacritic glyphs like agrave, etc. but for some reason when I click generate glyph from the anchors preview window it is only generating for instance the a glyph and not the full agrave with the diacritcal mark. My anchors are named correctly and everything is perfectly fine within the anchors preview window...Never had this happen so Im kinda of confused. Tried generating the glyphs a few other ways same solution(or lack there of really.)

Any ideas?

Thanks,
David

Mac OS 10.4 now translates some OpenType features into its AAT environment but not all of them. Notably contextual features are missing. So any .otf or .ttf with OT enhancement for languages such as Arabic are still unusable on Tiger because contextual features are vital for such languages.
I made some fonts that have both OT and AAT features to be compatible with any environment. Now with Tiger, the presence of OT features in these fonts results in partial translation of those features in AAT and ignoring the pre-existing AAT features of the font - including their contextual AAT features!
If you plan to add AAT to an OT font, beware of this problem. It will be useless.
All Apple has to do is to add a command in its text engine that 'if AAT detected in the font, ignore OT'. I know it's easier said than done but this shouldn't be too complicated.

Is there anything odd in the calt list of Vista/Windows 7's font "Segoe Script"? I was alerted today by an InDesign user that contextual alternates do work for Latin script, but don't appear to get activated for Cyrillic text.

I examined the OTF tables, and, sure enough, the calt tables for Latin are only defined in the Latin Script part, and the Cyrillic Script section has its own calt list. Nothing out of the ordinary, I presume.

Theoretically, the used program ought to recognize a series of Cyrillic characters and automatically switch over to the Cyrillic section -- right? I think that was the entire purpose of the Scripts sections. Could it be an error in InDesign CS4? Or am I misinterpreting the use of the Script tags and how they would work in practice?

To facilitate neat left-column edges in Polytonic setting, it makes sense to build-in the "hang" by giving the accented caps the same metrics as their non-accented counterparts.

However, this takes up a lot of the space preceding a capitalized word in running text.
Therefore, a contextual adjustment should be applied. But what?

  1. Substitute a wider space (eg en-space character) prior to accented caps.
  2. Add positive kerning between regular space and accented cap.

Some applications, of course, ignore the space character, and substitute a layout-level value. (e.g. CCI newspaper pagination system). How much of an issue is that for setting Polytonic -- can one assume that the users of Opentype Polytonic fonts will have Quark 7 and InDesign CS?

Hi.
I have this small problem in font production.
I have normal and stencil version of the font.
They share the same metrics and kerning.

in indesign they are nicely over each other.
But problem is, when I print it to pdf from indesign, the fonts doesnt have the same position.
Please look at attachment.

I already set alighnment zones and basic hinting (standard stems) but it didnt help.

Thanks a lot for suggestions!

Jan

| Attachment | Size | | --- | --- | | dezen_-_indesign.png | 51.04 KB | | dezen_-_pdf.png | 82.29 KB |

I'm adding Opentype features to a font for the first time. I have already added two sets of alternates and a set of discretionary ligatures. Most of the ligatures I want are made and I would like to add accents on some of them using anchors. Here's an example:

When I look at the preview, everything seems to be ok, but when I'm trying to generate composite, it doesn't work as you can see in the next picture.

The accents are positioned correctly but the ligature are replaced by both glyphs.

When I'm trying to positioned the accent on the second letter within the ligature. The preview is still correct:

When I generate composite, the ligature is still replaced by both glyphs, the position of the accent is not above the right part of the ligature and is too low:

Anyone knows what I'm doing wrong
Thanks

Raphael

This Belgian company, Alt-Soft, has a new software for font edition and conversion, called FTM (Font Type Master). It's a simple app, not really good for drawing or creating new fonts, there's not even a good metrics tool.

But this app has a very, very interesting feature. Maybe I shouldn't post this here, but... it opens fonts from PDFs! Using the demo, I was able to open a font from a PDF file. Quick and easy. No kerning though. I just wasn't able to save the font because it is a demo (no saving allowed).

I will not post a link to this, but I think interested people will find it.

Personally, I think this feature should be removed from this app. But, what do others think about it?

Hi there,
I have a major problem with InDesign CS2 not recognising kerning, neither class based nor classic kern table. InDesign CS1 works perfectly fine. I am generating OT TTF flavoured with all the necassary boxes ticked in FL 5.0.2 (see pic)
I know of at least another 3 people experiencing the same problem.

Can anybody help?

Much appreciated,
vik

| Attachment | Size | | --- | --- | | Picture 2.png | 71.32 KB |

The SVG font format has support for kerning via the hkern element. Is kerning in SVG fonts supported by any web browser?

I'm just trying to add kerning to my SVG fonts and it didn't work. I'm not sure what the source of the problem is, is it the lack of browser support or is it my font.

Any info or reference implementation would be helpful.

Thanks in advance
Eigi

to buy FL 4.6 or to wait to v. 5 Studio? (Mac)

I need help.

UltraLight weight in font family is smaller then Regular.

In FontLab, all weights have the same UPM size, very close values for descender, ascender, x-height and caps high. I tried to set bigger UPM size for UL weight, but when I open Illustrator, nothing changes. Also, I tried to increase size for UL at 115% but again, same result - nothing. This is what do I get:

Can anyone tell me how do fix this? What seems to be problem, I can't remember anything logical to me.

Thanks!

Does anybody know what is the purpose of the minRightSideBearing and xMaxExtent values and their vertical equivalents? For what exactly they were meant to be used? Entries themselves aside, how a particular glyph’s right bearing and extent value helps in text layout or rendering process?

I'm trying to export a six-layered font from FontLab Studio, but the .otf files are doing strange things in Illustrator. I don't know if I have missed something in the Font Info window in FontLab, or if it's an Illustrator setting I've overlooked (but I've tested the beta version on several computers now and the problem persists).

The font has 6 layers. 3 of them stack perfectly on top of each other when pasted in place. The other 3, however, do not. As illustrated in the screenshots here, one layer (Eclisse) sets itself a fraction higher than the baseline; one layer (Tonale) sets its baseline noticeably higher than it is supposed to; and one layer (Inline) sets its baseline significantly higher still.

When I highlight this text and change it back to one of the other, properly-working layers, the baselines align perfectly, so I haven't just accidentally nudged the text box. I've been right through the Font Info panels in FontLab and can't for the life of me work out why this problem could be happening.

Any help or guidance would be greatly appreciated!

Hi guys,
I'm having a problem with my typeface and with illustrator cs4, they just recongnize the regular version (i have also the italic).
And with illustrator and indesign cs4 they don't recognize my ligatures, small caps and linning figures although linotype font explorer recognize at least the ligatures.
Some help?

I have 3 questions related to the Open type feature 'locl'

  1. It seems that there is no application support for the 'locl' feature yet. Thomas Phinney agrees that there is none in Adobe products ( yet). But is it in Microsoft Vista/longhorn?

  2. Henadij posted some locl feature code here:

http://www.typophile.com/node/15506

Does anybody know if that code was written correctly? Is there is any sample code for this feature? I have been googling but to no avail.

  1. Would anybody share their code? I wanted to build some Polish & Czech localization into a font!

Thanks!

hi, everybody
I need some more help for my 1200 ligatures. Can I substitute a combination of letters only if it's in the beginning or at the end of a word? Or if it's a whole word?
Thanks alot

Konstantinos Siskakis
Anagrafi
Greece

Hello all. I hope that someone can help me solve an annoying problem I am having. (Especially Si Daniels. Hi Si.)

We have a client who has fully licensed one of our fonts, and wishes to embed those fonts in internal Microsoft Word documents. This is allowed under the terms of our EULA.

This client is having a hard time getting the fonts to embed in Microsoft Word 2002 and 2003, running on Windows XP. The software is probably localised for Norway.

I have generated the fonts in CFF-flavoured and TT-flavoured OpenType, as well as "traditional" TrueType without any OT features. The embedding was, of course, turned on when generating.

I have generated the fonts every way 'til Sunday, including using FontLab 45M, FontLab Studio 5W and 5MBeta, and have tried using TransType Pro 3M starting from every conceivable source: VFB, WinTTF, MacTTF, MacPST1, WinPST1...

In other words, I have jumped through every hoop, to no avail.

Is it possible that embedding in Word is a problem?
Is it possible that the client's font cache is now completely full of conflicting fonts?
Is it possible that FontLab and TransType are incorrectly saving embedding settings?

Any help would be massively appreciated. Any off-list emails can be sent to chester (at) vllg.com.

Thanks a bundle, phellow typophiles. (Can you believe that this is my first ever topic submission?)

Hello,

I'm new on the forum so I introduce myself

i'm a swiss student, and I tried for my studies In ancient history to build a font.
I used fontforge and finally fontlab. Everything works perfectly except the kerning.

MS word 2010 doesen't take count of the kerning of my new font...
Kerning works perfectly on Oppen office, but I have to make it work on MS word. Is it possible ?

Somebody knows what is the problem ? Can somebody help me ?

Thanks for help :)
1nordman

Hi,

I have a few .fnt fonts and would like to convert them to TrueType TTF format... What program should I use?

Best Regards,
jch02140

Hi,

I recently wanted to generate one font into OTF I made, but some weird things happened.
While generating, at 93% of whole process, in Output panel, it shows me this warnings. After a couple of seconds, it complete whole 100% process of generating and I can see OTF file, but when I try to double-click on it, it shows an error (file is corrupted).

I see that there are a lot of "removing duplicate glyph" in Output panel, but I can't find the reason why that appears.

One more thing... I tried somehow to bypass this errors by generating font first into Win Type1 (PFB) and then from PFB > OTF. It works, I can install font and on double-click I can see "Quick brown fox...", but... it looks like some kerning pairs are missing or are incorrect (not like they are in original VFB file), meaning this is not the solution for this problem.

I need help :)

P.S. - Sorry for such a looooong post.

[WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [z zacute zcaron zdotaccent] [i iacute icircumflex fi dotlessi igrave idieresis] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1897] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1898] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1898] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1898] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1898] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1898] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1898] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1898] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1898] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [z zacute zcaron zdotaccent] [i m n p r racute iacute icircumflex nacute ncaron rcaron dotlessi igrave idieresis ntilde] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1898] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1899] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1899] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1899] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [z zacute zcaron zdotaccent] [u uring uacute uhungarumlaut udieresis ugrave ucircumflex] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1899] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1900] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1900] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1900] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [z zacute zcaron zdotaccent] [q u uring uacute uhungarumlaut udieresis ugrave ucircumflex] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1900] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1901] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1901] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1901] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1901] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [z zacute zcaron zdotaccent] [v w y yacute ydieresis] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1901] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1903] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1903] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1903] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1903] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [z zacute zcaron zdotaccent] [b h k l lslash lcaron lacute] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1903] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [parenleft bracketleft braceleft] [j] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1904] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1905] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1905] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1905] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [parenleft bracketleft braceleft] [Y Yacute Ydieresis] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1906] [NOTE] Removing duplicate pair positioning in 'kern' feature: [parenleft bracketleft braceleft] [j] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1907] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [parenleft bracketleft braceleft] [T Tcaron Tcommaaccent] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1907] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1908] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [parenleft bracketleft braceleft] [C Cacute Ccedilla Ccaron] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1908] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1909] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1909] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1909] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1909] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1909] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1909] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [parenleft bracketleft braceleft] [E Eacute Eogonek Edieresis Ecaron AE OE Egrave Ecircumflex] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1909] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1910] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1910] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1910] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [parenleft bracketleft braceleft] [V W] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1910] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1911] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1911] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1911] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1911] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [parenleft bracketleft braceleft] [b h k l lslash lcaron lacute] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1911] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1912] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1912] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1912] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quoteleft quotedblleft] [A Aogonek Aacute Acircumflex Abreve Adieresis Agrave Atilde Aring] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1912] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1913] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1913] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1913] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quoteleft quotedblleft] [A Aogonek Aacute Acircumflex Abreve Adieresis AE Agrave Atilde Aring] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1913] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1914] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1914] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1914] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1914] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1914] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1914] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quoteleft quotedblleft] [E Eacute Eogonek Edieresis Ecaron AE OE Egrave Ecircumflex] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1914] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quoteleft quotedblleft] [P] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1915] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quoteleft quotedblleft] [R Racute Rcaron] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1916] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1917] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quoteleft quotedblleft] [c cacute ccedilla ccaron] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1917] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1918] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1918] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quoteleft quotedblleft] [d l lslash lcaron lacute dcaron dcroat fl] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1918] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1919] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1919] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1919] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quoteleft quotedblleft] [e eacute eogonek edieresis ecaron ae oe egrave ecircumflex] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1919] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1920] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1920] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1920] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quoteleft quotedblleft] [g] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1920] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quoteleft quotedblleft] [r racute rcaron] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1921] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1922] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quoteleft quotedblleft] [s sacute scaron scommaaccent] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1922] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1923] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quoteleft quotedblleft] [s sacute scaron scommaaccent germandbls] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1923] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1924] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quotesinglbase quotedblbase] [C Cacute Ccedilla Ccaron] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1924] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1925] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1925] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1925] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quotesinglbase quotedblbase] [G] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1925] [NOTE] Removing duplicate glyph <> [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1926] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quotesinglbase quotedblbase] [L Lslash Lcaron Lacute] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1926] [WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [quotesinglbase quotedblbase] [t tcaron tcommaaccent] [C:/Users/gore/Documents/FontLab/Studio5/fontlab.fea 1927] [WARNING] The feature file OS/2 overrides TypoAscender and TypoDescender do not sum to the font bbox size!

OK, I was just sitting and proofing my font on printouts and suddenly felt everything looked strange and then I realized that strange things had happened.

Why is this happening? I’ve tried to read/understand the manual but am not sure on what to do to avoid this EXTREME problem.

Please note that this is happening when I print in high-resolution 1200 dpi, and with large point sizes (40 pt).

I’m working on Fontographer.

Many thanks in advance from desperate man …

I have a font that has grown over time. I need to sort it by Unicode for ease in use with InDesign. The problem is all those glyphs (186 of them) that don't have Unicode indexes, just names -- all the number variants, small caps, etc. Is there some way I can get FontLab to let me organize them, so that A.smcp - Z.smcp are found sequentially, etc.?

TIA

Hey Guys...

I have a big problem and I know there are a bunch of smart font people on here so I sure you can help...

I'm building an icon font in FontLab Studio 5.1 and for the life of me I cannot get the font to show up in Microsoft Applications (Word, Powerpoint etc.). Shows up in every other professional app like Illustrator, InDesign... I read all the docs on Microsofts website pertaining to output when making a typeface by MS standards and I followed it perfectly (I think).

DOES ANYONE KNOW THE TRICK TO GETTING CUSTOM FONTS TO SHOW UP IN MICROSOFT APPLICATIONS?

I'm hoping someone can lead me in the right direction...

Thanks a ton in advance :)

High-Logic recently released FontCreator 7 , introducing OpenType layout features, web font support, optical metrics, and a lot more.

Detailed information, screen shots, and a trial version are available through the product page.
http://www.high-logic.com/font-editor/fontcreator.html

We appreciate feedback; both here and at the forum:
http://forum.high-logic.com/

When comparing the "superiors" feature with the "fractions" feature in a number of OpenType fonts from Adobe and Linotype (and others?), some questions arise. Specifically, in the superior glyph range, why do letters have a different baseline from numbers and punctation? This is not the case with glyphs covered by the fractions feature.

Here are some examples illustrated:

Superior numbers have a higher baseline than superior letters. Why? (Illustrated above: [normal capital H], [superior 1], [superior 2], [superior 2], [superior 3], [superior a], [superior b], [normal lowercase c])

What this leads to, is impossible typography, as pictured above. The period should have the same baseline as the superior letter, no? Instead, it has the baseline of the numbers.

Fraction numbers are larger than superior numbers. This is understandable.

Fraction numbers and letters share a common baseline. This seems to make typographic sense. Why here and not with superiors?

Could this have something to do with a legacy work-around? If a type designer, or major type foundry, were to change this, would it cause any problems? Are there users who expect the superior feature to be defined in this manner?