In the next several days I'll probably start looking into bold and/or italic design. If anyone currently trying out agave would like to see particular features or have certain expectations in those styles, please don't hesitate to jump in and mention them.
]]>my new favourite monospace font
Yay!
I hope maths glyphs are in your todo list
Certainly, and I'm open to any calls for addition/improvement, so my todo list is pretty loose.
Feel free to let me know if there are particular math symbols you'd like to see implemented -- for the sake of expedience you see; there are quite a few mathematical symbols and a lot of them look rather obscure to my untrained eyes.
You could also make a more formal request by using the bitbucket bug report if you so wish.
]]>Your note on the diacritics is helpful.
As you might imagine, it's a bit challenging to make psili and dasia distinct at small sizes, and especially so, considering the limited space that I've allotted to accents and diacritics (limited, that is, for the sake of regularity).
I've made an attempt at an improvement (AUR package revision 3-5), but I'm uncertain that it'll completely fix things, so I'll keep working on it. Hmph, if only this were a bitmap font... :-P
]]>I should mention that I rarely type or read greek, so I don't have the same "aesthetic handle" on its letters as I do the latin ones. Therefore any suggestion or criticism could be quite helpful -- even on little things like the shape of alpha, lack of curvature on pi, indistinct psili/dasia, etc.
Enjoy!
]]>Looking forward to an AUR package so I don't have to keep track of updates myself.
Done, ttf-agave. Updated the first post with the AUR link.
]]>@dauerbaustelle
Very much appreciate the AUR upload.
AUR registration seems to be having a little spam issue, so as soon as it lifts, I'm all over it.
I had also made a PKGBUILD meanwhile, and it's pretty much like yours except the use of package() instead of build(); not explicitly extracting the tarball (I think makepkg does this for us); and some license shtuff (as per these threads).
edit: license is now that of MIT X.
Also, does anyone know of a de facto (or documented) way of naming font packages? Why are there both foo-font and ttf-foo type names? I've searched forum/wiki to no avail.
edit: I realised that most truetype fonts on pacman have ttf- prefixes. So I'm sticking to that.
To update the package, download the source tarball (menu on the right) and edit the PKGBUILD: pkgver/pkgrel and sha51sums. The meaning of these options is described here: https://wiki.archlinux.org/index.php/PKGBUILD
Then use
makepkg --source
to create the updated package and submit it to the site using "submit" in the top menu. There are also tools that automate the submission process, see wiki.
]]>