First off, this is an excellent font. It's very readable, but it's missing a lot of accented characters. I see #18 references several accented characters being requested. I would also like to request some accented characters as well.

When I'm zoomed in, everything is fine:

But if I zoom out just a little, the right double quote renders incorrectly:

This occurs in Sublime Text 3 as well:

I'm using Windows 10 Pro.

Hi, sorry if this is too general a topic for this forum, feel free to close if it is.

I want to use this typeface in something close to an aircraft cockpit application - well, a hobbyist flight sim setup - on an OLED screen whose pixels are either on or off, no greyscale, no anti-aliasing.

If I wanted fixed-width B612 numerals with a letter height of 25-30 pixels, is there a canonical way to render the font like that?

What I've done instead, minimal effort, is to render the font at about the right size and manually select or unselect the anti-aliased pixels. This shows the general (incomplete) idea:

There is an ISO standard glyph for the compose key. It would be nice to have a glyph for this in B612. (Currently the only free typeface I know of which includes this glyph is Noto Sans Symbols.)

According to the commit log, the latest version is 1.005 (ac9a735) with fixes (1ed9915 and 97aa715). Could you please add a tag and release it?
Thanks!

README.md says that Eclipse Public License version 1.0 applies, but version 2.0 is included in the repository.

It would be useful if the slashed zero would be accessible as an OpenType feature. In case a contributor would like to take up this task, here is a suggestion for how to do it in FontLab.

1. FontLab > Window > Panels > Features
2. Features > + > type "zero"
3. Add the following in the code box:

feature zero {
# GSUB feature: Slashed Zero
# Lookups: 1

  sub zero by slashedzero;

  script latn; # Latin

  script cyrl; # Cyrillic

} zero;

4. File > Export Fonts As... > OpenType PS (OTF)

OpenType layout tables GPOS, GSUB and TrueType hinting tables LTSH, cvt, fpgm, hdmx and kern table have been missing from the TTFs after "Release new ttf files (1.005)" ac9a735.

At this moment it is no possible to generate the TTF files (or any other format) from the geometry without buying FontLab.

I would suggest a possible workflow in which the font geometry is initially exported to a vendor-neutral format that preserves all FontLab information (I'd assume one SVG per glyph and text representations for tables and other metadata). That neutral format would then become the "source code" and a designer would work by importing (or assembling) all geometry and information into their preferred program via a script (FontLab, Fontographer, Illustrator, FontForge, InkScape) and then export the changed elements back to the vendor neutral format, ready for a git commit and a pull-request.

Could be related #8 , i'm not really a font guy.
Left: 1.006 || Right: 1.005

Edit: Worth mentioning this existed prior to 1.005 aswell

The parenthesis () are very similar to the square brackets. This is causing readability issues because () looks like []. Function calls look like array declaration.

The capital letter 'O' and the number '0' are nearly identical in both the proportional and the mono-spaced fonts. I think it would be a wonderful improvement to have a slash through the zero glyph to more easily distinguish the two. This change would also align with the font's primary goal of being "highly legible"!

On mono font, punctuation should be centered, not left aligned :

b612 mono and b612 punctuation sample

other mono samples

I can't select B612 Mono as my preferred font in applications that limit the list to fixed-width fonts. fc-list :spacing=100 does not include any of the B612 or B612 Mono fonts.

See screenshot below:

Taken from Google Font

They are also visible when you browse the official site:

Perhaps it is expected, as it's really visible on large sizes.

I rendered the string “She said, ‘Don't make others suffer for your personal hatred.’” in all eight version of the typeface, and there is an oddity with the right single quotation mark (U+2019) in every weight and shape of the monospace font.

Note that in the non-monospaced b612, the left double quotation mark looks like a doubled version of the left single quotation mark, and the right double quotation mark looks like a doubled version of the right single quotation mark. This is because they are all derived from the base glyph quotesinglbase, with transformations applied.

However, in B612 Mono, the quotes are not derived from this quotesinglbase glyph (though it is defined in the UFO); they are all independently defined. And the right single quotation mark glyph looks to have more in common with the acute accent than anything else. It just plain looks wrong.

According to

medicalwei[m]> But if we need to convert vfb to ufo properly we might need FontLab Studio, or ask upstream to do that flavor...

I had to convert the vfbs using the non-free .exe from FontLab using wine to convert them to ufo files,
which I had troubles building from these sources for the Debian package:
http://phd-sid.ethz.ch/debian/fonts-b612/

Details: http://phd-sid.ethz.ch/debian/fonts-b612/fonts-b612-1.003%2Bgit20180121/debian/README.source

asked for at http://bugs.debian.org/919998

Problem details:
fonts/ufo2otf#5
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920708

One location (GitHub) says just OFL. Website says EPL, then OFL (was older EPL, or did EPL remain an option with new versions?). README says EPL 1, EPL 2, and OFL (does that mean one must comply with all 3, or any of the three?).

To me, it seems clear the intent is any of EPL 1, EPL 2, or OFL, but to others, it seems there is a lack of clarity.

Could the authors explicitly answer the correct interpretation of the licensing?

Hello,

Such a wonderful font, but not able to make use of it in coding. It's horrible for the eyes trying to make distinguish between the below characters.
; : ' " ` , . = ( ) O0

Please save our eyes!! An Incredible font, should not go down without usage.!!

Hello I want like to use b612 for an opensrc-project. However it's lacking the macron i [ī] used in our Latin creed. Please add ī.