There are some really nice templates out there for Latex... I need to look at xLingPaper and then take a look at what I want to do and if I want to create a look-alike template in LaTeX. All things considered XLingPaper still pulls data nicely from FLEx. But I haven't used FLEx in a bit.
I really like CharisSIL and Linux Libertine. ACM two-column format really looks nice, in Libertine, but I haven't checked the linguistic symbols with it recently.
I want to create annotated bibliographies with Chapters and which show: annotations, abstracts, and can be sorted by keywords or custom fields.
Filtering resources so as to edit them or edit in bulk.
I started looking at biblatex options. Jabref is the leading software I have found. It does not have an easy sync for PDF files in a team. Here are some latex templates. It would be good if I could find a flexible template in latex.
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 →