Add support for "brochure" document type's independently published appendices

[ronaldtse]

Appendix 4 of the SI brochure is published within the SI brochure, and also published separately.

Independent document:
https://www.bipm.org/utils/common/pdf/si-brochure/SI-Brochure-9-App4-EN.pdf

Within SI brochure (page 202 to 210):
https://www.bipm.org/utils/common/pdf/si-brochure/SI-Brochure-9.pdf

The document sources are provided in https://github.com/metanorma/bipm-si-brochure/tree/master/sources as
sib-a4-en.adoc and
sib-a4-fr.adoc.

[ronaldtse]

Mockup of an independent Appendix.

[opoudjis]

This will end up similar to what was done with ITU, with annextitle and annexid:

• The document has the same title as the main document
  • Although because of poor consistency, the separate publication actually treats the title of the main document as "SI Brochure" instead.
• The document has a distinct appendix-title
• The document also has a distinct appendix identifier. In ITU, that is treated as part of the structured identifier, along with the part number.

[opoudjis]

However, I am NOT treating this as a separate document type: I have no reason to think other document types might not also publish their appendixes separately. Instead, separate appendix publications shall be detected by the presence of an appendix ID in the structured identifier, but they shall otherwise have the same document type as their parent.

[ronaldtse]

separate appendix publications shall be detected by the presence of an appendix ID in the structured identifier, but they shall otherwise have the same document type as their parent

Agree. Renamed title.

[opoudjis]

@Intelligent2013 As with the other BIPM issues I've worked on, this is on hold for me, pending input from you.

[Intelligent2013]

@opoudjis
BIPM XSLT will process xml to produce PDF in such manner:

1. If input xml contains structuredidentifier/appendix, then bipm brochure xslt will be produce PDF with appendices only as independent document with design from SI-Brochure-9-App4-EN.pdf. One xml -> one pdf.
2. To pass appendix xml(s) into bipm brochure xslt to produce brochure together with appendices, I'll use the parameter --param appendicesXMLs for mn2pdf, for example:

java -jar mn2pdf.jar --xml-file collection.presentation.xml  --xsl-file bipm.brochure.presentation.xsl  -o out.pdf  --param appendicesXMLs="sib-a4-fr.presentation.xml,sib-a4-en.presentation.xml"

[Intelligent2013]

Here is resulted PDFs for independently published appendices:
sib-a4-fr.presentation.pdf
sib-a4-en.presentation.pdf

@opoudjis in source XML this data are absent:

to produce a cover page. Could you add it please? (I've hardcoded it in xslt temporarely)

[Intelligent2013]

I think no need to add a parameter appendicesXMLs processing into mn2pdf (to pass appendix xml(s) into bipm brochure xslt to produce a brochure together with appendices), because source XML contains appendix yet.

[ronaldtse]

@Intelligent2013 this is the latest design from our designer. Could you help update the PDF styling for appendices? Thanks!

SI Appendix_v2.pdf

[Intelligent2013]

this is the latest design from our designer. Could you help update the PDF styling for appendices? Thanks!

@ronaldtse I've confused a bit, looks like SI Appendix_v2.pdf is MEP document. But Appendix 4 is "brochure" document type.
Should I use one design from 'SI Appendix_v2.pdf' for both independently appendices types "brochure" and "mise-en-pratique"?

[opoudjis]

@Intelligent2013

To pass appendix xml(s) into bipm brochure xslt to produce brochure together with appendices, I'll use the parameter --param appendicesXMLs for mn2pdf, for example:

OK, but I am generating the appendixes XML as part of the brochure already, through AsciiDoc includes. So I do not need to invoke --param appendicesXMLs , do I? If the XML you have been getting is working, then I do not need to change anything.

[Intelligent2013]

OK, but I am generating the appendixes XML as part of the brochure already, through Asciidoctor includes. So I do not need to invoke --param appendicesXMLs , do I? If the XML you have been getting is working, then I do not need to change anything.

@opoudjis Actually I've refused my proposal (#5 (comment)), so you do not need to change anything.

[opoudjis]

In that case nothing further for me to do that I can see, and I am unassigning myself from this ticket.

[opoudjis]

"1". I've manually added 2 into source XML, because design PDF has this number, but xml source doesn't.

Changed source: we're using :appendix-id: not :appendix:

"2". Titles hard-coded in xlst, no such data in source xml.

The documents currently think the title of the parent document is "SI Brochure"/"Brochure sur le SI", because that's what the mockup said. "This should be supplied in the source XML (the source asciidoc)"? You should be telling me to beforehand.

Changed in source.

4. You want bilingual committee names now? Again: You should be telling me to beforehand.

Implementing bilingual committee names. @Intelligent2013 I will be using the variant tag to do so:

<committee acronym="CCTF><variant language="fr">Comité consultatif du temps et des fréquences</variant><variant language="en">Consultative Committee for Time and Frequency</variant></committee>

[opoudjis]

Need to add lang and script to metadata vector, in order to pick variants in Liquid metadata vector matching current language

[opoudjis]

Am compiling and sending updated files to @Intelligent2013

[Intelligent2013]

Latest PDFs for MEP and Appendix 4:
mep-ampere-definition-en.presentation.pdf
mep-candela-si-app2.presentation.pdf
mep-kelvin-definition-en.presentation.pdf
mep-kilogram-definition-en.presentation.pdf
mep-metre-definition-en.presentation.pdf
mep-mole-definition-en.presentation.pdf
mep-second-definition-en.presentation.pdf
sib-a4-en.presentation.pdf
sib-a4-fr.presentation.pdf

Found issue: Math char in header displays big metanorma/mn-native-pdf#269

[ronaldtse]

BIPM feedback provided in #32 and #33

[ronaldtse]

@opoudjis please close this if these document types are already properly implemented in gem. The remaining work are tweaks/bug fixes.

[ronaldtse]

Closing this since the documents are properly generated (pending #32 and #33)