[Parley-devel] [parley] [Bug 205261] can't properly specify multiple translations

[ancow]

https://bugs.kde.org/show_bug.cgi?id=205261

--- Comment #5 from ancow <bugs at ancow.no-ip.org> ---
Just one question: why use either as a separator, from a user perspective? Why
not choose a solution with multiple input fields? It does throw up a *real*
problem, though:

You'll frequently run into situations where word A from language X translates
into several words (e.g. B and C) from a different language Y. However, B will
then go on to translate to A and D and C to A and E in X. The point of this is,
that translations aren't reversible, so the assumption that they are is faulty
from the beginning. What is really needed is a model where there are
dictionaries for each language and the translations are represented by
uni-directional connections between the words of each dictionary.

To propose a quick solution for the "both commas and semi-colons are used in
translations" problem: that's what we have escape sequences for. Give the user
a way to enter each alternative translation in a separate text input box, and
if the box contains the separator character (sequence), escape it in the save
file.
To deal with the migration, just give the new file a new version number, and if
an old one is encountered, escape any separator characters/sequences found in
the translations before loading.

-- 
You are receiving this mail because:
You are the assignee for the bug.