Latex Legal citation

I'm looking for ways to use XeLaTeX and create legal citations in law reviews. In the USA this means following the Bluebook, but this has not been implemented in LateX.

The most productive discussion is here:

https://tex.stackexchange.com/questions/437824/what-is-best-practice-re-handling-legal-sources-with-biblatex-biber-for-discipl

biblatex chicago is mentioned and I wonder if I can use it in my other work to.

https://ctan.org/pkg/biblatex-chicago?lang=en

I wonder if I could mix these with the typography here:
https://www.overleaf.com/project/6114161a9903f93e3d55180c

In any case It looks like I need to think about biblatex.

Though this law citation package looks really interesting and I ought to explore it more:
https://github.com/texcicada/lawcite

See also:
https://tex.stackexchange.com/questions/71306/bluebook-support-in-latex

The problem with the following linked generic version is that their citations are all hand crafted.
https://www.overleaf.com/latex/templates/generic-law-review-article-template/kbmpvfbmrkgp

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