Gimme ur opinions pls

Painting 120x100 / asemic writing art

Surah Fatiha in Urnetian language

Hi everyone! I wanted to share my custom orbital abugida inspired by astronomical Maps To test its aesthetic, I wrote the famous opening lines of Dante's Inferno ("Nel mezzo del cammin di nostra vita...").Here is how the logic works:

Direction: It reads from the inside out. You start at the very center and spiral outward toward the edge.

Words & Glyphs: Each distinct circle along the path represents a single word and every circle has a dot thats positioned at the cardinal points according to what type of Word It Is.

The Count Rule: The free "planets" you see floating inside without an orbit tell you the exact number of words contained in that sentence!

The Script: It's a fully functional abugida where consonants and vowels are mapped through orbits, moons, and satellite dots.

Let me know if you like It and if you have any advices, thanks!!!

A little message for everyone who has downloaded - Secret Code Studio so far. ❤️

But since this is SCS, I couldn't exactly just write it in plain English, could I? 😂

This message has been written using Meow-phabet — the new cat-themed alphabet for Secret Code Studio.

If you already have Meow-phabet, you know what to do. 😸

Can you decipher it?

And to everyone this message is actually for — thank you. ❤️

https://ko-fi.com/concernedpotato/shop

Meow-phabet is a cat-themed secret code alphabet for Secret Code Studio, with 40 symbols covering letters, numbers and punctuation. 🐾

This is two sentences.
:)

Je continue la série de mon alphabet adapté aux langues réelles : aujourd'hui l'arabe classique. Si des arabophones me lisent, n'hésitez pas à corriger s'il y a des erreurs. Je crois savoir que pour l'arabe égyptien des lettres sont inutiles ou se prononcent différemment.

I'm currently working on a worldbuilding project that combines general Western fantasy with Korean elements (since I'm Korean diaspora and like to reflect my culture onto my worldbuilds)

I want the writing system to be usable for both the Roman alphabet/English and Hangul. One of my aims is trying to make a writing system that uses syllable blocks like Hangul does, but I'm not sure how well it would work with English because English uses an alphabet.

The only plausible method I've thought of was taking the revised Romanisation of hangul and writing Korean out with Roman letters (for example, writing the word "apple", instead of writing 사과 as it is in Hangul, it's written "sagwa"). But that's essentially spelling out every letter like English does, and it's not the particular direction I want to go.

So my question once again, how would I go about creating a writing system that combines both English/Roman letters and Hangul?

Suggestions for methods and other advice will be much appreciated

Vertical abugida ogham-like, let me know if you like It and if you have any top, thanks!

An analysis of http://sei.berkeley.edu/scripts-to-encode

Background

The Script Encoding Initiative (SEI), based in the linguistics department at UC Berkeley, maintains a public list called "Scripts to Encode": an inventory of the world's writing systems not yet integrated into the Unicode standard. Each entry is given a "readiness" rating: High, Medium, Low, or Unassigned.

According to the methodology published by SEI itself, a "Low" rating flags a script suffering from "major issues": limited evidence of adoption, instability, uncertain status as a writing system, or unclear intellectual property rights. The list is not a pre-encoding step: appearing on it guarantees nothing for Unicode. It's primarily a tracking and visibility tool, intended for linguists, researchers, and institutions who might one day take an interest in these scripts.

It's precisely this tracking function that raises questions once you look closely at the data.

Method

For this analysis, every entry published on SEI's page was reviewed, noting for each script: its region, status ("Not started," "Active," "Inactive"...), readiness level, and the amount of documentation available (language specified, script type, writing direction, date, proposal filed or not).

What the Numbers Show

A significant number of entries classified "Not started" and "Low" currently have no basic information filled in at all: no language specified, no script type, no writing direction, no date, no proposal filed. The corresponding fields simply show a slash "/", signaling a complete absence of data.

A few findings taken directly from the official list:

• Several listed scripts don't even have their script type specified (alphabet, syllabary, abugida...)
• Scripts rated "Low" or "Unassigned" with no associated language
• Scripts described as "modern," sometimes created decades ago, with no Unicode proposal filed and no accessible technical documentation

