Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

alphabetic Ugaritic: word divider error; h displaying as ḫ #381

Open
matthewrutz opened this issue May 21, 2019 · 2 comments
Open

alphabetic Ugaritic: word divider error; h displaying as ḫ #381

matthewrutz opened this issue May 21, 2019 · 2 comments

Comments

@matthewrutz
Copy link

  • Nammu's version: nammu-1.0.1.jar
  • Java version: java version "11.0.1" 2018-10-16 LTS
  • Computer Platform: OSX 10.13.6

@JacobLauinger and I have been working on editing texts in alphabetic Ugaritic (uga-040) using Nammu. We are following the Oracc documentation:

http://oracc.museum.upenn.edu/doc/help/languages/ugaritic/index.html

Two issues have emerged:

  1. The alphabetic cuneiform word divider is flagged as an error. The convention in the field is to use "." but the documentation demands "|". Neither worked. We deleted the word dividers and built the text, but we will need to put them back once the issue is resolved. I went to do a screen grab of the text with the error code, but the checker is not working at the moment; I'll append an example later.

  2. Unlike Akkadian cuneiform (akk), Ugaritic has both phonemes/graphemes /h/ and /ḫ/. We need to be able to input /h/ and have it display as /h/ NOT as /ḫ/ in uga-040. For example, the text KTU3 2 11 (RS 8 315) X000001 has the lemma "hnny" which should display as "hnny" NOT "ḫnny".
    KTU3-2-11_h-h_-problem

Many thanks!

@JacobLauinger
Copy link

Here's a screenshot of a different alphabetic text that still has the word dividers to show the errors.

Thanks!
Jake

Screen Shot 2019-05-22 at 10 43 17 AM

@giordano
Copy link
Contributor

Thanks for the detailed report! Note that Nammu receives those message from server validation and simply forwards them. @stinney is responsible for the server development, probably he can have a look at this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants