From 392983a71ccdceb9be18e0c3057ffd8116107274 Mon Sep 17 00:00:00 2001 From: Quarto GHA Workflow Runner Date: Mon, 8 Jan 2024 21:05:15 +0000 Subject: [PATCH] Built site for gh-pages --- .nojekyll | 2 +- chapters/appendices/glossary.html | 106 +- chapters/appendices/references.html | 106 +- chapters/appendices/resources.html | 106 +- chapters/appendices/terminal-help.html | 106 +- .../{00-intro.html => 00-aut-intro.html} | 112 +- ...ructions.html => 10-aut-instructions.html} | 118 +- .../11-aut-grammar-usage.html} | 130 ++- .../copyediting/12-cop-preliminaries.html | 156 ++- .../13-cop-preparing-a-manuscript.html | 154 ++- .../copyediting/15-cop-markdown-intro.html | 152 ++- chapters/copyediting/155-cop-checklist.html | 134 ++- chapters/copyediting/16-cop-metadata.html | 748 ++++++------ .../161-cop-title-and-subtitle.html | 778 +++++++++++++ .../162-cop-author-information.html | 848 ++++++++++++++ ...cop-abstract-keywords-acknowledgments.html | 841 ++++++++++++++ .../copyediting/17-cop-inline-elements.html | 202 ++-- .../171-cop-inline-special-chars.html | 140 ++- .../copyediting/19-cop-block-elements.html | 162 +-- .../copyediting/191-cop-block-quotations.html | 152 ++- chapters/copyediting/192-cop-block-lists.html | 176 +-- .../copyediting/193-cop-block-tables.html | 146 ++- .../copyediting/194-cop-block-figures.html | 164 +-- .../copyediting/195-cop-block-statements.html | 186 +-- .../copyediting/196-cop-block-columns.html | 116 +- chapters/copyediting/199-cop-block-other.html | 134 ++- .../20-cop-multiple-languages.html | 116 +- .../21-cop-block-crossreferencing.html | 146 ++- chapters/copyediting/23-cop-citations.html | 158 ++- chapters/copyediting/24-cop-bibliography.html | 444 ++++---- chapters/copyediting/241-cop-math-latex.html | 208 ++-- chapters/copyediting/25-cop-imagify.html | 188 +-- .../copyediting/27-cop-troubleshooting.html | 200 ++-- .../29-cop-markdown-cheatsheet.html | 134 ++- .../52-pub-the-structure-of-volumes.html | 138 ++- chapters/design/55-pub-technical-howtos.html | 138 ++- .../60-dialectica-house-outputs.html | 228 ++-- .../61-dialectica-new-house-outputs.html | 302 ++--- ...65-dialectica-troubleshooting-outputs.html | 178 +-- chapters/dialectica/70-dialectica-titles.html | 856 ++++++++++++++ .../dialectica/71-dialectica-authors.html | 786 +++++++++++++ .../dialectica/72-dialectica-abstract.html | 730 ++++++++++++ ...mplate.html => 74-dialectica-reviews.html} | 214 ++-- .../80-dialectica-bibliography.html | 139 ++- chapters/publishing/42-ojs-advice.html | 108 +- chapters/publishing/51-pub-why-markdown.html | 106 +- index.html | 112 +- search.json | 1006 +++++++++-------- 48 files changed, 9592 insertions(+), 3218 deletions(-) rename chapters/authoring/{00-intro.html => 00-aut-intro.html} (91%) rename chapters/authoring/{10-instructions.html => 10-aut-instructions.html} (91%) rename chapters/{copyediting/165-cop-grammar-usage.html => authoring/11-aut-grammar-usage.html} (89%) create mode 100644 chapters/copyediting/161-cop-title-and-subtitle.html create mode 100644 chapters/copyediting/162-cop-author-information.html create mode 100644 chapters/copyediting/163-cop-abstract-keywords-acknowledgments.html create mode 100644 chapters/dialectica/70-dialectica-titles.html create mode 100644 chapters/dialectica/71-dialectica-authors.html create mode 100644 chapters/dialectica/72-dialectica-abstract.html rename chapters/dialectica/{70-dialectica-template.html => 74-dialectica-reviews.html} (79%) diff --git a/.nojekyll b/.nojekyll index 5472003..3c6d4e3 100644 --- a/.nojekyll +++ b/.nojekyll @@ -1 +1 @@ -6eaa0618 \ No newline at end of file +dd023369 \ No newline at end of file diff --git a/chapters/appendices/glossary.html b/chapters/appendices/glossary.html index 8f2e5fc..55feadc 100644 --- a/chapters/appendices/glossary.html +++ b/chapters/appendices/glossary.html @@ -152,15 +152,21 @@ @@ -176,145 +182,157 @@ + + @@ -331,31 +349,49 @@ + + + @@ -372,13 +408,13 @@ diff --git a/chapters/appendices/references.html b/chapters/appendices/references.html index e72da33..676f64d 100644 --- a/chapters/appendices/references.html +++ b/chapters/appendices/references.html @@ -136,15 +136,21 @@ @@ -160,145 +166,157 @@ + + @@ -315,31 +333,49 @@ + + + @@ -356,13 +392,13 @@ diff --git a/chapters/appendices/resources.html b/chapters/appendices/resources.html index 75e83c8..379b573 100644 --- a/chapters/appendices/resources.html +++ b/chapters/appendices/resources.html @@ -137,15 +137,21 @@ @@ -161,145 +167,157 @@ + + @@ -316,31 +334,49 @@ + + + @@ -357,13 +393,13 @@ diff --git a/chapters/appendices/terminal-help.html b/chapters/appendices/terminal-help.html index 75fad22..e2a6b8d 100644 --- a/chapters/appendices/terminal-help.html +++ b/chapters/appendices/terminal-help.html @@ -152,15 +152,21 @@ @@ -176,145 +182,157 @@ + + @@ -331,31 +349,49 @@ + + + @@ -372,13 +408,13 @@ diff --git a/chapters/authoring/00-intro.html b/chapters/authoring/00-aut-intro.html similarity index 91% rename from chapters/authoring/00-intro.html rename to chapters/authoring/00-aut-intro.html index a246648..e246fdb 100644 --- a/chapters/authoring/00-intro.html +++ b/chapters/authoring/00-aut-intro.html @@ -30,7 +30,7 @@ - + @@ -76,7 +76,7 @@ - + - + + + + + + + + +
+ + +
+ + + +
+ +
+
+