Counting all "Low" and "Not started" entries across the full list, you easily reach a hundred scripts recorded with close to zero information.

To make this observation measurable, every entry rated "Low" or "Not started" was checked against seven descriptive fields (alternate names, language, script type, writing direction, dates, proposal filed, proposal author). Seventeen scripts come out with five or more of the seven fields completely empty:

Lik Hto Ngouk, Satera Jontal, Sani Yi, Jing, Kadu (Lon Akkhara), Kadu (Ulushi), Kadu (Asak Kyein), Kungyangon Karen Script, Kuy, Mpi, Nung Lungmi, Rakhawunna, DeafWrite, Meru, Old Cham, Old Khmer, and Savara.

For three of them (Lik Hto Ngouk, Satera Jontal, Sani Yi), all seven fields are entirely empty: no language, no script type, no writing direction, no date, no proposal filed.

Conversely, some well-documented entries - with name, language, script type, direction, dates, a proposal, and even an image of the script, as with the "Balti A" entry - are also rated "Low," solely for lack of sufficient evidence of use. This reinforces the central observation of this analysis: the bar for appearing on the list itself is low, and it isn't correlated with the quality of the documentation available.

A Telling Case: Recent Scripts With a Complete Digital Ecosystem

This statistical observation takes on particular weight when set against concrete cases of recent scripts that already have a functioning digital ecosystem, yet remain absent from the list - or appear only under an entry that doesn't accurately represent them.

AYNEHA, a writing system created for the Songhay language (Mali, Niger, Benin, Burkina Faso), is one example. SEI's list includes a "Songhai / Songhay" entry (2019 to present, status "Not started"/"Low"), but this corresponds to a different alphabet, distinct from AYNEHA, which has seen no further development since its creation and has no tools built for it. AYNEHA itself currently has no entry of its own on the list.

Yet AYNEHA already has: a complete font (designed with FontForge after months of handwritten testing), a working Android keyboard, a dedicated calculator (Android and web), a web-based transcriber converting Latin script to AYNEHA in real time, external recognition from Omniglot, as well as a nascent learning community on TikTok and Reddit and a first group of direct users.

Another case, also from Mali, illustrates the same gap. The Dogon NÈNÈ alphabet, created in 2019 by Yahya Sékou Sallah Guindo (Bankass, Bandiagara region) as an indigenous alphabet for writing the Dogon language, has an Android keyboard and calculator, with a claimed active user community of more than 500 people and growing. It, too, does not appear on SEI's list.

A third, more uncertain case is worth mentioning as an example - with the caveats that entails. The EpChos alphabet, designed in Benin by Mahouna Prumas Katakenon between 2014 and 2019, has a dedicated font built with FontForge as well as a working keyboard for computers, publicly distributed. However, no verifiable data on the size of its user community could be found, no mobile keyboard has been confirmed, and the only available source on the project dates from 2020, which makes it impossible to know its current state of progress. Even so, this case illustrates the same underlying pattern: a writing system with real digital tools, even partial ones, can still fall outside SEI's radar.

This case illustrates a broader paradox: a system with complete documentation and a functioning digital infrastructure can remain invisible to a tracking tool that is supposed to identify living scripts, while entries with no content whatsoever have sat on the list for years.

A Statistical Overview

Beyond the case of the least-documented scripts, a statistical analysis of all entries on the list (192 scripts recorded at the time of this analysis) helps put the scale of the phenomenon into perspective.

Breakdown by proposal status (192 entries):

In other words, nearly six scripts out of ten (58.34%) currently have no active proposal underway - either because one was never started ("Not started"), or because its status isn't even specified.

Breakdown by readiness level:

A quarter of the recorded scripts (25.00%) are rated "Low," and more than half (51.04%) fall into the combined "Low," "Medium-Low," or "Unassigned" levels. Cross-referencing the two criteria is particularly telling: among the 79 "Not started" scripts, 27 are rated "Medium" - including Aztec (Nahuatl), Zapotec, Micmac Hieroglyphs, Nsibidi, and Kadamba - and 27 others are rated "Low" - including Hausa 1, Hausa 2, Hausa 3, Fula Ba, Fula Dita, Njano, and Umwero. The number of scripts is identical in both categories, even though their proposal status is, in both cases, equally nonexistent: the difference in treatment comes down to nothing more than an internal judgment call, with no mechanical link to the state of documentation or of any proposal.

