'isFixedPitch' flag not set for Roboto Mono

[NAKlama]

This prevents the font to be used on Windows.
Workaround:
Use TTX to convert ttf file and edit flag before converting back.

[davelab6]

Thanks for reporting this!

[khaledhosny]

Note that isFixedPitch should be set only if all glyphs in the font (including combining marks) have the same width, otherwise rendering might be broken on applications that optimise reading glyph advance widths based on this flag.

[musm]

Pretty sure I just ran into this bug which gives the following : (
Looking forward to a fix for this great mono font. Currently this bug hampers usability on windows.

I'm using the TTF files provided here https://fonts.google.com/specimen/Roboto+Mono

@FKlama care to upload the patched ttf files?

[exoton]

Setting the isFixedPitch flag with ttx does not make this font available in the windows console properties (even after changes to the registry, that are not really required for the TrueType fonts in Windows 10), although it can be now selected in programs like Vim. Something else needs to be changed.

[davelab6]

I think probably also PANOSE monospace

[exoton]

Yes, proportion should be 9, not 0:

<panose>
   ...
    <bProportion value="9"/>
    ...
</panose>

[dangerousdan]

This is silly.
Roboto Mono is listed as a monospaced font, so why don't all glyphs have the same width?
Correct me if I'm wrong, but Isn't that the one thing monospaced fonts should have?

https://codepen.io/anon/pen/qyYoyJ/

[PiotrZierhoffer]

I noticed that running fc-list -v :spacing=mono | grep Roboto does not yield any results, neither for Roboto Mono nor for the patched version from @yurakl

I understand this is not a fully monospace font, as I notice the glyphs have different widths. Usually it's 1229, but also 0, 1106, 1227, 1230, 1249, etc etc., up to 2458. I might misunderstand the format (it's my first contact with it), but other monospace fonts I have report either some constant width or 0.

For us, the result is that we cannot align output with spaces when rendering via Pango, but rendering on Windows works fine (both the patched version and the original one).

[mailinglists35]

hello google, does anyone still work for these fonts?

[davelab6]

No.

[mailinglists35]

@yurakl given googles' response via @davelab6 which gives zero hopes for an official fix, do you mind sharing your source code patches? I see there are more than quite a few commits to roboto after your build and I'd like to try your patches on the roboto master tree.

[exoton]

@mailinglists35 I don't have patches. I've used ttx to convert ttf to xml, changed isFixedPitch and bProportion and converted it back to ttf

[s3rb31]

Why is this not fixed? Cannot be that hard to upload the fixed files.

[davelab6]

@thundernixon lets queue this up for Q1, you can use TTX to hotfix the binaries

[Kogl1n]

Thank you! Will you change the version number?

[thundernixon]

Sounds good! Should be a quick update.

[musm]

What's wrong with just using the fonts at #225 (comment) which has the flag correctly set ?

[musm]

Can you also set OS/2 PANOSE Proportion to Monospaced

[speller]

What's wrong with just using the fonts at #225 (comment) which has the flag correctly set ?

The Powerline fonts have some issues with naming (probably) and they're not recognized as a single group of fonts in Ubuntu. I have three groups of fonts in the system instead of a single one.