Subject: Re: [jats-list] Translations for section titles From: "Nikos Markantonatos nikos@xxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: Fri, 6 May 2022 07:48:01 -0000 |
Hi Gerrit. Thanks for sharing this illustrative example. I personally find the collection of all languages under the same <title> element by means of several <name-content> elements semantically inelegant and simply unacceptable. I suspect that the multi-lingual approach described by Vincent in JATSCon will be accompanied by a corresponding relaxing of several models in JATS to allow for "zero or more" instances rather than the stricter "zero or one" logic the models allow for today. So <label> and <title> under <sec> will have to allow for "zero or more" instances. They only allow for "zero or one" today. Same goes for <label> and <title> under <list>. A similar logic must be applied to <label> and <caption> under <table-wrap>. And the list goes on and on. Vincent, I wonder whether there has been any thought on how many models in JATS will need to be relaxed to allow for true side-by-side multi-lingual encoding. Nikos On 5/4/22 9:42 PM, Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx wrote: Hi Vincent (and list), Yesterday after your presentation and during the JATS-Con social (or happy) hour I complained that if you have a multiple-language document in which you choose to tag your content with block-level items and their translations side-by-side, you can't have translations for section titles. I was thinking of someone who followed the "content items in two or more languages" approach (https://www.ncbi.nlm.nih.gov/books/NBK579699/#lizzi-content-items-in-two-or-more-languages) by adding a translation for each figure, table-wrap, p etc. element that is allowed within a section, side by side. While you can have multiple figures, tables, paragraphs etc. in a row, you can't provide translation elements for elements that are allowed exactly once in a section, in particular, for the title element. But there's a workaround: You can have the title translations as inline content in the title element, like so: <sec id="sec1"> B <title><named-content content-type="title-content" lang-group="sec1-content" xml:lang="en">English Title</named-content> B B B <named-content content-type="title-content" lang-group="sec1-content" xml:lang="fr">Titre franC'ais</named-content> B B B <named-content content-type="title-content" lang-group="sec1-content" xml:lang="de">Deutscher Titel</named-content></title> B <p lang-group="sec1-p1" xml:lang="en">Paragraph</p> B <p lang-group="sec1-p1" xml:lang="fr">Paragraphe</p> B <p lang-group="sec1-p1" xml:lang="de">Absatz</p> </sec> So I think it's feasible by and large to pursue a block-level translation approach, with minor sacrifices where you need to process inline translations. (Note: I'm not advocating such an approach, but it came up occasionally when discussing how to tag multilingual content with customers.) Gerrit -- [IMAGE] Nikos Markantonatos | Atypon, Greece Operations Head Leoforos Ethnikis Antistaseos 39A, 3rd floor, Nea Ionia, 14234, Greece office +302110133003 | mobile +306974302945 | nikos@xxxxxxxxxx [IMAGE] atyponb.com CONFIDENTIAL: This email and any attachments may contain confidential and legally privileged information for the exclusive use of the designated recipients. Unauthorized review, use, storage, disclosure or distribution is prohibited. If you are not the intended recipient, contact the sender and destroy all copies of the original message. JATS-List info and archiveEasyUnsubscribe (by email)
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[jats-list] Translations for sectio, Imsieke, Gerrit, le- | Thread | Re: [jats-list] Translations for se, Gareth Oakes goakes@ |
[jats-list] JATS4R Accessibility Su, Beck, Jeff (NIH/NLM/ | Date | Re: [jats-list] Translations for se, Gareth Oakes goakes@ |
Month |