An additional point of concern (or maybe an alternate solution to the problem)
is the liberal use of file extensions. If I recall correctly, we now have:
* .uti = uncontracted include table
* .cti = contracted include table
* .utb = uncontracted table^1
* .ctb = contracted table^1
1. 'table' can be for translating forward, backward, or both.
First, I think these extensions could be used more consistently. A *.utb table
shouldn't be included (like you also don't normally include a *.cpp).
Second, we could maybe extend the list of extensions:
* .ftb = forward-translating table
* .btb = backward-translating table
On the other hand, if you also do this for the include tables you create a
forest of extensions that nobody will ever grasp. But I wanted to bring it up
anyway because of the first point (more consistent use). I am a huge proponent
of structured metadata in tables.
-----Oorspronkelijk bericht-----
Van: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] Namens Bert Frees
Verzonden: woensdag 12 augustus 2015 19:20
Aan: liblouis-liblouisxml@xxxxxxxxxxxxx
Onderwerp: [liblouis-liblouisxml] Re: Suggestion to all table authors: note
purpose and proper use inside table
Thanks Bue,
Yes, if we would tag tables suited for backward translation with e.g.
"#+backward", programs could use the "backward" tag as part of the table search
query in order to filter out the tables that don't have the tag.
Similarly the tag "#+forward" can be used for tables that are suited for
forward translation.
Tables that are suited only for inclusion in other tables can be distinguished
from the "top-level tables" based on whether the table header has meta tags or
not.
Also related: https://github.com/liblouis/liblouis/issues/43
/Bert
Bue Vester-Andersen writes:
Hi,For a description of the software, to download it and links to project pages go
In view of the recent discussions on back-translation on the list, I
would like to encourage all table authors to note down the specific
purpose and proper use of their tables.
Some tables only implement forward translation. Some implement both
forward and backward translation, and in some languages you might have
different tables for forward and backward translation. The latter is
actually recommended in the manual if you use multi-pass opcodes.
Also, some tables might only be for inclusion together with other tables.
For instance, this is true with da-dk-nocaps.uti, which use the "correct"
opcode to remove the so-called "unnecesary" caps before translation.
If we could note down in the tables how they are supposed to be used,
developers who use liblouis wouldn't have to break their necks trying
to find out, for instance, if a given table could be used for
back-translation.
I also thought that we could make this info available as part of the
meta data, but would it be of much use in a programatically readable form?
Best regards Bue
