[libcryptui] Created branch gnome-3-4

[Stefan Walter]

The branch 'gnome-3-4' was created pointing to:

 59b8bb1... Release 3.4.1

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

Re: gnome-online-accounts: string freeze break request

[Debarshi Ray]

> We would like to pick the fix for https://bugzilla.gnome.org/654168 from
> master to gnome-3-4, but that would require the addition of the following
> strings:
> 
> src/daemon/goadaemon.c
>   "ProviderType property is not set for account"
>   "Failed to find a provider for: %s"
> 
> src/goabackend/goaprovider.c
>   "Failed to delete credentials from the keyring: %s"
> 
> Requesting a string freeze break.

Ping. 3.4.1 is close at hand, so could you please take a look at this request?
Due to a mistake on our part the patch has already been committed to the
gnome-3-4 branch but the strings are currently unmarked.

Thanks,
Debarshi

-- 
Give a man ssh access, he'll still need computer. Give him a computer, he'll
give ssh access to you.  -- Ashish Shukla


pgprAPPN31gXI.pgp
Description: PGP signature
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

[gcr] Created branch gnome-3-4

[Stefan Walter]

The branch 'gnome-3-4' was created pointing to:

 ef5ea20... Release 3.4.1

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

[libgnome-keyring] Created branch gnome-3-4

[Stefan Walter]

The branch 'gnome-3-4' was created pointing to:

 5b15115... Release 3.4.1

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

String additions to 'glib.master'

