Mailing List Archive

2011/1/22 Nicolas Riendeau <knight at teksavvy.com>:
> I know back in december Chris Pinkham was suggesting downloading the themes
> to generate the themestrings file so as far as the translators were
> concerned they wouldn't see any difference.

Yep, and I'm perfectly fine with that solution. But the discussions
which followed the next days, gave me the impression that this was a
no-go, since "we" wanted to fix this properly instead of adding
"another hack" to the themestrings-generation process.

> The work he does now won't be lost anyway since the Qt ts files could be
> transformed into Qt phrase book (.qph I believe) to reuse these translation.

Ok, I'm not into Qt phrase books, but cool if that's a workaround for
keeping the existing translations on a future theme translation
solution.

If we're sticking with the old themestrings generation process for
0.25, with the minor addition of downloading the themes, then we
should probably get it fixed sooner rather than later. We still
haven't generated the themestrings after the last update to the run.sh
script (93c63ba0), so currently there's at least 100 unwanted
translatable themestrings in MythTV (another reason to give the
ThemeUI translations lowest priority at the moment, not to mention the
changes in available themes). If that's what we'll do for 0.25, then
I'll probably have time to add a hack for downloading themes next week
and then regenerate the themestrings while I'm at it.

Best regards
Kenni

Hi Kenni,

On 1/22/2011 12:38 PM, Kenni Lund wrote:
> 2011/1/22 Nicolas Riendeau<knight at teksavvy.com>:
>> I know back in december Chris Pinkham was suggesting downloading the themes
>> to generate the themestrings file so as far as the translators were
>> concerned they wouldn't see any difference.
>
> Yep, and I'm perfectly fine with that solution. But the discussions
> which followed the next days, gave me the impression that this was a
> no-go, since "we" wanted to fix this properly instead of adding
> "another hack" to the themestrings-generation process.

Doing it, at least temporarily, that way is not incompatible with that
goal (since there are ways to recuperate the translation work people
have done).

I looked up that discussion. It's funny, I didn't remember Stuart M had
proposed more or less the same thing I said in my previous message (I
was already familiar with Qt phrase books and rebuilding a theme
translation file using the translation in the other files just seemed to
make sense...).

>> The work he does now won't be lost anyway since the Qt ts files could be
>> transformed into Qt phrase book (.qph I believe) to reuse these translation.
>
> Ok, I'm not into Qt phrase books, but cool if that's a workaround for
> keeping the existing translations on a future theme translation
> solution.

I have used them in the past (you know, when some of the strings when
from all being in the MythFrontend translation file to the plugin files
(-; )... That's how I recuperated the work we had done...

> If we're sticking with the old themestrings generation process for
> 0.25, with the minor addition of downloading the themes, then we
> should probably get it fixed sooner rather than later. We still

Until there's something better I think we should provide something that
lets people translate as they always had.

This is especially important from translation which have not gone into
maintenance mode (ie translations which have never achieved 100%
completion status).

> haven't generated the themestrings after the last update to the run.sh
> script (93c63ba0), so currently there's at least 100 unwanted
> translatable themestrings in MythTV (another reason to give the
> ThemeUI translations lowest priority at the moment, not to mention the

I thought you had removed them as it was planned but you're right, the
themes were removed before you had a chance to run that script.

> changes in available themes). If that's what we'll do for 0.25, then
> I'll probably have time to add a hack for downloading themes next week
> and then regenerate the themestrings while I'm at it.

The worst thing that could happen is that what's translated gets
reorganized in other files but the translation will get reused one way
or the other.

Have a nice day,

Nicolas