BibTex Materials in XML Markup

It seems that BibTeX materials can be written as XML.

Here are some resources I found on this:

  • a python2 script: https://www.eecis.udel.edu/~sprenkle/bibtex2html/bibtex2xml.py
  • an overview presentation: https://pdfs.semanticscholar.org/8c8e/44b18bacac15f14113af3d4b55f028e0a842.pdf
  • Software Package: http://www.sfs.uni-tuebingen.de/hpsg/archive/projects/bibtex2html/
  • Prior research: https://web.science.mq.edu.au/~rdale/resources/bibtex/index.html
  • maybe some XSLT files: https://sourceforge.net/projects/bibtexml/

XML formats for publishing

  1. TEI based XML format at DHQ. Documentation.
  2. JATS based XML at de Gruyter and tons of other publishers.
  3. DocBook and Balisage-1.3 at Balisage. Example
  4. XLingPaper XML

https://relaxng.org/tutorial-20011203.html
https://www.w3.org/2000/04/schema_hack/

https://www.balisage.net/Proceedings/vol21/print/Tovey01/BalisageVol21-Tovey01.html

https://typeset.io/resources/typeset-evolving-into-scispace/
https://typeset.io/resources/jats-xml-everything-a-publisher-needs-to-know/

JATS in multilingual books:
https://www.ncbi.nlm.nih.gov/books/NBK579699/

JATS
https://www.escienceediting.org/upload/kcse-284.pdf
https://jats.nlm.nih.gov/jats-con/2013/presentations/graham2013.pdf
https://github.com/ncbi/JATSPreviewStylesheets/blob/master/xslt/main/jats-xslfo.xsl
https://assets.pubpub.org/z1qlpyk6/01566244075411.pdf

https://av.tib.eu/media/51339
https://github.com/pkp/texture
https://jats.niso.org/jatswiki/index.php/Tools
https://www.ncbi.nlm.nih.gov/books/NBK425544/

Interesting examples:
https://typeset.io/papers/defining-a-linguistic-area-south-asia-gilv2538jj
Pricing:
https://typeset.io/account/pricing/?source=plans-billing-page

Mixing LaTeX and Markdown

Several ways to do this.

Latex in Markdown files, markdown in Latex files, and conversion between the two...

https://mathpix.com/markdown-to-latex
https://www.overleaf.com/learn/how-to/Writing_Markdown_in_LaTeX_Documents

Interesting to me was the ability to do syntax highlighting from markdown... it seems easier than listings and might work better than XML for use with XLingPaper

Software Needs for a Language Documentation Project

In this post I take a look at some of the software needs of a language documentation team. One of my ongoing concerns of linguistic software development teams (like SIL International's Palaso or LSDev, or MPI's archive software group, or a host of other niche software products adapted from main stream open-source projects) is the approach they take in communicating how to use the various elements of their software together to create useful workflows for linguists participating in field research on minority languages. Many of these software development teams do not take the approach that potential software users coming to their website want to be oriented to how these software solutions work together to solve specific problems in the language documentation problem space. Now, it is true that every language documentation program is different and will have different goals and outputs, but many of these goals are the same across projects. New users to software want to know top level organizational assumptions made by software developers. That is, they want to evaluate how software will work in a given scenario (problem space) and to understand and make informed decisions based on the eco-system that the software will lead them into. This is not too unlike users asking which is better Android or iPhone, and then deciding what works not just with a given device but where they will buy their music, their digital books, and how they will get those digital assets to a new device, when the phone they are about to buy no-longer serves them. These digital consequences are not in the mind of every consumer... but they are nonetheless real consequences.
Continue reading