9  Title and subtitle

+
+ + + +
+ + + + +
+ + +
+ +
+

Title and (optionally) subtitle of an article are entered in the metadata title and subtitle field:

+
title: The Solution to the Problem that Plagued Everyone
+subtitle: A Brand New Discovery
+
+

Titles of the form “Time Travel: a Quantum Relativity Puzzle” should be split into title and subtitle. Exceptions are cases where splitting wouldn’t make sense, e.g. “Pleasure: friend or foe?”.

+

If a title or subtitle contains colons or quotation marks, it should be either wrapped within quotation marks or entered as a text block. See Section 8.2.1.

+

The title and subtitle fields should not contain explicit linebreaks. (See Section 8.5 on what explicit linebreaks are.) Not only it’s best to let the reader’s device set the linebreaks in ‘fluid’ outputs (HTML, EPUB), but these fields are also used for the table of contents and to send information to bibliographic database. They should thus be free or unnecessary formatting.

+

Sometimes, however, you need alternative forms of the title:

+
    +
  • a short title to be used in page headers and/or the table of contents.
  • +
  • a title with explicit line breaks, when the title is long and default line breaks don’t look good in PDF output.
  • +
+
+

For these, your journal’s template should provide extra title fields. Dialectica, for instance, uses shorttitle if a shorter version is needed for page headers and the table of contents, title-latex if we need specific linebreaks on the article’s first page in PDF output, and title-cover if we need different linebreaks on the offprint cover than on the article’s first page.

+

Your journal’s template may also have extra fields to handle how titles and subtitles appear in the table of contents. For instance, Dialectica shows both title and subtitle in the table of contents, separated by a colon. As the colon isn’t appropriate when the title ends with a question mark or other punctuation, the template provides a subtitleseparator field that can be used to replace the colon with a space.

+

For details see your journal template’s guidelines.

+ + + +
+ + +
+ + + + \ No newline at end of file diff --git a/chapters/copyediting/162-cop-author-information.html b/chapters/copyediting/162-cop-author-information.html new file mode 100644 index 0000000..3a31578 --- /dev/null +++ b/chapters/copyediting/162-cop-author-information.html @@ -0,0 +1,848 @@ + + + + + + + + + +Open Manual of Markdown Style - 10  Author metadata + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+ +
+ + +
+ + + +
+ +
+
+

10  Author metadata

+
+ + + +
+ + + + +
+ + +
+ +
+

Requires extension: scholarly-metadata.

+

The author field is a list, each item corresponding to one author. Each item has name, email, institute fields, and one author (the corresponding author) has correspondence: true:

