Hello, How to build Construct New Script?,
In My country, have many old scripts, so in unicode had not register,
So, how to line type in line, exampe right to left, left to right?,
Lets you create your own TTF fonts out of pixel font images! · By
I don’t think I fully understand the question (can you give an example?), but in fonts (and text display in general) you can only use glyphs that exist, so if you want to add a symbol that’s not part of the current Unicode standard, you can instead replace a symbol that is unlikely to be used with your font - there are many to choose from.
For right-to-left, don’t enter text in right-to-left mode in the “glyphs in the image” box, only in the font tester on the right.
I'm sorry beforehand for my lacking capabilities in english language, I asked my friend to translate it
In my country, we have thousands of languages. But what i mean is ancient alphabets(scripts) that support some languages with earlier manuscripts
What i'm trying to tell is, it's about the UNICODE, ligature systems of language and letters. But said UNICODE a takes a longer time to be registered(approved)
Thats what makes me confused, i want to make app like microsoft word, where these letters and alphabet have tgeir own keyboards, without editing from the existing UNICODE because each language in our region has its unique writing (ligature).
Perhaps what I mean is an application like Notepad, which can be imported into PNG/JPG, or if possible PDF, but in the application, it has an independent keyboard.
To be registered in UNICODE, there must be strong evidence supporting the script, such as old literature, inscriptions, and the likes.
Even if there is supporting evidence, it's not guaranteed to be approved by UNICODE. Not to mention, waiting for the update takes a very long time; you have to wait for a year for it to be approved. So, dealing with UNICODE can be quite complicated
So, how unicode build ttf? Hmm...
A glyph consists of series of vector shapes (if you look at the FontForge logo, you can get an idea) and a little information (such as size and spacing).
A font consists of series of glyphs and information about their relationships (kerning, ligatures). The symbols are addressed by their code-points (# is U+0023, for example).
A font renderer (including ones in your browser and Microsoft Word) displays sequences of code-points. It does not know (or care) about what’s in the font beyond some specifics (such as which symbols are spaces or punctuation for line breaks).
Therefore you could make a font that replaces glyphs with unrelated ones (like Webdings did) and the user would be able to view a document written for that font if they have it installed.
For viewing without installation, browsers have web font support.