cmvnd / fonts Goto Github PK

On screen remains the top pixel of the vertical line |.

I made a similar post a while ago but then closed it (#29). I'd like to re-open.

Powerline symbols are advertised but the basic ones are not in the standard position. They should be:

U+2B80 --> U+E0B0
U+2B81 --> U+E0B1
U+2B82 --> U+E0B2
U+2B83 --> U+E0B3

It's a great font. I hope these changes can be implemented in the future.
Thanks for all your hard work.

P.S. I also noticed the character at U+276D should be at U+276F. This character is quite popular and is used for several prompt apps, including powerlevel10k and pure. The character currently in this position is thicker gets cut off on its right side.

I absolutely ADORE spectrum's berry font. Seriously, I have scoured as far as I could across the internet for bitmap fonts and berry is the only one that scratches my itch for the right character shapes and size for my screen. Tewii is nice, but I find it too... curvy for my tastes. Unfortunately, the only thing it lacks for me is a proper bold variant. I'm considering taking a shot at making it myself, but I have no idea where to begin. Do you have any tips?

Otherwise, are you aware of other fonts similar to berry? May have to try those in the mean time.

When you get the chance, could you port over a few curses characters? I'd like to use lemon to draw bar graphs, specifically using this: ─ (U+2500) character.

Hi!

I've been using Lemon on my system for many years now, where space was a constraint and a small readable font was required. Thanks for making it!

Recently, I've noticed instances of Lemon being replaced with boxes. A few hours of research later, it turns out that Pango 1.44 has dropped support for bitmap fonts. People are naturally upset.

There's one saving grace tho: "Note that Harfbuzz does support loading bitmap-only OpenType fonts."

So, would it be a lot of effort to (also) release your fonts in this format? I'm currently refusing to upgrade Pango, but that won't be maintanable forever. I'd rather not lose bitmap fonts.

Cheers!

Hi. Thanks for these fonts. They are really nice.
I noticed a problem in the lemon and berry fonts: some powerline symbols do not correspond to the now-standard code positions. See below:

U+2B80 --> U+E0B0
U+2B81 --> U+E0B1
U+2B82 --> U+E0B2
U+2B83 --> U+E0B3

Some others, too. Just a heads-up.
:)

Edit: Hmmm. Seems like the mistake is mine, and these glyphs are different than standard powerline. My apologies.

Sorry for the lame issue, but I was wondering what the glyph viewer you're using in the README is called :)

Kerning for uushi is decreased/distored when used in programs such as bar. Works without issue in terminals.

ex.

I've seen that some of the iconic glyphs are cut e.g. clock, temperature and few more. In fontforge I've found that they have wrong width. "Set width" to higher values fix the issue.

Hi,

With pango no longer supporting bitmap fonts, is it possible to get a ttf version of uushi? I love using the font but I will need to upgrade pango at some point on my machine.

https://gitlab.gnome.org/GNOME/pango/issues/386

Links open up to githubusercontent.com and only say not found.
If link copied from .md file, it opens up to web archive way back machine and http 302 response at crawl time.

This font has the Er letter for U+450 https://www.fileformat.info/info/unicode/char/0450/index.htm
It should be for U+420 https://www.fileformat.info/info/unicode/char/0420/index.htm
This should be added to the bdf:

``
STARTCHAR uni0420
ENCODING 1056
SWIDTH 480 0
DWIDTH 5 0
BBX 5 6 0 0
BITMAP
70
48
48
70
40
40
ENDCHAR

``

