Help with this experiment! about juliamono HOT 39 CLOSED

Linux, with FullHD display. Running vim inside the Kitty terminal. JuliaMono-Medium at 10pt, without any sub-pixel antialiasing:

At 10 pt some of the characters look like they're bouncing around a bit, as described in #3, but I am still very much enjoying this font and have set it as the default for my terminal. Awesome work!

from juliamono.

ArchLinux, 1440p, font smoothing

from juliamono.

Dell LAtitude 5400 laptop. Display is Philips 25 inch monitor 2560x1440
Editor is Atom 1.50.0-beta0
Font should be JuliaMono at 17 points - apologies if this is FiraCode - I did try to configure it cirrectly

from juliamono.

Now looks great on v0.004!

from juliamono.

Hello,

with v0.004 on ubuntu 16.04, screen is samsung 24" 1920x1080, Xft.dpi: 92, Xft.antialias: true, Xft.hinting: true, Xft.hintstyle: hintsnone.
I usually first open files in vim in an xterm (using my default terminal font) and eventually remember to switch to gvim later. So two screenshots are attached, one with vim in xterm (xterm -fa "JuliaMono" -fs 12) and one in gvim (Regular, 12pt).

Probably I am not your typical user :-) Hope this helps anyway and thank you for the interesting project !

from juliamono.

Here is julia/base/ntuple.jl using emacs in Manjaro Linux and KDE Plasma. The monitor is a BenQ GW2765HT 27.0" 2560x1440 Monitor.

and here's some REPL tomfoolery:

from juliamono.

@MasonProtter Thanks - that's looking good! What terminal is it? I see you're not getting the contextual alternates by default. (eg -> to →).

Hi @cormullion , that wasn't a terminal it was the emacs GUI and getting ligature support in the emacs GUI is possible, but I never learned how to do it. Here's evidence that the ligatures are working properly in Konsole.

from juliamono.

Thanks - results are disappointing, there's quite a difference between the various platforms, which I didn't really anticipate. I'll probably switch from CFF to TTF internally, although that will make the files bigger...

@simeonschaub I appreciate your testing! :)

from juliamono.

• VS Code
• 12pt
• macOS 10.15.5
• 1920 x 1200

from juliamono.

I ended up using 13pt instead which seems to be better.

from juliamono.

It's a MacBook Pro 2018. My font smoothing is turned on already

from juliamono.

MacBook Pro (Retina, 13-inch, Mid 2014), 2560 x 1600.
Editor is Atom 1.49.0 with 12pt font.

from juliamono.

Just tried it on the Retina display rather than my 1900x1200 external monitor - it indeed looks better:

Even this screenshot on my external monitor looks less fuzzier than the actual rendered version ...?

from juliamono.

MacbBook Pro 2012 running Ubuntu, 1280x800, antialias, slight autohinting

you can see why I was optimistic about quality - I thought that if this was 2012 quality it would be better in 2020...

from juliamono.

@hearnsj Thanks - looks better at 17point... :) My eyes are not compatible with 10point text...

from juliamono.

@xukai92 Thanks! Seems fairly accurate rendering if a little fuzzier...

from juliamono.

Yes, I like larger sizes... :) Apple don't do font-hinting, so I suspect it won't get any better for Mac users. There's the Font smoothing option:

and that's about it. Is it a new Mac?

from juliamono.

@myrddin89 Thanks - one of the best environments for this!

from juliamono.

The screenshot from @myrddin89 looks much smoother than mine. What makes the difference here?

from juliamono.

@xukai92 I noticed your image was a little fuzzier... do you have a Retina display?

from juliamono.

It well may be the Retina resolution, I usually notice the difference, especially after a while I don’t use a non Retina monitor.

from juliamono.

@ckoe-bccms Thanks very much! It doesn't look too bad... 🤣

I think if I was using this setup, I'd choose the alternate designs for /a and /g... :) I know how to do this in Atom and VS-Code, and Kitty, but not in any other terminal app... 😕

