Skip to content

eBL ATF and other ATF flavors

Jussi Laasonen edited this page May 21, 2021 · 17 revisions

eBL-ATF specification

  • eBL validates transliterations against a sign list. If a value is not present in the sign list, the transliteration is considered invalid even if the syntax is correct.

Oracc ATF

  • $ for Is not a logogram (see here) is not supported. It should be removed from the text.
  • Line number is a sequence of non-space characters. Conversion to the stricter eBL-format is not possible in the general case.
  • * = Bullet, the "1" used at the start of each line in lexical texts, omen compendia, etc.. Should be converted to DIŠ.
  • \t always will be converted to a space character .
  • Only interlinear translations are supported. The extent of the translation can be given after the language code, e.g. tr.en.(o iii 3):.

Legacy grammar

  • Vowels ([aeiuAEIU]) can have acute and grave accents, which correspond to and in the sign respectively. Thus, šáša₂, àmam₃

Lemmatization

In Oracc lemmatization is done with #lem: lines. eBL has specialized GUI for lemmatization, which is separate from the transliteration. Oracc transliteration needs to be converted and saved first. Then the Oracc lemmatization has to be converted to the eBL lemmatization object and updated to the fragment.

C-ATF

Archibab ATF

See here

  • (){} (i.e., determinatives)
  • ⸢SIGN-SIGN SIGN SIGN⸣SIGN#-SIGN# SIGN# SIGN#
  • (?)? (after signs)
  • (!)! (after signs)
  • As in the ATF Legacy Grammar, Vowels ([aeiuAEIU]) can have acute and grave accents, which correspond to and in the sign respectively. Thus, šáša₂, àmam₃
  • The lemmatization is not convertible, since it uses French GWs Capture d’écran 2020-04-17 à 11 32 53