Re: help commit translation -ne_NP

2014-09-12 Thread Daniel Mustieles García
Hi Pawan,

As the the team coordinator, you can commit your translations directly from
the DL page. Once uploaded the translation, you will be able to commit it
into Git using the actions in the module's page.

If you need more help with this issue, ask us again and we'll help you.

Best regards

2014-09-12 10:11 GMT+02:00 CHAUTARI chaut...@gmail.com:

 Dear All,

 I have uploaded some of the translation for gnome 3.14 and need assistance
 for committing the same.

 Thanking you.

 Regards,
 Pawan



 ___
 gnome-i18n mailing list
 gnome-i18n@gnome.org
 https://mail.gnome.org/mailman/listinfo/gnome-i18n


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


String freeze break request for gnome-shell

2014-09-12 Thread Florian Müllner
Hey folks,

sorry for the late request, but the bug in question[0] only came in today ...

In the system menu, we'd like to link to the corresponding Settings
panel in the Location submenu (like all other submenus do), which
would add the new string Privacy Settings.

-- Florian

[0] https://bugzilla.gnome.org/show_bug.cgi?id=736542
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Committing translations

2014-09-12 Thread Ask Hjorth Larsen
Hello

Kenneth, our previous coordinator, has argued very convincingly that
working over the mailing list is more efficient than using damned
lies.  Amongst other things this is because we always proofread a
specially generated podiff.  It also seems to me that the damned lies
workflow involves the reviewer correcting the po-file.  In our group
the reviewer writes comments in the podiff to the translator who then
learns something and edits the po-file.  A minor issue perhaps, but
it's not so smooth with damned lies, and there are a few other reasons
as well.

So I would be quite interested in a git account.  Could this be arranged please?

Best regards
Ask

2014-09-12 0:30 GMT+02:00 Ask Hjorth Larsen asklar...@gmail.com:
 Hello Alexandre

 2014-09-12 0:15 GMT+02:00 Alexandre Franke alexandre.fra...@gmail.com:
 On Fri, Sep 12, 2014 at 12:02 AM, Ask Hjorth Larsen asklar...@gmail.com 
 wrote:
 Hello translators and other wise people

 Hey Ask!

 I recently became coordinator of the Danish translation team.  I am
 now using damned lies to commit some translations.  It results in a
 bit more clicking than strictly necessary.

 That's because you're doing it wrong. ;-)

 Right :).  Well...


 Basically we use a mailing list to facilitate the proofreading
 process, and our translators eventually send the finished files to our
 mailing list for committing.  What I do then is to go to damned lies,
 remove their reservation, upload the new file, claim that it's ready
 to be committed, and then I commit it.  This does not seem to fit 100%
 the way the system was thought out.  Is it an acceptable way to do
 things?  It is a lot of clicking to circumvent things that are
 obviously meant to be there.

 Acceptable, sure. Best choice? I don't think so.

 While a mailing list can be an okay tool for the job, Damned lies
 really shines in that context and was designed for that workflow. It's
 way better as it allows you to track the exact state of modules. You
 can see what's been translated and not reviewed yet, what's reviewed
 and needs to be pushed to the repos, or what is being left out by
 translators. You can also use the commenting system to have a
 discussion and I think this is better than a thread on a mailing list
 as it keeps the relevant messages grouped together in one place on the
 module page.

 The fact that you can diff between the submitted files and the repos,
 or the automatic merging/updating of files when new strings appear in
 the module, are also killer features that you won't find in a mailing
 list centered workflow.

 I may be forgetting other advantages to using Damned lies, but I hope
 I've made my point with what I already said.

 As an alternative I could use git directly, but I don't have a key
 registered for that.

 Meh. You can do it if you decide to keep using the mailing list, but I
 don't think it's a good idea.

 What do you generally do and think?

 Of course each team is free to work the way they want, but I strongly
 advise you to use Damned lies for the whole process. It will make your
 life way easier, believe me. :-)

 --
 Alexandre Franke

 We translate a lot of different projects through the mailinglist, many
 of which are not on damned lies.  I guess I can ask the others how
 they like to do things.  But since we (ir)regularly get po-files from
 translationproject.org, Launchpad, KDE, transifex and GNOME, it's a
 bit out of the way for us to make exceptions for GNOME.  I do agree
 with you that damned lies is very powerful though.  We'll see...

 Thank you again.

 Best regards
 Ask
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Committing translations

2014-09-12 Thread Daniel Mustieles García
2014-09-12 12:09 GMT+02:00 Ask Hjorth Larsen asklar...@gmail.com:



 So I would be quite interested in a git account.  Could this be arranged
 please?


Apart from this specific case, I would vote for giving team coordinators a
git account (if requested), so they will be able to directly fix typos in
original strings, or to use automated scripts to commit translations,
instead of uploading and commiting them individually. At least for the
Spanish team, the coordinator is who has more assigned modules (sadly, most
of the time I'm the only active translator in the team...), so commiting a
bunch of translations using DL may be painful (considering that nobody's
reviewing these translations, so DL's workflow is not used).

Also, it seems that DL is not friend of modules that don't have PO files in
standar places (video-subtitles is the most recent example of this, but
don't know if there are other modules affected), so a Git account is needed
in this situations.

Best regards
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: String freeze break request for gnome-shell

2014-09-12 Thread Daniel Mustieles García
1/2 from i18n

Cheers

2014-09-12 12:04 GMT+02:00 Florian Müllner fmuell...@gnome.org:

 Hey folks,

 sorry for the late request, but the bug in question[0] only came in today
 ...

 In the system menu, we'd like to link to the corresponding Settings
 panel in the Location submenu (like all other submenus do), which
 would add the new string Privacy Settings.

 -- Florian

 [0] https://bugzilla.gnome.org/show_bug.cgi?id=736542
 ___
 gnome-i18n mailing list
 gnome-i18n@gnome.org
 https://mail.gnome.org/mailman/listinfo/gnome-i18n

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: String freeze break request for gnome-shell

2014-09-12 Thread Alexandre Franke
2/2 from i18n.

-- 
Alexandre Franke
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


3.14 Release Notes

2014-09-12 Thread Allan Day
Hi everyone!

The 3.14 release notes are now available for translation. They can be found
in the gnome-3-14 branch of the release-notes module.

3.14 is due for release on 24 September.

Note that the images are currently not complete/finalised - I'll get those
finished soon. Will keep you notified.

Thanks!

Allan
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


String additions to 'gnome-shell.master'

2014-09-12 Thread GNOME Status Pages
This is an automatic notification from status generation scripts on:
http://l10n.gnome.org.

There have been following string additions to module 'gnome-shell.master':

+ Privacy Settings

Note that this doesn't directly indicate a string freeze break, but it
might be worth investigating.
http://git.gnome.org/browse/gnome-shell/log/?h=master
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n