from juliamono.

@MasonProtter Thanks - that's looking good! What terminal is it? I see you're not getting the contextual alternates by default. (eg -> to →).

from juliamono.

@MasonProtter Probably a few lines of LISP should do the trick.. :)

from juliamono.

@apparluk Thanks - I'm really looking to see what I can't see from my computer - namely how it looks on other people's.

from juliamono.

OS: Linux Mint 19.3 Tricia x86_64
Host: Aspire E5-575 V1.25
Resolution: 1920x1080
Editor: VS Code
Font Size: 14

from juliamono.

@EarthGoddessDude Thanks - that looks pretty acceptable, VS-Code does a good job I think.

@apparluk Thanks - considering the low resolution that's working quite well. But this won't be the best font for this environment... 😥

from juliamono.

@MasonProtter Hi! In emacs (on gnu/linux) I could enable ligatures on julia mono with code found for fira font (the one using set-char-table-range worked). (but emacs started freezing on certain buffers)

However, in general, my emacs window is rendering juliamono too bold (compared to your screenshot/rendering in other programs). How did you set it? With

(set-frame-font "JuliaMono 8")

this is the result

from juliamono.

No idea about emacs, but there's a Light version of the font. But much depends on the quality of the environment you have...

from juliamono.

The problem is that fc-match select the medium variant instead of the regular:

fc-match -v juliamono-20:weight=normal |grep file:
        file: "/home/nixo/.guix-profile/share/fonts/truetype/JuliaMono-Medium.ttf"(w)

from juliamono.

Errr... I have only five minutes of emacs experience, so I can't really help. A wild suggestion is to delete all the weights you don't need, leave just the one, and see if you can persuade your system to reluctantly use the only one that matches... ¯\_(ツ)_/¯

from juliamono.

I'm not 100% sure, but opening the JuliaMono-Medium with fontforge, element -> fontinfo -> ttf names -> styles (subfamily) shows Regular. Shouldn't it be "Medium"?

from juliamono.

Hack Bold -> Bold. Hack Regular -> Regular, JuliaMono Regular -> Regular...

from juliamono.

FontForge says Regular whatever you load:

When created, the family is "JuliaMono".

... there's no other box to type stuff.

Probably, when you open a single font in FontForge, it has no idea whether that one font is part of a family. Whereas, when created, the various instances are created as a family - they have to be, since they're interpolated masters called "Light", "Regular", "Medium", and so on.

from juliamono.

Are you sure it's the same for other fonts, and not only for juliamono?
Here's what I get with Hack Bold:

In your second screenshot, maybe it should be a custom parameter?

from juliamono.

Who knows ... it works everywhere else... 🤷

from juliamono.

Well yes, but fc-cache is from fontconfig, and it returns the wrong font. If manually setting the weight does works, that does not mean that the subfamily is correct.
In emacs, for example, I can set the right subfamily (i.e.: using the regular variant) by specifying the weight to book. But if it automatically sets the wrong one, maybe it's something related to the font itself (in hack is specified here: https://github.com/source-foundry/Hack/blob/1eddf943125a3f06945b86dbb7f55704a517331c/source/Hack-Regular.ufo/fontinfo.plist#L94).

But I do not know enough about fonts, maybe someone else.
By the way, will you share the sources you use to build TTFs?

Thanks!

from juliamono.

Sadly I don't really have the resources or skills to troubleshoot Linux or Windows issues, to be honest, and this little experiment designed for a 10 minute JuliaCon presentation probably won't satisfy everyone's needs.

Hack's a fine font, developed with open source tools by folks who know what they're doing - you may prefer to stick with them. 😂

from juliamono.

But I like JuliaMono, and with the workaround (weight=book) is working fine, I just wanted to fix this. But it might be my setup broken as well.

(By the way, the patch I submitted to the guix repository adding JuliaMono has been merged: https://issues.guix.gnu.org/44410)

from juliamono.