Hi everybody,

the font looks great, but it's so tiny, I must be at 3cm to be able to see it on my terminal, can someone help me ? I tried in the tweak application to make it bigger, but no differences.

I love the font running on my Linux laptop but I really wish if it can come to Windows as it appears to be an easy process. Is it coming anytime soon?

I did not know that enabling bitmap fonts would have some side-effects. I'm sure but something seems wrong with my the text in Chrome(just as if it's using a new font altogether). I don't like it.

Please help me disable bitmap fonts. I enabled them as mentioned in the README:

cd /etc/fonts/conf.d/
sudo rm /etc/fonts/conf.d/10* && sudo rm -rf 70-no-bitmaps.conf && sudo ln -s ../conf.avail/70-yes-bitmaps.conf
sudo dpkg-reconfigure fontconfig

Thanks in advance!

Hi, 22pxworks but it's still small on my screen :/ Can we make a 44px version for high dpi screen?

I guess all I need to do is to change all the 2 for 4 in doubler.py and run py doubler.py ?

Thanks and really nice font!

off topic
Color scheme from the screenshots?

I would like to use scientifica on a webpage of mine as the default font, knowing not too many people will have scientifica installed I looked for a way to @import this but I didn't find any, could you create one or tell me another way?

The current blocky style does not suit the font.

I have created a small caps version, to replace this 'bold' version.

Here are some previews:

Tell me what you think.

First off, thank you for supporting Turkish character set :)

Turkish characters Ş (U+015E, Latin capital letter S with cedilla) and ğ (U+011F Latin small letter g with breve) display an unnecessary space after them, the rest of the Turkish character set are fine;

Here's how it should look, using Noto Sans;

Having a PSF version of this font would be great for the linux famebuffer!
Also PF2 for grub would be great!

I'm not really clear on why this is happening, but st seems to be displaying scientifica glyphs twice as wide as they should be:

I noticed that after opening and saving with gbdfed, the issue goes away:

You can see what it does here: https://github.com/ma9e/scientifica/commit/bfa52a3d14c5dcf0975f0a1077072361b8bf15bc

So my hypothesis is that the bounding boxes are getting st confused. Not sure. Would you be opposed to just opening and saving all of the bdf files this way? I haven't checked but I can't imagine it would affect the size of the compressed .pcf.gz files much.

Many lines in the lines 1598~8720 of the FontForge glyph database have widths of 1000 rather than the intended 454.

Since my system's language is Polish, this leads to weird spaces after the Polish-exclusive letters (except ó, which exists in Latin-1 Supplement).

The correct text displayed using a normal font should be Zażółć gęślą jaźń. 1234567890.

Related to #55, but that issue was too specific.

So when I run doubler.py (which I assume is to systematically increase the size of the font), it doesn't ever get past this line:

bdf = reader.read_bdf(sys.stdin)

It just holds and doesn't do anything. Am I missing something about how to run the program, or does it just take a long time?

Also, side note- I'm absolutely loving this font, the cursive for italics is my favorite thing ever, and I want to say thanks for continually working on it :)

Can we put the OFL [1], an official FSF font license [2] on the font? Heres what it gives as its overview:

We want to:
enable others to participate in our projects
enable others to cater to needs for which we don't have the resources
share our wealth of knowledge and experience in the area of writing systems and pass on our tools
equip the community to meet its font needs

[1] http://scripts.sil.org/OFL

[2] https://www.gnu.org/licenses/license-list.html#Fonts

Is there any documentation on the doubler script? I assume it is supposed to increase the font's size by two but I don't really know a lot about fonts and how they work. The size 11 is far too small on my high DPI display so I figured I would try the script before moving on to a different font for me. I tried running the script like

python3 doubler.py < scientifica-11.bdf

But I get this error:

