search

readsoftware / ReadIssues

This is an issue repository for READ. Intended for issues and feature change request that arise during testing and development.
0 stars 0 forks source link

Parser - ü at compound boundary #163

Open IanMcCrabb opened 4 years ago

IanMcCrabb commented 4 years ago

All instances are at the beginning of the second member of a compound e.g. aya-üda. No errors on import, so would seem that there is an issue with the parser code on compound boundaries and the ü character. Stored as aya-uda

stevewh commented 4 years ago

Here is the explanation given to me. au is a ligature stored as a single grapheme and displayed as au aü is stored as a followed by u, the om-lat is used on import and in display to signify this when a is next to u in a word.

aya-üda while this seems redundant with the compound separator it matches the case above when the separator is not shown.

On Thu, Dec 5, 2019 at 1:32 AM IanMcCrabb notifications@github.com wrote:

Assigned #163 https://github.com/readsoftware/ReadIssues/issues/163 to @stevewh https://github.com/stevewh.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/readsoftware/ReadIssues/issues/163?email_source=notifications&email_token=AARYOIKG2US5YJTOOFVWEMDQXBDYLA5CNFSM4JVR7HG2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVI6BLTY#event-2856064463, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARYOIJHQLS5LQCPOK7QJRLQXBDYLANCNFSM4JVR7HGQ .

IanMcCrabb commented 4 years ago

Our case is that we are importing aya-üda and the parser is bringing this in as aya-uda where the supplied ü is being stored as ?u

stevewh commented 4 years ago

From what I understand, this is correct, as it is a separate u. The specification that was explained to me is that a separate standalone u that follows a or o (whether standalone or part of the preceding syllable) must have a displayed om-lat. The om-lat is display and import only. The u is stored in a syllable of ʔu.

Let me know if this needs to be looked at again.

On Thu, Dec 5, 2019 at 2:46 AM IanMcCrabb notifications@github.com wrote:

Our case is that we are importing aya-üda and the parser is bringing this in as aya-uda where the supplied ü is being stored as ?u

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/readsoftware/ReadIssues/issues/163?email_source=notifications&email_token=AARYOIPPGTHQAIDUKJKLWSLQXBMO7A5CNFSM4JVR7HG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF7FSKI#issuecomment-561928489, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARYOILN5BEFGOTUW6LYPSTQXBMO7ANCNFSM4JVR7HGQ .

IanMcCrabb commented 4 years ago

OK, get all that. What I've failed with in my explanation is that it is NOT displaying as ü

stevewh commented 4 years ago

The issue has been raised again in #183 where a compound word is composed of a word ending in 'a' and a second word beginning with 'u'. The issue is that it should be display with the om-lat.