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
For those who translates out of Pootle, msgctxt is to be removed, if you
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.
As
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
>
> For those who translat
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 consideration
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 time
