Glyphs 2 Beta

Here you go: One and Two

Note shape/point #4 in the light master which doesn’t exist in the bold master (nor does anything show up in the outline for light master either).

Another issue: When I revert a file, any text that is not unicode encoded disappears from the tabs.

Lastly on measurements, it would be handy to have an angle indicator in the “info panel” when two points are selected.

Amnother

What is the reason for renaming /dotlessi, yet not /dotlessj?
Both are renamed. Do you have a custom glyphData that might has the old name?
Probably. Thanks.

Two suggestions:

A. Considering that Glyphs is growing popularity in South America, could Glyphs have full support for Guaraní? I recommend to support the not unicode supported [G|g]+tilde. My suggestion is to name both glyphs following the ligature syntax:

G_tilde.loclGUA
g_tilde.loclGUA

So, will be great if the automatic feature generator could generate the following line on locl:

languageGUA;
sub G [tilde acsiitilde] by G_tilde.loclGUA;
sub g [tilde acsiitilde] by g_tilde.loclGUA;

B. When you have _topright and _top anchors in a mark glyph (acute , grave or hookabovecomb for example), glyphs with two or more marks eventually are taking by default the _topright anchor instead of the _top. So when you generate glyphs like:

odieresisacute
odieresisgrave
ohornacute
ohorngrave
ohornhookabove

You need to adjust the anchor of the second mark to _top.

Another issue with Vietnamese occur in glyphs with dotbelowcomb as a second mark, Glyphs is placing the dotbelowcomb as the first mark, and this is causing a misplacement on the glyphs. The error is fixed changing the order of those marks, putting the dotbelowcomb as the second (instead of the first) mark. Check the image attached, Left is the correct and right is how Glyphs is generating this glyph.

You are doing a amazing job with the software and all the support.

Thanks,

Nicolas

I can add the Guaraní code.

What version do you use?

Can you send me a font that has the double accents going wrong?

Version 2.0.0 (692)

Thanks Georg

Georg Seifert
Could you give me your email?

Georg Seifert
Here is the.glyphs from where I took the snapshots

The problem is that anchors from within the components are respected. If you decompose the dotbelow and delete the top anchor in it, then it will work. If you like to use components for both, use a third glyph, that has no anchors, for both dot below and dot above.

if a component can attach to two different anchors, there will be a anchor symbol in the info box. Click it to choose the anchor.

Thanks Georg

Definitely I am going to use this method in my workflow.

Some feedback regarding the newly introduced kerning indicator: (great feature!) it would be useful to have the indicator displayed at even smaller sizes, down to 50pt.

When in text edit mode (T keyboard shortcut): The metrics numbers seem to persist now and toggling “Show Metrics” only turns off the bounding box indicators.

The kerning indicator should be toggle-able separate to the metrics numbers in text view, as in, I want to be able to see only text, and kerning indicators. Currently the metrics numbers and kerning indicator must be viewed together.

But this gets quite fuzzy than. fixed that already

Any news on the rounded font filter bug I reported here? I’m really looking forward to using this feature.

I thought I had fixed this. Thanks for the reminder.

i just realized, that the custom parameter (Scale to UPM) set in the instances got a problem with components and accents. these experience shifting around in the otf and woffs.

Hi guys!

I have had problems with this issue. What I did is to generate an instance instead of a font, and with the new generated instance, with its UPM scaled, I fixed all the metrics parameters values like shoulder line, ascend, etc. (because this values are not scaled) and generated the fonts from this new instances. In this way, all the mark base and mark to mark stayed in order.

Changing the topic, I am working on a font that has a proper set of superior letters with glyphs named according with the Glyphs’ xml. But I see that these letters are not being taken in consideration by the OT feature generator in order to generate a sophisticated ordinals feature. Can I suggest that Glyphs be able to make the following ordinals feature automatically?

