We can trivially make a Report Bad Translation button on the website that pops up a 3-field dialog, where the input (static), output (static), and user's correction (that they fill in) can be submitted to a database.
-- Tino Didriksen On Sat, 5 Dec 2020 at 10:28, Hèctor Alòs i Font <hectora...@gmail.com> wrote: > A Sardinian collaborator commented to me: "Wouldn't it be possible that > every time there are more possible translations these come out in a little > window where the user chooses the right solution, as in spell checkers"? > > This could be an idea for a GSoC tool project. Nevertheless, I don't think > that, as he puts it, this is the best option because, in general, we have > few multiple options in the bilingual dictionaries. Probably, another type > of interface would be more appropriate. Is there anything done in the GSoC > projects that could be used? > > With him, we use a simple spreadsheet in a Google Documents-like system. > He enters a word or phrase, the current translation, the suitable > translation and the context (sentence). This is not at all intuitive, nor > easy, for a conventional user, but it is very useful. We have already dealt > with several hundred errors in the Italian-Sardinian translator. > > Hèctor >
_______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
