Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schubert: figure/head/list/item table. #4

Open
jcowey opened this issue Oct 15, 2021 · 3 comments
Open

Schubert: figure/head/list/item table. #4

jcowey opened this issue Oct 15, 2021 · 3 comments
Assignees

Comments

@jcowey
Copy link
Owner

jcowey commented Oct 15, 2021

In the Schubert article the following sections has to be rendered in XML:

Bildschirmfoto 2021-10-15 um 11 38 48

Before the rows and cells of the actual table start, there are some explanatory comments made about the cells, which effectively form part of a list.
My first stab at this is to use noteGrp with note for each comment in the list.

See: https://github.com/jcowey/P3/blob/master/pylon/pylon1schubert/schubert_liturgy_geography.xml#L273-L312.

               <table>
                  <head>Table 2: nominations to liturgy, approvals of liturgy, and liturgical oaths (2nd – 3rd c. CE)</head>       
                  <noteGrp>
                     <note>The format (pagina or demotic style) was assessed according to the general shape of the sheet, not by an exact calculation of the width/height ratio.</note>
                     <note>Fragmentary documents were omitted, unless enough was preserved to determine if they were prepared in the pagina or demotic style format.</note>
                     <note>In the columns “pagina format” and “demotic style format”, some documents are labelled as abstracts and copies. Strictly speaking, they are irrelevant for the present purpose, but they were kept in the table in order to provide a more balanced impression of the available data.</note>
                     <note>In the columns “nomination” and “approval”, bold characters indicate documents with a top space left free for the approval (or filled with the approval).</note>
                  </noteGrp>
                  <row>
                     <cell style="text-align: justify;">reference</cell>

Suggestions, improvements?

@jcowey
Copy link
Owner Author

jcowey commented Oct 15, 2021

Each note should probably have a xml:id, if we want to be able to refer to any specific note / sentence

@jcowey jcowey self-assigned this Oct 15, 2021
@jcowey
Copy link
Owner Author

jcowey commented Oct 15, 2021

 <figure>
    <head>Table 2: nominations to liturgy, approvals of liturgy, and liturgical oaths (2nd – 3rd c. CE)</head>             
    <list>
       <item xml:id n="n1">The format (pagina or demotic style) was assessed according to the general shape of the sheet, not by an exact calculation of the width/height ratio.</note>
       <item xml:id n="n2">Fragmentary documents were omitted, unless enough was preserved to determine if they were prepared in the pagina or demotic style format.</note>
       <item xml:id n="n3">In the columns “pagina format” and “demotic style format”, some documents are labelled as abstracts and copies. Strictly speaking, they are irrelevant for the present purpose, but they were kept in the table in order to provide a more balanced impression of the available data.</note>
       <item xml:id n="n4">In the columns “nomination” and “approval”, bold characters indicate documents with a top space left free for the approval (or filled with the approval).</note>
    </list>
    <table>
       <row>
          <cell style="text-align: justify;">reference</cell>
       ...
       </row>
    </table>
 </figure>

@jcowey jcowey changed the title Schubert: noteGrp in table. Schubert: figure/head/list/item table. Oct 15, 2021
@jcowey
Copy link
Owner Author

jcowey commented Feb 10, 2022

This should not be a figure at all. Can we put list with its items between head and table ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant