Re: [libreoffice-l10n] Re: .src and .ui gettext migration

On Wed, 2017-07-19 at 13:24 +0200, Leandro Regueiro wrote: > Hi, > changing the msgctxt is problematic from Pootle point of view since: > > - Pootle will detect these as new strings that will be imported with > no translation, and Pootle will mark old strings as obsolete. > > Please hold, and

Re: [libreoffice-l10n] Re: .src and .ui gettext migration

On Sun, Jul 16, 2017 at 12:21 AM, Martin Srebotnjak wrote: > Caolan, > > you should test this really extensively, with the Pootle content as well as > with the non-Pootle l10n teams. Hi, changing the msgctxt is problematic from Pootle point of view since: - Pootle will detect

Re: [libreoffice-l10n] Re: .src and .ui gettext migration

Caolan, you should test this really extensively, with the Pootle content as well as with the non-Pootle l10n teams. I can help you use the Slovenian translation, as I use a separate localization platform. Thus we could test if this change leads to translation corruption or loss of translated

[libreoffice-l10n] Re: .src and .ui gettext migration

On Fri, 2017-07-14 at 15:57 +0200, Eike Rathke wrote: > Questions: > * where does the new implementation live that determines the actual >   "resource" to be used for the current UI language, including > possible language fallbacks? We pass GetUILanguageTag to boost, and that's always one of the

[libreoffice-l10n] Re: .src and .ui gettext migration

Hi Caolán, On Thursday, 2017-07-13 10:43:24 +0100, Caolán McNamara wrote: > So, I'm pretty happy with my latest iteration of migrating to gettext > and I've got it up and running on all supported platforms. First: yay \ó/ > Is there any outstanding concerns or questions. Questions: * where