Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
N
numapde-bibliography
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • numapde-public
  • numapde-bibliography
  • Issues
  • #30

Closed
Open
Opened May 09, 2020 by Roland Herzog@griesse--tu-chemnitz.deOwner

Create a conversion file from BibLaTeX to BibTeX

This conversion is necessary since most journals still use BibTeX rather than BibLaTeX. However, numapde.bib uses the more modern BibLaTeX standard which is not downward compatible with BibTeX in all aspects.

I propose numapde-prepare-bibtex-file.sh as the tentative name for the conversion script.

In order to come from numapde.bib (and possibly other .bib files such a numapde-local.bib) to a BibTeX file, I propose to let numapade-prepare-manuscript.py trigger numapde-prepare-bib-file.sh. In this way, we could hard code all command line switches for numapde-prepare-bibtex-file.sh which are necessary to come up with manuscript-coap.bib (for example) compatible for the .bst of the respective journal. In this way, the user does not need to know whether or not the .bst file a particular journal uses can cope with, e.g., @ONLINE entries or not.

Among the replacements that numapde-prepare-bibtex-file.sh will typically need to make are:

  • conversion of @THESIS
  • conversion of @ONLINE
  • protection of uppercase characters, e.g., in the TITLE field
  • conversion of DATE to YEAR
  • possibly UTF8 transcription

There is one further issue. Since the preprint and journal version of a manuscript utilize the same .yaml file with meta data, they also normally use the same .bib file(s). I propose to override this behavior in the following manner. If an especially prepared .bib file exists, it will get preference and be the only .bib file used. The respective mechanism can be implemented into numapade-prepare-manuscript.py. If it does not exist, the file(s) specified in the .yaml file will be used. Our preprint class can be exempt from this rule.

Finally, the IntegrationTests should include a more thorough testing of all kinds of bibliography entries to ensure all types of entries to be treated correctly.

Edited May 09, 2020 by Roland Herzog
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: numapde-public/numapde-bibliography#30