bashareteam team mailing list archive

[Emilien Klein <emilien@xxxxxxxx>]

Jeroen,

Thanks for taking the time to reply, I understand you had a busy week!
I have been in touch with Henning Eggers, who has solved the issue:
https://answers.edge.launchpad.net/launchpad/+question/85064
However, in the process of doing so, we discovered a bug in Launchpad,
where the TranslationBranchApprover doesn't respect the status of a
template, which had the effect of reimporting blocked templates if
they got modified later.
https://bugs.edge.launchpad.net/rosetta/+bug/446160

A temporary fix should be in place, until the actual bug fix can be
shipped out on November 4th.

Thanks for your involvment!
Emilien Klein.

2009/10/9 Jeroen Vermeulen <jtv@xxxxxxxxxxxxx>
>
> Emilien Klein wrote:
>>
>> Hi Jeroen,
>
> Hi Emilien,
>
> My apologies for the slow response; our team has beem meeting this week, which involves a lot of travel and being away from email.  I will also, in principle, not be available next week.
>
>
>> Aside from generating the strangely named ".lang/.pot" translation
>> template, our IDE Gambas also generates a template for each ".class"
>> file in the project (don't know the justification behind that, but I
>> imagine it is used internally by Gambas to generate the full list of
>> strings to translate?)
>>
>> Those files were originally not included in our Bazaar repository,
>> because they are generated automatically. But the decision has been
>> made to now include them in the repository.
>>
>> But Launchpad has detected those new template files, and has imported
>> some of them as new translation templates for our project, BaShare.
>>
>> QUESTION: Is there a way to remove those extra templates, and to
>> instruct Launchpad not to import them again in the future (but still
>> having them in the version control)?
>
> Yes, we can do that by disabling those templates that have been created.  As far as I can tell, that has already been done.
>
>
>
>> Our project is BaShare: https://launchpad.net/bashare
>> The unnecessary templates that have been imported are:
>> - fmain
>> - impostazioni
>> - project
>>
>> We would like to keep only the template called "bashare".
>
>> P.S.: As a side note, do you know why only the 3 previously mentioned
>> templates got imported? This is the list of all the ".pot" files that
>> are in version control (of course we don't want them to be uploaded,
>> but just curiosity...)
>> #project.pot (unwantedly imported in the "project" template)
>> .pot (this is the "complete" template, that is used to import in the
>> "bashare" template)
>> About.pot
>> FMain.pot (unwantedly imported in the "fmain" template)
>> FormIP.pot
>> FPicTrayIcon.pot
>> FRic.pot
>> FStart.pot
>> HelpUPnP.pot
>> Impostazioni.pot (unwantedly imported in the "impostazioni" template)
>
> Probably because the special auto-approver that we use for imports from branches used to have a slight problem with capital letter.  That was fixed in Launchpad 3.0, and some those templates do exist now.  But again, someone seems to have disabled them already.
>
>
> Jeroen