Re: [jats-list] AW: preformatted text in BITS 2.

Subject: Re: [jats-list] AW: preformatted text in BITS 2.
From: "Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 10 Nov 2022 11:05:53 -0000
Or try to convince the BITS working group / JATS standing committee that <break> be allowed in <p>, at least in BITS and in green JATS.

But I'm afraid this train has already left the station long ago. This has been discussed before, and it has been rejected to add <break> to the allowed children of <p>.

One approach without customizing BITS for your purposes is maybe to add a @content-type or @specific-use to the Impressum <p> that will map to something like style="white-space: pre-line" in HTML.

Or you could turn your Impressum <p>s into <title> elements proper. In these you are allowed to use <break>. You can further influence the rendering of the (pseudo-) titles and the ToC generation by using a specific @sec-type on the containing <sec>.

Or try to convince aforementioned committees to add the @style attribute to <p> and to document how it should be used (for literal CSS, as in HTML).

Gerrit

On 10.11.2022 10:08, Buehring, Franziska franziska.buehring@xxxxxxxxxxxxx wrote:
Hi Denis,

Yes, Ibd agree with your approach as BITS isnbt really suited for that kind of content you have to work with workarounds.

<preformat> would be a bad choice, <verse-group> too as they have a different meaning.

To have different <p>s would naturally come with a new line. Another option if you wanted to keep them within one <p> would be the use of <named-content> and @content-type (but I donbt think thatbs better).

Looks like an interesting project by the way.

Best

Franziska

*Von:*denis.maier@xxxxxxxx <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
*Gesendet:* Donnerstag, 10. November 2022 09:19
*An:* jats-list@xxxxxxxxxxxxxxxxxxxxxx
*Betreff:* [jats-list] AW: preformatted text in BITS 2.

Dear colleagues,

May I kindly reiterate this question? Any thoughts about this?

Ibm currently leaning towards using `boxed-text` with an appropriate attribute. Anything that speaks against thisB ?

Best,

Denis

*Von:*Maier, Denis Christian (UB)
*Gesendet:* Freitag, 4. November 2022 17:14
*An:* jats-list@xxxxxxxxxxxxxxxxxxxxxx <mailto:jats-list@xxxxxxxxxxxxxxxxxxxxxx>
*Betreff:* preformatted text in BITS 2.


Dear colleagues

Ibm bit struggling with how a should tag the following type of text:

Webre going to produce a catalog of Incunables at our institution, each incunable will end up in its own `book-part` with the `body` looking like:

```

B B B B B <body>

B B B B B B B <sec>

B B B B B B B <p>Impressum gemC$ss Kolophon

GemC$ss GW und ISTC gedruckt in der Werkstatt des Andreas Asulanus

Foliierungsfehler: Blattzahlen 49-50 und 69-70 ausgelassen, Blattzahlen 120-121 wiederholt, zahlreiche weitere Fehler

Signaturformel: abdB9b0, eb8, fB9b0, gb8, hblB9b0, mB9B2, nbzB9b0, [et]b6

Blatt [et]b ist unbedruckt

</p>

B B B B B B B <p content-type="position-3">Venedig: Bernardino Stagnino oder Andreas Asulanus, 20.10.1492</p>

B B B B B B B <p content-type="position-4">235, das heisst 233 BlC$tter, 1 ungezC$hltes Blatt; 43 cm (2B0)</p>

B B B B B B B <p content-type="position-5"><ext-link xlink:href=http://inkunabeln.digitale-sammlungen.de/Ausgabe_B-186.html <http://inkunabeln.digitale-sammlungen.de/Ausgabe_B-186.html> ext-link-type="url">BSB-Ink B-186 </ext-link>; <ext-link xlink:href=http://www.gesamtkatalogderwiegendrucke.de/docs/GW03624.htm <http://www.gesamtkatalogderwiegendrucke.de/docs/GW03624.htm> ext-link-type="url">GW 03624</ext-link>; <ext-link xlink:href=http://data.cerl.org/istc/ib00236300 <http://data.cerl.org/istc/ib00236300> ext-link-type="url">ISTC ib00236300</ext-link></p>

B B B B B B B <p content-type="position-6">233 von 234 BlC$ttern (plus 2 zusC$tzliche), vorgesehene Stellen fC<r Initialen frei gelassen</p>

B B B B B B B <p content-type="position-7">Halbbezogener Ledereinband auf Kartondeckeln (braun, Kalb, 18./19. Jh.) mit flC$chig eingefC$rbtem Papier (grC<n), Linien-BlindprC$gung sowie Titelschild mit GoldprC$gung auf dem RC<cken</p>

B B B B B B B B B B B B B B B B B B B B B B B B B B B B B B <!-- leere Elemente bitte nicht C<bertragen -->

B B B B B B B <p></p>

B B B B B B B B <p></p>

B B B B B B B <p content-type="position-10">UnvollstC$ndiges Exemplar: Blatt 128 fehlt</p>

B B B B B B B <p content-type="position-11">Signatur: <ext-link xlink:href=https://swisscollections.ch/Record/99116802840105511 <https://swisscollections.ch/Record/99116802840105511>

B ext-link-type="url">MUE Inc I 8</ext-link></p>

B B B B B B B </sec>

B B B B B </body>

B B B </book-part>

```

