bentalagan/glaemscribe

Glaemscribe, the tolkienian languages/writings transcription engine.

glaemscribe's Issues

Vietnamese tengwar mode needed

[Quenya/Sarati] : wrong handling of 'qui'

Qenya ui is desambiguated as uy thus breaks disambiguation of qu and leads to wrong treatment of sequence 'qui' . Rules should be reversed.

Thanks to Roman Rausch for noticing!

IDE: Charset panel loses current font upon character addition

IDE v1.0.0 in Firefox
When I add a new character in the charset panel (let's say, default charset is sarati_eldamar, and I add char "38" as "SARATI_P_FINAL"), the font in the charset panel switches back to roman (apparently no style attribute in the HTML).
Workaround: Just changing the font name back and forth refreshes the panel ;-)

Missing E_TEHTA_GRAVE_INF (and other possible 'below' tehtar)

There are many tehtar that don't have a below counterpart, should we add them to the fonts?

They aren't defined in the standard unicode layout and the Free Tengwar Font, and are somewhat specific (for now) just for my Vietnamese mode, so my first thought is I should add them manually for my own, but I don't know if there is a toolchain to build the sdfs? When I generated Tengwar Annatar GlaemUnicode for testing, I see a big different in size (mine is 70KB, yours is 97KB).

So if you don't want to add these specific tehtar to the standard fonts here, please give me some guidelines to build the sdfs. Thank you. :)

IDE documentation minor issues

Documentation should state that conditions also accept the ! boolean operator for negation: it works well, yeah ;)

npm compatibility?

Hi!
Thank you for making this great framework! Would you consider creating a package.json file for npm compatibility? It would make it easier for us who use Glaemscribe to stay current.

Tengwar Eldamar GlaemUnicode doesn't stand alone

When I install both Glaemscrafu and GlaemUnicode versions, they are listed as 1 family with 2 “Regular” font faces. So when I specified the font to be “Tengwar Eldamar GlaemUnicode” in the editor, it doesn't work.

However, there is no problem with Annatar and others.

Custom Glaemscrafu font name issue

Font SaratiEldamarRTLBarGlaemscrafu.ttf (for instance, not check with other fonts yet) installs on Windows as "Sarati Eldamar RTL Bar", i.e. the same name as the original Sarati Eldamar RTL Bar, prompting for its replacement on the system. Some users might want to keep the original font for other applications.

Consider reversing sa-rinke and vowel-tehta in Dan Smith style fonts

You may want to consider reversing the order of sa-rinke and vowel-tehta for Dan Smith fonts. Right now it is:

consonant:sa-rinke:vowel-tehta

That puts the vowel-tehta above the sa-rinke, which looks weird. If you reverse the order you will get a better result:

consonant:vowel-tehta:sa-rinke

