Could all translations offer a resp attribute, allowing for the translator of that particular version? And could this please allow for several translations, (eg 2 English, one German, one Arabic) of the same text, with a different rep for each one?
I think that if we are going for a solution that covers everything, we need to reflect the fact that
Many translations will come from published sources - so @source if possible
For longer documents there are frequently translations of parts/sections. But each of those is a translation, a free-standing intellectual item. I suggest that each translation - whether of the complete text or of a section , is <div type="translation”>. If so, should the information about the relevant part which has been translated be encoded? How?
Last edit: BODARD Gabriel 2016-07-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Certainly <div> can take both @xml:lang and @resp (although not yet @source as far as I can see, which we would want to use if a translation was taken from a prior publication rather than new by an editor of the current edition).
One question that remains is whether to encode a separate <div type="translation"> for each separate translation, or have a single div with a <div type="textpart"> for each different language and author within it. I vote for the former, on the grounds that each is (presumably) a translation of the whole inscription, rather than of separate parts of it. Pretty sure this is what we did for IOSPE (although we haven't yet attributed Russian translations to Vinogradov and English to Polinskaya, but we probably should).
Some examples of this in the EpiDoc Guidelines would be nice. Perhaps a nice short text, translated into Russian, English and French? (Or a Libyan text into English, French, Italian, and Arabic?) @source for multiple published English translations would also be good, but we need to check with Hugh and Elli whether this is something that will come with the new TEI developments of @resp/@source?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Elli goes to TEI and follows up on @source and @resp - feature request that they should both be part of att.responsibility. Look into earlier discussions as well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
in response to Charlotte's last query - @source and @resp are now allowed to appear on <div>. As for best practice for translations - They could nest within a translation div, although the example given above has some bits that aren't really parallel. - There is an overall <div type="translation"> with a <head> within it. Then the <head> repeats inside the next two translations, but not in the third. Maybe the repeated <head> should only be on the outermost div.
In discussion, we agreed that ideally translations should be siblings, and did not need to nest inside a parent translation div. The heading "Translations" could be generated by the XSL and doesn't need to be part of the markup.
There should be no confusion if there is a series of translation divs that contain translations of the whole inscription. It may make sense to have nested translation divs if separate parts of the inscrption have different translators. These could also be handled with <div type="textpart">
Last edit: Elli Mylonas 2018-02-20
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Add a sentence noting the availability of @source and @resp DONE
Use @resp in the example. I found the Iospe inscription that is being used in that example and assume from the information in the XML file and the mention above that the Russian translator is AVinogradov and the English is IPolinskaya. I've added them. Spelling and abbreviation can be adjusted. DONE
Provide prose discussing when to nest translations. NOT DONE
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think that if we are going for a solution that covers everything, we need to reflect the fact that
<div type="translation”>. If so, should the information about the relevant part which has been translated be encoded? How?Last edit: BODARD Gabriel 2016-07-19
Certainly
<div>can take both@xml:langand@resp(although not yet@sourceas far as I can see, which we would want to use if a translation was taken from a prior publication rather than new by an editor of the current edition).One question that remains is whether to encode a separate
<div type="translation">for each separate translation, or have a single div with a<div type="textpart">for each different language and author within it. I vote for the former, on the grounds that each is (presumably) a translation of the whole inscription, rather than of separate parts of it. Pretty sure this is what we did for IOSPE (although we haven't yet attributed Russian translations to Vinogradov and English to Polinskaya, but we probably should).Some examples of this in the EpiDoc Guidelines would be nice. Perhaps a nice short text, translated into Russian, English and French? (Or a Libyan text into English, French, Italian, and Arabic?)
@sourcefor multiple published English translations would also be good, but we need to check with Hugh and Elli whether this is something that will come with the new TEI developments of@resp/@source?Elli goes to TEI and follows up on @source and @resp - feature request that they should both be part of att.responsibility. Look into earlier discussions as well.
Should this ticket be assigned to Elli given previous comment?
The source attribute will be inherited from the TEI 3.1.0 release (scheduled for Dec 6).
I'm confused: div can have both @source and @resp.
What remains seems to be an example with several translations.
However, the page on translation seems to a) mention both @source and @resp and there are some nice translation examples. What remains?
This what I have:
Is the redundancy of translation with translation OK?
Many thanks
C
Last edit: BODARD Gabriel 2018-02-20
in response to Charlotte's last query -
@sourceand@respare now allowed to appear on<div>. As for best practice for translations - They could nest within a translation div, although the example given above has some bits that aren't really parallel. - There is an overall<div type="translation">with a<head>within it. Then the<head>repeats inside the next two translations, but not in the third. Maybe the repeated<head>should only be on the outermost div.In discussion, we agreed that ideally translations should be siblings, and did not need to nest inside a parent translation div. The heading "Translations" could be generated by the XSL and doesn't need to be part of the markup.
There should be no confusion if there is a series of translation divs that contain translations of the whole inscription. It may make sense to have nested translation divs if separate parts of the inscrption have different translators. These could also be handled with
<div type="textpart">Last edit: Elli Mylonas 2018-02-20
What needs to be done with this FR:
@sourceand@respDONE@respin the example. I found the Iospe inscription that is being used in that example and assume from the information in the XML file and the mention above that the Russian translator is AVinogradov and the English is IPolinskaya. I've added them. Spelling and abbreviation can be adjusted. DONEPartially done with commit [r2695].
Related
Commit: [r2695]
closing with commit 2741