Unicode: Difference between revisions
→Concerns: per jan Lepeka: "Unicode hates gaps; they know what you're trying to pull when you do that"
mNo edit summary |
(→Concerns: per jan Lepeka: "Unicode hates gaps; they know what you're trying to pull when you do that") Tag: 2017 source edit |
||
Line 35:
(And as for which {{tok|nimi sin}} to add to the Extended block, I think for the time being we could add any word that any fontmaker wants to support in their font. Once SP font making becomes more common, perhaps when 2 or 3 font makers promise to add it to a font, or something like that.)
</blockquote></ref> This would come at the expense of complicating the encoding situation rather than submitting one proposal and being done with it.
*'''Commerciality'''. While the [[Toki Pona logo|Toki Pona "logo"]] {{sp|toki-pona}} would not receive its own codepoint, it occurs as part of {{tp|sitelen pona}} {{sp|[[pu]]}}. Moreover, {{sp|pu}} and {{sp|[[ku]]}} refer to and graphically represent commercial products that are not fully in the public domain. If this is an issue
==References==
| |||