Introduction

Gloss is a tool for interlinear annotation of texts. It arose from my frustration with existing tools, and from my desire to have a tool that works just right. I have logged countless hours interlinearizing texts, and Gloss is as efficient a tool as I can create for that purpose.

Features

Screenshot of Gloss

Origins

Gloss owes a tremendous conceptual debt to Language Explorer, but is also geared toward overcoming Language Explorer's weaknesses. In particular:

Cross-platform compatibility & building the source

Since Gloss is build with the Qt framework, it should work on platforms that Qt supports (Windows, Unix/Linux, Mac). I have only provided Windows binaries, since those are the ones I am able to generate easily. I am able to build the source code on my Ubuntu virtual machine, and to the extent that I've tested it, Gloss works in that environment. (I would provide Linux binaries if it were an easier task to distribute Linux binaries...)

Beyond the Qt libraries, Gloss requires the following external libraries:

The first three dependencies are easily installed:

sudo apt-get install libxml2-dev
sudo apt-get install libxslt-dev

Quazip is a bit trickier because you need to build the source. (For me, it was necessary to install the “qt4-dev-tools” package in order to build quazip.)

Downloads

Gloss is created with the Qt application framework, released under the GNU Public License. That means, among other things, that you are free to download it and use it, but not to re-sell it.

Qt is a cross-platform framework, so there is the possibility for using this on Mac OS X, Linux, etc. Right now I only have Windows executables because I only have a Windows machine. Perhaps some do-gooder will build versions for other operating systems and send them to me.

Executable Files

Gloss for Windows

Source code

Download the source as a zip file

Or if you're feeling geeky:

git clone https://github.com/adamb924/Gloss

I build in Windows with this, which assumes that Qt is installed and visible in your path:

qmake -config release
mingw32-make

Of course your system would have something different from “mingw32-make”—probably just “make”—if you are not building from Windows using MinGW.

All contents copyright © 2017 Adam Baker, except where otherwise noted.