lookup ordSpanish { # Portugese and Spanish
…sub [zero one two three four five six seven eight nine] [R r]’ [A a] period by rsuperior;
…sub [zero one two three four five six seven eight nine] rsuperior [A a]’ period’ by ordfeminine;
…sub [zero one two three four five six seven eight nine] [R r]’ [O o] period by rsuperior;
…sub [zero one two three four five six seven eight nine] rsuperior [O o]’ period’ by ordmasculine;
…sub [zero one two three four five six seven eight nine] [R r]’ [A a] by rsuperior;
…sub [zero one two three four five six seven eight nine] rsuperior [A a]’ by ordfeminine;
…sub [zero one two three four five six seven eight nine] [R r]’ [O o] by rsuperior;
…sub [zero one two three four five six seven eight nine] rsuperior [O o]’ by ordmasculine;
…sub [zero one two three four five six seven eight nine] [A a]’ by ordfeminine;
…sub [zero one two three four five six seven eight nine] [O o]’ by ordmasculine;
} ordSpanish;
lookup ordEnglish { # English
…sub one [S s]’ [T t ] by ssuperior;
…sub one ssuperior [T t]’ by tsuperior;
…sub two [N n]’ [D d ] by nmod;
…sub two nmod [D d]’ by dsuperior;
…sub three [R r]’ [D d ] by rsuperior;
…sub three rsuperior [D d]’ by dsuperior;
…sub [zero one two three four five six seven eight nine] [T t]’ [H t] by tsuperior;
…sub [zero one two three four five six seven eight nine] tsuperior [H t]’ by tsuperior;
} ordEnglish;
lookup ordFrench { # French
…sub one [E e]’ [R r] [S s] by esuperior;
…sub one esuperior [R r]’ [S s] by rsuperior;
…sub one esuperior rsuperior [S s]’ by ssuperior;
…sub one [R r]’ [E e] [S s] by rsuperior;
…sub one rsuperior [E e]’ [S s] by esuperior;
…sub one rsuperior esuperior [S s]’ by ssuperior;
…sub two [D d]’ [E e] [S s] by dsuperior;
…sub two dsuperior [E e]’ [S s] by esuperior;
…sub two dsuperior esuperior [S s]’ by ssuperior;
…sub one [E e]’ [R r] by esuperior;
…sub one esuperior [R r]’ by rsuperior;
…sub [zero one two three four five six seven eight nine] [E e]’ [S s] by esuperior;
…sub [zero one two three four five six seven eight nine] esuperior [S s]’ by ssuperior;
…sub one [R r]’ [E e] by rsuperior;
…sub one rsuperior [E e]’ by esuperior;
…sub one esuperior [R r]’ [S s] by rsuperior;
…sub one esuperior rsuperior [S s]’ by ssuperior;
…sub two [D d]’ [E e] by dsuperior;
…sub two dsuperior [E e]’ by esuperior;
…sub two [D d]’ [S s] by dsuperior;
…sub two dsuperior [S s]’ by ssuperior;
…sub two [D d]’ by dsuperior;
…sub [zero one two three four five six seven eight nine] [E e]’ by esuperior;
} ordFrench;
lookup ordAbbreviations {
…sub M [E e]’ [L l] [L l] [E e] parenleft [S s] parenright by esuperior;
…sub M esuperior [L l]’ [L l] [E e] parenleft [S s] parenright by lsuperior;
…sub M esuperior lsuperior [L l]’ [E e] parenleft [S s] parenright by lsuperior;
…sub M esuperior lsuperior lsuperior [E e]’ parenleft [S s] parenright by esuperior;
…sub M esuperior lsuperior lsuperior esuperior parenleft’ [S s] parenright by parenleftsuperior;
…sub M esuperior lsuperior lsuperior esuperior parenleftsuperior [S s]’ parenright by ssuperior;
…sub M esuperior lsuperior lsuperior esuperior parenleftsuperior ssuperior parenright’ by parenrightsuperior;
…sub M [M m]’ [E e] parenleft [S s] parenright by msuperior;
…sub M msuperior [E e]’ parenleft [S s] parenright by esuperior;
…sub M msuperior esuperior parenleft’ [S s] parenright by parenleftsuperior;
…sub M msuperior esuperior parenleftsuperior [S s]’ parenright by ssuperior;
…sub M msuperior esuperior parenleftsuperior ssuperior parenright’ by parenrightsuperior;
…sub M [E e]’ [L l] [L l] [E e] by esuperior;
…sub M esuperior [L l]’ [L l] [E e] by lsuperior;
…sub M esuperior lsuperior [L l]’ [E e] by lsuperior;
…sub M esuperior lsuperior lsuperior [E e]’ by esuperior;
…sub M [M m]’ [E e] by msuperior;
…sub M msuperior [E e]’ by esuperior;
…sub M [M m]’ period’ by msuperior;
} ordAbbreviations;

I am open to suggestions about this.

Regards,

Nicolás

I like the newly introduced kerning and metrics indicator. Would it be possible to have it as an option ? Like “Show Metrics” in the view menu ?

Is there a way to turn it off ?

Most of the things you show are not ordinals, but language-specific abbreviations. The letters should go into the sups feature, and the user can activate it when necessary. Glyphs can build that feature automatically if you use the sups suffix: "x.sups".