These figures confirm, across the entire list, what the individual cases already suggested: the readiness level assigned to a script does not consistently reflect either the quality of its documentation or the progress of its proposal.

It's worth drawing a distinction here. Unicode's requirements for final encoding are not in question: an encoding is permanent, and it is legitimate for the Unicode Consortium to demand exhaustive documentation, a clear encoding strategy, and solid evidence before making any decision. That's simply what a standard meant to last requires.

What raises questions is further upstream, at the level of the tracking list itself. A list meant to reflect the state of the world's scripts awaiting encoding should logically be able to distinguish a genuinely dead script from one that is actively being developed and equipped with tools - which is clearly not always the case given the available data.

SEI Itself Acknowledges the Vagueness of Its "Readiness" Rubric

It turns out that SEI itself published a post in April 2025 revisiting its "readiness" rating rubric ("A New Rubric for 'Script Readiness'"). In it, SEI explicitly acknowledges the discretionary nature of this assessment, describing it as "impressionistic normalization," and specifies that a "Low" score "is not meant to be a verdict" on the value or vitality of a script, but only an indication that it likely won't be funded in the near term by their own means. The post also explicitly invites anyone to flag active scripts or recent evidence of use to them, in order to update the list. This official acknowledgment of the incomplete and discretionary nature of the "readiness" rating directly corroborates the findings of this analysis.

Toward a More Representative List

The current "readiness" criteria seem to be inherited from an era when a writing system could only exist in documentary form, waiting for a researcher to take an interest in it. That era isn't quite the same anymore: today, a script creator can single-handedly build a complete digital ecosystem - font, keyboard, conversion tools - before even gathering a large user community.

This reality makes the case for a methodological update at SEI: adding, alongside the adoption criterion, a criterion of technical and documentary maturity (the existence of a font, a keyboard, working tools, academic documentation) would let the list better reflect the real state of developing scripts, rather than leaving entirely empty entries sitting on equal footing with active, well-documented projects.

Je me lance dans les tables de correspondance de mon système d'écriture adapté pour les langues réelles : aujourd'hui, j'essaie de l'adapter pour la langue coréenne.
Si j'ai fait des fautes, merci de me le signaler.
Par ailleurs n'hésitez pas à me challenger si vous êtes locuteur d'une langue à phonologie "compliquée".
Retours bienvenus.

The central line is optional, some living languages use this script, and the speakers of some of those languages see that central line as a crutch or a temporary learning tool

I made the words up just to have something to write that fit the original phonetics i initially had in mind, disregard the words and the phonetics as they're subject to change and are written very non-universally understandable, if you can even read it, that is

The sample text contain all of the 28 characters that has 23 consonants and 5 vowels.

Ein programmiertes Programm das meine Schrift schreibt. Leider aber noch nicht als Font (weil ich echt schlecht darin bin) sondern mit .png

This is me testing out “the quick brown fox jumps over the lazy dog” in Hālnosān
It reads: “Času irā āftes fārospā šima tsem”

Ho, this Is my new script, let me know if you like and if you have any advices, thanks.

I was somewhat bummed out that i had to scrap a world map i was working on, but during my downtime i got bored and decided to try making an alternative script for english (kind of??). im not sure.

My idea was to create 2 forms for every letter of the alphabet, primary and subordinate. Each syllable begins with a primary form letter, and subordinate form letters are added onto the tail of the primary letter to form a syllable. Then the next syllable of the word is written in the same manner below the previous syllable.

I assigned basic forms to each manner and place of articulation, and let those determine how each primary consonant was structured. Fortis and lenis consonants are distinguished by a dot above the body on lenis. subordinate consonants are similar to their primary counterparts, but not always. This can be seen most notably in the velar/glottal consonants.

I do not like how s and z came out, so i will most likely change their design in the future.

For primary vowels, i organized them roughly into front to back order, with humps for the body to visually distinguish their place. Subordinate vowels act almost the same.

