ohbendy / Phake-Ramayana

The Phake Ramayana font is a traditional design based on manuscript forms. It supports Tai Phake, Tai Aiton, Tai Khamyang, Tai Turung and Tai Khamti languages.
MIT License
0 stars 0 forks source link

Vowel signs #3

Closed ohbendy closed 3 years ago

ohbendy commented 3 years ago

Stephen's Phake Ramayana PDF shows us a couple of vowel signs that don't appear in UTN 11 for Phake language.

Screenshot 2021-05-24 at 08 30 16

We seem to have both the visarga း [1038] and Aiton vowel sign -a ႜ [109C] — are these distinct characters or would they just be different expressions of the same character depending who's writing the text?

The final letter on the first line seems to be the round -aa vowel ◌ာ [102C] but UTN11 doesn't include that letter in the Phake repertoire. The Khamti repertoire includes ◌ၢ [1062] so if we include this glyph, should we use 102C or 1062?

In our emails, Stephen wanted to make sure we support the -u vowel ◌ု [102F] with the -o vowel ◌ွ [103D]. In some manuscripts these seem to be touching and in other ones they have a bit of a gap between the two elements, so I'm not sure which way people prefer:

Screenshot 2021-05-24 at 08 47 13

Unicode would need these to be stored as 103D 102F so if people want to type them the other way the keyboard would need to switch them.

StephenMorey commented 3 years ago

Hi Ben. Firstly, in relation to the two 'visarga' symbols which on my font were at upper case C and X - these are simple /a/ vowels, perhaps more frequently associated with a short /a/ in the manuscripts. They are really variants but I suspect it might be useful to have both in the font, so if we can use 1038 and 109C, I think it's a good idea.

Secondly, yes I think we can include the round -aa vowel ◌ာ [other 102C] as a variant of the Khamti ◌ၢ [1062]. I hadn't thought about this before, but perhaps 1062 was added without fully realising that it is a 'modern Khamti' version of 102C. So I'm happy for it to be included at either 102C or 1062, but given that 1062 is the one used for Khamti then let's put it there

Thirdly, in connection with the u and o, I've put up a post on Facebook just now

ohbendy commented 3 years ago

If we include 1038 and 109C as different glyphs for the same character, text that uses 1038 will be encoded differently from text that uses 109C. We should try to avoid promoting two different encodings, that would break searching and sorting text.

StephenMorey commented 3 years ago

OK, in that situation I think it needs to be just 109C.

ohbendy commented 3 years ago

Stephen, was there any feedback on Facebook about how the U + O is preferred?

StephenMorey commented 3 years ago

I think it should be left to right o then u; do you have a screen shot I can share?

ohbendy commented 3 years ago

The image above shows the two possible approaches. I've also just found in your latest images another possible approach with the circle slanted:

Screenshot 2021-07-19 at 09 09 34 Screenshot 2021-07-19 at 09 09 44

ohbendy commented 3 years ago

Decided to keep the first version. Others are kept in the source file just in case we change our minds later. Closing this thread for now.