Skip to main content

Writing system

Go to Table of Contents

Writing system

The native writing system has not been created yet.

Glyph structure

Each syllable is represented by a glyph with a structure as shown here:

The structure of a glyph for a syllable

When a component in the syllable is missing, the other components expand to fill up the gap. Long vowel is represented as a horizontal line in the V2 position.

Because it requires more than a font to be able to write these glyphs, I cannot create a font to represent it. There will be a tool to generate svg/png for generaating glyphs from a word, however. All text samples in this book will be romanized, from which you can generate the native scripts.

Order

Hàäsdáïga does not have an alphabetic order. The alphabet order is used for us to more conveniently list words. The order for letters with tones is level, falling, and rising.

Letters

Letters used to form glyphs are listed in the table below:

Latin Letter
a Hàësdáïga letter a
b Hàësdáïga letter b
c Hàësdáïga letter c
ch Hàësdáïga letter ch
d Hàësdáïga letter d
e Hàësdáïga letter e
f Hàësdáïga letter f
g Hàësdáïga letter g
gh Hàësdáïga letter gh
h Hàësdáïga letter h
i Hàësdáïga letter i
j Hàësdáïga letter j
l Hàësdáïga letter l
m Hàësdáïga letter m
n Hàësdáïga letter n
ng Hàësdáïga letter ng
nj Hàësdáïga letter nj
o Hàësdáïga letter o
p Hàësdáïga letter p
r Hàësdáïga letter r
s Hàësdáïga letter s
t Hàësdáïga letter t
u Hàësdáïga letter u
v Hàësdáïga letter v
w Hàësdáïga letter w
y (empty)
z Hàësdáïga letter z
long vowel Hàësdáïga long vowel
rising tone Hàësdáïga rising tone
falling tone Hàësdáïga falling tone
level tone (empty)
glottal stop /ʔ/ Hàësdáïga glottal stop
. Hàësdáïga sentence start
, Hàësdáïga comma
: Hàësdáïga colon
! Hàësdáïga exclamation mark
? Hàësdáïga question mark
( or “ Hàësdáïga left bracket
) or ” Hàësdáïga right bracket

Punctuation usage:

  • Sentence punctuation . ! ? : are put at the beginning of the sentence, rather than the end.
  • Colon is considered a sentence punctuation. It is put at the beginning of the quoted phrase.
  • Comma is used in a similar way as in English.
  • Brackets are used for both quotation and explanation. In case of quotation, there should be a colon preceding the phrase.

Input for glyph generation

While this is not a part of the language, in order to generate native script with the provided tool, one MUST follow this guideline for writing romanization, which is not the same as the normal romanization guideline.

  • If there is a tone, the schwa y must be explicit. That is, never put the tone on a consonant.
  • The second vowel should not come with the diaresis.
  • Long vowel should be represented by a tilde ~ rather than duplicating vowels.
  • Always write syllables separately. For example càhánzy (to give) must be written as cà hán zy.
  • The glottal stop must be explicit. For example aäratse (ash) must be written as 'a~ rat se.
  • Punctuations should be separated from syllables.
  • Spaces should be noted with a hyphen.

The output may look bad; you can blame my poor drawing skills (I did not align some of the strokes) and the limitation of technology (the letters are stretched and therefore the thickness is not consistent).

Articles from blogs I read Generated by openring

Urgent: End filibuster and pass For the People Act

US citizens: call on the Senate to end the filibuster and pass the For the People Act.

via Richard Stallman's Political Notes June 6, 2021

Online Open House Goes Over openSUSE, Survey Opens

The openSUSE Project has a lot going on lately. The project just released Leap 15.3, had 24-hour release party in the openSUSE Bar and opened a survey to get feedback on the release of the new Leap version. There are many other things happening and one of…

via openSUSE News June 4, 2021

Fuzzing is Beta Ready

We are excited to announce that native fuzzing is ready for beta testing in its development branch, dev.fuzz! Fuzzing is a type of automated testing which continuously manipulates inputs to a program to find issues such as panics or bug…

via The Go Programming Language Blog June 3, 2021