blobject / agave Goto Github PK

View Code? Open in Web Editor NEW

712.0 30.0 14.0 10.86 MB

succulent monospace programming font

Home Page: https://b.agaric.net/page/agave

License: MIT License

Tcl 100.00%

font typeface programming-font monospace monospace-font

agave's Introduction

NOTICE: github namespace recently changed from ~~agarick~~ to blobject.

version 37, 06 jan 2021

download	Regular	Bold
size	261KB	85KB
dotted zero	Agave-Regular.ttf	Agave-Bold.ttf
slashed zero	Agave-Regular-slashed.ttf	Agave-Bold-slashed.ttf

variant	glyph count	(partially) implemented ranges
Regular	2443	ascii, latin ext, greek, cyrillic, ipa, math, arrows, box-drawing, braille, powerline, others
Bold	96	ascii
Italic	15	not ready
BoldItalic	2	not ready

agave is a fixed-width outline typeface, designed and produced by type agaric.

Free to use, peruse, and diffuse – everything (font files, glyph designs, glyph databases, and documentation) is released under the MIT license.

more about: https://b.agaric.net/page/agave

install

The .ttf font files can be found at either of:

Please install according to common procedures specified by your platform. Maybe these pages might help: repology, howtogeek.

sample

2160x1440 screen resolution, 200 dpi, freetype v2.10.4, libXft v2.3.3, libpng v1.6.37, gimp v2.10.20

glyph distinction in ASCII

code, sampling C syntax (emacs v27.1, height 55)

terminal (alacritty v0.6.0, size 5.5)

literary text, sampling ASCII, Greek, Cyrillic, and Czech (alacritty v0.6.0, size 5.5)

cataclysm: dark days ahead (alacritty v0.6.0, size 5.5)

unicode (alacritty v0.6.0, size 5.5)

in the wild:
(particular glyph shapes may be out of date)

build

For example, with the Regular variant:

Open src/agave-r.sfd in FontForge.
Click File –> Generate Fonts –> pick TrueType, No Bitmap Fonts, No Rename –> Options: pick TrueType Hints, PS Glyph Names, OpenType –> Generate.
- You might see (and can ignore, I think) some warnings about non-integral coordinates, etc.
Hint the generated font file using ttfautohint.
- Assuming the generated file is raw.ttf, run ttfautohint -v -t raw.ttf Agave-Regular.ttf

naming

type agaric opted for a slightly eponymic name for their first typeface.
“Agave” refers either to the green plant or to the daughter of Kadmos in mythology.
agave is sister to autonoe and ino.

discussion

Feel free to use the issue tracker to voice your feedback, questions, and suggestions. Or contact type agaric via email at [email protected].

thanks

… foremost to bc, Inkscape, ttfautohint, and FontForge as I relied on them to respectively measure, draw, hint, and generate agave,

to GitHub for hosting this repo,

and to all the users ♥

agave's People

Contributors

Stargazers

Watchers

Forkers

egnawake gkqha aasutossh f-carraro nemw kittydev10 haunt98 strider zoomlogo eiromz qtgiebel iforking alexmyczko kylerchang

agave's Issues

make b, d, h, k shape more defined

consider adapting curves of c, n

make upper arm of k longer or end better

Swapped U+0281 and U+1D1A

The glyphs for U+0281 LATIN LETTER SMALL CAPITAL INVERTED R and U+1D1A LATIN LETTER SMALL CAPITAL TURNED R are swapped.

Doesn't work on Visual Studio Community 2019.

Hey!
I just fell in love with Agave. Trying to make it work in Visual Studio Community 2019 but i've failed.
(Visual Studio displays different font (Courier New for example) when i choose Agave from settings interface)
Does someone know workaround or fix for that?
Thanks.

Inconsistencies introduced in v27

The glyphs of ⟨a⟩ and ⟨f⟩ changed in version 27, but not the glyphs of all related characters:

U+00AA FEMININE ORDINAL INDICATOR
U+2090 LATIN SUBSCRIPT SMALL LETTER A
U+0192 LATIN SMALL LETTER F WITH HOOK
U+02A9 LATIN SMALL LETTER FENG DIGRAPH

FWIW, I think the sharper curve of ⟨f⟩ looks too lumpy. It is only really noticeable at large font sizes. It looks okay in the SVG, so perhaps something went wrong in the conversion to SFD.

powerline glyphs?

Hi! Long-time fan of this wonderful font!

Have you considered adding the powerline symbols/glyphs to this font?

Fiddling with fontconfig is a pain in the best of circumstances, and would be wonderful to see official support for this! Not sure how much work this involves so I apologize if it's a lot of work-- but I'd be interested in hearing your thoughts on this regardless!