[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 'glib.master':

+ "No DNS record of the requested type for '%s'"

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

GNOME Quarterly Report Q1/2012

[Andre Klapper]

Hi everybody, 

it's time again for a quarterly GNOME report to let community and
companies know what has been going on between January and March 2012.

Please update your section for Q1/2012 here:

  https://live.gnome.org/GnomeMarketing/QuarterlyReports/2012/Q1


The list of potential teams and writers:

 * Board and Executive Director - Karen Sandler
 * Bugsquad - Andre Klapper
 * Membership and Elections Committee - Tobias Mueller
 * GNOME User Groups - ???
 * Accessibility Team - Alejandro Piñeiro Iglesias, Joanmarie Diggs
 * Outreach Program for Women - Marina Zhurakhinskaya
 * Localization - Petr Kovar
 * Documentation - ???
 * Web - Andreas Nilsson, Vinicius Depizzol
 * Google Summer of Code 2012 - ???
 * Marketing - ???
 * Sysadmin - ???
 * Design - ???
 * Conference planning: GUADEC, GNOME.asia? - ???


If you do not have time, please consider delegating the task! 

There are some sections that do not have writers yet - please fill your
name in on the wiki if you could write a summary. It really does not
have to be long!

I also assume that every writer welcomes help and input (that's why I
also send this to corresponding mailing lists).

We would like to finish the Q1 report before by May 11, 2012.

Thanks for your help, 
andre
-- 
mailto:ak...@gmx.net | failed
http://blogs.gnome.org/aklapper

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

Re: Boxes: Two more strings

[Zeeshan Ali (Khattak)]

On Fri, Mar 30, 2012 at 4:06 AM, Zeeshan Ali (Khattak)
 wrote:
> On Thu, Mar 29, 2012 at 1:23 AM, Zeeshan Ali (Khattak)
>  wrote:
>> Hi,
>>   Now that hard code freeze is over I'll soon be making another Boxes
>> release with some fixes from 3.5 branch. Unfortunately two of them
>> displays new strings to user and therefore we must request string
>> freeze break for them. Here are the strings from pot file:
>>
>> #: ../src/fedora-installer.vala:54
>> msgid ""
>> "Internet access required for express installation of Fedora 16 and older"
>> msgstr ""
>>
>> #: ../src/unattended-installer.vala:160
>> #, c-format
>> msgid "Password required for express installation of %s"
>> msgstr ""
>
> Sorry I forgot to mention that I'll appreciate any urgency on this
> cause I intend to make a nano release tomorrow for some very urgent
> fixes so it would be nice to merge all fixes after 3.4.0 release.

Its been more than 2 weeks now and I haven't gotten any reply to this
simple request even after reminder here and on IRC. Its time for 3.4.1
and i'll just go ahead and break the string freeze if nobody is
interested any ways.

-- 
Regards,

Zeeshan Ali (Khattak)
FSF member#5124
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Boxes: Two more strings

[Petr Kovar]

Hi,

On Mon, 16 Apr 2012 17:59:09 +0300
"Zeeshan Ali (Khattak)"  wrote:

> On Fri, Mar 30, 2012 at 4:06 AM, Zeeshan Ali (Khattak)
>  wrote:
> > On Thu, Mar 29, 2012 at 1:23 AM, Zeeshan Ali (Khattak)
> >  wrote:
> >> Hi,
> >>   Now that hard code freeze is over I'll soon be making another Boxes
> >> release with some fixes from 3.5 branch. Unfortunately two of them
> >> displays new strings to user and therefore we must request string
> >> freeze break for them. Here are the strings from pot file:
> >>
> >> #: ../src/fedora-installer.vala:54
> >> msgid ""
> >> "Internet access required for express installation of Fedora 16 and older"
> >> msgstr ""
> >>
> >> #: ../src/unattended-installer.vala:160
> >> #, c-format
> >> msgid "Password required for express installation of %s"
> >> msgstr ""
> >
> > Sorry I forgot to mention that I'll appreciate any urgency on this
> > cause I intend to make a nano release tomorrow for some very urgent
> > fixes so it would be nice to merge all fixes after 3.4.0 release.
> 
> Its been more than 2 weeks now and I haven't gotten any reply to this
> simple request even after reminder here and on IRC. Its time for 3.4.1
> and i'll just go ahead and break the string freeze if nobody is
> interested any ways.

I18n approval 1 of 2.

Sorry for the delay!

Cheers,
-- 
Petr Kovar

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

Mistakes in doc translations

[Shaun McCance]

Hi,

Sometimes translators make markup mistakes in docs translations.
When it happens in modules I make releases from, I go ahead and
fix the mistakes when I can. I don't mind doing that.

But recently, my fixes have been getting reverted. I don't know
what everybody's workflow is, but probably some translators treat
what's on their machine as canonical, and copy it over without
ever trying to merge. This is a very dangerous way to work with
a version control system.

I don't mind fixing problems, but I don't want to make the same
fixes every single release. Please merge your po files with the
files on git.gnome.org.

Thanks,
Shaun


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

kyrgyz language

[chingis]

I want to translate the Gnome, but there are no any active members. How
can I begin to translate and commit.

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

Re: Mistakes in doc translations

[Bruno Brouard]

Le lundi 16 avril 2012 à 14:25 -0400, Shaun McCance a écrit :
> Hi,
> 
> Sometimes translators make markup mistakes in docs translations.
> When it happens in modules I make releases from, I go ahead and
> fix the mistakes when I can. I don't mind doing that.
> 
> But recently, my fixes have been getting reverted. I don't know
> what everybody's workflow is, but probably some translators treat
> what's on their machine as canonical, and copy it over without
> ever trying to merge. This is a very dangerous way to work with
> a version control system.
> 
I am sorry, i don't understand what you mean. Is it possible to have an
example?

Bruno

> I don't mind fixing problems, but I don't want to make the same
> fixes every single release. Please merge your po files with the
> files on git.gnome.org.
> 
> Thanks,
> Shaun
> 
> 
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-i18n


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

Re: kyrgyz language

[Bahodir]

Welcome to Gnome!

Follow this link: https://live.gnome.org/TranslationProject

It has all the information you need. Bascially, you want to apply for 
the team coordinator position first. Once you are the coordinator, you 
can push your changes to git.


Best,
Bahodir

On 04/16/12 14:27, chingis wrote:

I want to translate the Gnome, but there are no any active members. How
can I begin to translate and commit.

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


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

Re: kyrgyz language

[Mario Blättermann]

Am 16.04.2012 20:27, schrieb chingis:
> I want to translate the Gnome, but there are no any active members. How
> can I begin to translate and commit.
> 
>
Do you've tried to contact the current coordinator Timur Jamakeev
? If he doesn't response within two weeks or so, we
should consider him as really inactive. Then you could become the new
team coordinator.

However, you are a member of the team and you are able to upload your
translations to the appropriate modules. As long as you are the one and
only translator, it shouldn't be a problem to commit them to the Git
repo by one of us. Once you have contributed some translations (don't
know what "some" means in particular here) you should try to get your
own Git account.

Just a technical issue: Don't use the function "Write a comment" in the
Damned Lies statistics pages. As a translator, you have to use first
"Reserve for translation" and then "Upload the new translation". Besides
that (assuming you want to become the coordinator), you can assign
yourself to the "Committers" group in your team to make your translation
available for committing. Once this has been happened, please inform
this mailing list so that one of us can commit your file.

Last but not least, it would be nice to know your full name.

Best Regards,
Mario
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: kyrgyz language

[Mario Blättermann]

Am 16.04.2012 21:58, schrieb Bahodir:
> Welcome to Gnome!
> 
> Follow this link: https://live.gnome.org/TranslationProject
> 
> It has all the information you need. Bascially, you want to apply
> for the team coordinator position first. Once you are the
> coordinator, you can push your changes to git.
> 
No, not right. Team coordinators don't get their Git accounts
automatically. They have to contribute some (or some more) translations
first. In my case - some years ago - I have translated approximately
more than 2000 strings before.

Best Regards,
Mario
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

[libsoup] Created branch gnome-3-4

[Dan Winship]

The branch 'gnome-3-4' was created pointing to:

 127d3b0... 2.38.1

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

Re: Mistakes in doc translations

[Andre Klapper]

On Mon, 2012-04-16 at 21:01 +0200, Bruno Brouard wrote:
> I am sorry, i don't understand what you mean. Is it possible to have an
> example?

To put it into other words:
Shaun fixed something in Git, and the translators OVERWROTE the fix with
his/her next commit to Git.

andre
-- 
mailto:ak...@gmx.net | failed
http://blogs.gnome.org/aklapper

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

Re: kyrgyz language

[Chingis Jumaliev]

I want to be the coordinator of kyrgyz team.

On Tue, Apr 17, 2012 at 1:58 AM, Bahodir <6aho...@gmail.com> wrote:

> Welcome to Gnome!
>
> Follow this link: 
> https://live.gnome.org/**TranslationProject
>
> It has all the information you need. Bascially, you want to apply for the
> team coordinator position first. Once you are the coordinator, you can push
> your changes to git.
>
> Best,
> Bahodir
>
>
> On 04/16/12 14:27, chingis wrote:
>
>> I want to translate the Gnome, but there are no any active members. How
>> can I begin to translate and commit.
>>
>> __**_
>> gnome-i18n mailing list
>> gnome-i18n@gnome.org
>> http://mail.gnome.org/mailman/**listinfo/gnome-i18n
>>
>
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Mistakes in doc translations

[Daniel Mustieles García]

Hi Shaun,

I opened a bug in Gtranslator asking to create a plugin based on gtxml
[1], to check this kind of incrrect markups.

I know Nacho is working on it, but at this moment, it isn't fisnished.
I hope he can get it fully implemented, so Gtranslator will warn about
incorrect markpup in documentation, like it does with variables.

BTW, gtxml is a very simple and useful tool, and can be used with
several po files (gtxml -c *.po). Once a month I try to review all the
spanish doc po files, to fix this kind of errors. It would be great if
all translation coordinators could do this task in their own teams.

Best regards

[1] https://launchpad.net/pyg3t

El día 16 de abril de 2012 20:25, Shaun McCance  escribió:
> Hi,
>
> Sometimes translators make markup mistakes in docs translations.
> When it happens in modules I make releases from, I go ahead and
> fix the mistakes when I can. I don't mind doing that.
>
> But recently, my fixes have been getting reverted. I don't know
> what everybody's workflow is, but probably some translators treat
> what's on their machine as canonical, and copy it over without
> ever trying to merge. This is a very dangerous way to work with
> a version control system.
>
> I don't mind fixing problems, but I don't want to make the same
> fixes every single release. Please merge your po files with the
> files on git.gnome.org.
>
> Thanks,
> Shaun
>
>
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-i18n
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Mistakes in doc translations

[Bruno Brouard]

Le lundi 16 avril 2012 à 22:14 +0200, Andre Klapper a écrit :
> On Mon, 2012-04-16 at 21:01 +0200, Bruno Brouard wrote:
> > I am sorry, i don't understand what you mean. Is it possible to have an
> > example?
> 
> To put it into other words:
> Shaun fixed something in Git, and the translators OVERWROTE the fix with
> his/her next commit to Git.
> 
Thank you again, I am not stupid :-)

