Re: [jats-list] Translations for section titles

["Lizzi, Vincent vincent.lizzi@xxxxxxxxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Hi Gerrit and Nikos,

Thank you for your comments! Gerrit, I am reading your discussion with Tommie.

Nikos, in reply to your question, the committee has given thought to this
though found that changes were needed in metadata structures more than in
content structures to support alternative language versions within a single
document. In content items (figures, tables, sections, boxes, etc.) that are
presented with alternative language versions of the text there is sometimes a
choice to either repeat the entire content item in another language or present
the content item only once with some parts of it (e.g. title) repeated in
another language. This choice might be influenced by editorial, technical, or
design concerns to present the content in a coherent way. There are examples
of content the committee members had available in which a figure appears once
with a title/caption in two or more languages and in which an entire figure is
repeated in two or more languages. However, this variation wasnbt seen for
all kinds of content items. Usually the entire content item is repeated in
another language (instead of repeating some parts within a content item), and
this seems to be easier to structure and easier to read. If you have content
that shows some parts being repeated in alternative languages within a content
item for different kinds of content items it would be helpful to see examples.

Best regards,
Vincent

_____________________________________________
Vincent M. Lizzi
Head of Information Standards | Taylor & Francis Group
vincent.lizzi@xxxxxxxxxxxxxxxxxxxx<mailto:vincent.lizzi@xxxxxxxxxxxxxxxxxxxx>




Information Classification: General
From: Nikos Markantonatos nikos@xxxxxxxxxx
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, May 6, 2022 3:48 AM
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [jats-list] Translations for section titles

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<mailto: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<https://www.ncbi.nlm.nih.gov/books/NBK579699/#lizzi-content-it
ems-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">
  <title><named-content content-type="title-content" lang-group="sec1-content"
xml:lang="en">English Title</named-content>
    <named-content content-type="title-content" lang-group="sec1-content"
xml:lang="fr">Titre franC'ais</named-content>
    <named-content content-type="title-content" lang-group="sec1-content"
xml:lang="de">Deutscher Titel</named-content></title>
  <p lang-group="sec1-p1" xml:lang="en">Paragraph</p>
  <p lang-group="sec1-p1" xml:lang="fr">Paragraphe</p>
  <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

--
[https://www.atypon.com/atypon-signature/assets/_i/atypon-logo-sig-new-2x.png
]<https://www.atypon.com>
Nikos Markantonatos | Atypon, Greece Operations Head
Leoforos Ethnikis Antistaseos 39A, 3rd floor, Nea Ionia, 14234, Greece
office +302110133003 | mobile +306974302945 |
nikos@xxxxxxxxxx<mailto:nikos@xxxxxxxxxx>
[https://www.atypon.com/atypon-signature/assets/_i/atypon-wordmark-new-2x.png
]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 archive<http://www.mulberrytech.com/JATS/JATS-List>
EasyUnsubscribe<http://lists.mulberrytech.com/unsub/jats-list/194671> (by
email<>)