julietaula / montserrat Goto Github PK

The Serbian letter Đ has misplaced dash; it should pass through the middle of the vertical line of letter D. The non-caps version is good.

In Montserrat:

Should be:

I'm hoping this is a known issue or someone else has experienced this. We have a Ricoh copier that won't allow any of our Macs to print from Word, Pages, TextEdit, and the like whenever we use Montserrat as a font. From what I understand, these program send the font and text to the printer. It prints fine to this copier from Windows. It prints fine from high-end applications like Photoshop or InDesign. Just not regular word processors.

Here is the error that prints out:

ERROR: invalidfont
OFFENDING COMMAND: define font

STACK:

/Font
-dictionary-
/VHGQJC+Montserrat-Light

I've been wracking my brain trying to find some sort of solution for this, and I'm really hoping someone here has an idea of what is going on.

Very nice font. Thank you!

What languages it support? Is there Latin Extended. I'm interested in Polish case, where exist some special letters.

What is different than Google Font?

The anchor 'top' is incorrectly positioned on the uppercase 'W' glyph such that it causes misalignment in 'Wacute', 'Wcircumflex', 'Wdieresis', 'Wgrave'. This applies largely to the 'extremes' masters, although it also affects the 'Regular' master ever so slightly.

Reference images:

P.S.: Would it be possible for me to contribute directly to this project/repository instead of bothering you everytime I find an issue with the sources? :)

Best regards,
Kalapi

In the previous version, there is no problem. Until I delete my website accidentally and downloading a new version of Montserrat-Light font v4.001. Now, Montserrat-Light looks like this:

http://oi65.tinypic.com/6tcxfq.jpg

As prevention, font-variant css now temporary disabled on my website.

I just downloaded the latest fonts (v4) and in Medium, SemiBold, Bold and ExtraBold weights, the dots of the Umlauts äöü and ÄÖÜ are too close to each other. The other weights look OK, but might be worth checking anyway. The issue seems to be the same with the TTF and OTF versions, and also with the "Montserrat Alternates".

• h in Regular master is missing a topright anchor.
• fl.ss01in Bold master has top, topright and bottom anchors which are not in the other two masters.

Could you add the following to the locl feature of Montserrat?

language DNK;
sub Eng by Eng.ss01;
sub eng.sc by eng.sc.ss01;

@andjc requested this for Noto Sans in https://github.com/googlei18n/noto-fonts/issues/900, but this equally applies to other fonts such as Montserrat. It would be great to know if this should also be done for other languages beyond Dinka; perhaps @andjc or @moyogo might know which languages are affected.

ķ is part of the set of Latvian letters ĶĻŅŖķļņŗ which are traditionally expected to have the preferred comma-shaped cedilla. Right now it’s the only one in the set with a classic cedilla while ĶĻŅŖļņŗ have the preferred shape.

Somehow the curves of h and n in the regular and light weights look thicker than the vertical stems.
It's a small thing, maybe it's only my impression, but it makes theses shapes top-heavy for me.

Identical problem to #23, using versions of the font downloaded today.

ERROR: invalidfont OFFENDING COMMAND: definefont

Using the TTF version works fine.

Before we merge the Cyrillic, I'll be making a few quick reviews.

We're missing unicode 02BB from the version which is hosted on Google Fonts.

Hello @JulietaUla,

I noticed the Reserve Font Name has been removed in the latest v4.000 release. Would you like me to include it?

Cheers,
Marc

Hello! Ideally the 'comma below' is aligned to the centre of the lowercase 'k' as seen in the following image:

(Typefaces from the left: Source Sans Pro, Constantia, Droid Serif, Gentium, Lucida Sans, Palatino Linotype, and Roboto. Images courtesy www.fileformat.info)
However, in Montserrat, the 'comma below' is centered below the stem of the 'k' instead of being centered below the entire letter;

Hi, thanks for your nice Font!

It seems that the last version of the font has a mismatch with the brackets, the {} look like [] and the {} look like []

You can check it easily in the Google Fonts demo:

https://fonts.google.com/specimen/Montserrat

Thanks!!

Would it make sense to add top and bottom anchors to all base glyphs? For most glyphs, they are already present, but eg. b has no anchors yet. This would make it possible to attach combining marks to any base Latin latin letter.

Hey folks,

Before I can accept v6.001, the following needs to be fixed:

Family:

• Version numbers incremented to 6.001, they're currently 5.000
• delete .null glyph and give NULL unicode 0000
• The following glyphs are present in either the Roman or the Italic but not both:
  eight.lf
  jacute
  zero.lf
  three.lf
  one.lf
  c_t
  Tdieresis
  semicolon.sc
  nine.lf
  idotless.sc
  _temp.tildecomb
  f_f_ij
  quotesinglbase.sc
  two.lf
  ogonekcomb.a.u.alt
  c_h
  Napostrophe
  question.002
  seven.lf
  f_ij
  four.lf
  s_t
  comma.sc
  f_f
  _temp.interpol
  f_f_i
  f_f_l
  colon.sc
  Jacute
  commaaccentcomn
  five.lf
  six.lf
  I understand some of these may not be needed in one font or the other. However glyphs like Tdieresis are essential.