+
author: 
+- name: Vincent Conitzer
+  email: conitzer@cs.duke.edu
+  correspondence: true  
+  institute: Duke University
+- name: Nadine Elzein
+  email: nadine.elzein@warwick.ac.uk
+  institute: University of Warwick
+
+

Note that there is a dash (-) before the first line (name field) of each author, and that all the other lines for that author are indented to align with that field (see cop-metadata-lists-maps? for background).

+
+

10.1 Corresponding author

+

There must be one and only one author for which correspondence: true is included. This will print out their email as the correspondence address for that article.

+
+
+

10.2 Institutions

+

Institutions can be entered on one line, separated by commas, or as a list. The two following declaration are equivalent:

+
  institute: Princeton, Yale
+
  institute:
+  - Princeton
+  - Yale
+
+

For this reason, institutes with a comma in their name must be entered as a list, even if there is only one:

+ ++++ + + + + + + + + + + + + +
BADGOOD
  institute: Bedford College, London
  institute:
+  - Bedford College, London
+

The left would be interpreted as two institutes, “Bedford College” and “London”.

+

You can also specify a list of affiliations separately, and associate each author to their institute(s), which is most useful when several authors share the same affiliation:

+
institute:
+- kcl: "King's College London"
+- bedford: Bedford College, London
+author:
+- name: Susan Stebbing
+  institute: [kcl, beford]
+- name: "Jane Q. Doe"
+  institute: bedford
+
+

Here kcl, bedford are used as internal identifiers to associate authors with their affiliations—they won’t be printed. Note that when an author has several, the institution identifiers should be listed in brackets, separated by commas: [kcl, bedford]. When they have only one, the brackets are optional: for Jane Q. Doe above we could have written institute: bedford instead.

+

You can do without identifiers, by listing affiliations in some order and using numbers to refer to them. The metadata below is equivalent to the above:

+
institute:
+- "King's College London"
+- Bedford College, London
+author:
+- name: Susan Stebbing
+  institute: [1, 2]
+- name: Jane Doe
+  institute: [2]
+
+

See the scholarly-metadata filter page for more options and information.

+
+
+

10.3 Multiple short institute names

+

If an author’s institute includes multiple short acronyms, e.g. “ENS, CNRS, EHESS” they may look awkward in the article signature, depending on how your journal template formats it. See your journal template’s guidelines on whether to handle these cases in a special manner.

+
+
+

10.4 Author in page headers and table of contents

+

You sometimes need to provide a shorter alternative for the author names, e.g. “Smith et al.”, for page headers and the table of contents.

+

Your journal template should provide extra fields for this. Dialectica uses author-toc and author-header, for instance. See your journal template’s guidelines.

+ + +
+ +
+ + +
+ + + + \ No newline at end of file diff --git a/chapters/copyediting/163-cop-abstract-keywords-acknowledgments.html b/chapters/copyediting/163-cop-abstract-keywords-acknowledgments.html new file mode 100644 index 0000000..ea10dd3 --- /dev/null +++ b/chapters/copyediting/163-cop-abstract-keywords-acknowledgments.html @@ -0,0 +1,841 @@ + + + + + + + + + +Open Manual of Markdown Style - 11  Abstract, keywords, acknowledgments + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+ +
+ + +
+ + + +
+ +
+
+

11  Abstract, keywords, acknowledgments

+
+ + + +
+ + + + +
+ + +
+ +
+

Abstract, keywords and acknowledgments should be entered in either of two ways:

+
    +
  • special sections at the beginning of the paper,
  • +
  • metadata fields.
  • +
+
+

This ensures they are handled by the journal template. Do not try to format them yourself (e.g. to place the acknowledgements in a footnote).

+

Whichever way you choose is up to you, they are equivalent. The first requires the sec-to-meta extension.

+
+

11.1 As special sections

+

Requires extension: Sections-to-Meta.

+

