Differentiating capability

Bilingual and multilingual journals in JATS XML

We produce and remediate ES/EN (and other language pairs) with the right structure for the destination: bilingual abstracts, full translations, sub-article, shared DOI, and per-language HTML when required.

Request a quote

The editorial problem

A bilingual policy is not one extra xml:lang attribute. It drives cost, indexing, DOI strategy, shared vs duplicated figures, and whether SciELO, PMC, or a repository expect one XML or language-specific packages. Schema-valid XML can still be rejected or double-counted without a clear model.

Our solution

We agree the linguistic scenario and destination (SciELO SPS, PMC, generic JATS) with the journal, then produce or remediate XML so metadata, body, tables, figures, and references follow that model — as a named capability, not a hidden JATS feature.

How we approach it

01
Language policy
We confirm whether the second language is abstracts/keywords only, a full translation, or a mixed issue — and whether HTML is published per language.
02
JATS model
We choose bilingual abstracts, translated article titles, or a translation sub-article based on destination and journal policy.
03
Assets and references
We define whether figures/tables are shared, duplicated with translated captions, or versioned — and how references are treated.
04
Destination validation
We validate against the agreed profile (JATS / SciELO / PMC) and deliver a package ready for the journal workflow.

Common scenarios

Bilingual abstract and keywords

Single article; front matter with abstract/kwd-group in ES and EN. Best when the body is monolingual and the destination indexes bilingual metadata.

Full translation with sub-article

Primary article plus translation sub-article (shared DOI or an agreed DOI policy). Figures and tables shared or captioned per language as the destination requires.

Two HTML versions, one canonical XML

When the platform publishes HTML per language from structured XML: naming, xml:lang, and assets aligned with the journal handoff.

Destination × language treatment

The same bilingual policy is marked differently by destination. This matrix is indicative; the project proposal locks the exact model.

Scenario	SciELO (SPS)	PMC	JATS / repository
Bilingual abstract/keywords only	Abstracts with xml:lang; stable journal metadata	Bilingual abstracts; body in primary language	Flexible; prioritize xml:lang consistency
Full translation	Model agreed with the collection (often sub-article)	sub-article or related articles per publisher policy	sub-article or two articles + relationship
Shared DOI	One DOI for the canonical article; translations linked	Publisher Crossref/PMC policy	Document in article-id and relationships
HTML per language	Per collection / site pipeline	Derived from accepted XML	Asset handoff and naming per language

Typical deliverables

JATS XML with the agreed language model
Normalized bilingual metadata (titles, abstracts, keywords)
Destination × language decision note
Asset package (figures/tables) consistent with the model
Validation report for the contracted profile

Before and after the project

FAQ

Do you charge per language or per article?

Pricing reflects the scenario (bilingual metadata only vs full translation) and table/figure complexity. We lock it after reviewing a sample.

Do you handle Portuguese or languages beyond ES/EN?

Yes, when the destination and journal policy allow it. The JATS model is defined per language pair and validation profile.

Can you remediate XML already produced by a third party?

Yes. Our XML correction and rescue service covers bilingual remediation when SciELO or PMC reject the current markup.

Tell us your language policy

Share the destination (SciELO, PMC, or other), whether you have full translations, and a sample article. We will propose the model and a quote.