Simplest install on MS Windows (script) or Linux (script)
If you want consultant help, see also this page
You can now create a Demo database to try out A-Z+T.
A-Z+T is designed to accelerate community-based language development, supplemented by (not as a replacement for) formal linguistic training. It does this by systematically checking a dictionary (and thus a writing system), with respect to consonants, vowels, and tone.
You can collect a wordlist from scratch in A-Z+T, if you don't already have one created elsewhere. But parsing roots is still in development, so for now you should do that elsewhere (e.g., FLEx or WeSay) if your citation forms have obligatory affixation.
A-Z+T work results in a lexical database which is checked, backed up with sound files, and stored as LIFT, an open XML format designed for sharing lexical data. So this database should be forward compatible with other tools that can read LIFT, e.g., WeSay and FLEx.
If you currently use FLEx, and want to understand what A-Z+T is and decide if you should use it, please see this page.
See RATIONALE for more information on why one should use this tool; see Why Work with Computers to see A-Z+T compared with pen and paper participatory methods. See Why Work with Communities to see A-Z+T compared with more traditional field methods
A-Z+T is written in Python (3+) and Tkinter, with PyAudio for recording and playing sound files. A-Z+T produces reports to the screen, plain text files, and XLingPaper XML documents —which can in turn be easily converted to PDF and HTML, each with clickable links to sound files.
To get the program, run git clone https://github.com/kent-rasmussen/azt.git in a terminal, or download through the green code button on the main page.
To run: python main.py (or python3 main.py, as appropriate for the (3+) version of python on your system)
See INSTALL for more help installing; see USAGE for how to use this tool.
See CHANGELOG to see features by version, and ROADMAP to see what I'm working on next.
You can keep A-Z+T up to date with the user interface, as well as try out a testing version.
See BUGS for information to send me if you have problems; see KNOWNISSUES with recommended work-arounds to a couple known issues.