88b 88 888888  dP"Yb  .dP"Y8 Yb  dP 88b 88 888888 88  88     88b 88 888888 88888
88Yb88 88__   dP   Yb `Ybo."  YbdP  88Yb88   88   88  88     88Yb88 88__     88
88 Y88 88""   Yb   dP o.`Y8b   8P   88 Y88   88   888888 .o. 88 Y88 88""     88
88  Y8 888888  YbodP  8bodP'  dP    88  Y8   88   88  88 `"' 88  Y8 888888   88
°±²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²±°
TALES FROM THE DIGITAL FRONTiER
°±²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²²±°

// 2025-12-07 // by Neon

Lekis Kojfo Text Converter

Lekis Kojfo is a fictional language spoken by the reclusive hermit kingdom called the Unified Collaborative (𐴘𐴉𐴡𐴏𐴞𐴏𐴞𐴓𐴃𐴝𐴑𐴡𐴏) in the universe of The Zeta Directive. This page allows you to convert Latin text into Lekis Kojfo script.

Converter

Type Latin text below to convert it into Lekis Kojfo script (encoded in Unicode as Hanifi Rohingya).

Output

Technical Info

Normally, the best practice with implementing custom written scripts in Unicode is to make use of the Private Use Area.

However, since Lekis Kojfo is written from right to left, Anglocentric computing conventions put us in an awkward situation (see rant). Let's go over the technical details of how this font is implemented:

• Lekis Kojfo (as displayed on this site), is implemented to use Unicode characters from Hanifi Rohingya script.
  • This way, if we were to use the font in a text block without an explicitly defined directionality, most programs would still know that it needs to be rendered right-to-left (RTL).
• Hanifi Rohingya script is not a perfect one-to-one for the letters present in Lekis Kojfo writing, but it's as close as we can get from all the available real-world RTL writing systems.
  • I've attempted to transliterate the script as closely as possible. This way if someone were to read the text as Rohingya, the phonemic information of what is written is mostly preserved.
  • I do not speak Rohingya, so (if you do) it is my apology if my transliteration isn't exactly what a native speaker would do if transliterating Lekis Kojfo into their writing system. I am, however, very grateful to be able to use your writing system to represent my conlang. It is very slim pickings when it comes to Unicode-represented RTL alphabetic writing systems in the real world.
• The glyphs for so-called weak vowels (aj,ij, uj, ej, oj) are implemented via ligatures. They map to unused Hanifi Rohingya characters U+10D28 through U+10D2C. These letters are implemented this way because they are individuated letters within Lekis Kojfo, despite being represented in Latin or Rohingya using digraphs.

Rant - Diversity & Computing

The Unicode Private Use Area is nominally directionless, but the de-facto reality is that most programs will consider any Unicode character that isn't in an RTL character space to be left-to-right (LTR). Effectively, you don't get native RTL text processing in some programs unless you make use of an existing Unicode character space that is explicitly defined for a right-to-left writing system.

Because Unicode does not explicitly set aside any part of the Private Use Area for right-to-left characters, the only way to universally get right-to-left text processing without requiring external directionality tags is to co-opt an existing right-to-left script' character space.

In the context of real-world writing systems, this is actually a fantastic computing-world demonstration of the concept behind disparate impact: Although the Unicode Private Use Areas are formally equal by not taking a stance on directionality one way or another, the substantive reality is that out of the 137,468 Unicode characters allotted specifically for private use, RTL language users get first-class support in zero of them.

This is a nitpicky non-issue for most people and the only reason I encountered it was because of a project I made for fun, but I can't help but think it's unfair. There are over 7,000 spoken languages in the world right now, and new writing systems get added to Unicode even in the modern day. Hanifi Rohingya was added to Unicode in 2018, less than ten years ago as of this writing. What other languages might be out there that don't yet have an official place in Unicode?

Well, if someone wanted to implement it for themselves in the meantime, they'd probably want to use a Unicode Private Use Area. Sucks to be them if their script is written right-to-left, I guess. It's ridiculous that co-opting a different script is the best way to get hassle-free cross-program RTL character support. You would think there should be a Private Use Area explicitly codified for RTL use. Nope! Eat shit!

This is the kind of problem that highlights the critical need for diversity among the people who implement computer systems. Even the smartest dudebro dev team who thinks they've accounted for everything will ship broken experiences if no one is the room to point out that not everyone reads, writes, or navigates the world the same way they do.

To-Do List

• I haven't yet implemented numerals in this font. These will be interesting because Lekis Kojfo speakers generally use senary numbering.
• I haven't yet implemented any punctuation into this font. You can use an interpunct (·) to punctuate sentences, but I'd like to make cleaner glyphs for this as well as for some other things in the future.

Download This Font

• The font family name that you will want to use if referencing the font in HTML is lekis kojfo.
• The BCP-47 HTML lang tag to use for text written to be rendered using this font (if you care about such things) is x-hr-lekiskojfo.

Resources Used

This font was made using fully open source tooling for use on neosynth.net. It is released to you under Creative Commons CC-BY-SA 4.0.

• The glyphs for the individual Lekis Kojfo letters were made by me from scratch using Inkscape.
• The font was created by me using FontForge.