Thanks, and thanks for this great font!

Questionable glyph for U+02AC LATIN LETTER BILABIAL PERCUSSIVE

In all other fonts that I know of, U+02AC LATIN LETTER BILABIAL PERCUSSIVE is a ⟨w⟩ above another ⟨w⟩. Is this rectilinear glyph intentional?

bold: ascii improvements

thicker curves
5: raise middle stroke
6,9: stem angle
D,P(,E,F,J): less side-bearing
M,W: subtler ink traps
X,Z: thicker stem
(b,d,e,g,h,k,n,p,q,r,u,y): less side-bearing
k,!,<,>,',`: thicker strokes
{,}: thinner strokes and better shape
@: top-right corner
%: fatter dots

SUGGESTION: Link "latest" to current release

Hi bud.

Great work as always.
I jump in every few days to get an updated copy and see if I can spot / appreciate the differences.

To that end, is there a way to link "latest" somehow straight to a download / zip?
I pull up latest then scroll down to "Assets" to get a TTF or just pull the master.zip from the home page.

Is pulling master.zip the recommended way to stay up-to-date or can you somehow link "latest" to the current TTF?

Thanks!

Misalignment and gaps in box-drawing characters

Hello! First of all, thank you for this awesome font!

My only issue with it is the gap in box-drawing characters.

An image to illustrate:

This is in Windows 10, using Notepad and Agave version 14.

maybe shift iota a bit left

make height of slash same as that of parens

Agave on Nerd Fonts!?

I was looking at Nerd Fonts collection on their website and they included Agave.
I didn't even knew that.
I feel good.

𝑛-ary operators are too short

n-ary mathematical operators should be taller than normal operators: U+220F N-ARY PRODUCT, U+2210 N-ARY COPRODUCT, and U+2211 N-ARY SUMMATION should descend below the baseline. The current glyph for U+2210 would be appropriate for U+2A3F AMALGAMATION OR COPRODUCT.

improve stroke thickness for u2201, u2211

u2201 (complement): narrower
u2211 (n-ary summation): thicker

NOTICE: agave font creator's github username is now "blobject"

I recently changed my github username from "agarick" to "blobject".

Please change your links that reference this repository to:

https://github.com/blobject/agave

Braille patterns have confusing spacing

The side bearings of the braille patterns are too small relative to the internal spacing between dots. For example, U+2831 is hard to distinguish from <U+2808, U+2806>. Table 703.3.1 of the ADA Accessibility Guidelines indicates the proper ratios.

lowercase letters (f,i,j,t) should be more consistent

Look at the picture

as you see the lowercase f,i,j,t are not in the same "wave".for more info you can read this reply

PS: @Agarick I couldn't come up with a better title.if you think its not good you can change that.

Inconsistencies introduced in v30

The x-heights of ⟨b⟩, ⟨d⟩, and ⟨h⟩ and the bottom corner of ⟨d⟩ changed in version 30, but not the glyphs of all related characters:

U+01C6 LATIN SMALL LETTER DZ WITH CARON
U+01F3 LATIN SMALL LETTER DZ
U+0238 LATIN SMALL LETTER DB DIGRAPH
U+02A4 LATIN SMALL LETTER DEZH DIGRAPH
U+0195 LATIN SMALL LETTER HV

While you’re updating x-heights, you might want to change U+01F6 LATIN CAPITAL LETTER HWAIR, the capital of U+0195, too.

Appreciation for making Agave

Hi !
My name is Catalin, I am a CS student ! I begin by saying I used so many fonts over the years in my programming environments, commercial and non-commercial ! I was obsessed to find the one that I like and stick with it! Easy to say, hard to do ! I used so many fonts that I can recognize them from screenshots !

Agave was almost always in my view but for some reasons I didn't test it too much(like in a real scenario, just some programming font test app).I recently rediscovered Agave font and I must say I feel sorry I didn't rediscovered earlier. It makes programming much more pleasant and also clean ! I now use it for all my projects and it feels good, it's like I feel the passion that was put into this and also my eye strain reduced significantly!
I understand why the dev process is a little bit irregular, time is everyone's enemy and best friend at the same time !

Looking forward to seeing this project evolve and become better(the italics and bolds would be a great feature) !
Thank you for your amazing work! If there is anything I can do as a programmer don't hesitate to ask ! I feel like supporting this project would be a great idea !
A friend you haven't made yet,
Catalin

How to build this font from source ?

Acutally I am trying to create italic variant using imagemagick by shear and kerning all svgs. But I don't know How can I combine those svg glyphs ?

agave v010 - goals/todo before official release?

Not to rush things if they're not ready, just hoping to help see this through-- so there's a release with shiny powerline goodness among other things!

