Validation error on K. 333

[ajaniak]

Dear @chhomkunthea,

The issue regarding this file can be easily settled. There are 2 <supplied> tags used without @reason:

• XML line 183 for

  <p n="A34-36">Équipe de serviteurs de la commune de Carāṃ, <foreign>pramān</foreign> de Qamoghapura <supplied >suit une liste comprenant, dans l’ordre : 1 <foreign>qamraḥ</foreign>, 1 <foreign>gho</foreign>, 1 <foreign>tai</foreign>, 1 <foreign>sī pau</foreign>, 1 <foreign>sī rat</foreign>, 2 <foreign>tai</foreign>, 1 <foreign>gvāl</foreign></supplied> ;</p>

• XML line 200 for

  <p n="B46-47">Équipe de serviteurs de la commune de Travāṅ Kbas : <supplied >suit une liste de serviteurs comprenant, dans l’ordre : 1 <foreign>qamraḥ</foreign>, 1 <foreign>gvāl</foreign></supplied> ;</p>

Let me know if you need help Best,

[arlogriffiths]

my eyes fall in this example on some other things that need to be changes systematically when encoding translations:

1. adapt transliteration to the system prescribed in DHARMA TG.

   • Carāṃ should be Carāṁ.
   • I am not sure yet about the conclusions that can be drawn from the discussion with Michel Antelme, but I suspect we’ll be able to revert to more conventional Amoighapura

2. don’t apply French spaces before punctuation signs.

   • dans l’ordre : 1 --> dans l’ordre: 1 (if our system is smart, il will be able to insert French espaces insécables automatically, because of the attribution of xml:lang="fra".)

@danbalogh @ajaniak : if you agree on the second point, we probably want to include a rule in the EG.

[chhomkunthea]

Dear Axelle and Arlo,

I have corrected the errors reading and ṁ. For the colon (:), I have removed all the space before the punctuation mark. I’ll see that this rule is applied also in other files.

Best, Kunthea

Le 9 avr. 2020 à 00:37, arlogriffiths notifications@github.com a écrit :

my eyes fall in this example on some other things that need to be changes systematically when encoding translations:

adapt transliteration to the system prescribed in DHARMA TG.

Carāṃ should be Carāṁ. I am not sure yet about the conclusions that can be drawn from the discussion with Michel Antelme, but I suspect we’ll be able to revert to more conventional Amoighapura don’t apply French spaces before punctuation signs.

dans l’ordre : 1 --> dans l’ordre: 1 (if our system is smart, il will be able to insert French espaces insécables automatically, because of the attribution of xml:lang="fra".) @danbalogh https://github.com/danbalogh @ajaniak https://github.com/ajaniak : if you agree on the second point, we probably want to include a rule in the EG.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/erc-dharma/tfc-khmer-epigraphy/issues/9#issuecomment-611093488, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM4GVN5JD3P7UVOAVFHDHCLRLSY6NANCNFSM4MEBY72A.

[arlogriffiths]

@ajaniak : please confirm that when encoding text in French language, layout space of the type "espace insécable devant ponctuation" should/can be left out; if yes, then @danbalogh will add a note to that effect in EG; if no, then @chhomkunthea needs to undo the changes she has just made on that point.

[ajaniak]

@arlogriffiths, I will handle it.

[danbalogh]

I've added §10.8 to the Encoding Guide, mentioning this:

• in general, observe the punctuation conventions of whichever modern language you are writing in
• when writing in French, it is not necessary to create the espace insécable devant ponctuation, which can be handled automatically

I don't think it makes sense to forbid such spaces, since I suppose many of us will be copy-pasting pre-written text into our XML files, and having to manually remove these pre-existing spaces is a needless chore. (For one, I'm certainly pasting Estienne-Monod's French translations of Calukya plates and would rather not have to delete those spaces manually.) I should also note that punctuation is not an encoding matter and that if we do include punctuation instructions of any kind in the EG, they should be more exhaustive than the two lines above, which in turn means that some of us will have to devise and agree on specific punctuation rules for several languages. Do we really need this?

[arlogriffiths]

Thanks @danbalogh . After discussion with Axelle, it seems that she is able to take this matter out of the hands of the encoders — in other words, even if the encoded bits of French text are inconsistent in use/non-use of spaces before punctuation signs, or in use of non-breaking/breaking spaces, she can impose regularity on our files, and thus in display, on her end.

So @danbalogh: you could perhaps undo the addition you've made to §10.8, or leave it intact because the fact that French is singled out is perhaps justified because French will certainly be our most commonly use European language after English.

@chhomkunthea : the upshot is that it wouldn't have been necessary to remove those spaces before ":", but their removal doesn't hurt either. In the future, no need to worry about this issue.

[chhomkunthea]

Ok, well noted. I have removed the space. So I just leave the file like this.

Best, Kunthea

Le 10 avr. 2020 à 21:13, arlogriffiths notifications@github.com a écrit :

Thanks @danbalogh https://github.com/danbalogh . After discussion with Axelle, it seems that she is able to take this matter out of the hands of the encoders — in other words, even if the encoded bits of French text are inconsistent in use/non-use of spaces before punctuation signs, or in use of non-breaking/breaking spaces, she can impose regularity on our files, and thus in display, on her end.

So @danbalogh https://github.com/danbalogh: you could perhaps undo the addition you've made to §10.8, or leave it intact because the fact that French is singled out is perhaps justified because French will certainly be our most commonly use European language after English.

@chhomkunthea https://github.com/chhomkunthea : the upshot is that it wouldn't have been necessary to remove those spaces before ":", but their removal doesn't hurt either. In the future, no need to worry about this issue.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/erc-dharma/tfc-khmer-epigraphy/issues/9#issuecomment-612046212, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM4GVNY4LXAA6Y47CVLH4ALRL4SP5ANCNFSM4MEBY72A.