Normal paragraphs are not to problem. We use `@content-type` to distinguish between different types of paragraphs. However the `p` element that starts with `<p>Impressum gemC$ss Kolophon` is bit tricky as this should preserve line breaks when going HTML later. How would you deal with that kind of requirement?

Ibve seen there is a `preformat` tag, which would sound like a good fit here. However, the specification says this will typically be rendered in a monospace font, which is not the case here.

Another option Ibve considered is using `verse-group` and `verse-line` elements, like soB :

```

<verse-group>

B <verse-line>Impressum gemC$ss Kolophon</verse-line>

B <verse-line>GemC$ss GW und ISTC gedruckt in der Werkstatt des Andreas Asulanus</verse-line>

B <verse-line>Foliierungsfehler: Blattzahlen 49-50 und 69-70 ausgelassen, Blattzahlen 120-121 wiederholt, zahlreiche weitere Fehler</verse-line>

B <verse-line>Signaturformel: abdB9b0, eb8, fB9b0, gb8, hblB9b0, mB9B2, nbzB9b0, [et]b6 </verse-line>

B <verse-line>Blatt [et]b ist unbedruckt</verse-line>

</verse-group>

```

That way you can explicity tag each line, and also you can have proper indentation. I donbt know if itbs just me, but I feel this here looks wrong (content of `preformat` is left-aligned, not indented to where where the tag startes):

```

<preformat>Impressum gemC$ss Kolophon

GemC$ss GW und ISTC gedruckt in der Werkstatt des Andreas Asulanus

Foliierungsfehler: Blattzahlen 49-50 und 69-70 ausgelassen, Blattzahlen 120-121 wiederholt, zahlreiche weitere Fehler

Signaturformel: abdB9b0, eb8, fB9b0, gb8, hblB9b0, mB9B2, nbzB9b0, [et]b6

Blatt [et]b ist unbedruckt

</preformat>

B B B B B B B <p content-type="position-3">Venedig: Bernardino Stagnino oder Andreas Asulanus, 20.10.1492</p>

```

Last option Ibve considered is using `p` elements for the individual lines, and wrapping these in a `boxed-text` container:

```

<boxed-text >

B <p >Impressum gemC$ss Kolophon</p>

B <p>GemC$ss GW und ISTC gedruckt in der Werkstatt des Andreas Asulanus</p>

B <p>Foliierungsfehler: Blattzahlen 49-50 und 69-70 ausgelassen, Blattzahlen 120-121 wiederholt, zahlreiche weitere Fehler</p>

B <p>Signaturformel: abdB9b0, eb8, fB9b0, gb8, hblB9b0, mB9B2, nbzB9b0, [et]b6 </p>

<p>Blatt [et]b ist unbedruckt</p>

</boxed-text >

```

Of course, with all three options a proper attribute (`@content-type`, `@preformat-type`) may help to add meaningful semantics.

Anyway, sorry for the long post. Is there something Ibm missing? Which option would you choose? Is one of these options completely off the rails? Do you see other options?

Best,

Denis

JATS-List info and archive <http://www.mulberrytech.com/JATS/JATS-List/>

EasyUnsubscribe <http://lists.mulberrytech.com/unsub/jats-list/2751862> (by email)

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

-- Gerrit Imsieke GeschC$ftsfC<hrer / Managing Director le-tex publishing services GmbH Weissenfelser Str. 84, 04229 Leipzig, Germany Phone +49 341 355356 110, Fax +49 341 355356 510 gerrit.imsieke@xxxxxxxxx, http://www.le-tex.de

Registergericht / Commercial Register: Amtsgericht Leipzig
Registernummer / Registration Number: HRB 24930

GeschC$ftsfC<hrer / Managing Directors:
Gerrit Imsieke, Svea Jelonek, Thomas Schmidt

Current Thread