You can enter abstract, acknowledgments and keywords as special sections with level 1 (#) headings Abstract (or Summary), Acknowledgements (or Thanks or Acknowledgments) and Keywords. The keywords section must be a bullet-point list. If the article’s body text does not itself start with a heading, separate these special sections from the body text with a horizontal rule (* * * or ---). For example:

+
---
+title: "If You Squint You'll See an Effect"
+author: Patricia I. Smith
+---
+
+# Abstract
+
+In this paper, I explain that the *problem* is more difficult to
+solve than the equation $4x^2 = 8$ and more complicated than the
+formula $(P \land \lnot P) \rightarrow Q$. Thankfully, I have
+found the solution.
+
+# Thanks
+
+The author would like to thank Jane Doe and Erika Mustermann
+as well as audiences at the Universities of Shallow Objections.
+
+# Keywords
+-   problem
+-   solution
+-   symbols
+
+* * *
+
+Since the dawn of humanity, people have been wondering about
+my PhD research topic...
+
+
+

11.2 As metadata

+

Alternatively, you can enter abstract, acknowledgments, and keywords as metadata fields abstract, thanks and keywords, respectively. The keywords fields must be a list. As the other two are typically multiple lines long, they are better entered as text blocks (see ssec-metadata-text-block-values?). Make sure you indent each line of text blocks properly, without getting confused by genuine vs merely apparent linebreaks see 8.5. To illustrate, the example could be entered instead as:

+
---
+title: "If You Squint You'll See an Effect"
+author: Patricia I. Smith
+abstract: |
+  In this paper I explain that the *problem* is more difficult to
+  solve that the equation $4x^2 = 8$ and more complicated than the
+  formula $(P \land \lnot P) \rightarrow Q$. Thankfully, I have
+  found the solution.
+thanks: |
+  The author would like to thank Jane Doe and Erika Mustermann
+  as well as audiences at the Universities of Shallow Objections.
+keywords:
+-   problem
+-   solution
+-   symbols
+---
+
+Since the dawn of humanity, people have been wondering about
+my PhD research topic...
+
+

Dialectica guidelines.

+

Abstracts are strongly recommended. Most people who bump on the article will only read that. They must be at most 200 words or so, to fit in the first article page.

+
+
+
+

11.3 Citations and formulas in abstract and acknowledgements

+

(TO BE CONFIRMED). Abstract and acknowledgments cannot contain markdown citations like @Smith. Write them in plain text instead, Smith (1980).

+

(TO BE CONFIRMED). Formulas in the abstract should be kept simple, or better, entered directly in unicode. This is because they are exported to public databases that may not handle LaTeX.

+ + +
+ +
+ + +
+ + + + \ No newline at end of file diff --git a/chapters/copyediting/17-cop-inline-elements.html b/chapters/copyediting/17-cop-inline-elements.html index 63d3f27..9fd9f95 100644 --- a/chapters/copyediting/17-cop-inline-elements.html +++ b/chapters/copyediting/17-cop-inline-elements.html @@ -7,7 +7,7 @@ -Open Manual of Markdown Style - 9  Inline elements +Open Manual of Markdown Style - 12  Inline elements + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+ +
+ + +
+ + + +
+ +
+
+

33  Title and subtitle

+
+ + + +
+ + + + +
+ + +
+ +
+

The metadata fields title and, if the article has a subtitle, subtitle must be present. They may contain markdown formatting and special symbols, but no explicit linebreaks.1

+

In addition, you may provide:

+
    +
  • shorttitle: shorter title to use in page headers and the table of contents.
  • +
  • title-latex, subtitle-latex: title to be used in PDF’s output on the article’s first page and (unless (sub)title-cover is specified) on the article’s offprint cover. Used to specify explicit line breaks.
  • +
  • title-cover, subtitle-cover: title to be used in PDF’s output on the offprint cover. Used to specify explicit linebreaks.
  • +
+
+

Here is an example using all the available fields. They are explained in detail in the sections below.

+
title: Plain title here
+subtitle: Plain subtitle here
+subtitle-separator: ':'
+shorttitle: Shorter title for page headers
+title-latex: |
+  Title for the first page title \
+  (and cover unless otherwise specified) \
+  with possibly some linebreaks
+subtitle-latex: |
+  Subtitle for the first page title \
+  (and cover unless otherwise specified) \
+  with possibly some linebreaks
+title-cover: |
+  Title for the offprint cover \
+  with possibly some \
+  different linebreaks
+subtitle-cover: |
+  Subtitle for the cover
+title-cover-size: \huge
+subtitle-cover-size: \Large
+
+

33.1 Short title

+

If the title is too long to fit in the header, you can specify a short title in addition:

+
title: An extremely long-winded and verbose title about a range of topics including but not restricted to the weather
+shorttitle: A long-winded title about the weather
+
+

This will be used in the table of contents too.

+
+

33.1.1 Linebreaks in a title and subtitle

+

Requires: dialectica templates.

+

In LaTeX/PDF output it is sometimes useful to manually specify a line break within the title and/or subtitle. There are two fields to provide this, title-latex and title-cover:

+
title: A Very Long Title that Can be Broken in Various Places
+title-latex: |
+  A Very Long Title that \
+  Can be Broken in Various Places
+title-cover: |
+  A Very Long Title that Can be\
+  Broken in Various Places
+
+

In a metadata field, the \ at then end of a line specifies a linebreak. Warning: it must be immediately followed by an end of line (no spaces!).

+
    +
  • title-latex controls the title on the first page (“chapter” title). It also sets the offprint cover page unless title-cover is also supplied.
  • +
  • title-cover controls the title on the offprint’s cover page. If you want title-latex to modify the first page’s title only, simply insert title-cover with the same content as title.
  • +
+
+

The title field must be provided, even if title-cover and/or title-latex are given.

+

By default titles on the offprint’s cover are of LaTeX size \Huge if they are less than 31 characters long, otherwise the slightly smaller size \huge. You can specify a custom LaTeX size if needed (\Huge, \huge, \LARGE, \Large, \large etc.) with the title-cover-size field. This only affects LaTeX/PDF output.

+
title-cover-size: \huge
+
+

The same options are available for subtitles: use subtitle-latex, subtitle-cover and subtitle-cover-size. The default size for subtitles on offprint covers is \LARGE.

+
+
+
+

33.2 Subtitle in the table of contents

+

The subtitle is used in three places. On the paper’s first page and on the offprint’s cover, it is printed below the title, in smaller font. It’s also used in the table of contents, where it’s printed after a column:

+
title: Frankstein
+subtitle: The Modern Prometheus
+
+

Output in the table of contents:

+
+
+

Frankenstein: The Modern Promoetheus

+
+
+

You can override the colon by specifying a subtitle separator, e.g. a simple space:

+
title: So What?
+subtitle: My Quest for the Meaning of Life
+subtitleseparator: ' '
+ + +
+
+
+
    +
  1. You may enter a long title or a title containing quotation marks as a text block, this does not constitute explicit line breaks. See Section 8.3 and Section 8.5.↩︎

  2. +
+
+ +
+ + +
+ + + + \ No newline at end of file diff --git a/chapters/dialectica/71-dialectica-authors.html b/chapters/dialectica/71-dialectica-authors.html new file mode 100644 index 0000000..8ef1292 --- /dev/null +++ b/chapters/dialectica/71-dialectica-authors.html @@ -0,0 +1,786 @@ + + + + + + + + + +Open Manual of Markdown Style - 34  Author information + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+ +
+ + +
+ + + +
+ +
+
+

34  Author information

+
+ + + +
+ + + + +
+ + +
+ +
+

34.1 Et al. author for page headers and table of contents

+

For articles with multiple authors, you may need a shorter alternative for page headers and the table of contents. This is done using the author-header and author-toc fields:

+
author:
+- name: Doe, Alice
+- name: Doe, Brit
+- name: Doe, Celia
+- name: Doe, Denis
+- name: Doe, Ethne
+author-header: Doe et al.
+author-toc: Doe A., Doe B., Doe C., Doe D., and Doe E.
+
+
+

34.2 Multiple short institute names in the signature block

+

Problem. An author’s affiliations consists of several short acronyms, e.g. “CRNS, ENS, EHESS”. If you enter them as three distinct institutes, they each appear on a single line in the signature block at the end of the article. This looks awkward. Treat them as a single institute instead, using a list item (e.g. on a line starting with a -):

+
  institute:
+  - ENS, CRNS, EHESS
+ + +
+ +
+ + +
+ + + + \ No newline at end of file diff --git a/chapters/dialectica/72-dialectica-abstract.html b/chapters/dialectica/72-dialectica-abstract.html new file mode 100644 index 0000000..44b5bdc --- /dev/null +++ b/chapters/dialectica/72-dialectica-abstract.html @@ -0,0 +1,730 @@ + + + + + + + + + +Open Manual of Markdown Style - 35  Abstracts + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+ +
+ + +
+ + + +
+ +
+
+

35  Abstracts

+
+ + + +
+ + + + +
+ + +
+ +
+

Abstracts are strongly recommended. Most people who bump on the article will only read that.

+

Abstracts must be at most 200 words or so and fit in the first article’s page in PDF output.

+ + + +
+ + +
+ + + + \ No newline at end of file diff --git a/chapters/dialectica/70-dialectica-template.html b/chapters/dialectica/74-dialectica-reviews.html similarity index 79% rename from chapters/dialectica/70-dialectica-template.html rename to chapters/dialectica/74-dialectica-reviews.html index 00cd47e..8935837 100644 --- a/chapters/dialectica/70-dialectica-template.html +++ b/chapters/dialectica/74-dialectica-reviews.html @@ -7,7 +7,7 @@ -Open Manual of Markdown Style - 30  Dialectica template +Open Manual of Markdown Style - 36  Review articles