Italic:
-nbspace must be same width as space

Roman:

• ss01 glyph count inconsistent with Italic 20+ missing. Is this intentional?

cc @davelab6

The newest version has narrowed the dots of the i and the trema. They look much more oval than in the other weights, where they are optically nearly circular.

In the .glyphs files, we use two customParameters in each instance to do this, Rename Glyphs, Remove Glyphs.

When the fonts get genned: the rename parameter will do the following:

A-cy.ss01 --> A-cy

Then A-cy.ss01 gets deleted, thus giving us the alternative family.

I'd like both customParameters updated to include the Cyrillic glyphs

cc @davelab6

When I use FontForge to open Montserrat Light, I noticed the family name is set to "Montserrat Light" instead of just "Montserrat". Same applies to woff files as well as all the other font weights (not just Light).

In the app, I can see the incorrectly set "Montserrat Light" font family in:
Element -> Font Info -> PS Names
Element -> Font Info -> TTF Names

Please make a new release on https://github.com/JulietaUla/Montserrat/releases with a few notes about what changed :)

why ttf is not in webfonts folder?
does ttf could be used for web pages?
And do you have a .css file for the webfonts?

Hello @JulietaUla and @juandelperal!

First of all, thank you for your great Montserrat font 👍 One of the biggest issues I had initially was that it was only available in 2 weights in Google Fonts, but last year I discovered the Thin and Light weights and I loved them. I now see that you have been working in all the 9 weights (yaaay!) but when I downloaded this repo I found there are actually 10 weights 😕

I noticed that the Hairline and Thin weights are almost identical, but the font height seems to be different. I assume one of them is repeated. Which one is the right one?

Thanks a lot,
Regards from Madrid

Osiyo Julieta,

Will you add Cherokee (Tsalagi, or ᏣᎳᎩ) to Montserrat?

Cherokee is of interest to Americans with ancestors native to North America. Cherokee, having 84 glyphs is included in every version of Windows and Apple operating systems. Keyboard setup and use in both is a snap. However... designing and building a font is no snap. Neither is Montserrat any Everson Mono, yet. Request.

Wado, Taya'koia Takwah (Mark)

Hi Julieta,

I'm wondering about how you use the MontserratAlternates.glyphs file. It looks like it's the same as Montserrat.glyphs with the ss01 feauture turned on. If so, and if there's no other variation I wonder if we could use Adam Twardochs pyftfeatfreeze to produce an equivalent result. The advantage of that approach would be that there would be just on source file to maintain.

Best, Lasse

Please take a look at: https://github.com/JulietaUla/Montserrat/network

There are unfortunately 4 commits in your master that happened without prior merging the work of @kalapi
Unfortunately we cannot merge the branch of @kalapi (and mine) back into master, because of conflicts.

I added the vendorID and I fixed the z.alt glyph.

My branch builds on Kalapis: https://github.com/graphicore/Montserrat/tree/mastering and I prepared it to get the ttf fonts into google fonts.

We should somehow merge the branches, however, I think the best approach at this point is to redo the missing changes on top of my branch and force push it to master.

@juandelperal please tag a 6.001 release asap :)

Currently the contents of the sources/ directory is like this:

sources/
├── Montserrat-Italic.glyphs
├── Montserrat-Italic_autospace.py
├── Montserrat.glyphs
├── Montserrat_autospace.py
└── temp
    └── rmx
        ├── review\ overshoot.txt
        ├── sc.list.txt
        └── sc.txt

Can the *autospace.py files and and temp directory be removed?

Hello julieta

Great work on Montserrat I love it
I'm working on an Arabic matching version for Montserrat please check it out
https://github.com/Gue3bara/Montserrat-Arabic




Work is still in progress and will take sometime but would love if you check it out and let me know what you think

I know this is not an "issue" but wasn't sure where else to write you this :)

cheers

When I generate the fonts, I get this:

However, It seems fine in the glyphs file:

I'm guessing GlyphsApp may be at fault on this one.

I'm using Glyphs Version 2.4.4 (1075).

cc @schriftgestalt

We should add the previous v1.6xxx as a release. We can point people to this for future complaints.

cc @davelab6

This is a fontbakery error, the full thing reads:

ERROR    OS/2 VendorID is 'UKWN', a font editor default. You should set it to your own 4 character code, and register that code with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx  

The 'z' in Alternates is missing the main shape. It's just a dash at the moment.

