Skip to content

Commit

Permalink
Update faq.html
Browse files Browse the repository at this point in the history
  • Loading branch information
lawrennd committed Jan 23, 2024
1 parent d2a842b commit d970c5a
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions faq.html
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ <h2>There's a Mistake in a Paper: Can it be Fixed?</h2>
<p>If the mistake is a clear typo (e.g. abstract or authors not matching to the PDF) you can submit a pull request to fix it. You'll need a GitHub account for this. Log into your GitHub account and click the "edit" button on the abstract page and if you are logged into GitHub you will be able to edit the meta information directly.
</p>

<p>Pages are generated by jekyll in github, which is a static webpage generation framework. Information for each paper is included in the `_posts/` subdirectory, clicking edit from the abstract page will allow you to edit the relevant file. Each file is a markdown with a yaml header. All the meta information is in the yaml header. The format is based on [Martin Fenner's citeproc](https://blog.front-matter.io/posts/citeproc-yaml-for-bibliographies/). Note title information and author information is stored twice. Once in a format appropriate for html (e.g. with unicode characters) and once in a format appropriate for LaTeX (e.g. with LaTeX accents and curly brackets to preserve case). find information on the format </p>
<p>Pages are generated by jekyll in github, which is a static webpage generation framework. Information for each paper is included in the `_posts/` subdirectory, clicking edit from the abstract page will allow you to edit the relevant file. Each file is a markdown with a yaml header. All the meta information is in the yaml header. The format is based on <a href="http://blog.martinfenner.org/2013/07/30/citeproc-yaml-for-bibliographies/">Martin Fenner's citeproc</a>. Note title information and author information is stored twice. Once in a format appropriate for html (e.g. with unicode characters) and once in a format appropriate for LaTeX (e.g. with LaTeX accents and curly brackets to preserve case). find information on the format </p>

<p>Do not edit the bib file, this has no effect on the generated pages or the generated bibfiles.</p>

Expand All @@ -32,7 +32,9 @@ <h2>How do I publish my proceedings with you?</h2>
provide brief CVs of the organizers and an overview of the subject
matter. Potential proceedings are judged on the basis of the
appropriateness of the material, the perceived quality of the workshop
and the track record of the organizers.</p>
and the track record of the organizers. We expect papers to be peer reviewed, but we are open to innovative mechanisms on how this is done. Please provide a description of your approach.</p>



<h2>I would like to register a Reissue Proceedings with you?</h2>

Expand All @@ -41,7 +43,7 @@ <h2>I would like to register a Reissue Proceedings with you?</h2>
<h2>What Volume Number will my Proceedings be?</h2>

<p>When you are close to finalizing the proceedings, email the series
editor. He will give you a volume number by allocating from those
editor. You'll receive you a volume number by allocating from those
currently available.

<h2>What if I want a Paper Copy?</h2>
Expand Down

0 comments on commit d970c5a

Please sign in to comment.