Hi Samuel,
You are probably aware that there is already a way to search tables based
on table metadata such as the locale and the grade.
What we also have planned but isn't there yet, is:
- A way to retrieve info about a table, using the Liblouis API. This will
also be based on metadata inside the tables.
- A way to list all the available tables.
I was never sure about where to store the human readable table descriptions
because these strings typically also need to be localised in various
languages, and while table descriptions fit nicely in the concept of
metadata, the translations do not.
But anyway, now I've decided that I'm going to approach this as two
separate problems. We can add the English description, and maybe also the
description in the native language, to the table as metadata, and if it
turns out people want these descriptions localised in more languages, we'll
put the translations in a separate file(s), and use a special syntax in the
metadata to lookup a localized value.
Something like this (just an example to illustrate the idea):
#+locale: fr
#+grade: 1
#+description_en: French Braille Français Unifié
#+description: %{desc.fr_g1}
Some other system will then map the keyword "desc.fr_g1" to the description
of the table translated in the current locale. You would be able to set the
current locale using the Liblouis API.
I hope to implement this (the functions to retrieve metadata and list
tables, not the localisation feature) in the next version of Liblouis, v3.2.
In the meantime, it would be great if you could help me get the
descriptions into the table headers. The spreadsheet that Greg has started
and that several people contributed to might be useful:
https://docs.google.com/spreadsheets/d/1bSXsCu6WZSzfTriZLtVM5r6IBzK25u4_nWMwxuucgKc/edit#gid=0
.
2017-02-27 10:42 GMT+01:00 Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>:
Larry Skutchan, on lun. 27 févr. 2017 09:34:31 +0000, wrote:
Even as a plain text file with the file name followed by its meaning isa format any language can then process.
There are probably other ideas, but it seems like including that textfile on the project page goes a long way toward solving the problem.
Well, the idea was rather that the file is installed by "make install" :)
Samuel
