[jats-list] Title language in multilingual documents

Subject: [jats-list] Title language in multilingual documents
From: "Chiara Del Vescovo chiara.delvescovo@xxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 17 Sep 2025 11:32:09 -0000
Hi Chandi and Vincent,

Thank you for your responses so far! I just want to point out that I am not
looking at translations here, so the element <trans-title> and the attribute
@lang-group are out of scope. I am looking for the standardised way to express
the language of the title in a multilingual document. And more in general, to
understand how to make sure that a screen reader can pronounce a text
correctly.

Vincent, thank you for the insight on browsers and systems mostly being unable
to process the "mul" value in @xml:lang, this is very interesting, and
something that was already on my "to investigate" list. I quite like the
solution that makes use of a specific language code as the "fall-back"
language of a document regardless of whether it's a mono- or a multi-lingual
document. Indeed, there is already the possibility to use multiple
<content-language> tags to express that a document is multi-lingual, and your
interpretation helps decoupling the two fields.
I cannot really see how the value "mul" can be used at all, since:

  *
The presence of multiple <content-language> elements already means that a
document is multi-lingual, and
  *
"mul" doesn't provide any information about the language of any text, so it's
not used to process text either.

I think I'll recommend OUP not to use the "mul" value at all. Unless someone
here has a convincing use-case for it, in which case I'm all ears!

Just for completeness, BITS recommends using the IANA language code list
available at
https://www.iana.org/assignments/language-subtag-registry/language-subtag-reg
istry. Do you have any recommended practice to share regarding this list?

I also have a question on how to express the language of an extended part of
text in a multilingual document (my understanding is that this is provided by
using the element <sec>), but I think this is not in scope with this thread.

Thank you again!
Chiara

Chiara Del Vescovo

Senior Content Data Model Architect | Operations

Oxford University Press

Oxford University Press (UK) Disclaimer
This message is confidential. You should not copy it or disclose its contents
to anyone. You may use and apply the information for the intended purpose
only. OUP does not accept legal responsibility for the contents of this
message. Any views or opinions presented are those of the author only and not
of OUP. If this email has come to you in error, please delete it, along with
any attachments. Please note that OUP may intercept incoming and outgoing
email communications.

Current Thread