bashareteam team mailing list archive

[Emilien Klein <emilien@xxxxxxxx>]

Hi Jeroen,

My name is Emilien Klein, and I am currently helping Guido Iodice with
his project BaShare.
He submitted a translation template a few weeks ago, but you didn't
approve the upload because the template was named
"BaShare/.lang/.pot". In order to get our translations in Launchpad, I
had created a hard link called bashare.pot that linked to
BaShare/.lang/.pot. The idea was to have a hard link "bashare.pot" ->
"BaShare/.lang/.pot", so that when the original template got modified
(the .pot file), the hard link would also get updated, and launchpad
would detect the changes and update the translation template.
However, the hard link is not working, once you get it in bzr it
behaves as a completely different file, so we have to manually copy
the .pot to the bashare.pot file and commit both files. This, as you
can imagine, is not a satisfactory automatic behavior, and an
unnecessary duplication of resources.

I realize that the easy solution might seem to just rename the
template ".pot" to something more suitable. However, this name is
automatically chosen by our IDE Gambas:

BaShare is written using Gambas. Gambas automatically creates the
translation template, and stores it by automatically in a file called
".pot" in a project subfolder called ".lang". This explains why our
translation template is located in the versioned file
"BaShare/.lang/.pot".

The first time that Guido submitted this file to Launchpad to get
automatically imported, it got suspended because (and it is a valid
remark) the dot in front of the file name usually means a hidden file
in the Linux world (and my guess is that the creator of Gambas
explicitely wants to hide the .pot file, because Gambas is able to
handle the translation process directly from within, and doesn't want
people to notice this translation template file).

Hard linking to this file is not a valid option in Bazaar, so I would
like to ask if it is possible to import the original template file
directly into the template "bashare" in BaShare trunk.

I'd greatly appreciate Jeroen if you could give this idea some more thought.

Bedankt!
Emilien Klein.