public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: dooteo <dooteo@zundan.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluez-gnome 0.23 translated to Basque lang
Date: Sat, 08 Mar 2008 13:57:33 +0100	[thread overview]
Message-ID: <1204981053.3231.448.camel@desktop.zundan.com> (raw)
In-Reply-To: <D3BF31B1-0166-4138-AB2E-5725EEB73CFE@holtmann.org>

Hi Marcel,

Don't worry, two days ago I inserted each translated message into
Launchap . 

Let me underline that Launchpad PO version is different from 0.23 (maybe
TRUNK version?)

So I hope Launchpad version will be usefull for  you :)

Best regards,

Dooteo


Jatorrizko mezua: or., 2008-03-07 19:45 +0100, egilea: Marcel Holtmann
> Hi,
> 
> > Inkscape project uses Launchpad.net, but translators must send PO  
> > files
> > as bug to the project, so then Inkscape developers take them and put
> > into the source code. It could be a way for bluez-gnome too. See:
> >
> > https://bugs.launchpad.net/bugs/198101
> >
> > Other way (I think the best), to not take care about translation,  
> > could
> > be to include as GNOME project into gnome.org site... There we
> > (translators) use SVN too to access source code (checkout/update), and
> > once a PO is updated we commit. All access is done by SSH passphrase,
> > and all source  code is taken by many GNU/Linux distributions (with
> > translated files of course) to be packet into their releases.
> >
> > Most of translators uses KBabel or Gtranslator like tools to translate
> > and use translation memorie. https://translations.launchpad.net has
> > translation memories, but some community translators doesn't use them,
> > and make wrong style translations.
> >
> > By the other hand, can I submit translated file to you directly?
> 
> can't you simply upload your PO file into launchpad and I request a  
> download of all translations just before I do the release. This way, I  
> don't have to deal with the details.
> 
> Regards
> 
> Marcel
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
> 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-03-08 12:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03 22:03 [Bluez-devel] bluez-gnome 0.23 translated to Basque lang dooteo
2008-03-04  2:45 ` Marcel Holtmann
2008-03-04 17:09   ` dooteo
2008-03-07 18:45     ` Marcel Holtmann
2008-03-08 12:57       ` dooteo [this message]
2008-03-08 19:28         ` Marcel Holtmann
2008-03-10 17:26           ` dooteo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1204981053.3231.448.camel@desktop.zundan.com \
    --to=dooteo@zundan.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox