Hi René,
I have an unfinished transliteration with some non-standard notations that I could (maybe) make compatible with some flavor of the EVA format for sharing.
I used:
, for uncertain spaces: when the spacing is noticeably larger than in the rest of the word but smaller than a half-space
; for half-spaces: they are not uncertain, large enough to insert a i or small e
. for full spaces (as large as the previous glyph or close)
.; for large spaces, not as large as double spaces
.. for double spaces (as large as two previous glyphs)
/ and \ for (large) vertical offsets with less than a full horizontal space
[e] for the rare e under a gallows leg
+ for the possibly fused glyphs (with a common part): a+r instead of a', a+n instead of u, etc.
";" conflicts with the HTML-like "@number;" or maybe not, because ";" is not really necessary after @number for parsing so I omitted it.
"[e]" conflicts with the "[:]" notation, or maybe not, because there is no ":".
Any suggestions? Thanks.
I have an unfinished transliteration with some non-standard notations that I could (maybe) make compatible with some flavor of the EVA format for sharing.
I used:
, for uncertain spaces: when the spacing is noticeably larger than in the rest of the word but smaller than a half-space
; for half-spaces: they are not uncertain, large enough to insert a i or small e
. for full spaces (as large as the previous glyph or close)
.; for large spaces, not as large as double spaces
.. for double spaces (as large as two previous glyphs)
/ and \ for (large) vertical offsets with less than a full horizontal space
[e] for the rare e under a gallows leg
+ for the possibly fused glyphs (with a common part): a+r instead of a', a+n instead of u, etc.
";" conflicts with the HTML-like "@number;" or maybe not, because ";" is not really necessary after @number for parsing so I omitted it.
"[e]" conflicts with the "[:]" notation, or maybe not, because there is no ":".
Any suggestions? Thanks.