Fwd: Start translating GNUmed into your language now

View: New views
2 Messages — Rating Filter:   Alert me  

Parent Message unknown Fwd: Start translating GNUmed into your language now

by Jim Busser :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

From Sebastian who is not on his regular email:

From: sebastian-hilbert
Date: October 29, 2009 3:50:09 AM PDT
To: Jim Busser
Subject: Re: Re: [Gnumed-devel] Start translating GNUmed into your language now

Please forward to the list.

I have set permissions to open since that (for the time being) will let all Launchpad users contribute instead of members of a dedicated team only. If that gives problems we could set to structured and let only people in the Launchpad-GNUmed-Team do the translations but for now I see no risk.

I have back in time told bazaar where to find the GNUmed CVS and periodically CVS is imported into bazaar.

I have not checked if the translations go missing when importing a template but that should be solvable by importing the template and checking a translated po file into CVS. This should get synced.

I believe they are not parsing the bazaar for po files per se but if you register a template they will try to find it and merge.

Can anyone try to change a string in CVS in say pt_BR.po in CVS and see if it turns up online ?

The safest way to associate CSV branches/releases with translations are to use the branch feature of bzr as well but for the time being one could download the translations for the main branch (== CVS head) once a release is tagged.

We will see how it works.

_______________________________________________
Gnumed-devel mailing list
Gnumed-devel@...
http://lists.gnu.org/mailman/listinfo/gnumed-devel

Re: Fwd: Start translating GNUmed into your language now

by Karsten Hilbert :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Thu, Oct 29, 2009 at 07:56:01AM -0700, Jim Busser wrote:

> >I have set permissions to open since that (for the time being)
> >will let all Launchpad users contribute instead of members of a
> >dedicated team only. If that gives problems we could set to
> >structured and let only people in the Launchpad-GNUmed-Team do the
> >translations but for now I see no risk.

OK, good.

> >I have back in time told bazaar where to find the GNUmed CVS and
> >periodically CVS is imported into bazaar.

That explains some of that. Good.

> >I have not checked if the translations go missing when importing a
> >template

It (bzr, or the translation service *from* bzr) cannot
import a template (gnumed.pot) because there IS NO template
in CVS.

> but that should be solvable by importing the template and
> >checking a translated po file into CVS. This should get synced.

I fully assume it would.

> >Can anyone try to change a string in CVS in say pt_BR.po in CVS
> >and see if it turns up online ?

I did (as told by Jim) in the de.po file.

> >The safest way to associate CSV branches/releases with
> >translations are to use the branch feature of bzr as well but for
> >the time being one could download the translations for the main
> >branch (== CVS head) once a release is tagged.

HEAD is fine for now.

Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346


_______________________________________________
Gnumed-devel mailing list
Gnumed-devel@...
http://lists.gnu.org/mailman/listinfo/gnumed-devel