7,935
edits
Font guidelines for sitelen pona: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| (8 intermediate revisions by 3 users not shown) | |||
Line 1:
{{tp title|sitelen pona}}
By now, there are many fonts for {{tp|[[sitelen pona]]}}—and more are getting created, and some old ones are getting improved. This article seeks to collect the ideal state of a font, recommendations that emerged from dealing with many fonts, and guidelines for anyone who wants to make a "good" font.▼
{{SP sidebar}}
▲
The less technical advice may also be of use for people who want to improve their handwriting.
==Technically complete==
When a font is considered complete is going to differ for different font creators and font users. Generally speaking, though, a font might be considered usable by the majority of users when it has the following technical features:
*
* Any character that is found in [[UCSUR]] should be assigned the codepoint according to UCSUR.
* In fact, beyond
* Also add glyphs for cartouche start, cartouche end, cartouche extension lines, extended {{tp|pi}} start, expanded character extension line, cartouche interpunct, and cartouche colon in the corresponding UCSUR codepoint.
* Add a functionality that cartouches and extended {{tp|pi}} work with any {{tp|sitelen pona}} character without any gaps between the lines. This can be achieved either by making new glyphs where each {{tp|sitelen pona}} character is combined with extension lines, or by creating zero-width extension and cartouche lines that can be used <em>after</em> a word to reach <em>under</em> another character.
* Ideally, cartouches and extended pi should work without adding a control character for the lines each time—instead, through ''contextual ligatures'', lines get filled automatically between a start and end character.
* For increased accessibility, add [[ASCII transcription|ligatures for any {{tp|sitelen pona}} character]], as well as for any functionality the font supports. "Ligatures" (through "lookup tables") make it so a text in ASCII will get substituted with {{tp|sitelen pona}} characters, meaning that <code>{{tok|toki}}</code> typed out in {{tp|[[sitelen Lasina]]}} automatically becomes <code>{{sp|toki}}</code> in the font.
Beyond that, the following features require a large amount of work, so it tends not to be seen as a marker of completion:
Line 39 ⟶ 40:
===Flexible glyphs===
Many characters in sitelen pona are widely considered to not be static and aren't supposed to be drawn the same way every time.
* '''{{tp|jaki}}''': any scribble, usually with overlaps, such as {{sp|jaki1 jaki2 jaki3 jaki4 jaki5 jaki6 jaki7 jaki8 jaki9 jaki10 jaki11|font=linja lipamanka}}
* '''{{tp|ko}}''': any blobby unshapely form, such as {{sp|ko1 ko2 ko3 ko4 ko5 ko6|font=linja lipamanka}}
* '''{{tp|ni}}''': many use {{tp|ni}} to point to the part {{tp|ni}} is referencing (up, down, right, or other directions, instead of the standard downwards arrow) like so: {{sp|ni> ni< ni^ niv|font=linja lipamanka}}
* '''{{tp|ni}}:''' often the line is extended if it's been rotated to the left or right, such as {{sp|ni>(--)|font=linja lipamanka}}
* '''{{tp|lete, kin}}''': rotation, and maybe even exact number of intersecting lines, aren't important
* '''{{tp|linja, kon, telo, pakala, mun}}''': can be mirrored
Line 57 ⟶ 59:
* '''{{tp|kala}}''': adding 2 dots for eyes
* '''{{tp|epiku, kokosila, lanpan}}''': although there is a more widely accepted version for all of these, their glyphs are relatively recent and have had more than one shape, so older versions are still in use
{{SP nav}}
{{Fonts}}
[[Category:sitelen pona]]
[[Category:Fonts| ~]]
| |||