source-foundry / alt-hack Goto Github PK

(u00EC) igrave slab style to complete the i slab variant.

New shell script added to repository in #40. Add CI testing with shellcheck.

PR #7

Propose:

• black on white screenshot of the glyphs x 4 variants at font size of ____ that is included in a Markdown file at the Unicode label directory root of the Unicode code point.

Propose the following paths from the root of the repository for each Unicode position:

glyphs
    ├── uXXX
          ├── bold
          ├── bolditalic
          ├── italic
          ├── regular

with the *.glif file under the respective variant directory. For ASCII set glyphs, we will need to consider another level of subdirectories that include manual hinting modifications when they are used in the main set.

This won't support multiple glyphs at a single Unicode code point. How do we address that? With an additional string after the Unicode path like this maybe?

glyphs
    ├── uXXX-slashed
          ├── bold
          ├── bolditalic
          ├── italic
          ├── regular
    ├── uXXX-dotted
          ├── bold
          ├── bolditalic
          ├── italic
          ├── regular

Thoughts @jublo @burodepeper?

cc:@jublo @burodepeper

Hi Hack developers!

First of all, thanks for making this wonderful monospace font. Is there a way add a custom patch for '#' and '%'?

Thanks!

Feel free to link to my site in the README or wherever you want.
https://equwal.com/alt-hacks.html

I'm hosting some opinionated variants there. Of course, I can't host all variants there, but if anyone asks I'll generate a variant and add it.

Setting up pip and compiling yourself a Hack can be a lot for some users. I have had conversations specifically about the i and 0 glyphs, which are controversial.

Why not include a small subset of possible permutations? That is what I am doing at https://github.com/equwal/alt-hack0, but I think it would be nice to do them here.

Here are my proposed variants to include:

1. Dotted zero
2. Forwardslashed zero
3. Slabbed i with unslabbed one.

./generator.ros dot
./generator.ros forwardslash
./generator.ros slabi noslab1
./generator.ros dot slabi noslab1
./generator.ros forwardslash slabi noslab1

Here is a chat log from a few minutes ago on #lisp

<_death> with hack I find the "i" glyph jarring..

And paraphrasing a source I've lost track of

"You know you can change that zero right?"
"Yeah but it is kind of hard and the script doesn't work."

I believe I'm not the only one who prefers the original version of U+0031 (digit 1) with a less angled top stroke, which was replaced by the current steep angle in version 3.001.
I've therefore been using version 3.000 but I'd love to see alt-hack provide this config option so I can enjoy other updates of latest versions, while still keeping my digit 1 with a flat angled top stroke.

Old digit 1 (my preferred style)

New digit 1 after v3.001 (steeper angle: more legible, but less aesthetically pleasing IMHO)

cc: @jublo @burodepeper

Design by @dok42

I believe I'm not the only one who prefers the old version of U+0031 (digit 1) with a less angled top stroke, which was replaced by the current steep angle in version 3.001.
I've therefore been using version 3.000 but I'd love to see alt-hack provide this config option so I can enjoy other updates of latest versions, while still keeping my digit 1 with a flat angled top stroke.

Old digit 1 (my preferred style)

New digit 1 after v3.001 (steeper angle: more legible, but less aesthetically pleasing IMHO)

PR #23

@vl4dimir any interest in adding support for command line options to specify the patched glyph names and the repo root path? This would permit automation with this script (including the release of patched alternate versions of Hack) and would support CI testing of the source patch process.