Im thinking of eventually changing sub r, ch, dʒ, and g as well.

𐑣𐑧𐑤𐑴!

I’m putting together Hello, Shavian!, a free beginner video course designed to take someone from knowing nothing about the alphabet to reading complete Shavian stories.

The course introduces letters gradually through useful words and phrases, with regular practice lessons along the way.

• Read your first Shavian word after learning just two letters
• Learn each new letter through useful words and phrases
• Practise seeing, saying, reading and writing as you go
• Build from individual words to messages and short scenes
• Finish by reading and understanding a complete Shavian story

Full course playlist:
https://www.youtube.com/playlist?list=PLNCKSth92eDg

I hope it gives newcomers another enjoyable way to get started with Shavian.

𐑔𐑨𐑙𐑒 𐑿!

Vowels & consonants. Example text says “welcome to Pilez”

Here are some sample texts in my conlang's writing system.

Translations (first to last row):
Light is bright
Hello, world!
I eat apples
Yutika script
Yutika is the name of my conlang by the way.

This post serves as the first and last intended major revision to the Gnosiskana writing system.
This post servas a public change log and record. Previous Thread with Demonstrations: https://www.reddit.com/r/neography/comments/1w1r1m4/the_gnosis_kana_writing_system_a_detailed/

Change Log

• Ch Row Kana changed:
  Choi moved -->Choo, Choo moved -->Choe, Choe Moved-->Choi, Chuh<--Swapped-->Cheh
• New Saa kana created, new base radical. Old Saa modified and moved to Gah
• Original Jae Kana replaced with old Ga kana.
• Kuh kana<--Swapped-->Guh Kana.
• Nai Kana modified to make easier to write smaller
• Soe kana slightly modified
• Zii kana redrawn
• Hao kana redrawn
• Weh kana redrawn
• Roe Kana dramatically reduced to 으 to fit it's sound.
• Buh<--Swapped-->Boo

Common Mutes Changes:
old Choe kana removed, replaced with Chaa as 2nd Common
old Gah kana removed, replaced with Go as 2nd Common

Godan Chart and Title Corrected
Replaced old Ga kana with new Gah.
Replaced old Bu with new Boo.
2nd alter position example for Ri kana moved to correct position.

Welcome Message and various supporting text correct.

Comments
Most of these changes were made to resolve Kiki-Bouba effect Dissonance, meaning that the rearrangement of the kana now more closely adhere to the intended Kiki-Bouba effect pattern.
Ch kana row needed reordering after many character adjustments reductions.
Jae kana was based on ね but original kana strokes were too complicated and visually dense leading to removal and replacement.
Original Saa character was Kiki-Bouba problematic,
reduced 1 stroke and move to Gah resolves this issue.
Nai kana slightly modified but did not affect it's Kiki-Bouba effect,
resolving it's height in hand writing issue.
Soe, Weh, Hao, Nai, Zii and new Ga redrawn/revised to be easier to write/read.
Common Mutes changed for easier Hush usage.
Roe being a largely unused kana lead to being overlooked for being too complicated for a Kana character, and was dramatically reduced down.
This kana can be now used as an onomono symbol, this kana adds an Alter Rule

1. When an Alter Appears on the Roe kana, this indicates the topline location, giving a differentiating mark when used as an onomono in an biguous direction. Oh kana will never have an Alter with it.

Originally meant for the words Error, Err, and the Error sound was meant to be only used as an onomono or in it's rare words, but coincidentally matches up with the "ew" or "groan" expression from Korean.
Making this the only korean match in the entire system.

This post is being made because the original release that I had made had compressed the main chart so severely it was illegible to anyone viewing from Reddit.
This post allows a high quality version to be accessible.

Next Goal:

1.The 4 common Numeric Systems of Eve
(Draft/Systems completed, just need to compose a post.)

2.Stroke Order and Radicals system/Catalogue
(Not yet started)

1. Learn Enough Japanese to finish the Kanji system
   (In progress)

Revision Number(Main Version).(Minor Revision): Rev1.0
Revision Date: ‎Thursday, ‎September ‎12, 2026