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

Conversion of transliteration from ge'ez #116

Closed
FrancescaPanini opened this issue Aug 10, 2016 · 21 comments
Closed

Conversion of transliteration from ge'ez #116

FrancescaPanini opened this issue Aug 10, 2016 · 21 comments
Assignees
Labels
data changes to the TEI or RDF data required

Comments

@FrancescaPanini
Copy link
Contributor

The rules on the conversion of the translitteration of ge'ez names (eg Addäbabay -> Āddabābāy?) are unclear: is it possible to clarify how the translitteration needs to be changed from how it appears in the Encyclopaedia in order to avoid inconsistencies and misunderstandings, please?

@PietroLiuzzo
Copy link
Member

PietroLiuzzo commented Aug 10, 2016

just to add reference to what we have now as minimal guidance in the guidelines
https://github.com/SChAth/ScAthiop/wiki/guidelines#omologation-of-transcription-from-ea

@abausi
Copy link

abausi commented Aug 11, 2016

Dear Francesca,

please, note that there is a correction to be done in the general rules,
namely:

ፀ = ḍ (not ś plus dot below)

Moreover: note that there will be inconsistencies at this stage, the
reason for which is that in previous projects ("Encyclopaedia
Aethiopica" and "Ethio-SPaRe") were used transcription systems which are
not good for written texts. For the moment we cannot do anything else,
unfortunately, but to render them mechanically, since without precise
linguistic competences and in some cases without checking the texts, we
cannot decide automatically for all cases.

Ambiguity is still in the rule:

  Omologation of transcription from EA (and Ethio-SPaRe)
  • all the above should be applied to transcriptions from ETHIOPIC only.
  • ä for first order should be changed into a
  • a for fourth order should be changed into ā

because (that's the problem!), for "a" with laryngeals we can have both
first and fourth order.

Note here in details the following ambiguities (with the so-called
laryngeals):

A, a (at the beginning of a word, A/a vowel occurs only here) > ʾA / ʾĀ,
ʾa / ʾā: IN PRACTICE: render it with ʾA, ʾa

ʿA (or ʿa) > ʿA / ʿĀ (or ʿa / ʿā): IN PRACTICE: render it with ʿA, ʿa

Ha (or ha) > Ha / Hā(or ha / hā): IN PRACTICE: render it with Ha, ha

Ḥa (or ḥa) > Ḥa / Ḥā (or ḥa / ḥā): IN PRACTICE: render it with Ḥa, ḥa

Ḫa (or ḫa) > Ḫa / Ḫā (or ḫa / ḫā): IN PRACTICE: render it with Ḫa, ḫa

Best,

Alessandro

Il 10.08.2016 21:43, Pietro Liuzzo ha scritto:

https://github.com/SChAth/ScAthiop/wiki/guidelines#omologation-of-transcription-from-ea


You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
#116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATDMaKKPh6h7hd81-3-XBnw74H8Ptgqkks5qejfhgaJpZM4Jhjje.

@PietroLiuzzo
Copy link
Member

@abausi may I copy the laryngeals guidances in the guidelines as it is here? I have updated already ḍ .

@FrancescaPanini
Copy link
Contributor Author

Thank you very much, this helps putting it into context.

Just one last confirmation, if possible, please: these rules are to be applied to ALL translitterations from ge'ez, including all place names so that Gondär (Encyclopaedia Aethiopica) will become Gondar?

Thanks again,
regards
Francesca

@abausi
Copy link

abausi commented Aug 11, 2016

Please, do it. If there are further corrections, we will update again.

Il 11.08.2016 09:23, Pietro Liuzzo ha scritto:

@abausi https://github.com/abausi may I copy the laryngeals
guidances in the guidelines as it is here? I have updated already ḍ .


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATDMaMJYVVlkV4Z19ZMe-nA6tFZ_oNpWks5qes35gaJpZM4Jhjje.

@abausi
Copy link

abausi commented Aug 11, 2016

We should agree on this, since the name has also an Amharic form and I
do not know how this question was solved. Yet, since we are meanly
dealing with written sources, I think it should be "Gondar" as well (not
"Gondär").

Il 11.08.2016 09:50, FrancescaPanini ha scritto:

Thank you very much, this helps putting it into context.

Just one last confirmation, if possible, please: these rules are to be
applied to ALL translitterations from ge'ez, including all place names
so that Gondär (Encyclopaedia Aethiopica) will become Gondar?

Thanks again,
regards
Francesca


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATDMaMiee9kmkPX-6fiR2dIKRAFVR1lwks5qetRTgaJpZM4Jhjje.

@eu-genia
Copy link
Contributor

eu-genia commented Aug 17, 2016

A, a (at the beginning of a word, A/a vowel occurs only here) > ʾA / ʾĀ, ʾa / ʾā: IN PRACTICE: render it with ʾA, ʾa (@abausi)

while this is of course correct, if we always use short a after laryngeals we shall have transcriptions in BM that are different from the ones used in TraCES. E.g., in TraCES አምሃራ will be rendered as ʾAmhāra and in BM as ʾAmhara; ሃይማኖት as Hāymanot and Haymanot, etc. I see a problem of consistency esp. when we link the named entities.

@abausi
Copy link

abausi commented Aug 17, 2016

This was OBVIOUSLY only the indication for the first step of automatic
conversion before the actual real transcription is established in each
case. The "good" final form (either a or ā) can only be verified on the
single textual passages, and cannot be automatically determined (that's
why it would have been so important that in cataloguing a different
system, based upon writing and not pronunciation, was used).


I am out of office and will have only limited access to email and even less time to answer. Your message can go lost. Probably better to write again later, in September?

Many thanks!

A.B.


Non sono in servizio e avrò solo un accesso limitato alla posta elettronica, e ancor meno tempo per rispondere. Il messaggio può andar perduto. Forse meglio riscrivere tra un po', verso settembre?

Grazie molte,

A.B.

Il 17.08.2016 13:36, eu-genia ha scritto:

A, a (at the beginning of a word, A/a vowel occurs only here) > ʾA
/ ʾĀ,
ʾa / ʾā: IN PRACTICE: render it with ʾA, ʾa
(@abausi <https://github.com/abausi>)
while this is of course correct, if we always use short a after
laryngeals we shall have transcriptions in BM that are different
from the ones used in TraCES. E.g., in TraCES አምሃራ will be
rendered as ʾAmhāra and in BM as ʾAmhara; ሃይማኖት as Hāymanot and
Haymanot, etc. I see a problem of consistency esp. when we link
the named entities.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATDMaLGV62CoQQkHjWH9RS8XYf9rOhzZks5qgwBegaJpZM4Jhjje.

@abausi
Copy link

abausi commented Aug 17, 2016

Of course, even in the case of the form to be necessarily used for
reference (apart from variations in single textual passages), no general
decision can be automatically taken. For linguistically determined
forms, we can base on the work of TraCES, which considers patterns,
nominal formation and derivation, morphology etc. but there cases where
a decision is not easy. This, once again, cannot be automatically done.
But important is that we start from a uniform situation, where the new
system is set up (with an a/ā oppoistion, against ä/a of EAe and
Ethio-SPaRe). The provided indications were intended to start correctly
the conversion into our (BM and TraCES) system, devised for written
evidence.

Il 17.08.2016 13:36, eu-genia ha scritto:

A, a (at the beginning of a word, A/a vowel occurs only here) > ʾA
/ ʾĀ,
ʾa / ʾā: IN PRACTICE: render it with ʾA, ʾa
(@abausi <https://github.com/abausi>)
while this is of course correct, if we always use short a after
laryngeals we shall have transcriptions in BM that are different
from the ones used in TraCES. E.g., in TraCES አምሃራ will be
rendered as ʾAmhāra and in BM as ʾAmhara; ሃይማኖት as Hāymanot and
Haymanot, etc. I see a problem of consistency esp. when we link
the named entities.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATDMaLGV62CoQQkHjWH9RS8XYf9rOhzZks5qgwBegaJpZM4Jhjje.

@eu-genia
Copy link
Contributor

so, @FrancescaPanini and everyone else: we do distinguish between the 1st and the 4th order also after laryngeals when we can/know - so please correct everywhere ʾAmhāra , ʾAzazo Takla Hāymanot, etc. (@PietroLiuzzo: to be corrected also in the guidelines)

@abausi
Copy link

abausi commented Aug 17, 2016

Yes - when we can: but this is a completely different step from the
question of the automatic conversion from the index of "EAe" (ʾAmhāra is
probably etymologically "ʾAmḥāra", but difficult to say more).

Il 17.08.2016 14:34, eu-genia ha scritto:

so, @FrancescaPanini https://github.com/FrancescaPanini and everyone
else: we do distinguish between the 1st and the 4th order also after
laryngeals when we can/know - so please correct everywhere ʾAmhāra ,
ʾAzazo Takla Hāymanot, etc. (@PietroLiuzzo
https://github.com/PietroLiuzzo: to be corrected also in the guidelines)


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATDMaIy5xcRLxHZ9nbScMH8fzww0NVo_ks5qgw3rgaJpZM4Jhjje.

@eu-genia
Copy link
Contributor

we do not do any automatic conversion though

@abausi
Copy link

abausi commented Aug 17, 2016

But this could be considered as a first setp, it would spare time.

Il 17.08.2016 14:49, eu-genia ha scritto:

we do not do any automatic conversion though


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATDMaKLvtF-miCa31tZE_SPhBj2SmuNyks5qgxFYgaJpZM4Jhjje.

@PietroLiuzzo PietroLiuzzo added the data changes to the TEI or RDF data required label Aug 17, 2016
@PietroLiuzzo PietroLiuzzo assigned PietroLiuzzo and unassigned eu-genia and abausi Aug 17, 2016
@PietroLiuzzo
Copy link
Member

we need then to change in every file not yet manually reworked which comes from EA or Ethio-SPaRe in the following sequence:

  • all a to ā
  • all ä to a
  • add ʾ at the beginning of each word starting with vowel in the transcription

@abausi
Copy link

abausi commented Aug 17, 2016

yes, but again: in case of "laryngeal + a", this is just a first
preliminary step to be later verified, case by case, or to be
immediately further interpreted, if there is enough evidence for that:
in particular, it has to be decided whether "a" has to remain or has to
be further converted into "ā": every complete systematic conversion is
impossible to apply, because it implies linguistic and other
considerations, to be seen case by case

Il 17.08.2016 16:57, Pietro Liuzzo ha scritto:

we need then to change in every file not yet manually reworked which
comes from EA or Ethio-SPaRe in the following sequence:

  • all a to ā
  • all ä to a
  • add ʾ at the beginning of each word starting with vowel in the
    transcription


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATDMaBUuC_TKK8qf3PjPvwUIVdzVsFWUks5qgy9cgaJpZM4Jhjje.

@eu-genia
Copy link
Contributor

potentially, all a to ā except if at the beginning or following a laryngeal where they remain a
Ethio-SPaRe files have ʾat the beginning

BUT: the problem remains with the non-Ethiopic words
what comes out of a work like "Acta Pilati"? or a place like "Abbaa Maalo" (Oromo)? these must not be changed

@abausi
Copy link

abausi commented Aug 17, 2016

Offline for some days.

  A.B.

@abausi
Copy link

abausi commented Aug 17, 2016

laryngeals here are to be considered only when they precede "a" ("La"),
not when they follow; in that case we have to do with another
phenomenon, that does not imply any ambiguity for the transcription: the
order perfectly corresponds

Il 17.08.2016 17:02, eu-genia ha scritto:

potentially, all a to ā except if at the beginning or following a
laryngeal where they remain a
Ethio-SPaRe files have ʾat the beginning

BUT: the problem remains with the non-Ethiopic words
what comes out of a work like "Acta Pilati"? or a place like "Abbaa
Maalo" (Oromo)? these must not be changed


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATDMaPAtUMiug757Sd_IhQ95RKi9FlQiks5qgzCzgaJpZM4Jhjje.

@abausi
Copy link

abausi commented Aug 17, 2016

OK, sorry, Zhenia had correctly formulated: I misunderstood what she
wrote ("at the beginning [of a word] or following a laryngeal", i.e. in
the position "La", is correct)

Il 17.08.2016 18:06, Alessandro Bausi ha scritto:

laryngeals here are to be considered only when they precede "a"
("La"), not when they follow; in that case we have to do with another
phenomenon, that does not imply any ambiguity for the transcription:
the order perfectly corresponds

Il 17.08.2016 17:02, eu-genia ha scritto:

potentially, all a to ā except if at the beginning or following a
laryngeal where they remain a
Ethio-SPaRe files have ʾat the beginning

BUT: the problem remains with the non-Ethiopic words
what comes out of a work like "Acta Pilati"? or a place like "Abbaa
Maalo" (Oromo)? these must not be changed


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATDMaPAtUMiug757Sd_IhQ95RKi9FlQiks5qgzCzgaJpZM4Jhjje.

@PietroLiuzzo
Copy link
Member

PietroLiuzzo commented Aug 17, 2016

From this conversation and email exchange, the proposed solution is to have a self standing tool (xslt transformation) available for cataloguers.

in the scenario of some work being carried out on a file from EA or ES, the cataloguer will have to tag with @xml:lang='gez' and @type='transcription' or other all the elements on which to apply the automatic update of the translitteration, then run once and only once the transformation which will operate the substitutions and save them to the same file for further work.

this will be useful only where a lot of text is provided inside a single element.

Links importing text from eventually not corrected files will continue to display eventually uncorrected transcriptions.

As we are not currently working mainly on this records, I will not prioritize this requirement DAT26 for now.

@abausi
Copy link

abausi commented Aug 17, 2016

OK so, it is not a priority. Important is that the fiundamental
coordinates of the process, and the relevant conditions, have been cleared.

Il 17.08.2016 17:33, Pietro Liuzzo ha scritto:

From this conversation and email exchange, the proposed solution is to
have a self standing tool (xslt transformation) available for
cataloguers.

in the scenario of some work being carried out on a file from EA or
ES, the cataloguer will have to tag with @xml
https://github.com/xml:lang='gez' and @type
https://github.com/type='transcription' or other all the elements on
which to apply the automatic update of the translitteration, then run
once and only once the transformation which will operate the
substitutions and save them to the same file for further work.

Links importing text from eventually not corrected files will continue
to display eventually uncorrected transcriptions.

As we are not currently working mainly on this records, I will not
prioritize this requirement DAT26
https://github.com/SChAth/ScAthiop/wiki/DAT26 for now.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATDMaEJbyD1Ur-M50AGHgz-Vcx7BeEJxks5qgzf2gaJpZM4Jhjje.

@eu-genia eu-genia changed the title Conversion of translitteration from ge'ez Conversion of transliteration from ge'ez Aug 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data changes to the TEI or RDF data required
Projects
None yet
Development

No branches or pull requests

4 participants