kreativekorp / open-relay Goto Github PK

for fairfaxHD, it has a very large margin on the first line for some reason. this did not happen in a december version of the font. it also does not apply to the SMHD version.
see example in this font viewing app:

used as a font in other apps:

not sure what causes this yet.

Family Basic was a Basic interpreter for the Famicom which had a font with 104 Semigraphical characters that are taken from background tiles of other early Nintendo games. Seems like a good fit for Kreative Square though converting it to 1bpp will be a challenge.

There's a "Charset A" as well, but it's only for sprites and despite being given the ability to make it the main Charset it doesn't work as a font.

Looks like there are issues for sure with: ᛋᛟᚢᛈ᛫​᛬​ᛏᛢᚹᛞᚱ​

And there could be issues with some runes that are not shown like: ᛇᛠ

https://bulbapedia.bulbagarden.net/wiki/Character_encoding_(Generation_V%E2%80%93present)

You already have the Generation 1 ones but Pokémon added quite a few interesting characters since then.

• Disunified fullwidth and halfwidth dingbats and emoji
• Proprietary Picture Emoticons (halfwidth and fullwidth)
• Precomposed superscript ^er and ^re
• Sleep symbol _z^z (halfwidth and fullwidth)

There are also "bag item" symbols which can't be typed in game but are instead used for in game text and the bag.

Nintendo Consoles also include a font containing UI elements and button prompts from the DS to the Switch. Most interestingly the Pictochat logo

Though if it were up to me I think it would be better to have a "button prompt block" similar to Promptfont that includes button prompts for old and new systems alike. Such as the roman numeral numbered buttons on the TurbografX16 or the keypad on the Colecovision.

I am not sure if those are within scope of the UCSUR. Hylian is a conscript used in The Legend of Zelda... actually multiple conscripts as you can see here. Similar to the Standard Galactic Alphabet from Commander Keen and Minecraft. Though this opens the door for the mess that's Inkling script

Borginian is a conscript from the Ace Attorney series from the fictional country of Borginia from Dino Crisis. As far as anyone knows it's has no phonetic meaning and is internally mapped to Cyrillic codepoints. There are only 17 letters in the script so it can't be based on Latin, Cyrillic or Kana. Here's the font I grabbed from one of the game's files.

In Constructium, U+04C5 CYRILLIC CAPITAL LETTER EL WITH TAIL has no tail: it looks identical to U+041B CYRILLIC CAPITAL LETTER EL.

I have an archive of a page with almost all of the scripts:

http://web.archive.org/web/20171210193150/https://www.prismnet.com/~hmiller/lang/KolagianWriting.html

(The page is still up unarchived, but not the images. That archive should have all the images.)

Just thought I'd show you this, you can now add them to Fairfax HD and others if you want.

Based on Lucitone's binary notation. On which the youtube video the best way to count by the best way to count is based.

I haven't selected codepoints yet. I am discussing it with an internet friend and we are in disagreement on what the codepoints should be.

The characters I want to propose are:
Binary Figure Space - Space the width of a binary digit. The binary digits proposed are very thin so I feel like this might be useful.
Binary Underline - Combining character to combine two binary digits.
Radix Point - Self Explanatory.
Rep Mark - proposed as a way to write repeating fractions. Also a combining character.
Binary 0 - Short vertical line
Binary 1 - Long vertical line.

I already made a basic font for these based on my own code points assignments and it works fine. How do I propose characters to the UCSUR?

In Fairfax HD, U+A789 MODIFIER LETTER COLON looks identical to U+003A COLON. According to L2/06-259R, “Compared with a typical colon glyph, the dots of the MODIFIER LETTER COLON should be closer together”.

hi this is cadex twenty-four's github account (i can prove it if you like) and i saw ihatemysalf was added to your character repertoire and got so excited! however theres a few things i had in mind

firstly there are duplicates of ꟻ ꭅ Ꝯ ꝯ as that's what they're intended to be

secondly rename requests:
FF33C;IHATEMYSALF CAPITAL LETTER VOLAPUK T
FF33D;IHATEMYSALF SMALL LETTER VOLAPUK T
FF33E;IHATEMYSALF CAPITAL LETTER KUPALOV A
FF33F;IHATEMYSALF SMALL LETTER KUPALOV A
FF350;IHATEMYSALF CAPITAL LETTER COMFORTAA A
FF351;IHATEMYSALF SMALL LETTER COMFORTAA A
FF352;IHATEMYSALF LETTER PHALLIC THISENT (just "LETTER THISENT" could work too)
FF375;IHATEMYSALF LETTER SATCHAY
FF37A;IHATEMYSALF LETTER LUCAS'S TWO
FF37E;IHATEMYSALF LETTER THE HOLY

also the stacked PW and TV originate from Poliespo, and the letters from the split crossbar ie to the mirrored ie originate from the Metelko alphabet for Slovenian, idk if these will really affect anything but if you want to encode those for those alphabets instead then feel free
unsure about having precomposed letters like ST but i guess it wouldnt hurt

U+A71F MODIFIER LETTER LOW INVERTED EXCLAMATION MARK is supposed to be subscript, but in Fairfax HD it is only slightly less superscript than U+A71E MODIFIER LETTER RAISED INVERTED EXCLAMATION MARK. See JTC1/SC2/WG2 N2945 pp. 5–7.