Traceback (most recent call last):
  File "doubler.py", line 30, in <module>
    bdf = reader.read_bdf(sys.stdin)
  File "/home/cnnr/.local/lib/python3.5/site-packages/bdflib/reader.py", line 117, in read_bdf
    [_read_property(iterable, font) for i in range(propertyCount)]
  File "/home/cnnr/.local/lib/python3.5/site-packages/bdflib/reader.py", line 117, in <listcomp>
    [_read_property(iterable, font) for i in range(propertyCount)]
  File "/home/cnnr/.local/lib/python3.5/site-packages/bdflib/reader.py", line 66, in _read_property
    key, value = iterable.next().strip().split(' ', 1)
AttributeError: 'generator' object has no attribute 'next'

Any help would be appreciated, thanks.

Hello. I recently installed the ttf version of scientifica and started using it in Konsole, but am noticing that some glyphs (the plus, times, boxtimes and arrow symbol from my experience) are slightly but noticeably off center when surrounded by parentheses. The screenshot below shows that they seem to be slightly biased towards the right.

Do you think this is an artifact of my setup or something to do with the font itself?

PS: Thanks for your work on scientifica and curie, they're two of my favorite fonts!

The italic ttf variant is mislabelled as Medium. Just notifying :)

Amazing font, btw. Keep up the great work.

When I try using scientifica on my terminal, it ends up looking tiny. Is there a way to increase the size of the font?

You should upload the images to github and use a relative path in your README.md such as

[image-alt-tag](screenshots/screenshot.png)

0x0 seems to have deleted the images, so they no longer show up in the README.md

