Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closing single quote issue #59

Closed
kartynnik opened this issue Dec 22, 2015 · 7 comments
Closed

Closing single quote issue #59

kartynnik opened this issue Dec 22, 2015 · 7 comments

Comments

@kartynnik
Copy link

In GCC output, single quotes are distinct from apostrophes:

../fstext/deterministic-fst-compo.h:96:12: error: ‘state_table_’ was not declared in this scope

I get the following rendering issue with Fantasque Sans Mono Bold 1.7 on this line:
image

@belluzj
Copy link
Owner

belluzj commented Dec 23, 2015

I can't reproduce. Which OS and terminal are you using? At what size?

@kartynnik
Copy link
Author

kartynnik commented Dec 23, 2015

Gnome Terminal, Ubuntu, Fantasque Sans Mono Bold 14.
This behavior may also be attributed to Infinality being installed. Would be great if someone could try to reproduce on a vanilla Ubuntu installation.

@kartynnik
Copy link
Author

This may also be connected with LC_ALL=en_US.UTF-8 (I mean, that the programs do use the curved closing bracket instead of the plain apostrophe). The same rendering was observed with the string

mv: cannot move ‘.config/nvimrc’ to ‘.config/nvim/init.vim’: No such file or directory

@kartynnik
Copy link
Author

Interestingly, this issue doesn't come up with the released fonts - I had built them from sources.
Closing the issue, sorry for the false alarm.
I'll try to find out which versions of FontForge etc. I was using to build the fonts - just in case it would be helpful to warn against using them somewhere.

@kartynnik
Copy link
Author

The FontForge version available in Ubuntu repositories is 20120731, which seems ancient.
@belluzj, which one do you use?

@belluzj
Copy link
Owner

belluzj commented Jan 8, 2016

@kartynnik
Copy link
Author

Replacing the outdated FontForge version with the one from the PPA seems to resolve the issue.
Added the PR #61 to warn about that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants