Translations for SchoolTool and SchoolBell

[Brian Sutherland]

On Tue, May 17, 2005 at 05:06:52PM +0200, Carlos Perelló Marín wrote:
> On Tue, 2005-05-17 at 16:42 +0200, Brian Sutherland wrote:
> > On Tue, May 17, 2005 at 01:09:24PM +0200, Carlos Perelló Marín wrote:
> > > On Mon, 2005-05-16 at 11:28 +0200, Brian Sutherland wrote:
> > > It will not work for upstream projects, only for packages inside Ubuntu.
> > 
> > Both SchoolTool and SchoolBell are packages in the ubuntu universe for a
> > while now. (source packages schooltool and schoolbell)
> 
> Ok. Then they are not automatically imported because we need to
> implement the layout python uses to store the .pot/.po files.
> 
> It's part of our TODO but will not be done in next month and a half.
> 
> > 
> > Or do you mean only debconf translations?
> 
> No, usually all .po files are automatically imported into Rosetta, but
> there are some corner cases like python/PHP projects that are not being
> imported because a limitation in our importer.
> 
> You should note too that if you choose to use Ubuntu translations
> directly only the .pot files that are released will be imported into
> Rosetta. Depending on the project that's a problem or not, is up to you
> to decide if it works for you or not. Also, your translation team should
> be integrated with Ubuntu's translation teams.
> 
> Please, tell me if you choose this option so we put the python layout
> support on top of our priorities after our 1.0 release in a month and a
> half.

Very much appreciated!

I think we would prefer it this way. Already on our mailing list we
discussed making a translation only release a few weeks after the real
release. As opposed to string freezes.

But finding our translations may be a problem, because the 
schoolbell package unfortunately contains quite a bit of zope, which has
quite a few *.po and *.pot files lying around.

If you need any testing help, etc... let me know.

> > > We plan to prepare a solution for upstream translations, but it's not a
> > > planned feature for next month and a half.
> > > 
> > > > 
> > > > The other option seems to be to update the translations manually every
> > > > now and then.
> > > 
> > > Yes, that's the solution we have now for upstream translations.
> > > 
> > > 
> > > For the initial import of SchoolTool's .pot and .po files I need you
> > > send us the URL where we can get them so we import it inside the release
> > > I think you created at:
> > > https://launchpad.ubuntu.com/products/schooltool/0.10-rc1
> > 
> > That is just the problem, there is no canonical url as the .pot's are
> > automatically generated and not stored in the repository at all
> > (Following the never store auto-generated files in repositories mantra).
> 
> Well, I will do the upload only the first time, the other times should
> be uploaded by you so I only need a .pot file that you generate for me,
> that's all.

Great, I have attached a gzipped pot file, and will update it manually
until things can become more automatic (re above)

> > > btw, will you be the "official" contact with the SchoolTool project?
> > > (the direct question is... will you be the one uploading .pot files?)
> > 
> > In so far as I have picked up the task, it seems a good fit with my
> > "odd-job man of the project (Release manager/Package Maintainer)" role.
> 
> 
> Ok, will ask an ownership change for the Schoolbell POTemplate so when
> the restrictions we are implementing land in the server you are able to
> update it.

Fine with me, I have CC'ed this to Tom so that he can shout if he has
any issues.

> If you choose to use Ubuntu as you translation source, we could move
> current SchoolBell translations there. The same for SchoolTool, we can
> go now with the manual import and when we implement the support for
> Python layout, move them to Ubuntu translations.

Perfect!

One final question: I wrote a small sctipt to mass download the .po
files from rosetta. But it's not very good. anyone know of a better one?

-- 
Brian Sutherland

It's 10 minutes, 5 if you walk fast.