Any details left to work on? Testing to be done? :)

U+23AF HORIZONTAL LINE EXTENSION is too low

The names list says U+23AF HORIZONTAL LINE EXTENSION is “used for extension of arrows”, so it should be aligned with horizontal arrows.

Ligatures?

I do not expect this anytime soon, but I want to put it out there : ligatures. Italics & Bold will be great, but I’d rather have fresh ligatures to use in my agave code in the future!

Also, thank you for creating this font. It Oozes unusual monospace beauty & helps your eyes over lengths of time. ✨🌵

top overshoot sinks the whole glyph down

edit: fixed links with namespace change

For glyphs with overshooting top diacritics, the diacritics are drawn successfully but the entire glyph is shifted down to compensate.

Can be seen in the screenshot https://github.com/blobject/agave/blob/37a7459e20a2dbf4fa02eaadda2650d31adc1f9a/img/lit.png
(in the greek section, the "E" in Eleates - screenshot taken in kitty on voidlinux, size 11, dpi 120)

Guessing that this began occurring when bounds were explicitly set, https://github.com/blobject/agave/releases/tag/v22

See also: cormullion / juliamono, issue 17

Unmatched bracket heights? Is this expected?

The image shows the unequal height of brackets.
Is this expected?

keep improving bowls

"e" - u00e6, u018f, u04bc-u04bd
"g" - u01e5, u0260
"p" - u00fe, u01a5, u0239, u048f
"q" - (u024a), u024b, u02a0
(rho)
(be)
update u02ae, u02af

slight improvements: comma-like, underscore, a, f, Yogh

a: improve shape
comma, semicolon, psili, dasia: more recognisable tadpole shape
underscore: slightly more space between two underscores
f: sharper curve if possible
Yogh: lessen top bowl

Inconsistent baselines for glyphs with descenders and vertical stems

Most glyphs that have descenders as well as vertical stems, such as U+014B, U+019E, and U+0220, shorten their vertical stems a bit so they float above the baseline. U+0267 LATIN SMALL LETTER HENG WITH HOOK and U+02A9 LATIN SMALL LETTER FENG DIGRAPH are exceptions.

Wrong glyph for U+0263 LATIN SMALL LETTER GAMMA

The glyph of U+0263 LATIN SMALL LETTER GAMMA would be fine for U+0194 LATIN CAPITAL LETTER GAMMA, but it is too tall for a lowercase letter. Here it is, with the existing U+0194 for comparison.

Stroke width of U+23B7 RADICAL SYMBOL BOTTOM

The stroke width of U+23B7 RADICAL SYMBOL BOTTOM is wider than that of other radical symbol pieces, which are unified with the box drawing symbols U+2502 and U+250C according to L2/00-159. Here it is below U+2502.

U+23B7 does, however, have the same width as U+23AE INTEGRAL EXTENSION, which L2/00-159 lists as an alternative to U+2502, but I think using U+2502 is preferable, since U+2502 has the same stroke width as U+250C for the corner piece, for which L2/00-159 lists no alternative.

U+0462 CYRILLIC CAPITAL LETTER YAT has misplaced crossbar

The crossbar of U+0462 CYRILLIC CAPITAL LETTER YAT should go through the vertical stroke, not on top of it.

add more math connectives

support more languages