But Shaun speak specifically of "markup mistakes" and said
"I don't know what everybody's workflow is, but probably some
translators treat
what's on their machine as canonical, and copy it over without ever
trying to merge."
I don't understand this previous sentence.

Can HE give a concrete example of the error (that maybe i am doing)?

As the message is intended to all commiters, i think it is better to be
clearer, even if it
is necessary to name someone. If i am doing mistake, i want to learn my
mistake.
I am just a human.

Bruno

> andre


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

String additions to 'gnome-boxes.gnome-3-4'

[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-boxes.gnome-3-4':

+ "Internet access required for express installation of Fedora 16 and older"
+ "Password required for express installation of %s"

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

Re: Boxes: Two more strings

[Gil Forcada]

El dl 16 de 04 de 2012 a les 17:18 +0200, en/na Petr Kovar va escriure:
> Hi,
> 
> On Mon, 16 Apr 2012 17:59:09 +0300
> "Zeeshan Ali (Khattak)"  wrote:
> 
> > On Fri, Mar 30, 2012 at 4:06 AM, Zeeshan Ali (Khattak)
> >  wrote:
> > > On Thu, Mar 29, 2012 at 1:23 AM, Zeeshan Ali (Khattak)
> > >  wrote:
> > >> Hi,
> > >>   Now that hard code freeze is over I'll soon be making another Boxes
> > >> release with some fixes from 3.5 branch. Unfortunately two of them
> > >> displays new strings to user and therefore we must request string
> > >> freeze break for them. Here are the strings from pot file:
> > >>
> > >> #: ../src/fedora-installer.vala:54
> > >> msgid ""
> > >> "Internet access required for express installation of Fedora 16 and 
> > >> older"
> > >> msgstr ""
> > >>
> > >> #: ../src/unattended-installer.vala:160
> > >> #, c-format
> > >> msgid "Password required for express installation of %s"
> > >> msgstr ""
> > >
> > > Sorry I forgot to mention that I'll appreciate any urgency on this
> > > cause I intend to make a nano release tomorrow for some very urgent
> > > fixes so it would be nice to merge all fixes after 3.4.0 release.
> > 
> > Its been more than 2 weeks now and I haven't gotten any reply to this
> > simple request even after reminder here and on IRC. Its time for 3.4.1
> > and i'll just go ahead and break the string freeze if nobody is
> > interested any ways.
> 
> I18n approval 1 of 2.
> 
> Sorry for the delay!
> 
> Cheers,

(we were shy :)

i18n 2 of 2.

Cheers,

-- 
Gil Forcada

[ca] guifi.net - una xarxa lliure que no para de créixer
[en] guifi.net - a non-stopping free network
bloc: http://gil.badall.net
planet: http://planet.guifi.net

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

Re: Mistakes in doc translations

[Shaun McCance]

On Mon, 2012-04-16 at 23:04 +0200, Bruno Brouard wrote:
> Le lundi 16 avril 2012 à 22:14 +0200, Andre Klapper a écrit :
> > On Mon, 2012-04-16 at 21:01 +0200, Bruno Brouard wrote:
> > > I am sorry, i don't understand what you mean. Is it possible to have an
> > > example?
> > 
> > To put it into other words:
> > Shaun fixed something in Git, and the translators OVERWROTE the fix with
> > his/her next commit to Git.
> > 
> Thank you again, I am not stupid :-)
> 
> But Shaun speak specifically of "markup mistakes" and said
> "I don't know what everybody's workflow is, but probably some
> translators treat
> what's on their machine as canonical, and copy it over without ever
> trying to merge."
> I don't understand this previous sentence.
> 
> Can HE give a concrete example of the error (that maybe i am doing)?
> 
> As the message is intended to all commiters, i think it is better to be
> clearer, even if it
> is necessary to name someone. If i am doing mistake, i want to learn my
> mistake.
> I am just a human.

I have corrected markup errors in the French translations. See my
commits here:

http://git.gnome.org/browse/gnome-user-docs/log/gnome-help/fr/fr.po

But the errors are always new errors. As an example of my corrections
being overwritten, look at the Slovenian translations. Here's a commit
I made about two weeks ago:

http://git.gnome.org/browse/gnome-user-docs/commit/gnome-help/sl/sl.po?id=34f54c24c2d69d94fdf4124436c84b2d977045e0

And here's the commit I made today:

http://git.gnome.org/browse/gnome-user-docs/commit/gnome-help/sl/sl.po?id=4f68f59f5da11f193cc4eaa91c34c4c9f6e045b7

This is the workflow that usually leads to these kinds of problems:

1) Get the file from git and copy it to some folder somewhere.
2) Edit the file.
3) Update your git repository, or clone it fresh.
4) Copy the file from some folder into the repository and commit.

Using this workflow, you will never get merges of other people's work.
If anybody else edits the files you edit, you will always overwrite
whatever they do.

And I realize many translators are used to basically owning their own
po files and not having to worry about other people editing them. But
module maintainers have to be able to fix syntax errors. And until we
get better tool support (like the kinds of checks you all already have
for format strings), we'll continue to see these mistakes.

--
Shaun


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