feature

Plastica: Experimental 3D typeface issues

Forums: 

Hello guys,
I’m nearly finishing work on my new experimental 3D typeface called Plastica. I’m facing few problems I would like to discuss.

It is CFF OpenType made in FontLab on PC. Outlines are very precise and I used atypical custom UPM of 2300 units (23 modules at 100 units). But this should be fine regarding to older nodes on Typophile.
There are two versions: Plastica One (Striped) and Plastica Two (Outlined).
And here is what I struggle with:

1) On-screen rendering issues:

FontLab 5.2.1 Output: GSUB feature 'ÿÿÿÿ' causes overflow of offset to a subtable

Forums: 

Hi all,

I'm designing a handwriten font wich contain many alternate sets of characters and I programmed a calt feature to randomize it. The feature contains a lot of lines mixing and conditioning the substition of each character. I thing the sintaxis is fine and the replacement works fine too, but when I increase the number of characters in each of the classes used in the code the output panel shows the following warning:

[FATAL] GSUB feature 'ÿÿÿÿ' causes overflow of offset to a subtable (0x1140a)

(I don't know why the name of the feature is swhown without the correct name).

Splitting dingbat glyph / OpenType

Forums: 

Hello, moved by the curiosity for the recent Flagsmith, I was just practising by playing around with OpenType on a dingbat font and I was trying to have a symbol (called "logo") splitting in its component by adding "-div" behind the name of the logo. So, for instance, "logo-div".
Given the logo "logo" and its four components:

logo.alt001
logo.alt002
logo.alt003
logo.alt004

I was looking at the Flagsmith and I therefore coded in the "liga" feature:


sub l' o g o hyphen d i v by logo.alt001;
sub logo.alt001 o' g o hyphen d i v by logo.alt002;
sub logo.alt001 logo.alt002 g' o hyphen d i v by logo.alt003;
sub logo.alt001 logo.alt002 logo.alt003 o' hyphen d i v by f_glyph;
sub logo.alt001 logo.alt002 logo.alt003 f_glyph hyphen' d i v by f_glyph;

Why can't I have my OpenType fonts work in Microsoft Office Word and some other softwares?

Forums: 

I've been using Fontlab Studio 5.2 for compiling OpenType features. But my generated fonts only work in Notepad and some Adobe softwares such as Photoshop, InDesign, Illustrator,... I can't have it work in Microsoft Office or Manga Studio. For example, I can't have the Katakana prolonged sound mark turn vertical in a vertical text line. Only original fonts such as Arial, Times New Roman, MS Mincho, MS Gothic,... and other commercial fonts can work well. Do you have any idea what's the thing I have to deal with? Thanks in advance.

Why can't I have my OpenType fonts work in Office Word and some other softwares?

I've been using Fontlab Studio 5.2 for compiling OpenType features. But my generated fonts only work in Notepad and some Adobe softwares such as Photoshop, InDesign, Illustrator,... I can't have it work in Microsoft Office or Manga Studio. For example, I can't have the Katakana prolonged sound mark turn vertical in a vertical text line. Only original fonts such as Arial, Times New Roman, MS Mincho, MS Gothic,... and other commercial fonts can work well. Do you have any idea what's the thing I have to deal with? Thanks in advance.

Contextual alternate feature – confusion

Forums: 

Hello,

I have a font that i'd like to utilise the calt feature, and have found Thomas Phinney's article [http://forums.adobe.com/thread/395648], among others [http://typophile.com/node/19625] to be most helpful. YET I still can't get my head around writing the feature so that it creates a more 'random' outcome.

The details are:
– x3 variants for all characters
– x3 classes [00 / 01 / 02] including one of each character, 79 characters in total [A–Z, a–z, 0-9, punctuation]
– feature currently looks like:

feature calt {
lookup calt_one {
sub @set_00 @set_00' by @set_01;
sub @set_01 @set_00' by @set_02;
} calt_one;

lookup calt_two {
sub @set_02 @set_00' by @set_02;
sub @set_01 @set_02' by @set_00;
sub @set_01 @set_00' by @set_02;
sub @set_00 @set_01' by @set_02;

Open Type scripting dilemma

Forums: 

hello folks, i have aquestion about ot scripting.

the font i'm working on is uppercase only and it has a lot of stylistic sets. of course i had to include lowercase glyphs too, but they just mirror the uppercase glyphs. however, for the alternative glyphs, i don't do uc and lc for each one of them, only the uc.

then i put only the uc glyphs in my stylistic sets classes and so for this to work with the lc as well, i'm doing a lookup that changes lowercase into uppercase before each substitution.

feature ss01 {
lookup ss01a { sub @lower by @upper; } ss01a;
lookup ss01b { sub @class_0 by @class_1; } ss01b; # they contain only uppercase
} ss01;

Font editor (FontLab?) feature suggestion: floating sidebearings linked to outlines in glyph

Forums: 

I use FontLab Studio, so that's what I have in mind. But other font editors might find some of this useful.

Constant Sidebearings

About 90% of the time, when I am editing a glyph, I wish I could edit the outlines and keep the sidebearings in place... which of course means the sidebearing line needs to "float" with and glyph changes I make that affect the advance width. Of course, occasionally one does not want this, so it would be ideal to have some sort of "force linked sidebearings" toggle button when in the glyph window. Maybe the button would be part of the FLS glyph properties floating palette?

Even when the sidebearings are linked to the outlines, you would still be able to click and drag on the sidebearings as you can today, to adjust them.

Which Open-Type feature should I use?

Forums: 

I created a font for a school assignment a while ago, and I'm having a little trouble with Open-Type in order to make it work properly.see the font here: http://www.behance.net/gallery/Shoelace-Typefeet/465085
Since the typeface uses shoes as characters, I needed it to be like this:
Right foot, Left foot,Right foot, Left foot,Right foot, Left foot,

At first I just put all the right feet in uppercase glyphs and left feet in lowercase glyphs, so you needed to type ThIs WaY to make it work (not the best solution, but I had a tight deadline). Now I am trying to find an open-type solution to make it look right regardless of how you write, but I'm not sure about which open-type feature I should use.
I am a bit of a noob at Font Lab, so any help would be appreciated.