A (mostly) 3x4 pixel font for tiny rich text and math typesetting.

https://gurki.github.io/pixeltex/

Generatrix is a Generated Graphic Symbol using particle's of typographics.

Don't repeat the same word without using space. As long as you do not press space it will remain on the same symbol.

Generatrix Body Structure:

f = five 5 bist = 2 ^ 5
b = ball
h = horizontal line
v = vertical
a = upward diagonal
b = descending diagonal

The first shows the position and the second the letter of the keyboard.

F-BHBHB.VDAVDAV.BHBHB.VDAVDAV.BHBHB.VDAVDAV.BHBHB.VDAVDAV.BHBHB-F

012345-ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz. - 6789

[00000]-[00000].[0000000]:[00000].[0000000]:[00000].[0000000]:[00000].[0000000]:[00000]-[00000] 

There are 63 main parts of the Generatrix. There are possible to generate 9,223,372,036,854,775,808 different symbols. Those are just the main ones, not all. Those are just the main ones, not all. However, as I think that the others are mutually exclusive, they have no combinatory potential as much as the first 63, although there are 8 accents that will only take the place of the 10 upper and lower strokes and therefore the 53 parts are not excluded, but the top 10 and bottom.

My part was creating the symbol, now how you will use it is up to you. My recommendation is to use a mathematical function and associate it with binaries. Using base 64, you will only need 9 digits for the main body. That's why I think the base 64 is ideal. Associate the symbol with a mathematical and binary function, not directly the letters on the keyboard. The letters are used only to access the symbol. However, the geratrix algorithm is something else. Something like Codetrix which is the base 64 binary function for Generatrix. It just converts any symbol into a code in a more formal way. So, even without the font, you can reference it using Codetrix 64.
Do not associate the Codetrix directly with the keyboard. In base 64, it is used from A to Z, from a to z, from 0 to 9 or that is alphanumeric but the '+' becomes '.' and '/' becomes '_' to end 64. Base 64 is a base already consolidated in computing and programming, but the symbols in addition to alphanumeric symbols have been replaced by '.' and '_'. A sum of two most popular symbols: '+' and '-', so I took the base 64 standard body. Codetrix is ​​a function that adapts base 64 to Generatrix. Another difference beyond the end for the standard base 64 is that it starts with the numbers 0 to 9, then the letters come, becoming more similar to the hexadecimal in values ​​less than 16 in the units.

{

0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz._

}

Main 64 symbols, only 63 are part of the main body. Probably many had confused 63 parts with 64 bit and 64 base. 6 parts makes 64 bits, because they are 2 ^ 6. But in fact I add it in the alphanumeric representation 64 using letters, numbers and symbols. There are 3 different things. Keyboard Buttons/Symbols Parts, Base 64 with 6 bits, Alphanumeric representation of base 64.  In base 64, 0 is an item so integers are 63 as well, since the non-zero positive integer value that starts at 1 is considered the second number after zero which is the first.

How Codetrix works:
There are 63 bits, each 6bit is worth 2 ^ 6 which is 64, but the division is perfect if we separate it by 7, that is 1 more bit, so that each element of the base 64 will be repeated 9 times to complete the 63 digits. Amount of values:

[2 * 64 * 2 * 64 * 2 * 64 * 2 * 64 * 2 * 64 * 2 * 64 * 2 * 64 * 2 * 64 * 2 * 64 * 2 * 64 * 2 * 64] = ([2 ^ 1] [2 ^ 6] * [2 ^ 1] [2 ^ 6] * [2 ^ 1] [2 ^ 6] * [2 ^ 1] [2 ^ 6] * [2 ^ 1] [2 ^ 6] * [2 ^ 1] [2 ^ 6] * [2 ^ 1] [2 ^ 6] * [2 ^ 1] [2 ^ 6] * [2 ^ 1] [2 ^ 6]) = (7 + 7 + 7 + 7 + 7 + 7 + 7 + 7 + 7) = 63 binaries. But you will see: [+ 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0] or at the end [+ _ + _ + _ + _ + _ + _ + _ + _ + _] (o ' _ 'is the last character in my system 64), using the polynomial [sn * 64 ^ p], n is the base number, 64 is the base and p is the power position (-1, becouse of the 0) of the digit from right to left, s is the sign that only alternates between + or -, by default I leave it at +, so 0 = +, 1 = -.

[+ 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0] = ([+] [n * 64 ^ p] [+] [n * 64 ^ p] [+] [n * 64 ^ p] [+] [n * 64 ^ p] [+] [n * 64 ^ p] [+] [n * 64 ^ p] [+] [n * 64 ^ p] [+] [n * 64 ^ p] [+] [n * 64 ^ p] [+] [n * 64 ^ p])

[+ _ + D + A + N + I + L + O + _ + _]

= ([+] [64 * 64 ^ 9] [+] [13 * 64 ^ 8] [+] [10* 64 ^ 7] [ +] [23 * 64 ^ 6] [+] [18 * 64 ^ 5] [+] [21 * 64 ^ 4] [+] [24 * 64 ^ 3] [ +] [64 * 64 ^ 1] [+] [64 * 64 ^ 0])

