Re: [jats-list] Converting OASIS tables to JATS

["Gareth Oakes goakes@xxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

See if you can find an existing CALS-to-XHTML table transform. This transform
gets really gnarly once you start accounting for all possibilities (spanning
cells, rotated content, align/valign, multiple tgroups, custom attributes,
table frames mixed with table header/footer, and so on).

In general, you can handle the borders as you propose or map to some other
attribute and apply styling via a separate CSS (rather than hard-coding it
into the style attribute).

// Gareth Oakes
// Chief Project Officer, GPSL
// www.gpsl.co

From: "Michael Boudreau mboudreau@xxxxxxxxxxxx"
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Reply to: "jats-list@xxxxxxxxxxxxxxxxxxxxxx"
<jats-list@xxxxxxxxxxxxxxxxxxxxxx>
Date: Sunday, 16 October 2022 at 00:46
To: "jats-list@xxxxxxxxxxxxxxxxxxxxxx" <jats-list@xxxxxxxxxxxxxxxxxxxxxx>
Subject: [jats-list] Converting OASIS tables to JATS

Webre moving forward with a plan to convert OASIS table markup to the JATS
model in-house before sending it to our platform vendor. For the most part
itbs pretty straightforward, but one issue Ibm puzzling over is the colsep
and rowsep attributes of OASIS <entry> elements, which donbt have a direct
analogue in the JATS <th> and <td> elements.

For the moment, Ibm accounting for this by adding a style attribute
depending on whether colsep or rowsep or both are specified as b1b:

colsep="1" => style="border-right: solid thin black"
rowsep="1" => style="border-bottom: solid thin black"
colsep="1" and rowsep="1" => style="border-right: solid thin black;
border-bottom: solid thin black"

Is there a better way?

--
Michael R. Boudreau
Electronic Publishing Technology Manager
The University of Chicago Press
1427 E. 60th Street
Chicago, IL 60637
www.journals.uchicago.edu<http://www.journals.uchicago.edu>

JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/>
EasyUnsubscribe<http://lists.mulberrytech.com/unsub/jats-list/2708257> (by
email<>)