Hi Julieta, I’ve drawn a couple additional Latin glyphs for Montserrat, used mainly in African languages. In the attached Glyphs file, I’ve marked my changes in yellow. Specifically, I added drafts for the following glyphs:

• Combining marks: circumflexbelowcomb

• Uppercase letters: Acaron, Adieresismacron, Bdotbelow, Bhook, Bstroke, Chook, Dafrican, Dcircumflexbelow, Dhook, Ecedilla, Eopen, Ereversed, Esh, Fhook, Ghook, Ghook.ss01, Hhook, Hturned, Icaron, Lcircumflexbelow, Ncircumflexbelow, Nhookleft, Nhookleft.ss01, Ocaron, Oopen, Phook, Rstroke, Tcircumflexbelow, Thook, Tretroflexhook, Vturned

• Lowercase letters: acaron, adieresismacron, bhook, chook, dcircumflexbelow, dhook, dtail, ecedilla, ecircumflexdotbelow, eopen, esh, eturned, eturned.ss01, ghook, hhook, hturned, icaron, istroke, jdotless, khook, lcircumflexbelow, ncircumflexbelow, nhookleft, ocaron, oopen, phook, qhooktail, rfishhook, rhook, tcircumflexbelow, thook, thook.ss01, tretroflexhook, tretroflexhook.ss01, vhook, vturned, whook, wturned, yhook, yhook.ss01

To fully support African languages, one would need to do more work. But before completing it, I wanted to ask if the direction is reasonable. I haven’t done any kerning, but I’ve tried to assign reasonable kerning classes to the new glyphs. Also, I haven’t drawn any small caps glyphs yet — again, I first wanted to get your feedback on the current drafts.

Feel free to incorporate these glyphs into the main Montserrat master, perhaps after tweaking.

Per @rgrundig comment in #40 (comment) here is Montserrat vs Exo 2, Roboto, and and Rubik

I think he is probably right that they are too big... certainly in the italic, its very wide

Julieta, you have made a very beautiful font with Montserrat, but you keep changing it at Google fonts, and so my website changes as well. Could you please keep it the way it is so I don't have to fear my website looks different next time? I know there are many more who use your font Montserrat because it looks so great, and they also have this issue. Could you just rather add to it instead of changing? Thank you.
Pieter

I created appdata for your typeface according to Appstream guideline: https://freedesktop.org/software/appstream/docs/sect-Metadata-Fonts.html needed for Gnome Software and other appstream applications.

http://pkgs.fedoraproject.org/cgit/rpms/julietaula-montserrat-fonts.git/tree/julietaula-montserrat.metainfo.xml

Feel free to edit the line like ownership.

Sincerely,

Luya

The horizontal segment on the top of the centre 'apex' of the glyph is not perfectly flat.

Masters Affected: Black, and Regular

Reference:

In heavier versions of the Montserrat font (bold, black,...) the tittles (dots) on "i" and "j" are not the same size. Was this on purpose? The Google font version does not have this issue.

The file "MontserratAlternates-UltraLight.otf" appears to be corrupt because Windows 7 x64 isn't accepting it.

"dcaron", "lcaron", and "tcaron" have stray nodes below the baseline.

Some little problems remain

uni04AD must look like this:

We have this:

I'm not sure if I like the new changes made to Montserrat on google webfonts. https://fonts.google.com/specimen/Montserrat

I love the fact that new styles were added and that Montserrat has grown. What I don't like is that the 'normal' font weight of the previous version is nowhere to be found in the new version. The closest one is 500(Medium), but that one is slightly bolder.

To sum things up: the 400 font weight of the previous version should have been the 500 of this one.

Without it we can't install the font per npm / bower / yarn
Thank you!

Have been using this font on a website through Google Fonts. Looked great, spent a long time choosing it.

Now the weights of the font have changed on the live website and it looks worse, i've tried selecting the original weight but it just doesn't look right anymore.

How do i revert or get a copy of the older version of this font?

uni04Be, uni04BF

Montserrat Cyrillic

System font

uni04B0

Montserrat Cyrillic

System font

uni20B4

Montserrat Cyrillic

System font

System font

Montserrat's version is more aesthetic but the direction may be wrong?

Other glyph errors

izhitsa-cy: Contour direction is wrong

MS val report.

review these glyphs across all master please.

Nice work :-)

Hello team,
I am a Fedora Project contributor ready to package your fonts. I would like to know what is the current version i.e. 1.0 or 2.1 for example. Thank you,

Luya

Hello,
do you have any plan to add to Google font any of the other Montserrat variations like Hairline, Light and so on?

Hello,

We have incompatibility issues in the following:

Roman:

• quotedbl.cs
• area
• fl.ss01

Italics:

• areas
• oe
• oe.ss01