If I am not mistaken, currently the cpu icons, among some few other icons, are only implemented in the lemon font. Could you add the cpu icons (and eventually the other ones that uushi doesn't have) to uushi? This would be great as I am limited to using only one of your lovely fonts (and Lemon has a bit small icons for me).

When I display the date using the uushi font, I notice that the colons look rather misplaced, or maybe it's the preceding numbers that come too close. http://a.pomf.se/diarzt.png

I'm using herbstluftwm with Ubuntu 16.04

The issue has been like this since Ubuntu 12.04 but was able to workaround this by adding the install bash script as startup script. Anyway, I decided to submit this issue after I realized I can use Issues in Github.

ps: Thank you for the awesome font.

Here are the logs:

 ./install 
/usr/share/fonts: caching, new cache contents: 0 fonts, 5 dirs
/usr/share/fonts/X11: caching, new cache contents: 0 fonts, 4 dirs
/usr/share/fonts/X11/Type1: caching, new cache contents: 8 fonts, 0 dirs
/usr/share/fonts/X11/encodings: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/X11/encodings/large: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/X11/misc: caching, new cache contents: 59 fonts, 0 dirs
/usr/share/fonts/X11/util: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap: caching, new cache contents: 0 fonts, 5 dirs
/usr/share/fonts/cmap/adobe-cns1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-gb1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-japan1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-japan2: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-korea1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/opentype: caching, new cache contents: 0 fonts, 3 dirs
/usr/share/fonts/opentype/noto: caching, new cache contents: 36 fonts, 0 dirs
/usr/share/fonts/opentype/stix: caching, new cache contents: 29 fonts, 0 dirs
/usr/share/fonts/opentype/stix-word: caching, new cache contents: 5 fonts, 0 dirs
/usr/share/fonts/truetype: caching, new cache contents: 1 fonts, 21 dirs
/usr/share/fonts/truetype/abyssinica: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/ancient-scripts: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/dejavu: caching, new cache contents: 21 fonts, 0 dirs
/usr/share/fonts/truetype/fonts-guru-extra: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/freefont: caching, new cache contents: 12 fonts, 0 dirs
/usr/share/fonts/truetype/kacst: caching, new cache contents: 15 fonts, 0 dirs
/usr/share/fonts/truetype/kacst-one: caching, new cache contents: 2 fonts, 0 dirs
/usr/share/fonts/truetype/lao: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/lato: caching, new cache contents: 18 fonts, 0 dirs
/usr/share/fonts/truetype/liberation: caching, new cache contents: 16 fonts, 0 dirs
/usr/share/fonts/truetype/lohit-punjabi: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/nanum: caching, new cache contents: 6 fonts, 0 dirs
/usr/share/fonts/truetype/openoffice: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/padauk: caching, new cache contents: 4 fonts, 0 dirs
/usr/share/fonts/truetype/sinhala: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/takao-gothic: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/tibetan-machine: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/tlwg: caching, new cache contents: 58 fonts, 0 dirs
/usr/share/fonts/truetype/ttf-dejavu: caching, new cache contents: 21 fonts, 0 dirs
/usr/share/fonts/truetype/ttf-khmeros-core: caching, new cache contents: 2 fonts, 0 dirs
/usr/share/fonts/truetype/ubuntu-font-family: caching, new cache contents: 13 fonts, 0 dirs
/usr/share/fonts/type1: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/type1/gsfonts: caching, new cache contents: 35 fonts, 0 dirs
/usr/local/share/fonts: caching, new cache contents: 0 fonts, 0 dirs
/home/sohaeb/.local/share/fonts: skipping, no such directory
/home/sohaeb/.fonts: caching, new cache contents: 2 fonts, 0 dirs
Re-scanning /usr/share/fonts: caching, new cache contents: 0 fonts, 5 dirs
Re-scanning /usr/share/fonts/X11: caching, new cache contents: 0 fonts, 4 dirs
Re-scanning /usr/share/fonts/X11/encodings: caching, new cache contents: 0 fonts, 1 dirs
Re-scanning /usr/share/fonts/cmap: caching, new cache contents: 0 fonts, 5 dirs
Re-scanning /usr/share/fonts/opentype: caching, new cache contents: 0 fonts, 3 dirs
Re-scanning /usr/share/fonts/truetype: caching, new cache contents: 1 fonts, 21 dirs
Re-scanning /usr/share/fonts/type1: caching, new cache contents: 0 fonts, 1 dirs
/var/cache/fontconfig: not cleaning unwritable cache directory
/home/sohaeb/.cache/fontconfig: cleaning cache directory
/home/sohaeb/.fontconfig: not cleaning non-existent cache directory
fc-cache: succeeded

In certain programs such as xfd and dmenu, all the lowercase characters appear as the number 4. I'm using the X font string: -benis-lemon-medium-r-normal--10-110-75-75-m-50-iso8859-1

I've compiled the bdf to pcf using the latest version.

I'm using Arch with the infinality fontconfig bundle.

I am getting the following error when trying to install from the AUR:

ucs2any: FONT name in 'lemon-ISO8859-15.bdf' is '-benis-lemon-medium-r-normal--10-110-75-75-m-50-ISO8859-15' and not '*-ISO10646-1'!

Here is a screenshot of the error, in case the additional context is helpful:

It seems you removed them for the links being broken in this commit, but never replaced them with working image links?

Lemon is fantastic.

I use it as my main programming/text editing font, and I love it.

The only thing I miss from my previous font, Consolas, is the possibility of bold/italics. My IDE, in fact, supports syntax highlighting which can make certain C++ symbols bold or italic, and I would really like to use that feature with Lemon.

I do not know much about font creation, and even less about bitmap fonts, but is it possible to create a bold/italic for Lemon? (obviously handmade, to preserve quality).

If it is, and you do not want/have time to do it, is there any software I can use to try it myself?

Thanks.

I don't know what's the exact difference in font codes between powerline and airline but for airline power symbols don't show up.

Looks great, many thanks!

Hey I created a ttf version of lemon. I figure it would be more use to people if it were included in your repo, so I was wondering if you'd like me to migrate it over?

I can just keep my repo separate if its not worth the maintenance burden. Though maybe providing a link in your README would be useful to some people.

Thanks!

Edit: Fixed broken link