This character ("👁" U1F441 # EYE) was not mentioned in the proposal to disunify legacy computing symbols with emoji because it is a unification with a character which already requires a variation selector to become a valid emoji.

(ref)

Sample below:

- 🌳: DECIDUOUS TREE (U+1F333)
- 🍎: RED APPLE (U+1F34E)
- 🍒: CHERRIES (U+1F352)
- 🍓: STRAWBERRY (U+1F353)
- 🍷: WINE GLASS (U+1F377)
- 🏘: HOUSE BUILDINGS (U+1F3D8)
- 🏠: HOUSE BUILDING (U+1F3E0)
- 🏢: OFFICE BUILDING (U+1F3E2)
- 🐍: SNAKE (U+1F40D)
- 👁: EYE (U+1F441)
- 👃: NOSE (U+1F443)
- 💣: BOMB (U+1F4A3)
- 🛧: UP-POINTING AIRPLANE (U+1F6E7)
- 🛸: FLYING SAUCER (U+1F6F8)

In Fairfax HD, U+1D10 LATIN LETTER SMALL CAPITAL OPEN O looks identical to U+0254 LATIN SMALL LETTER OPEN O, instead of like a small capital U+0186 LATIN CAPITAL LETTER OPEN O. Here is <U+0186, U+0254, U+1D10>:

Compare <U+0043, U+0063, U+1D04>:

The ZX80/81 and Spectrum have special character codes in their character sets for entire basic tokens in order to save some of their limited memory. So there were character codes for full strings like IF, FOR, GO TO etc. Of course those can be encoded as just a sequence of ASCII characters, but then there is no way to distinguish between 0xEC and the sequence 0x47 0x4f 0x20 0x54 0x4f 0x20 in the translated output making the 2 way translation impossible.

Many BASIC dialects used the extended characters for tokens, but not in a way so fundamental to the way the Computer displayed characters like the Sinclair machines ZX Spectrum. Even in machine code programs if you tried displaying the character 0xEC on the screen it would instead display the string GO TO. (Edit: Turns out the ZX81 doesn't)

Considering the font supports so many "Legacy Computing" symbols, including ones that aren't supported by unicode. I think this is feasible.

There are several Sign Language Orthographies that are designed to be written linearly and have already been implemented in ad hoc fonts.

One of the most important being Stokoe Notation which was brought to Unicode's attention back in 2012:
PDF of paper: Towards a Unicode encoding for Stokoe Notation

There is also a Stokoe inspired system used in Sweden that has a working font and online dictionary:
Teckenskrift – Att skriva teckenspråk [edit: corrected link]

It should also be noted that SignWriting recently received official Unicode support, however it does require quite a manipulation by software to be displayed correctly as it is not meant to be typed/displayed linearly.

Hey there, I'd love to be able to install the font using homebrew. They suggest going via google fonts instead of directly adding to the font repo. https://github.com/Homebrew/homebrew-cask-fonts/blob/master/CONTRIBUTING.md

I wonder if you'd be interested in doing that? Instructions: https://github.com/google/fonts/blob/main/CONTRIBUTING.md

I attached a picture of the characters in question. These are used in the Fantasy computer Pico8.

Some of these are already in the font, but characters like "Jelpi", "Throwing Star" and all of the buttons don't really have proper equivalents. So.. let me propose.

0xffc27 => Jelpi
0xffc28 => Pico 8 Down Key
0xffc29 => Scattered Dots
0xffc2a => Throwing Star
0xffc2b => Ball
0xffc2c => Eye
0xffc2d => Man
0xffc2e => House
0xffc2f => Pico8 Left Key
0xffc37 => Face
0xffc38 => Pico8 Circle Key
0xffc39 => Pico8 Right Key
0xffc3a => Pico8 Up Key
0xffc3b => Birds
0xffc3c => Sawtooth
0xffc3d => Pico8 Cross Key
0xffc3e => Three Horizontal Lines
0xffc3f => Three Vertical Lines

Hi,

This is a great font! Thanks for your work!
One thing that I'd like to know is whether you are going to add Ligatures (for example like those in https://github.com/tonsky/FiraCode) ?

Where did the Commander X16 Symbols block (F5C0-F5FE) come from? The only one I've seen is F5FF which is part of the Commander X16 font ROM.

What is a Dogcow (F607) and why does Betty Boop (FB009) get a block?

Are the Pico-8 symbols at FF800-FF80F stable or are they subject to change? Was making them narrower than the actual Pico-8 the intention?

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

The bar is not a mere serif: it does appear in sans-serif fonts. There are plenty of examples in the “на молодцовском алфавите 1920-тых годов” section of this Komi book list. In all the sans-serif text in those books, I have 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.

⋆ (star operator) is kind of small. i can't see the pointy parts well and confuse it with · (Middle Dot U+00B7) in BQN code. though also to worry about not getting the size too close to ★ (Black Star U+2605).

also not sure where else to put this minor issue.

Fairfax HD looks like a little bad hinting and not clean on that lower dpi(96) monitor.
Also smaller size is more bad. I feel good at least 19px or more.
Lately many popular fonts look to provide medium width, even a one replace half with medium for regular size .
Literally many people chose the medium width.
Here compared to some other on my monitor.

This is not an issue, just an observation.

It would be interesting to read history, examples, and references explaining the rationale for creating some glyphs, especially in the Private Area of the font.

For example, in FairfaxHD why are there Quarter Capitals only for the 8 letters in "VOLS NICE" (FFC67 to FFC7E)?

Just curious.

horizontally alignment for t, f seems to be at too right,
Here's simple compared other fonts,

Incorporate if this prevents clipping in GDI applications without increasing line height

Turns out I completely missed the existence of these. I thought they were Japanese punctuation marks.

The characters 🕒 and 🔔 appear in the Atari ST set, but they're not in Fairfax.

This is a well-defined script that is also a conscript that is in use in Canada and among some First People groups in the US.
These would add 640, 70, and 16 glyphs for each of the three blocks.

Pointed out by a sweet, innocent child /s

The glyphs for U+21D8 ⇘ and U+21D9 ⇙ are swapped in all Fairfax fonts. ⇘ should point south-east (lower right), and ⇙ south-west (lower left).