Font Forum

I was under the impression that it was an optional procedure to be employed where there was not enough room for the accents` The low profile accents are optional for uppercase accented glyphs to save space. These smaller accents are also better suited for use with Petite Capitals. After running the...

Here is a quick edit of your font to show what I would do with it. I adjusted the scale factor for Petite Caps to 73 horizontal and 69.10 vertical. Take a look, then adapt your scripts to suit whatever you need. After running the Petite Capital script you should manually adjust the serifs, which wil...

A few observations: The acute and grave accents are in the right position, but the other modifier accents from circumflex to hungarumlaut are below the x-height. The usual position is about half-way between the x-height and CapHeight metric lines. None of the accented glyphs are composites. If you u...

As my screenshot shows, the Y position of the lowprofile diacritics is zero.

Please attach your CompositeData.xml file and Petite Capitals Transform script from AppData. Zip them together with your font project if you're willing to share that.

You really must learn how to report bugs effectively. Rants drive me crazy

1. Be polite: Erwin is the sole developer. He is not "you folks."
2. Since it is a new topic, start a new thread in the right forum.
3. Be specific about the behaviour that you think is buggy.

Thanks

Don't be loath to edit the CompositeData.xml file if you need to. That's why there is an option to "Copy Data Files to User Data Folder" in Tools, Options, Advanced. The original file is saved in Program Files when FontCreator is installed: <!-- Updated 27th April 2017 for FontCreator 11.0 --> You c...

Thread moved to the correct forum

Please read the tutorial on Adding OpenType Features or watch the video.

The zero has a left side bearing of -1052, hence the overlapping problems. Use the Glyph Properties dialogue (F4) to set the left side-bearing to 91, and set the left side-bearing point to zero. Zero Bearings.png You have not yet designed any glyphs for quotation marks. Word will automatically repla...

The scripts do not use the funits/em setting. The scale is by a percentage, but the bold transform is in funits. Almost all of the scripts will need manual adjustment to suit each font. They were designed using my Verajja font (derived from Bitstream Vera), and won't be right for other fonts. The sc...

This does not look like a bug in FontCreator; just some bugs in your font with incorrect side-bearings. If you can share the font project we can take a look.

As far as I can tell, a glyphname with spaces, e.g. "f f i" works OK, but it seems to violate the specification: so I suggest not using spaces. I just leave out the underscores to make the name easier to read and type, e.g. "ffi" 2.f.i. Glyph name A glyph name may be up to 63 characters in length, m...

H with dot above is in Latin Extended Additional. It does not exist in your Tahoma New font.

I think your problem is that you have not installed your modified font, and MathType is only seeing the default Tahoma font.

180 is the decimal codepoint for acute accent. Use shortcut Ctrl+J to switch to decimal codepoints Use shortcut Ctrl+K to switch to hexadecimal codepoints Hexidecimal.png Decimal.png If those are the codepoints you have used to map your new glyphs, they are in the Latin-Extended B character set. Doe...

I deleted your duplicate thread in the Support forum, as I am sure that such a feature does not exist. I don't understand how this could help in designing a clone of an existing font unless you're doing something dodgy like copying the glyph outlines to a new font. You could just copy the metrics, a...

What code-points did you map them to? Does Math Type support glyphs in the Private Use Area like Windows Character Map does?