I used apsa, otso and tixe to test this (tixe doesn't change).

Other Pustar punctuation

Should we address these Quadruple Pusta, Squared Quadruple Pusta, Quintuple Pusta which are included in FreeMonoTengwar, Elfica and Eldamar, but not in Annatar and others? I mean the fonts, not the charsets.

P/S: Elfica doesn't have the middle one, Squared Quadruple Pusta.

Typo: xanga in website side panel

In the raw tengwar side panel on the website, the "xanga" character is actually the "xungwe" character.

Four dots (U+2058) and tricolon (U+205D) appear incorrectly in printed document (pdf)

This only happen when I use Microsoft Word and export pdf file from it. This doesn't happen with LibreOffice. (I only use Microsoft Print to PDF to export the pdf.)

This is in MS Word, the text appear correct

This is the pdf I've exported

Elfica is wrong too, I've forgot to draw the rectangle around it.

PUNCT_TDOT is missing in every charsets

No charset has the definition for three-dots punctuation (U+02C6).

Fonts : No XS version of the consonant modification signs (tild+dash) for halla/ara/telco

1. It seems that Halla isn't included in any virtual tehta below, though Telco and Ara are (even Ara cannot hold any tehta below either way).

2. I have another small problem. It turns out that my mode doesn't play well with Tengwar Annatar (and possibly some other fonts). I use the GEMINATE_SIGN to represent the labialization mark, but the DASH_INF_S doesn't appear well on Telco and Halla. I wonder if you can generate an XS size for just Telco and Halla? I know it could be bothersome because you might also have to generate a XS version for other dashes and tildes. If you don't want to make it, I could make it by my own later on.

Currently

Should be like this

Have full control of unicode input chars, like invisible spaces, and glaemscribe mode language specific characters

This discussion was originally started in #15.

Glaemscribe did not give the possibility to have certain chars as input for a mode, either because they are invisible chars (word joiners, & so on) so they are extremely hard to write in the mode file, or because they are part of the language (* [ ] ( ) _ , and so on).

This is now fixed by commit 06c4fea with the new following feature, unicode vars can be used in rule source members and also in variable definitions. The syntax is {UNI_XXXX} with XXXX being a hexadecimal value.

The following shortcuts have been added to the engine :

        # Characters that are not easily entered or visible in a text editor
        add_var("NBSP",           "{UNI_A0}")
        add_var("WJ",             "{UNI_2060}")
        add_var("ZWSP",           "{UNI_200B}")
        add_var("ZWNJ",           "{UNI_200C}")        

        # The following characters are used by the mode syntax.
        add_var("UNDERSCORE",     "{UNI_5F}")
        add_var("ASTERISK",       "{UNI_2A}")
        add_var("COMMA",          "{UNI_2C}")
        add_var("LPAREN",         "{UNI_28}")
        add_var("RPAREN",         "{UNI_29}")
        add_var("LBRACKET",       "{UNI_5B}")
        add_var("RBRACKET",       "{UNI_5D}")

Will be released with the branch TolkiensReadingDay2018 .

Design advanced Tengwar fonts for handling complex combinations and layouts

Opening this thread as a follow up of #22, #15 and other numerous issues regarding tehta/sarince/ar-rince/consonant modifier placement, for further discussions.

Feature : [Quenya/Sarati] : Punctuation

Not yet handled, should be added!

Thanks to Roman Rausch for noticing!

Error when try to load sessions which use FreeMonoTengwar or Tengwar Telcontar fonts

I cannot load this saved session:

Console log:

Add support for Eldamar Opentype

All is in the title, the font was released recently by Måns :

http://at.mansbjorkman.net/eldamar/

[Guni Charsets] DQUOT_OPEN and DQUOT_CLOSE do not correspond to elvish usage

In the standard mapping of Tengwar Unicode, DQUOT_OPEN is the higher one, while DQUOT_CLOSE is the lower. This problem appears in all GlaemUnicode fonts.

Wrong position of U+E054 in Tengwar Eldamar Glaemscrafu font

This is the comparision table between Tengwar Eldamar Glaemscrafu and Tengwar Eldamar Alt. Green cells are the expected results.

[Quenya/Sarati] hl/hr not treated correctly

hl & hr do not exist in early Qenya, but do exist in later Quenya, so they should be treated as units.

Thanks to Roman Rausch for noticing!

Is there a way to merge the rules?

Could I possibly do something to merge these rules into 1 single rule, since the vowels are the only things that make them different?

_a [{TONES_FULL}] [{FINALS}] --> 1, 4, 2, 3 --> {_ZERO_} [{_FINALS_OPENED_}] {_A_}       [{_TONES_FULL_}]
_ă [{TONES_FULL}] [{FINALS}] --> 1, 4, 2, 3 --> {_ZERO_} [{_FINALS_OPENED_}] {_A_BREVE_} [{_TONES_FULL_}]
_â [{TONES_FULL}] [{FINALS}] --> 1, 4, 2, 3 --> {_ZERO_} [{_FINALS_OPENED_}] {_A_HAT_}   [{_TONES_FULL_}]
_e [{TONES_FULL}] [{FINALS}] --> 1, 4, 2, 3 --> {_ZERO_} [{_FINALS_OPENED_}] {_E_}       [{_TONES_FULL_}]
_ê [{TONES_FULL}] [{FINALS}] --> 1, 4, 2, 3 --> {_ZERO_} [{_FINALS_OPENED_}] {_E_HAT_}   [{_TONES_FULL_}]
_i [{TONES_FULL}] [{FINALS}] --> 1, 4, 2, 3 --> {_ZERO_} [{_FINALS_OPENED_}] {_I_}       [{_TONES_FULL_}]
_ơ [{TONES_FULL}] [{FINALS}] --> 1, 4, 2, 3 --> {_ZERO_} [{_FINALS_OPENED_}] {_O_HORN_}  [{_TONES_FULL_}]
_ư [{TONES_FULL}] [{FINALS}] --> 1, 4, 2, 3 --> {_ZERO_} [{_FINALS_OPENED_}] {_U_HORN_}  [{_TONES_FULL_}]
_y [{TONES_FULL}] [{FINALS}] --> 1, 4, 2, 3 --> {_ZERO_} [{_FINALS_OPENED_}] {_Y_}       [{_TONES_FULL_}]
_ō [{TONES_FULL}] [{FINALS}] --> 1, 4, 2, 3 --> {_ZERO_} [{_FINALS_OPENED_}] {_OO_}      [{_TONES_FULL_}]

Note: {_ZERO_}, {_FINALS_OPENED_}, {_TONES_FULL_} are the Tengwar counterparts of {NULL}. {FINALS}, {TONES_FULL} which are Latin. The same for the others.

Phonetic mode for Vietnamese

I see no problem sharing my mode implementation for Vietnamese, which is my mother tongue, at all. I still haven't made any changes to the rules yet. I think sharing this in its current form might help you a bit figuring out any potential problem. Since Vietnamese has 6 tones and many vowels, could it be complex enough for some problems to emerge out of your prediction?

Phonetic mode for Vietnamese.zip

This is an example text. Note: the parantheses indicate words written in other modes.

Reposition characters that override the soft-hyphen

Please reposition any character that overrides the soft-hyphen (U+00AD). Because soft-hyphens are always hidden in modern text processors, then characters at this position are hidden also.
Fonts affected: Tengwar Annatar, Tengwar Parmaite, Tengwar Elfica, Tengwar Sindarin (also Quenya).

Currently Tengwar Eldamar uses the position U+20AC instead.

Add missing documentation

New features are missing some doc :

Modes :

• Dynamic, pointer vars
• Macros

Charsets :

• Sequence chars

Broken link in Readme.md

The integration link on the main page of this repo https://bentalagan.github.com/glaemscribe should be https://bentalagan.github.io/glaemscribe.

[Discussion/Specification] Relayout/Remap legacy fonts ?

I've just found out that non-breaking space is missing in Annatar, Eldamar and Sindarin fonts. If I use that space, its font will be changed to the default and the spacing is not correct.

Also, Glaemscribe processor seems to ignore the non-breaking space. I've added a definition for it in the charset and use it in the mode, but the output text contains only normal spaces.

\outspace doesn't support a sequence

I would like to use \outspace with a sequence of characters (\outspace CIRTH_SPACE CIRTH_PUNCT_MID_DOT CIRTH_SPACE) so there's a bit of space around the dot), which the documentation says is supported - however it doesn't work and I get:

Mode has some errors:

45: Element 'outspace' should have 1 arguments.

Web browsers word-wrapping may break some words when using some tengwar fonts in certain circumstances

A good example is better than an explanation ; with the currently merged annatar fonts, a word like lumbule would be transcribed :

な&w&j$

because the ligatured lambe is mapped within the japanese unicode set, the word wrap breaking logic of web browsers will allow this word to be cut after the ligatured lambe at the end of a line.

Solution 1 (fastest) : change the mapping of incriminated characters. One good idea would probably to stick to tengwar elfica's mapping.

Solution 2 (painful, and a long work : but cool) : start migrating the old generation fonts to opentype with gsub and gpos tables, and use the free tengwar font project mapping .