Hi Simon,
We have an idea of how to do the API but haven't coded anything yet.
What I'll do is I'll create a Github issue where I explain the current
plans, and then you can add your own requirements if needed. If you want
you may even write the code, that would be most welcome.
Bert
2017-03-05 10:07 GMT+01:00 Simon Aittamaa <simon.aittamaa@xxxxxxxxx>:
Hello,
Just thought I'd chime in on this issue (been on vaction so a bit late
reply, sorry for the revive).
At Index Braille we really need a way to list all tables, as we wish
to present the available tables to the user. Currently we have our own
mapping for that (created before the metadata approach was available).
The idea is to update our code to use liblouis instead, but for that
we of course need an API to query all available tables. We probably
need to extend the metadata with some tags/keywords, but I'll know
more once we've started the transition. We might also need a
translation of the name, description, etc. (or for standardized
values, we can simply create a separate translation outside of
liblouis), but it might be worth to place _some_ translations in the
metadata (e.g., non-standard values such as the description).
I'll gladly write the code for the API, the problem is that I'm not
sure when I'll have the time for it. I do belive that we'll be doing
it shortly though, as we're getting more request to translate the name
of the tables (and I'd rather do it the right way than create another
hack).
I know we've made some noise about this earlier, but sadly these kind
of refactoring tend to get pushed back by more critical issues. I'll
try to make something happen before I go on parental leave (1th of
Aptil). If someone is already working on this API, then I'll gladly
review it! (and/or contribute to it!).
Best,
Simon
On 27 February 2017 at 23:22, Bert Frees <bertfrees@xxxxxxxxx> wrote:
2017-02-27 22:33 GMT+01:00 Samuel Thibault <samuel.thibault@xxxxxxxxxxxxI
:
Bert Frees, on lun. 27 févr. 2017 20:56:20 +0100, wrote:
and if it turns out people want these descriptions localised in more
languages,
I'm not sure in which case that would be useful: if somebody needs to
translate a langage, she probably knows it, or at least its name ? :)
I see what you mean, but still, I can imagine some people would want to
translate into a language they don't know. Not the most common use case,
admit. We'll see what happens. Also, if you want to present a list oftables
I think it looks a bit weird if they are not all in the same language.For
example Wikipedia does it with the list of translations of a page.For a description of the software, to download it and links to
project pages go to http://liblouis.org