6bit (64 base) to binary:

2^6 = [([1]x2^5)+([1]x2^4)+([1]x2^3)+([1]x2^2)+([1]x2^1)+([1]x2^0)]

In fact the 2 ^ 6 is 100000 in binary, but in base 64, zero subtracts a digit and 32 + 16 + 8 + 2 + 1 = 63. The latter is 1 because zero does not add up, but zero is a number. I use the position and not the text value for 64, but 64 for binary uses value due to the powers of 2 (maximum 63).

I use the sum total myself and associate each position with the following values:
([1]x2^5)        =  0 or 32, 100000 = 32, 
([1]x2^4)        =  0 or 16, 010000 = 16
([1]x2^3)        =  0 or 8,   001000 = 8
([1]x2^2)        =  0 or 4,   000100 = 4
([1]x2^1)        =  0 or 2,   000010 = 2
([1]x2^0)        =  0 or 1,   000001 = 1

total: 63 in vabue, 64 in position = 111111

 [([0]x2^6)+([0]x2^5)+([0]x2^4)+([1]x2^3)+([1]x2^2)+([0]x2^1)+([1]x2^0)] = 13 = 8+ 4 + 1 = 2^3+2^2+2^0

= ([0] [111111] [0] [001101] [0] [001010] [ 0] [010111] [0] [010010] [0] [010101] [0] [011000] [ 0][0] [111111] [0] [111111])

=  011111100011010001010 0010111001001000101010011000001111110111111

I haven't finished or completed the codetrix yet, so I think you are free to do a better job. Maybe using binary without using base 64 is useful, I only used base 64, because in it there are only 9 digits plus the sign that stores 2 bits. Although I think the formulas will be more intended to turn texts into symbols. From the symbol it is easier to use direct binary.

What does the binary code mean? '0' means it has no dash (so I put it as a default and '1' means it has the dash or the typographic part of the symbol. That way in general Codetrix will be just a beautiful name for binaries that bridge the text and Generatrix symbol For you know where you press on the keyboard, because converting text directly to generatrix has a problem: Generatrix does not allow to differentiate the same words, since they overlap. If you write AVA with the font, you will see that it has only 2 typographic particles because only A and V was considered. Being more suitable it turns AVA into base 64 using its position, where A is the 10th and V is the 31st, then in binary (remembering not to confuse ordinal and cardinal numbers) and finally the binary converting for the symbol.

Generatrix's goal is to compress information. We stopped writing more and started to process more information. For future goals, it would be the idea of being able to write entire pages of books in just one symbol. A wording on a symbol.

As you can see, this system of font have been made to be customizable and generated many symbols.

It is under the Creative Commons Non Commercial v3 license, so that everyone can adapt to their needs.

Inspired by Neoletters.

Finished! (Took me 3 days)

Private use characters are encoded in Variation Selectors and Latin Ext. D.

OCR-like font.

Based off of a puzzle game Idea I have.

It's sort of like a cross between Gunpey and a 1-D Sudoku.

If you want to see the specific rules to the game, take a look at this document:

https://docs.google.com/document/d/1lXeDR1XjB7zTUVcm7y7BlOcOmg9rxpAkX7CK_rhQx_I/edit?usp=sharing

Version 1.1

*

A font designed and optimized for writing very small and dense math equations, especially those related to ESOSVM. This should make cramming equations onto a small canvas much easier.

I included A-Z and a-z so you can write with the font or use the letters to declare variable names. So it isn't just a "pure math" font like most other mathematics fonts I have seen around.

*

DIAGRAMMING PIECES

These are still being drawn and tested. The sizes these have to be will depend on the sizes of all other glyphs, so these pieces will be made last.

*

ANIMA OPERATORS

` - skein

@ - infH (infinitude of harmony)

# - infD (infinitude of dissonance)

_ - rskamacha

Ó - Palkyl's number

Ô - Marräd's number

Õ - Ehnetahinian void

Ö - Quanta/Phenom interface

*

LILTS

& - aShift

* - kShift

Ø - Phlogistian

Ù - Quintessential

*

PHENOMS

ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐ - quanta

Ñ - Marinanian constant

Ò - Dheenian constant

*

A pixel-for-pixel recreation of the font on TI-83 and black and white TI-84 graphing calculators, remapped to Unicode. There are lots of TI fonts already on FontStruct, but this is the only one that features the full set of 249 characters, including semigraphics characters. Everything that doesn't have a Unicode BMP codepoint has been mapped to Control Pictures because FontStruct doesn't support the Private Use Area.

Source for characters: http://tibasicdev.wikidot.com/83lgfont

Version 2.6

*

Inspired by a comment by jonrgrover.

I built diamonds sized according to the Fibonacci series, then made a segmented display out of them. The design was then carved away to make the glyphs you see here. I used the members 1, 2, 3, 5, and 8. These sizes proved most feasible to work with in this sort of arrangement.

I gave the terminals a flared appearance which I think makes the glyphs look slightly Celtic. The design also makes me think of beach sand and things found on the beach - shells, pretty rocks, and so on.