Il 01/06/2017 21:45, Mihkel Tõnnov ha scritto:
2017-06-01 18:14 GMT+03:00 Sophie :
Hi all,
I invite all of you to have a read to that message from Caolan, it's a
discussion, so please share your concerns, your solutions, your views :)
Hi,
one thing which I miss in the current system is the possibility to
translate plurals correctly. gettext supports that - maybe that it would
be necessary to change something in code, but I think its is worth that.
Pls, think about this
best
Milos
On 2017-06-05 13:44, Sophie wrote:
> Hi all,
>
Hi all,
Le 04/06/2017 à 22:38, Cor Nouws a écrit :
> m.balaba...@gmail.com wrote on 04-06-17 21:23:
>> Yes, Bulgarian is also one of those inflected languages that require
>> different translations to the same English phrase depending on the context.
>> If we lose msgctxt, we must have another
m.balaba...@gmail.com wrote on 04-06-17 21:23:
> Yes, Bulgarian is also one of those inflected languages that require
> different translations to the same English phrase depending on the context.
> If we lose msgctxt, we must have another way to separate different instances
> of the same
Hello,
Yes, Bulgarian is also one of those inflected languages that require different
translations to the same English phrase depending on the context. If we lose
msgctxt, we must have another way to separate different instances of the same
English phrase. Years ago at my workplace, we had
Another big +1 for what Martin and Mikhel have said about matching
existing translations and not losing the ability to translate to
different targets depending on the context.
And another bad thing if we lost qtz (KeyIDs) pseudo locale to differ
one entry from another.
--
wbr, sb, Russian Team
I've used the .PO based workflow from the
beginning of my OOO/LO L10N stint, and yes,
you'd get those problems in such environment.
You'd just have to keep the IDs for strings
translations' variants/exceptions/etc. separately.
That was how I was dealing with the problem,
anyway -- last
Big +1 for what Martin and Mikhel have said about matching existing
translations and not losing the ability to translate to different
targets depending on the context.
If there is going to be wholesale re-organisation as to how the strings
are presented for translation, two other
2017-06-01 18:14 GMT+03:00 Sophie :
> Hi all,
>
> I invite all of you to have a read to that message from Caolan, it's a
> discussion, so please share your concerns, your solutions, your views :)
>
> https://lists.freedesktop.org/archives/libreoffice/2017-May/077818.html
Hi, Sophie,
regarding 16 and 18, I think these are important or even most important
ones.
The 18 is the crucial one and should be tried in a separate world, with an
extra instance of Pootle to test what really happens. Without testing this
with real world examples it should not be introduced.
10 matches
Mail list logo