code script (# users)

u0531-u058f armenian (12m)
u0591-u05f4 hebrew (14m)
u0606-u06ff arabic (660m)
u07c0-u07fa nko (? 20m)
u0900-u097f devanagari (608m)
u0981-u09fb bengali (265m)
u0a01-u0a75 gurmukhi (22m)
u0a81-u0af1 gujarati (48m)
u0e01-u0e5b thai (38m)
u0e81-u0edd lao (22m)
u0f00-u0fb9 tibetan (5m)
u10a0-u10ff georgian (4.5m)
u1100-u11ff hangul jamo (78m)

plan

Order of implementation: by number of users, starting with arabic and devanagari.
Will probably work on bold/italic variants of extant glyphs before getting into this.
Don't know when (or in what decade) implementation will occur, but the intention is there.

consideration filters

Only unicode range u0531-u1cff.
Only currently active scripts with at least a million users.
Only scripts with glyphs that can reliably fit into single boxes (still unsure about devanagari, bengali, gurmukhi, gujarati).
Only scripts that I can reference in Arial Unicode MS and TITUS Cyberbit Unicode.

Some editors can't find agave

Hi, as you already know, agave is the one. So I am trying to use it with a bunch of editors.

Android Studio doesn't find agave, same with Python IDLE.

But others, like gVim, PyCharm, IDEA, Sublime Text, VS Code can locate the font.

Are those specific software problems or font issues?

remove P, V decorations

Always felt that the quirks in the designs of "P" and "V" were too whimsical (the stroke on "V" was to distinguish it from logical_or; the cut off in "P" has no excuse).

https://github.com/Trabincle/agave-earth convinces me to revert back to plain, standard designs.

Seeing as modifications are sparse, this single edit will (finally) finalise version 009 of agave.

U+2201 COMPLEMENT looks like ⟨C⟩

U+2201 COMPLEMENT looks identical to U+0043 LATIN CAPITAL LETTER C. It should look more stretched, as in \complement in LaTeX.

why the line-height changed?

One of the main reasons that I liked agave was the line-height.It was so compact (but completely legible) and I could have more lines in my terminal (for example in vim) but unfortunately v16 changed the line-height.for example before that I could have 43 line in my terminal but now I just have 37 line and I think 6 line less is a big change.I don't know anything about font designing but I hope the line height can get back to v15.(sorry for my English)
screenshot is from neovim.
left is v21 ... right is v15
https://0x0.st/iv_I.png

bold, italic, bold-italic

do it

Inconsistencies introduced in v32

Version 32 missed some ⟨e⟩-like letters when the corner of ⟨e⟩ was rounded.

U+0153 LATIN SMALL LIGATURE OE
U+025A LATIN SMALL LETTER SCHWA WITH HOOK
U+04BC CYRILLIC CAPITAL LETTER ABKHASIAN CHE
U+04DA CYRILLIC CAPITAL LETTER SCHWA WITH DIAERESIS
U+1D14 LATIN SMALL LETTER TURNED OE
U+2091 LATIN SUBSCRIPT SMALL LETTER E
U+2094 LATIN SUBSCRIPT SMALL LETTER SCHWA

Missing bars on palatalized Komi letters

The palatalized Komi letters U+0502..U+0505 and U+0508..U+050F should have horizontal bars upon their upwards curls. Currently, U+050C..U+050D have only the left half of the bar, and the rest have no bar at all.

There are plenty of examples in the “на молодцовском алфавите 1920-тых годов” section of this Komi book list. In all the sans-serif text in those books, I only found two counterexamples, both on the title page of Шонді југӧр (1926) in “ЛЫԂԂӦГПАНЫԌ”, though the rest of the sans-serif text within that book follows the general pattern. Here is another Komi book list.

U+027F LATIN SMALL LETTER REVERSED R WITH FISHHOOK should have a descender

U+027F LATIN SMALL LETTER REVERSED R WITH FISHHOOK should have a descender: the code chart says “preferred presentation is with a descender”.

RFC: change lowercase l letter to make it more distinguish from number 1

I think the current lowercase l is too similar with number 1.I have two suggestion
1. erase the left-bottom part of the current l to make it more distinguish
left is current version - right is modified by me in gimp :)

2. borrow the lowercase l from ubuntu mono font.
In my eyes agave looks a bit similar with ubuntu mono font so maybe we can barrow the lowercase l from that.
left is current version - right is lowercase l from ubuntu mono font

Yogh looks like ezh

The top of U+021C LATIN CAPITAL LETTER YOGH and U+021D LATIN SMALL LETTER YOGH should be round, unlike U+01B7 LATIN CAPITAL LETTER EZH and U+0292 LATIN SMALL LETTER EZH.

Visual Studio Community 2019 renders Agave poorly.

After i installed the new version of agave from here it works in VSCommunity but it renders the font poorly. (I guess it might be some anti-aliasing problem with VSCommunity, not sure)

Here is the example screenshot.

The font size is 10 in this picture.
Thanks.

finish fixing box-drawing (block and shade) glyph gaps and add more glyphs

try overshooting by 64 only
decide whether to overshoot shade (test on different programs)
add u256d-u257f
add sample that utilises all the box-drawing glyphs

'z' height above bar for 'f', 't'?

Hi!

I'm not actually sure if this is a feature or a bug, but thought I'd ask :).

Image demonstrating:

I put 'z' in the middle so it pops.

I was staring closely at the glyphs after updating to v30 and noticed this and was wondering if it's intentional,
and assuming it is :), out of curiosity why? (if you don't mind explaining, I'm just curious ^_^)

provide short line-height variant or not

In the 009 release, without preamble, I simply did away with the *-just.ttf file, which had provided an agave with a shorter line-height (and a corresponding inability to see diacritics on certain glyphs).

I justify my choice to remove the variant on the grounds of simplicity and of duplicate functionality with terminals and text editors that allow changing line-heights -- but it was wrong of me to get rid of it without warning.

If any user wants the *-just.ttf back, please leave a comment. Otherwise, this issue will be closed in a week should it get no response; please reopen as you see fit.

currency
math operators
music
weather
shapes and arrows