I downloaded the v2.2 tarball, to try manually building it before using it in an xbps-src template. (it's akin to a PKGBUILD for pacman)

No matter what flags I pass to tar, it returns some variant of "tar: This does not look like a tar archive".

scientifica.tar works fine, but as xbps would install it to /usr/share/fonts, I'd like to build it myself. (per xbps conventions for building font packages)

Greetings, I've installed the ttf version of scientifica. Since that the font is not rendering to well

Screenshot

As you can see the font doesn't look sharp, is more like blur

Can this font work well on Windows or would you need to make a port for it?

The current font size is way too wee when used on a retina/HiDPI display.

Hello again. Not sure whether this is something that can be resolved for all sizes (I'm not super familiar with how fonts work), but I noticed that the powerline triangular delimiter thing doesn't quite fill its row at all sizes of the ttf font. In my Konsole setup, the glyph lines up perfectly at font size 8, but is slightly misaligned at larger sizes until it lined up again at 25 point size.

Excellent font.

I noticed some box drawing glyphs (e.g. '├') have inconsistent width.
Box drawing isn't seen often, but is super useful for https://gresyk.dev/features/2018/01/15/hfsm-magic.html

Hi!
What's about adding cyrillic symbols?

Nice work on the font, using it right now on my laptop but specially on a couple of raspberry pi attached to small lcd screens that display various info.

Just checked you also made a .fon version that technically works on Windows systems and even though it's pretty much working no problems I'm getting a weird "ÿ" character instead of "❯" when using it with ConEmu as you can see on my screencap.

The other font used is Knack NF which somehow has full support for every symbol I've seen so far.

Is this expected? Is it fixable?

Not sure if it's intended but the ligatures have spaces between the characters, which don't look so nice in my opinion. For example the left arrow has no space while the right arrow has one empty pixel .
The shown file is creep's arrowtest.hs using creep.vim.

I'd like to package scientifica for my distribution, and I'd like to refer to a specific version instead of just “the latest master” or “commit hash x”. Do you think it would be possible to tag commits you deem relevant with a version number x.y.z?

Everything that isn't in bold is shown as a unicode box

(Note, the box before "Chats" is expected, it's an emoji)

Here's my dunstrc;
https://gist.github.com/anonaii/a0115432fb3e8b3c51f28654d184532a

Since curie has it, is it possible for scientifica to have it as well?

Do you have plans to make a .ttf variant of scientifica? I really like your font, and I would quite like to use it on my Android phone as well. I've grabbed the Niivu conversion, but that's a bit out of date and doesn't have the bold variant.

I would be happy to do it myself, but I don't know the first thing about manipulating fonts. If you have some pointers on what I should do to convert the font myself, I would really appreciate it.

I just installed the font and the very thing I noticed is that the font looks completely different than how it looks in the screenshots on the readme page and r/unixporn. I don't know if I am doing something wrong. I installed it over the AUR (also tried installing manually) and followed the installation steps on the readme.md and this is how it looks on my urxvt:

For example the "a" is completely different.

An issue I've encountered with scientifica is the impossibility to display properly "utf pixel arts" with block characters due to scientifica's uncomplete half-block character U+2584 (and the absence of the upper-half block U+2580 character).

Scientifica :

Any other font:

Such pixel arts in terminal can be rendered with catimg or [batimg] (https://github.com/kugge/batimg), a tool of mine. It can also happen in some softwares such as cava.
It would be great to display those pixel arts with scientifica.

The font is much smaller in terminal windows than it is any other appIication. I suppose it may have something to do with resolution settings, but I really don't understand why it's happening. Hoping you might be able and willing to offer some insight. thanks.

The glyph for U+019D LATIN CAPITAL LETTER N WITH LEFT HOOK is wrong: the hook is on the right side but should be on the left side.

These look brilliant fantastic, any chance you could generate windows/webfont compatible versions?

I'd like to know what files I would need to restore in /etc/fonts/conf.d/ if I decide to reverse the instructions provided for this font.
Thanks. I'm on Ubuntu 19.10.

The glyphs of U+2039 SINGLE LEFT-POINTING ANGLE QUOTATION MARK and U+203A SINGLE RIGHT-POINTING ANGLE QUOTATION MARK are wrong.

The glyph for U+00DD LATIN CAPITAL LETTER Y WITH ACUTE lacks a pixel at the bottom right which U+0059 LATIN CAPITAL LETTER Y and other glyphs based on it have.

I code in Elixir and use the pipe |> operator pretty frequently. I would love to see a ligature for |> as this font is otherwise perfect. Fira Code is a good reference, of course in bitmap it would be a bit trickier. Anything that matches the > to the height of the | would be welcome as well, but a complete triangle would be great. Thanks for this great font.

All polish characters seem to have a gap between them in firefox and some other apps when using scientifica size 8 on arch linux with the display resolution of 1336x768. (URL bar)
http://raii.cf/huh.png

Many glyphs have excessive right side bearings. For example, here is “(Ă)”.

So I really love the look of this font, and have been able to enjoy using it briefly. Unfortunately whenever I try to use this font for a program it seems to have an issue. The issue is all the character turn into blocks instead of your font. When I use it for rxvt it makes it so I can't open it with i3. When I use it with rofi all the characters are blocks, but it still works. And in the i3 config i3bar appears all as blocks.

Thanks again, I would really appreciate it if I could start using your font again.

Reading through other issues, the doubler.py script doesn't seem to work, and Curie is still too small on higher DPI displays(such as my ~109 DPI monitor). Would integer scaled versions for 2x, 3x, etc., be possible?

The loop of U+01AA LATIN LETTER REVERSED ESH LOOP is incomplete.

I'm not sure if I'm being a complete idiot here and this is how bitmap fonts work, but I can't set the size of the font anywhere - it doesn't scale up, and it's extremely tiny. Readable, but tiny. What could be wrong here? I'm not sure what info precisely to provide since I'm nowhere near sure where this could originate. I'm using the AUR package, but cloning and symlinking produces the same result.

scientificaItalic.ttf should show scientifica:style=Italic when fc-list | grep scientifica

as the title says
i did all instructions in the install readme even tough it's a little out dated
i did fc-list | grep scientifica, it's all there
kitty works with other fonts
i got told that kitty expects to have spacing either 100 or 90 but scientifica has 110(?)
is there a workaround to make it work in kitty?