Re: [Announcement] Upcoming changes to GNOME’s mail infrastructure : gnome-i18n@gnome.org mailing list is to be discountinuited

[Daniel Mustieles García via gnome-i18n]

Sorry but what does it mean "in order to move to any other mailing list to
keep tracking of team announcements"?

Can we create a new label/tag in Discourse to manage translations teams?
And how/where to do this?

Won't DL notice about new uploaded translations and so in Discourse?

Thanks


El mié., 23 nov. 2022 17:10, Guillaume Bernard <
associati...@guillaume-bernard.fr> escribió:

> Hi all!
>
> This message comes after a previous announcement indicating that
> @gnome.org mailing list are going to be retired [0]. The last to remain
> are the gnome-i18n (this one) and localised mailing lists. The removal
> of mailing lists is planed for tomorrow UTC+1.
>
> The Damned-Lies application will now notify of string break changes in a
> dedicated Gitlab project [1].
>
> If you are involved in internationalisation/localisation teams, do not
> forget to subscribe (by selecting the bell icon and set the parameter to
> ‘Watch’ in order to receive notification in case of a string break.
>
> All discussions and threads that were opened on gnome-i18n gnome org
> will now happen on discourse.gnome.org [2] with the *i18n* tag under the
> **Community** category for general discussions or under the **Platform**
> category for more development focused conversations, still with the same
> *i18n* tag.
>
> In case you notice an issue with the notification system, please open
> and fill an issue directly on the Damned Lies project [3].
>
> All language teams that sill use @gnome.org mailing lists should update
> their teams configurations on Damned Lies in order to move to any other
> mailing list to keep tracking of team announcements.
>
> We are available for any question on element.gnome.org [4] under the
> #i18n channel.
>
> [0] :
>
> https://discourse.gnome.org/t/announcement-upcoming-changes-to-gnomes-mail-infrastructure/11568
> [1] : https://gitlab.gnome.org/Teams/Translation/Coordination
> [2] : https://discourse.gnome.org
> [3] : https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues
> [4] : https://gnome.element.io
>
> Regards,
> --
> Guillaume Bernard
>
> GNOME Foundation − https://www.gnome.org
> Association Rochelug − https://www.rochelug.org
> ___
> 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: [evolution] String freeze break plea for gnome-43 branch

[Daniel Mustieles García via gnome-i18n]

Yes sorry, I meant 2/2

El jue., 22 sept. 2022 16:51, Milan Crha via gnome-i18n <
gnome-i18n@gnome.org> escribió:

> On Thu, 2022-09-22 at 15:28 +0200, Daniel Mustieles García wrote:
> > 1/2 from i18n
>
> Hi,
> I guess it's meant to be 2/2, as Alexandre gave the first one, thus
> I'll commit the change shortly. Thank you both.
> Bye,
> Milan
>
> ___
> 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: [evolution] String freeze break plea for gnome-43 branch

[Daniel Mustieles García via gnome-i18n]

1/2 from i18n

Regards


El jue, 22 sept 2022 a las 12:53, Alexandre Franke ()
escribió:

> On Thu, Sep 22, 2022 at 12:41 PM Milan Crha via gnome-i18n
>  wrote:
> > > I suppose the other new strings about icon size in the commit are not
> > > going to be backported.
> >
> > I thought of using both options, to have 1:1 correspondence of the
> > change between the stable and the development branch, but yes, I can
> > skip it.
>
> The other two strings are fine and don’t add that much, so I’m fine
> with extending the exception to them.
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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: Freeze break request for gnome-shell

[Daniel Mustieles García via gnome-i18n]

2/2 from i18n

Thanks

El mié., 14 sept. 2022 19:26, Piotr Drąg via gnome-i18n <
gnome-i18n@gnome.org> escribió:

> śr., 14 wrz 2022 o 14:53 Florian Müllner via gnome-i18n
>  napisał(a):
> >
> > Hey,
> >
> > I'd like to request a freeze break for
> >
> > https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2485
> >
> > It adds context to an existing translation as requested by Alexandre.
> >
> > Besides approval, I'd also appreciate feedback that the added context
> > is actually helpful :-)
> >
>
> It is helpful, and here is 1/2 from i18n. :)
>
>
> --
> Piotr Drąg
> ___
> 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: Freeze break request for gnome shell

[Daniel Mustieles García via gnome-i18n]

2/2 from i18n.

Thanks!

El lun, 5 sept 2022 a las 10:22, Alexandre Franke ()
escribió:

> On Sat, Sep 3, 2022 at 7:09 PM Florian Müllner 
> wrote:
> > https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2467
> >
> > It adds an ellipsis to a menu item that should have it according to the
> HIG.
>
> Trivial enough. 1/2 from i18n.
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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 requests

[Daniel Mustieles García via gnome-i18n]

1/2 from i18n

Regards 

El vie., 2 sept. 2022 21:36, Carlos Garnacho  escribió:

> On Fri, Sep 2, 2022 at 9:05 PM Carlos Garnacho  wrote:
> >
> > Hello translators!,
> >
> > There are two merge requests (unrelated between them) that add some
> > new strings, and would be nice to get for GNOME 43:
> >
> > -
> https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/merge_requests/57
> > adds speciific settings for pointing sticks (the red knob in the
> > middle of lenovo laptops)
> >
> > -
> https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/295
> > adds notifications about applications being closed due to OOM
>
> Oops, make it three:
>
>
> https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/merge_requests/58
> ,
> containing more settings for missing libinput features.
>
> Cheers,
>   Carlos
>
> >
> > Each contains a small number of new translatable strings, it would be
> > nice to get your approvals to get this small niceties ready before
> > GNOME 43 :).
> >
> > Cheers,
> >   Carlos
> ___
> 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-control-center 42.1

[Daniel Mustieles García via gnome-i18n]

Never mind! ;-)

El jue, 7 abr 2022 a las 13:44, Claude Paroz ()
escribió:

> Le 07.04.22 à 13:43, Claude Paroz a écrit :
> >> Easy fix for translators and two weeks before the release should be
> >> plenty of time for it. Here’s approval 1/2 from i18n.
> >
> > 2/2 from i18n.
> >
> > Claude
>
> Sorry Daniel I missed your mail, then  3/2 :-)
>
> ___
> 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-control-center 42.1

[Daniel Mustieles García via gnome-i18n]

2/2 from i18n

Thanks!

El jue, 7 abr 2022 a las 11:58, Alexandre Franke ()
escribió:

> On Thu, Apr 7, 2022 at 7:52 AM Sebastian Keller via gnome-i18n
>  wrote:
> > Hi all,
>
> Hi,
>
> > I would like to ask for string freeze break approval for
> > gnome-control-center 42.1.
> >
> > There was a typo in one of the strings used in the dropdown menu under
> > `Privacy->Screen Lock->Automatic Screen Lock Delay` causing the
> > 5 minutes setting to wrongly be displayed as "3 minutes". In addition
> > to being wrong this also makes it difficult to distinguish from the
> > actual 3 minutes setting. Fixing this requires changing "3 minutes" to
> > "5 minutes".
>
> Easy fix for translators and two weeks before the release should be
> plenty of time for it. Here’s approval 1/2 from i18n.
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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: GNOME Boxes has changed its default development branch name to "main"

[Daniel Mustieles García via gnome-i18n]

Change applied in DL ;-)

Thanks!

El mar, 29 mar 2022 a las 10:55, Felipe Borges ()
escribió:

> Hi,
>
> This is a notification that GNOME Boxes has renamed its git default
> development branch to "main".
>
> It is of my understanding that tools such as Damned Lies
> (l10n.gnome.org) might need manual intervention to handle this.
>
> Cheers,
> Felipe Borges.
> ___
> 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: Next steps for Fractal

[Daniel Mustieles García via gnome-i18n]

Hi Alexandre,

It's ok for me to copy the old PO files to avoid repeating translations
already done in the past.

Many thanks for asking us about this, I think your proposal makes sense and
it's a good idea to do it.

Regards


El lun, 28 mar 2022 a las 18:47, Alexandre Franke ()
escribió:

> Hello,
>
> CCing Julian, co-maintainer of the Fractal
>
> As some of you may know, a rewrite of Fractal has been happening for a
> while now. The master branch was mostly inactive while the rewrite was
> happening on the fractal-next branch. The application was not yet
> usable, we didn’t even offer a nightly flatpak, and the pace of
> changes was such that it didn’t make sense to put it on Damned lies
> yet. We are now about to change that.
>
> `master` will be renamed to `legacy` and `fractal-next` will be
> renamed to `main`. `main` will, as the name states, become the main
> branch. A nightly flatpak will be provided through the GNOME apps
> nightly repository, replacing the current nightly built from `master`.
> The application is not advanced enough to be considered beta, we are
> not replacing the beta and stable builds from flathub. This is still
> in development and we are not freezing strings yet, but we’ve reached
> a point where strings are going to be moving a lot less and it makes
> sense to start translating. I’ll announce when the change happens so
> we can do the switcheroo on DL.
>
> That’s for the heads up to translators. Now the question that came up
> when planning this is whether we could bring back the old translations
> to provide a base for translators, so they don’t have to start from
> scratch if the old version was already translated. I am the first one
> to say that developers should stay away from po files, but in this
> case… I don’t know. Can we just copy over files from the old `po`
> directory` into the new one? We aren’t going to “touch” the files and
> try any magic, merging, or replacement. This would be a simple
> copy-paste of the files. I think that is the same thing we’ve been
> doing in the past for instance for release notes. Does that work here?
>
> Cheers,
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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: Please add 42 release-notes

[Daniel Mustieles García via gnome-i18n]

Hi Rafael

There is no need to have a single "po" folder. If you see libgweather, for
example, it has two folders: po and po-locations.

As Alexandre has said it might be something related with the method used to
generate the pot file in the repo.

I hope we can solve this soon.

Regards

El dom, 27 mar 2022 a las 12:36, Rafael Fontenelle ()
escribió:

> Hi Daniel,
>
> I see that there are 2 po folders ("po-42" and "po-homepage"), and I think
> Damned Lies looks for "po" directory [1]. 樂
>
> [1]
> https://gitlab.gnome.org/Infrastructure/damned-lies/-/blob/master/stats/management/commands/compile-trans.py#L23
>
> Rafael
>
> Em dom, 27 de mar de 2022 06:20, Daniel Mustieles García <
> daniel.mustie...@gmail.com> escreveu:
>
>> I'm trying to add it to DL but stats are not shown... don't know why this
>> happens.
>>
>> Could someone take a look into this? If I've done something wrong please
>> excuse me, just tried to help.
>>
>> Thanks in advance
>>
>> El sáb, 26 mar 2022 a las 1:42, Rafael Fontenelle ()
>> escribió:
>>
>>> I'd love to see it in Damned Lies. Can the i18n coordinators consider
>>> this?
>>>
>>> Rafael Fontenelle
>>>
>>> On Wed, Mar 23, 2022 at 11:07 AM Sophie Herold  wrote:
>>>
 Hey!

 I created an emergency-solution to have translations for the release
 notes. The strings are now frozen as well.

 The release notes are at
 https://gitlab.gnome.org/Teams/Design/release-notes

 - po-homepage contains general homepage strings
 - po-42 containts the strings for the 42 release notes

 Can someone add this to damned lies?

 The new page is available at

 https://release.gnome.org/

 Best,
 Sophie


 ___
 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
>>>
>>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Please add 42 release-notes

[Daniel Mustieles García via gnome-i18n]

I'm trying to add it to DL but stats are not shown... don't know why this
happens.

Could someone take a look into this? If I've done something wrong please
excuse me, just tried to help.

Thanks in advance

El sáb, 26 mar 2022 a las 1:42, Rafael Fontenelle ()
escribió:

> I'd love to see it in Damned Lies. Can the i18n coordinators consider this?
>
> Rafael Fontenelle
>
> On Wed, Mar 23, 2022 at 11:07 AM Sophie Herold  wrote:
>
>> Hey!
>>
>> I created an emergency-solution to have translations for the release
>> notes. The strings are now frozen as well.
>>
>> The release notes are at
>> https://gitlab.gnome.org/Teams/Design/release-notes
>>
>> - po-homepage contains general homepage strings
>> - po-42 containts the strings for the 42 release notes
>>
>> Can someone add this to damned lies?
>>
>> The new page is available at
>>
>> https://release.gnome.org/
>>
>> Best,
>> Sophie
>>
>>
>> ___
>> 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
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: [DL]String additions to 'seahorse.master'

[Daniel Mustieles García via gnome-i18n]

No problem from my side, here is the second approval from i18n

Thanks!

El vie., 25 mar. 2022 17:33, Alexandre Franke  escribió:

> Hey,
>
> tl;dr: can we get a second approval from another i18n coordinator,
> please? Details follow.
>
> On Tue, Mar 8, 2022 at 9:36 AM Alexandre Franke  wrote:
> > Niels,
> >
> > By merging https://gitlab.gnome.org/GNOME/seahorse/-/merge_requests/196
> > now, you broke the String Freeze. I don’t see this change as essential
> > for 42.0, but it’s small enough that I’d be inclined to approve it for
> > 42.1. Please revert it for now, and we’ll see if you get a second
> > approval to merge it **after** you release 42.0.
> >
> > On Mon, Mar 7, 2022 at 11:41 PM GNOME Status Pages 
> wrote:
> > > There have been following string additions to module 'seahorse.master':
> > >
> > > + "keyring;encryption;security;sign;ssh;gpg;pgp;"
>
> The bad news is that the revert didn’t happen, and many translations
> have been committed since. Niels reached out to me and apologised for
> that (which we appreciate!). He also didn’t make a 42 release yet, and
> considering there aren’t that many changes it’s not urgent as far as
> he’s concerned. I offered to not do the revert and do a 42 release
> that coincides with GNOME 42.1, which is basically equivalent to my
> initial proposal now. A second approval from i18n is needed.
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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: Retroactive string break request

[Daniel Mustieles García via gnome-i18n]

2/2 from i18n

Regards

El vie, 4 mar 2022 a las 15:38, Alexandre Franke ()
escribió:

> On Fri, Mar 4, 2022 at 2:57 PM Marcus Lundblad via gnome-i18n
>  wrote:
> > Hi!
>
> Hi,
>
> > I'm sorry, I added a last-minute change in Maps saving the state of
> > showing the scale (we already had a keyboard shortcut to toggle showing
> > the map scale, but it was always shown when starting). I completely
> > forgot that adding the new gschema adds new strings for i18n.
>
> Still early, only a couple of simple strings, and as mentionned we
> already have a fair amount of translations which would be a shame to
> lose. 1/2 from i18n.
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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-control-center!1684

[Daniel Mustieles García via gnome-i18n]

1/2 from i18n

Un abrazo!

El jue, 3 mar 2022 a las 16:53, Carlos Garnacho ()
escribió:

> Dear translators,
>
> https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1684 has
> a fix for a little mishap that happened during the GTK4 port of
> gnome-control-center. Some UI and strings were mistakenly removed,
> just to be added back (with a slight change in one of the strings, a
> missing closing period).
>
> Since this technically accounts to a string break, it would be nice to
> get your votes to have this small issue fixed before release.
>
> Cheers,
>   Carlos
> ___
> 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 for gnome-software for 42.0

[Daniel Mustieles García via gnome-i18n]

1/2 from i18n

Regards

El mié, 2 mar 2022 a las 11:08, Philip Withnall ()
escribió:

> Hi all,
>
> Can we have a string freeze break for gnome-software to add more
> information about privacy policy to one string shown to users when they
> are writing a review of an app?
>
> The change is here:
> https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/1229
>
> Without this change, it’s not clear to users that their full name will
> be shown next to the review. They currently have to actually read the
> privacy policy to know that. (Nobody reads privacy policies.)
>
> Philip
> ___
> 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: [DL]String additions to 'totem.master'

[Daniel Mustieles García via gnome-i18n]

Why do you keep sending this kind of messages?

We do ont want to know this, please do not send every update for your
translations you do, that's not relevant for other translators.

You've been told several times to not do that but you keep doing it. What's
happening?

Once again.. please stop.

Thanks

El lun, 7 feb 2022 a las 19:26, Luna Jernberg via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> Hey!
>
> Done took some extra days as it was FOSDEM 2022 Online last week
>
> On Thu, Feb 3, 2022 at 6:20 PM GNOME Status Pages 
> wrote:
>
>> This is an automatic notification from status generation scripts on:
>> https://l10n.gnome.org.
>>
>> There have been following string additions to module 'totem.master':
>>
>> + "@APPLICATION_NAME@"
>> + "Videos Preview"
>>
>> Note that this doesn't directly indicate a string freeze break, but it
>> might be worth investigating.
>> https://gitlab.gnome.org/GNOME/totem/commits/master
>> ___
>> 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
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: POT file is obsolete. How do I generate a new one?

[Daniel Mustieles García via gnome-i18n]

It's a button in Damned Lies, maybe only available for team coordinators
(not 100% about this)

El jue, 28 oct 2021 a las 14:27, Alexander Shopov ()
escribió:

> > I forced the update
> Can you also share the command to regenerate the pot-file, please?
> Kind regards:
> al_shopov
>
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: POT file is obsolete. How do I generate a new one?

[Daniel Mustieles García via gnome-i18n]

Now it should be up-to-date in Damned Lies.

I forced the update of the stats for that module. Please check it's ok.

Regards

El jue, 28 oct 2021 a las 12:47, Davide Ferracin via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> Hi all,
> I recently started translating the Health app. In the meantime a new
> version was published, but the POT file on l10n.gnome.org [1] still
> refers to the previous version, so if I published my translation it would
> already be obsolete (also, I would not be able to test it locally). Since I
> do not know how long it will get to see the updated POT file on the
> website, I tried to generate one manually from the app source code using
> xgettext, but it seems it does not recognise Rust, which the app is written
> in, as a language and a lot of translatable strings are missing as a
> consequence. I did not find anything that could help me in the online
> translation guides; what should I do now?
>
> [1] https://l10n.gnome.org/vertimus/health/master/po/it/
>
> Cheers
> --
> Davide Ferracin
> ___
> 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: New genius release to happen

[Daniel Mustieles García via gnome-i18n]

There is a problem with the help's PO file:

xml2po -o /git/genius/help/C/genius-help.pot -e
C/legal.xml C/genius.xml
Traceback (most recent call last):
  File "/usr/bin/xml2po", line 191, in
main(sys.argv[1:])
  File "/usr/bin/xml2po", line 160, in main
xml2po_main = Main(default_mode, operation, output, options)
  File "/usr/lib/python3.6/site-packages/xml2po/__init__.py", line
559, in __init__
self.out = file(output, 'w')
NameError: name 'file' is not defined

Could you please review it?

Thanks!


El dom, 17 oct 2021 a las 23:52, Jiri Lebl via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> Just a heads up, I plan to make a new genius release by end of next week
> (thursday or friday perhaps).  Not too many string changes, but just a
> heads up.
>
> Best,
>
> Jiri
>
> --
> Jiri (George) Lebl, http://math.okstate.edu/people/lebl/ or
> http://www.jirka.org/
> ___
> 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: Release notes translation

[Daniel Mustieles García via gnome-i18n]

Done, thanks!

El lun, 27 sept 2021 a las 12:59, Alexandre Franke ()
escribió:

> Please comment on the issue. The people working on this are most
> likely not reading it here.
>
> On Mon, Sep 27, 2021 at 9:22 AM Daniel Mustieles García
>  wrote:
> >
> > A quick search in stackoverflow returned this:
> >
> >
> https://stackoverflow.com/questions/53468548/detect-language-with-javascript-and-redirect-to-another-page
> >
> > With a very simple modification in the language-based redirection it
> could do the trick
> >
> > Hope it helps :-)
> >
> > Regards
> >
> > El vie, 24 sept 2021 a las 10:49, Alexandre Franke ()
> escribió:
> >>
> >> On Fri, Sep 24, 2021 at 9:16 AM Rafael Fontenelle 
> wrote:
> >> > It doesn't seem to have language selector or browser content
> negotiation for switching languages manually or automatically, but the
> translation is there. It is a new implementation, to be improved.
> >>
> >> Help with that is welcome:
> >> https://gitlab.gnome.org/Teams/Engagement/release-notes/-/issues/34
> >>
> >> --
> >> Alexandre Franke
> >> GNOME Hacker
> >> ___
> >> gnome-i18n mailing list
> >> gnome-i18n@gnome.org
> >> https://mail.gnome.org/mailman/listinfo/gnome-i18n
>
>
>
> --
> Alexandre Franke
> GNOME Hacker
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Release notes translation

[Daniel Mustieles García via gnome-i18n]

Here is a very simplified implementation of the previous suggestion:


window.onload = function() {

var ln = window.navigator.language||navigator.browserLanguage;
window.location.href = 'https://help.gnome.org/misc/release-notes/41.0/'
+ ln;

}


Maybe someone with more experience in JS could review/check it, but I think
it's a first step.

El lun, 27 sept 2021 a las 9:22, Daniel Mustieles García (<
daniel.mustie...@gmail.com>) escribió:

> A quick search in stackoverflow returned this:
>
>
> https://stackoverflow.com/questions/53468548/detect-language-with-javascript-and-redirect-to-another-page
>
> With a very simple modification in the language-based redirection it could
> do the trick
>
> Hope it helps :-)
>
> Regards
>
> El vie, 24 sept 2021 a las 10:49, Alexandre Franke ()
> escribió:
>
>> On Fri, Sep 24, 2021 at 9:16 AM Rafael Fontenelle 
>> wrote:
>> > It doesn't seem to have language selector or browser content
>> negotiation for switching languages manually or automatically, but the
>> translation is there. It is a new implementation, to be improved.
>>
>> Help with that is welcome:
>> https://gitlab.gnome.org/Teams/Engagement/release-notes/-/issues/34
>>
>> --
>> Alexandre Franke
>> GNOME Hacker
>> ___
>> 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: Release notes translation

[Daniel Mustieles García via gnome-i18n]

A quick search in stackoverflow returned this:

https://stackoverflow.com/questions/53468548/detect-language-with-javascript-and-redirect-to-another-page

With a very simple modification in the language-based redirection it could
do the trick

Hope it helps :-)

Regards

El vie, 24 sept 2021 a las 10:49, Alexandre Franke ()
escribió:

> On Fri, Sep 24, 2021 at 9:16 AM Rafael Fontenelle 
> wrote:
> > It doesn't seem to have language selector or browser content negotiation
> for switching languages manually or automatically, but the translation is
> there. It is a new implementation, to be improved.
>
> Help with that is welcome:
> https://gitlab.gnome.org/Teams/Engagement/release-notes/-/issues/34
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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 for gnome-software for 41.0

[Daniel Mustieles García via gnome-i18n]

2/2 from i18n.

Thanks!

El jue, 16 sept 2021 a las 14:00, Alexandre Franke ()
escribió:

> On Thu, Sep 16, 2021 at 1:45 PM Philip Withnall 
> wrote:
> > Yeah, I believe this can’t wait until 41.1. 
>
> 1/2 from i18n then, hoping that you merge ASAP and release 41.0 as
> late as possible.
>
> Please do report when the strings are in.
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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: evolution: String freeze break plea

[Daniel Mustieles García via gnome-i18n]

2/2

Regards

El jue, 9 sept 2021 a las 11:08, Alexandre Franke ()
escribió:

> On Tue, Aug 31, 2021 at 11:45 AM Milan Crha via gnome-i18n
>  wrote:
> > Hi,
> > there had been filled [1] while I've been gone and I've got to it only
> > yesterday. I'd like to add a context to one of the occurrences of the
> > "Title" word, thus it can be properly translated. While it might not be
> > a problem for the language the reporter translates to, it can be a
> > problem for other languages, thus I guess it makes sense to do the
> > change now, rather than in the next series.
> > Thanks and bye,
> > Milan
> >
> > [1] https://gitlab.gnome.org/GNOME/evolution/-/issues/1596
>
> Useful and small change. 1/2 from i18n.
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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 exception for user-accounts/parental-controls in GNOME Settings

[Daniel Mustieles García via gnome-i18n]

2/2

Regards

El mié, 8 sept 2021 a las 9:28, Alexandre Franke ()
escribió:

> Hi,
>
> On Tue, Sep 7, 2021 at 9:59 AM Felipe Borges 
> wrote:
> > This way, we need the User Accounts desktop file to contain keywords
> > related to parental controls, so the User Accounts panel shows up in
> > Shell searches. The merge-request for this is at
> >
> https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1053
>
> The string changes from
> "Login;Name;Fingerprint;Avatar;Logo;Face;Password;"
> to
> "Login;Name;Fingerprint;Avatar;Logo;Face;Password;Parental
> Controls;Screen Time;App Restrictions;Web Restrictions;Usage;Usage
> Limit;Kid;Child;"
>
> Please include this directly in the mail next time. The easier you
> make it to accept your request, the more likely you are to get a
> positive response. I really shouldn’t have had to leave my email
> client for this.
>
> Approval 1/2 from i18n.
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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: [DL]String additions to 'polari.main'

[Daniel Mustieles García via gnome-i18n]

2/2

Regards

El mar, 7 sept 2021 a las 15:52, Florian Müllner ()
escribió:

>
>
> On Tue, Sep 7 2021 at 15:49:40 +0200, Alexandre Franke
>  wrote:
> >
> > that Florian will confirm he’s requesting in reply to this email.
> > :-)
>
>
> Confirmed :-)
>
>
> ___
> 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: Problems with D-L

[Daniel Mustieles García via gnome-i18n]

I'm also having problems to commit that module.

@Marek Černocký  have you been able to use your git
account? I'm also having problems with that, cannot use my ssh key to clone
repos or push commits (tried with two different computers)

Regards

El mar, 7 sept 2021 a las 14:34, Marek Černocký () escribió:

> Hi,
>
> I'm not able to commit the following translation:
> https://l10n.gnome.org/vertimus/gnome-tour/master/po/cs/
> It ends with the message:
> 504 Gateway Time-out
> So I have pushed it directly with git, but D-L doesn't reflect the
> changes and still shows the untranslated strings.
>
> I also need fix global statistics for Czech GNOME 41 documentation. It
> shows 288 untranslated strings but it should be 285.
>
> Thanks
> Marek
>
> ___
> 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 exception request for gnome-control-center

[Daniel Mustieles García via gnome-i18n]

1/2 from i18n

Regards

El lun, 6 sept 2021 a las 15:54, Felipe Borges ()
escribió:

> Hi,
>
> The Keyboard settings user interface in GNOME Settings has changed and
> we forgot to update the panel's desktop file.
>
> This merge-request addresses this
> https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1051
>
> Cheers,
> Felipe.
> ___
> 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: [DL]String additions to 'gnome-control-center.master'

[Daniel Mustieles García via gnome-i18n]

2/2 from i18n

Regards

El lun, 6 sept 2021 a las 7:52, Alexandre Franke ()
escribió:

> On Mon, Sep 6, 2021 at 7:48 AM Alexandre Franke  wrote:
> > Here is approval 1/2 from i18n, even if the maintainer forgot to ask
> > (or even to warn us).
>
> And I just saw that there was an announcement email. Still not a
> warning, but at least that’s something. Still requires a second
> approval.
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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: gnome-software string freeze break approval plea

[Daniel Mustieles García via gnome-i18n]

Oh. I thought only adding new strings was a break, sorry for the mistake.

Of course I give my vote, 2/2 from i18n.

Thanks for the explanation!

El vie, 3 sept 2021 a las 8:43, Claude Paroz ()
escribió:

> Le 03.09.21 à 08:34, Daniel Mustieles García via gnome-i18n a écrit :
> > Technically this is not a freeze break since no new strings are added so
> > you can go ahead with it.
>
> Wow, wow, wow :-) That's not true. Changing a string is also a break!
>
> I would tend to add my approval, though. 1/2
>
> Claude
> --
> www.2xlibre.net
> ___
> 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: gnome-software string freeze break approval plea

[Daniel Mustieles García via gnome-i18n]

Hi Milan,

Technically this is not a freeze break since no new strings are added so
you can go ahead with it.

Many thanks for telling us about this change :-)

Regards

El vie, 3 sept 2021 a las 8:16, Milan Crha via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> Hi,
> there had been found a typo in a translated string:
> https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/946
>
> -   g_dngettext (..., "%u reviews total", "%u reviews total", ...
> +   g_dngettext (..., "%u review total", "%u reviews total", ...
>
> It would be nice to have it fixed before the .rc release, though I'm
> afraid I cannot do it without the approval, thus I'm asking here.
> Thanks and bye,
> Milan
>
> ___
> 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 for GNOME Tour

[Daniel Mustieles García via gnome-i18n]

2/2 from i18n but, please, next time tell us which strings are being added.

Thanks

El mié, 1 sept 2021 a las 10:04, Alexandre Franke ()
escribió:

> On Wed, Sep 1, 2021 at 9:08 AM Jakub Steiner via gnome-i18n
>  wrote:
> > Hi,
>
> Hi,
>
> > I'd like to request a string freeze break for GNOME Tour 41, which
> > didn't land in time.
>
> So my colleague doesn’t have click on that link, then click on another
> link to the actual MR, then click on the changes tab, then read
> through and hunt for actual relevant changes before they can give you
> what you’re asking for, here is a list of the affected strings.
>
> "Learn about new and essential features in {} {}.", becomes "Learn
> about the key features in {} {}.",
>
> "Press Activities to see open windows and apps." becomes "Press the
> Super key to see open windows and apps."
>
> "Just Type to Search" and "Type in the overview to search. Launch
> apps, find things." have been added.
>
> "Easily organize windows with the new workspaces view." becomes
> "Easily organize windows with the workspaces view."
>
> "That's it! We hope that you enjoy {} {}." becomes "That's it. Have a nice
> day!"
>
>
> That’s a bit more changes than I’d like to see during the freeze, but
> it’s still early and I got the impression that the overall amount of
> strings for GNOME this cycle is on the lower side of the range.
>
> i18n approval 1/2.
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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: gnome-software string freeze break approval plea

[Daniel Mustieles García via gnome-i18n]

No problem, 1/2 from i18n ;-)

regards

El lun, 30 ago 2021 a las 9:32, Milan Crha via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> Hi,
> this is a late string freeze break approval plea for gnome-software.
>
> It's late, because the change already landed:
>
> https://gitlab.gnome.org/GNOME/gnome-software/-/commit/fb27aa9fbdbba86ed7c3873fe281b5606dc9b307
>
> It received the UI freeze break approval, but before I've got to the
> review the string freeze took into effect. I confused the two and
> committed the change before asking freeze break/announcing the new
> strings. I'm sorry about that.
> Bye,
> Milan
>
> ___
> 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: libadwaita showing as if there were no translatable strings

[Daniel Mustieles García via gnome-i18n]

Great! :-)

maybe you need to be logged into DL or be a team coordinator, but I don't
know, sorry

Regards

El mar, 17 ago 2021 a las 12:59, Philipp Kiemle ()
escribió:

> Hello!
> Yes, it is indeed fixed now. Thanks!
> Out of curiosity, I don't see the button you mentioned... Is this
> something I'd need special rights for?
> Philipp
>
> Am Di., 17. Aug. 2021 um 12:51 Uhr schrieb Daniel Mustieles García <
> daniel.mustie...@gmail.com>:
>
>> Hi Philipp,
>>
>> It should be fixed now... at least now I see stats ok.
>>
>> I've just forced the update of the module's branch, using the buttow with
>> two arrows in [1].
>>
>> Hope this helps
>>
>> Regards
>>
>> [1] https://l10n.gnome.org/module/libadwaita/
>>
>> El mar, 17 ago 2021 a las 12:15, Philipp Kiemle via gnome-i18n (<
>> gnome-i18n@gnome.org>) escribió:
>>
>>> Hello all,
>>> In DL, the libadwaita package seems to have no translatable strings at
>>> all [1]. However, when clicking on the Download button, it downloads a po
>>> file that contains already translated strings.
>>>
>>> At libadwaita's module page [2], I can see that other languages haven't
>>> got this problem - their translation status is displayed correctly. Also,
>>> their po files claim to be a "translation for libhandy" (line 1 in the po
>>> file), which was a former name of libadwaita, if I'm not mistaken.
>>> Only the German translation says "German translation for libadwaita" -
>>> is this the cause?
>>>
>>> Is this the right place to report this issue? I am happy to open an
>>> issue in libadwaita's Gitlab repo, if it is necessary.
>>> If not, kindly direct me to the correct place. Thanks!
>>> Philipp Kiemle
>>>
>>> [1] https://l10n.gnome.org/vertimus/libadwaita/main/po/de/
>>> [2] https://l10n.gnome.org/module/libadwaita/
>>> ___
>>> 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: libadwaita showing as if there were no translatable strings

[Daniel Mustieles García via gnome-i18n]

Hi Philipp,

It should be fixed now... at least now I see stats ok.

I've just forced the update of the module's branch, using the buttow with
two arrows in [1].

Hope this helps

Regards

[1] https://l10n.gnome.org/module/libadwaita/

El mar, 17 ago 2021 a las 12:15, Philipp Kiemle via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> Hello all,
> In DL, the libadwaita package seems to have no translatable strings at all
> [1]. However, when clicking on the Download button, it downloads a po file
> that contains already translated strings.
>
> At libadwaita's module page [2], I can see that other languages haven't
> got this problem - their translation status is displayed correctly. Also,
> their po files claim to be a "translation for libhandy" (line 1 in the po
> file), which was a former name of libadwaita, if I'm not mistaken.
> Only the German translation says "German translation for libadwaita" - is
> this the cause?
>
> Is this the right place to report this issue? I am happy to open an issue
> in libadwaita's Gitlab repo, if it is necessary.
> If not, kindly direct me to the correct place. Thanks!
> Philipp Kiemle
>
> [1] https://l10n.gnome.org/vertimus/libadwaita/main/po/de/
> [2] https://l10n.gnome.org/module/libadwaita/
> ___
> 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: New default branch for Devhelp

[Daniel Mustieles García via gnome-i18n]

Works perfectly.

Many thanks!

El mié, 14 jul 2021 a las 12:47, Emmanuele Bassi ()
escribió:

> Please try now. I changed the branch protection policy.
>
> Ciao,
>  Emmanuele.
>
> On Wed, 14 Jul 2021 at 09:15, Daniel Mustieles García <
> daniel.mustie...@gmail.com> wrote:
>
>> Hi all,
>>
>> The new branch doesn't allow pushing commits:
>>
>> [Errno 1] Command: "['git', 'push', 'origin', 'main']", Error: Warning:
>> Permanently added 'gitlab.gnome.org,172.31.2.39' (ECDSA) to the list of
>> known hosts. remote: GitLab: You are not allowed to push code to protected
>> branches on this project. To gitlab.gnome.org:GNOME/devhelp.git !
>> [remote rejected] main -> main (pre-receive hook declined) error: failed to
>> push some refs to 'gitlab.gnome.org:GNOME/devhelp.git' »
>>
>> Could you please review?
>>
>> Thanks in advance
>>
>> El mié, 14 jul 2021 a las 9:33, Claude Paroz ()
>> escribió:
>>
>>> Le 10.07.21 à 17:02, Emmanuele Bassi via gnome-i18n a écrit :
>>> > Hi all;
>>> >
>>> > I have just changed the default development branch of Devhelp from
>>> > "master" to "main".
>>> >
>>> > The "master" branch still exists, while we update the various bits of
>>> > infrastructure that reference it, but any translations of the
>>> > development version of Devhelp should happen on the "main" branch from
>>> > now on.
>>> >
>>> > After the beta release scheduled for August 14th, I will delete the
>>> > "master" branch from the repository.
>>>
>>> Thanks for the notice, l10n.gnome.org updated accordingly.
>>>
>>> Claude
>>> --
>>> www.2xlibre.net
>>> ___
>>> gnome-i18n mailing list
>>> gnome-i18n@gnome.org
>>> https://mail.gnome.org/mailman/listinfo/gnome-i18n
>>>
>>
>
> --
> https://www.bassi.io
> [@] ebassi [@gmail.com]
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: New default branch for Devhelp

[Daniel Mustieles García via gnome-i18n]

Hi all,

The new branch doesn't allow pushing commits:

[Errno 1] Command: "['git', 'push', 'origin', 'main']", Error: Warning:
Permanently added 'gitlab.gnome.org,172.31.2.39' (ECDSA) to the list of
known hosts. remote: GitLab: You are not allowed to push code to protected
branches on this project. To gitlab.gnome.org:GNOME/devhelp.git ! [remote
rejected] main -> main (pre-receive hook declined) error: failed to push
some refs to 'gitlab.gnome.org:GNOME/devhelp.git' »

Could you please review?

Thanks in advance

El mié, 14 jul 2021 a las 9:33, Claude Paroz ()
escribió:

> Le 10.07.21 à 17:02, Emmanuele Bassi via gnome-i18n a écrit :
> > Hi all;
> >
> > I have just changed the default development branch of Devhelp from
> > "master" to "main".
> >
> > The "master" branch still exists, while we update the various bits of
> > infrastructure that reference it, but any translations of the
> > development version of Devhelp should happen on the "main" branch from
> > now on.
> >
> > After the beta release scheduled for August 14th, I will delete the
> > "master" branch from the repository.
>
> Thanks for the notice, l10n.gnome.org updated accordingly.
>
> Claude
> --
> www.2xlibre.net
> ___
> 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: Build error

[Daniel Mustieles García via gnome-i18n]

Look at this string:

msgid "Purge trash  temporary files"
msgstr "Prullenbak legen & tijdelijke bestanden definitief verwijderen"

It might be the & what it's breaking the build.

I don't know what gtml is but it doesn't seem to the same as gtxml... to
make gtxml work you have to download PyG3t (see previous email to get the
link). It very easy to compile and install it, but if you get stuck I could
help you with it.

Hope this helps.

Regards

El jue, 20 may 2021 a las 10:04, hannie () escribió:

> Sorry guys, but the errors are not yet fixed. I fixed the 3 tag errors
> André mentioned here, but I still get this build error. And uploading
> Daniel's attached file did not work either.
> I also tried Daniel's gtxml -c  command, but it does not work
> in Ubuntu. I will have to do further reading to try and get gtml working.
> Hannie
>
> Op 18-05-2021 om 10:52 schreef Andre Klapper via gnome-i18n:
> > On Tue, 2021-05-18 at 10:20 +0200, Hannie Dumoleyn wrote:
> >> Entity: line 1: parser error : Premature end of data in tag p line 1
> >>
> >> Can anyone help?
> > "Open het Systeemmenu
> > aan de rechterzijde van de bovenbalk." and "Kies welk apparaat,
> > Wifi" and "Energie" are broken markup.
> >
> > Cheers,
> > andre
> > --
> > Andre Klapper  |  ak...@gmx.net
> > https://blogs.gnome.org/aklapper/
> >
> >
> > ___
> > 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
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: String freeze request for mutter

[Daniel Mustieles García via gnome-i18n]

1/2 from i18n

Regards

El mié., 14 abr. 2021 23:15, Florian Müllner  escribió:

> Hey y'all,
>
> I'd like to request a string freeze request for the upcoming 40.1
> release:
>
>   https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1814
>
> The strings in question are descriptions of keyboard shortcuts that can
> be configured in Settings' Keyboard panel, namely the shortcuts for
> navigating between vertical workspaces.
>
> Those descriptions existed previously, but were removed for GNOME 40
> when we switched to a horizontal workspace layout. That turned out to
> be a problem for users who customize the shortcuts, and want to re-use
> the same shortcuts with the new layout: The old shortcut conflicts with
> the new one, but Settings is unable to detect that conflict because it
> no longer knows about the old shortcut.
>
> For that reason the merge requests adds back the definitions for the
> old shortcuts, but tells Settings to not show them in the UI. That
> means most users will never see the string, except when they want to
> reassign one of the affected shortcuts, and Settings quotes the
> description in a warning ("j is already used for ¨Move to
> workspace above¨")
>
> Without the change users that run into the issue have to fiddle with
> the shortcut configuration on the command line (for example "gsettings
> reset org.gnome.desktop.wm.keybindings switch-to-workspace-up"). In my
> opinion that's worse than a stray untranslated string in the
> conflicting-shortcut warning.
>
> Cheers,
> Florian
>
>
> ___
> 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: evolution & evolution-data-server string & UI freeze break approval plea

[Daniel Mustieles García via gnome-i18n]

2/2 from i18n

Regards

El mar, 30 mar 2021 a las 19:36, Milan Crha via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> On Thu, 2021-03-18 at 15:48 +0100, Alexandre Franke wrote:
> > > I'd like to ask for a string and UI freeze break approval for the
> > > 3.40.1
> >
> > Thanks a lot for the detailed and clear explanation. 1/2 from i18n
> > for 3.40.1.
> >
>
> Hi,
> thanks Alexandre.
>
> May I ping here, in case someone else would give the second approval,
> thus the lighter (in the translatable strings) change can get into the
> gnome-40 branches, please?
>
> Thanks and bye,
> Milan
>
> ___
> 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: GNOME 40 release notes

[Daniel Mustieles García via gnome-i18n]

Sure, now it's everything shown properly.

Thanks

El mar, 30 mar 2021 a las 22:03, Andre Klapper via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> On Thu, 2021-03-25 at 08:16 +0100, Daniel Mustieles García via gnome-
> i18n wrote:
> > Spanish translation is complete but webpage still shows some strings
> > in English.
>
> Not anymore. I assume things get updated once every 24 hours.
>
> andre
> --
> Andre Klapper  |  ak...@gmx.net
> https://blogs.gnome.org/aklapper/
>
>
> ___
> 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: GNOME 40 release notes

[Daniel Mustieles García via gnome-i18n]

Hi Matthias,

Spanish translation is complete but webpage still shows some strings in
English.

Is there any way to force an update to bring up new changes?

Thanks in advance

El mar, 23 mar 2021 a las 0:19, Fran Dieguez ()
escribió:

> Thanks Matthias,
>
> Galician language is completed. This will be an awesome release. Cheers to
> all people involved.
>
> Regards,
> Fran
>
> On Mon, 22 Mar 2021 at 22:48, Matthias Clasen via gnome-i18n <
> gnome-i18n@gnome.org> wrote:
>
>> Hi translators,
>>
>> between pandemic and gnome-shell redesign, we totally dropped the ball on
>> release notes this cycle. Due to the heroic efforts of a few people, we now
>> have
>>
>> https://gitlab.gnome.org/Teams/Engagement/release-notes/-/tree/gnome-40
>>
>> which is ready for translation. The bad news is that the release is only
>> 2 days away, so you
>> basically have tomorrow to provide translations. If you can provide
>> translation on such short
>> notice, that will be greatly appreciated. If not, that is fine too.
>>
>> Thanks,
>>
>> Matthias for the release team
>> ___
>> 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
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: String freeze break for gnome-software to add context

[Daniel Mustieles García via gnome-i18n]

I agree with you so we should wait for the second approval for this request.

Regards

El vie, 5 mar 2021 a las 13:31, Alexandre Franke ()
escribió:

> On Fri, Mar 5, 2021 at 1:18 PM Daniel Mustieles García via gnome-i18n <
> gnome-i18n@gnome.org> wrote:
>
>> Sorry, I missed this email...
>>
>> Here is the 1/2 fron i18n.
>>
>> I believe Alexandre will give you the second vote, but let's wait his
>> response ;-)
>>
>
> As the reporter I’m obviously biased towards approving it… which is
> exactly why I didn’t respond. We have a pool of coordinators, it would be
> better if I wasn’t one of the two approvals, seeing as I’m basically the
> requester.
>
> --
> Alexandre Franke
> GNOME Hacker
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: String freeze break for gnome-software to add context

[Daniel Mustieles García via gnome-i18n]

Sorry, I missed this email...

Here is the 1/2 fron i18n.

I believe Alexandre will give you the second vote, but let's wait his
response ;-)

Regards

El vie, 5 mar 2021 a las 12:32, Philip Withnall ()
escribió:

> Anyone? Or is that a no?
>
> On Mon, 2021-03-01 at 16:32 +, Philip Withnall wrote:
> > Hi all,
> >
> > Can we have a string freeze break for gnome-software to add some
> > missing translation contexts please:
> > https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/639
> >
> > The changes add context to 4 instances of ‘Unknown’, and a set of
> > ‘None‘/‘Low’/‘Medium’/‘High’ strings.
> >
> > This was reported by Alexandre here:
> > https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1158
> >
> > Philip
>
>
> ___
> 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 Boxes

[Daniel Mustieles García via gnome-i18n]

2/2 from i18n

Thanks!

El lun, 1 mar 2021 a las 12:23, Alexandre Franke ()
escribió:

> On Mon, Mar 1, 2021 at 12:14 PM Felipe Borges 
> wrote:
>
>> Hi,
>>
>
> Hi,
>
> During this cycle we added support for handling a few file formats,
>> yet we forgot to update the UI label that indicates the supported
>> files. See the screenshot at
>> https://gitlab.gnome.org/GNOME/gnome-boxes/-/merge_requests/413
>>
>> I'd like to ask permission to merge
>> https://gitlab.gnome.org/GNOME/gnome-boxes/-/merge_requests/413 and
>> apologize for forgetting about this change.
>>
>
> Since it is a single string with a very simple change, and it’s very early
> in the freeze period, here is 1/2 from i18n.
>
> For my fellow coordinators, so they don’t have to check in the MR: the
> string goes from
> "Select an .iso file to install a virtual machine."
> to
> "Select a file to install a virtual machine."
>
> Felipe, next time, please mention more details about changed strings (how
> many, what changes) and provide a rationale (how bad would it be if we
> didn’t grant the exception?) so that it’s easier for us to make a decision.
>
> Cheers,
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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

Error in simple-scan

[Daniel Mustieles García via gnome-i18n]

Hi,

I've got the following error when trying to upload a translation for
simple-scan, using Damned Lies:

«[Errno 1] Command: "['git', 'push', 'origin', 'master']", Error: Warning:
Permanently added 'gitlab.gnome.org,172.31.2.39' (ECDSA) to the list of
known hosts. remote: GitLab: You are not allowed to push code to protected
branches on this project.To g...@gitlab.gnome.org:GNOME/simple-scan.git !
[remote rejected] master -> master (pre-receive hook declined) error:
failed to push some refs to 'g...@gitlab.gnome.org:GNOME/simple-scan.git' »

Could someone please review it?

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

Re: Fwd: Submit Help Translation on GNOME Terminal

[Daniel Mustieles García via gnome-i18n]

Ok, I agree with you in the procedure but there still a remaining question.
Could someone help us improving/fixing missing features in Damned Lies, so
we will not need to directly commit into git?

Adding a new language for help files should be directly resolved thought DL
and being able to upload/commit a bunch of translations would ease our work
a lot (think about 20+ PO files to be commited manually...)

We only want some useful tools to do our work, don't want to bother nor
interfere in other's tasks, but we don't have enough tools to do it.

Again, sorry for the mistake, but please hear our requests to improve our
translation tasks.

Regards

El mié., 4 nov. 2020 a las 14:12, Emmanuele Bassi ()
escribió:

> On Wed, 4 Nov 2020 at 12:51, Daniel Mustieles García via gnome-i18n <
> gnome-i18n@gnome.org> wrote:
>
>> Hi Andika,
>>
>> Yes, it seems that my commit broke some continuous build in Gitlab, so
>> Michael reverted it. To avoid wasting time, could someone indicate us how
>> to proceed?
>>
>
> To avoid wasting time, you should open a merge request against the
> project, instead of pushing directly to the main or stable branches.
> Otherwise, any breakage will be uncaught, and somebody will have to revert
> the commit.
>
> For instance:
>
>
> https://gitlab.gnome.org/GNOME/gnome-user-docs/-/commit/2486d2414a0239ad02cb54d1b28447ffdce5f4df
>
> the change was pushed to Git and the CI pipeline broke because of a
> missing file:
>
>  https://gitlab.gnome.org/GNOME/gnome-user-docs/-/jobs/970067
>
> If you had opened a merge request, instead, you would have noticed the
> missing file, and you could have amended the commit to your merge request
> branch.
>
> Another example:
>
>
> https://gitlab.gnome.org/GNOME/five-or-more/-/commit/cfde961fd479906826832e23033deba6f9f751ce
>
> Another failure:
>
>  https://gitlab.gnome.org/GNOME/five-or-more/-/jobs/970068
>
> ```
> FileNotFoundError: [Errno 2] No such file or directory:
> '/run/build/five-or-more/_flatpak_build/help/id/bug-filing.page'
> ```
>
> Again, opening a merge request would have found this issue before it hit
> the main development branch.
>
> That commit (and the similar one in iagno) ought to be reversed as well,
> but at least the games are not part of core GNOME.
>
> I don't mind to do it again (even adding the PO files in the commit) but I
>> think that's not the proper way to do things.
>>
>
> Micheal is part of the release team; the release team is empowered to
> revert any commit that breaks the continuous integration build of GNOME,
> because that continuous integration is what generates:
>
>  - the nightly and stable application flatpaks
>  - the nightly and stable run times (also used for CI in various
> applications)
>  - the release VM builds
>
> Breaking those means stalling the work of a lot of other projects.
>
> Maybe someone could review DL's way to add new languages for help or, at
>> least, grant team coordinators commit access to be able to solve this
>> issues without breaking anything (nor depend on other people)
>>
>
> The appropriate way to commit changes is to have them run through the
> per-module continuous integration. If that passes, but things still break
> when we try to build the whole of GNOME core modules and applications, then
> we can discuss about that; but if you work around the measures we have in
> place *precisely* to catch these issues, then I'm afraid you're going to
> get more commits reverted. Or the release team might simply decide to
> revoke direct commit access to localisation team coordinators, and avoid
> reverting broken commits.
>
> Ciao,
>  Emmanuele.
>
>
>> Regards
>>
>> El mié., 4 nov. 2020 a las 13:20, Andika Triwidada ()
>> escribió:
>>
>>> Hi Daniel,
>>>
>>> Thanks for your help. It seems that Michael Catanzaro revert all your
>>> modifications before I have chance to commit files. Please advice how to
>>> proceed?
>>>
>>> On Tue, Nov 3, 2020 at 4:50 PM Daniel Mustieles García <
>>> daniel.mustie...@gmail.com> wrote:
>>>
>>>> Hi Andika,
>>>>
>>>> I've added 'id' language to those modules. Please check if you can now
>>>> commit translations for them using DL.
>>>>
>>>> Let us know if you have any problem with it.
>>>>
>>>> Regards
>>>>
>>>> El dom., 1 nov. 2020 a las 2:48, Andika Triwidada ()
>>>> escribió:
>>>>
>>>>> Hello, I think this problem is well known for Documentation
>>>>> translation. If a language has not been t

Re: Fwd: Submit Help Translation on GNOME Terminal

[Daniel Mustieles García via gnome-i18n]

Hi Andika,

Yes, it seems that my commit broke some continuous build in Gitlab, so
Michael reverted it. To avoid wasting time, could someone indicate us how
to proceed?

I don't mind to do it again (even adding the PO files in the commit) but I
think that's not the proper way to do things.

Maybe someone could review DL's way to add new languages for help or, at
least, grant team coordinators commit access to be able to solve this
issues without breaking anything (nor depend on other people)

Regards

El mié., 4 nov. 2020 a las 13:20, Andika Triwidada ()
escribió:

> Hi Daniel,
>
> Thanks for your help. It seems that Michael Catanzaro revert all your
> modifications before I have chance to commit files. Please advice how to
> proceed?
>
> On Tue, Nov 3, 2020 at 4:50 PM Daniel Mustieles García <
> daniel.mustie...@gmail.com> wrote:
>
>> Hi Andika,
>>
>> I've added 'id' language to those modules. Please check if you can now
>> commit translations for them using DL.
>>
>> Let us know if you have any problem with it.
>>
>> Regards
>>
>> El dom., 1 nov. 2020 a las 2:48, Andika Triwidada ()
>> escribió:
>>
>>> Hello, I think this problem is well known for Documentation translation.
>>> If a language has not been translated, required directory
>>> help/language-code will not be there, and DL can not automatically create
>>> it. Then in turn, DL will not present "submit to repository" on pull down
>>> options.
>>>
>>> Currently, we face this problem on these modules:
>>> *
>>> https://l10n.gnome.org/vertimus/gnome-user-docs/master/system-admin-guide/id/
>>> * https://l10n.gnome.org/vertimus/five-or-more/master/help/id/
>>> * https://l10n.gnome.org/vertimus/iagno/master/help/id/
>>> * https://l10n.gnome.org/vertimus/31/27/89/ (gnome system monitor)
>>> * https://l10n.gnome.org/vertimus/gnote/master/help/id/
>>> * https://l10n.gnome.org/vertimus/gthumb/master/help/id/
>>> * https://l10n.gnome.org/vertimus/gucharmap/master/help/id/
>>> * https://l10n.gnome.org/vertimus/shotwell/master/help/id/
>>>
>>> We would be very grateful if someone who has git write access to those
>>> modules can help us create those prerequisite directories and language
>>> entry in config files.
>>>
>>> Regards,
>>> Andika
>>>
>>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Fwd: Submit Help Translation on GNOME Terminal

[Daniel Mustieles García via gnome-i18n]

Hi Andika,

I've added 'id' language to those modules. Please check if you can now
commit translations for them using DL.

Let us know if you have any problem with it.

Regards

El dom., 1 nov. 2020 a las 2:48, Andika Triwidada ()
escribió:

> Hello, I think this problem is well known for Documentation translation.
> If a language has not been translated, required directory
> help/language-code will not be there, and DL can not automatically create
> it. Then in turn, DL will not present "submit to repository" on pull down
> options.
>
> Currently, we face this problem on these modules:
> *
> https://l10n.gnome.org/vertimus/gnome-user-docs/master/system-admin-guide/id/
> * https://l10n.gnome.org/vertimus/five-or-more/master/help/id/
> * https://l10n.gnome.org/vertimus/iagno/master/help/id/
> * https://l10n.gnome.org/vertimus/31/27/89/ (gnome system monitor)
> * https://l10n.gnome.org/vertimus/gnote/master/help/id/
> * https://l10n.gnome.org/vertimus/gthumb/master/help/id/
> * https://l10n.gnome.org/vertimus/gucharmap/master/help/id/
> * https://l10n.gnome.org/vertimus/shotwell/master/help/id/
>
> We would be very grateful if someone who has git write access to those
> modules can help us create those prerequisite directories and language
> entry in config files.
>
> Regards,
> Andika
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Technical feasibility to translate a project on Github

[Daniel Mustieles García via gnome-i18n]

Problem solved ;-)

I also didn't check that section.

Thanks!

El mié., 14 oct. 2020 a las 10:54, Thibault Martin ()
escribió:

> Oh right, I didn’t check that scary freedesktop section! Thanks a lot
> Piotr :)
>
> Le mar. 13 oct. 2020 à 17:12, Piotr Drąg  a écrit :
>
> wt., 13 paź 2020 o 15:45 Alexandre Franke  > napisał(a):
>
> I think you are omitting a possible scenario. We can have it on Damned
> lies and not take responsibility for it, like we do for the Freedesktop
> modules. You don’t need to have teams on board to do that: the i18n
> coordinators just have to decide that it is part of our extended platform,
> like Freedesktop is, and we can add it immediately so we see its status
> alongside the rest of the platform.
>
> https://l10n.gnome.org/module/flatpak/ has been here for years. :) Best,
> --
> Piotr Drąg https://piotrdrag.fedorapeople.org
>
> ___
> 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: Technical feasibility to translate a project on Github

[Daniel Mustieles García via gnome-i18n]

Thanks for the quick response!

Doing a quick review of the PO file I see the strings are (in the most of
cases) very short and often used in GNOME, so using a translation memory
would be really easy to have it done.

Yes, I was thinking in the same examples. Just adding a link in the
module's page in DL to directly open an MR in the target repo would be a
medium-directly way to have it.

Taking this into account, I give a +1 for having this available for
translation in Damned Lies. Of course, now it's time to hear another
coordinator's opinion about this.

Regards


El mar., 13 oct. 2020 a las 13:09, Thibault Martin ()
escribió:

> Hello Daniel and thanks for your answser,
>
> There seems to be 1112 strings to translate for the Flatpak software
> only.
>
> Those strings are in files in the PO format. I’m not quite sure about
> how (often) those are generated, but if we need adjustments, I’m
> quite sure we can ask them a few things. Let’s not forget Alexander
> Larsson is working on it :)
>
> The files can be found here:
> https://github.com/flatpak/flatpak/tree/master/po
>
> As of today, DL is used to follow the translation status of several
> projects it can't commit on. The two examples I have in mind are the
> freedesktop and Librem 5 ones. To commit our translations, someone
> manually opens a MR on the Gitlab, and then reports to their
> translation coordinator. It’s far from ideal, but still preferable to
> a completely manual process in my opinion.
>
> Best,
>
>
> Le mar. 13 oct. 2020 à 12:58, Daniel Mustieles García
>  a écrit :
> > Hi Thibault,
> >
> > I have some questions about this, hope you can help us with them
> >
> > 1 .To have a better idea about the necessary work for this, how many
> > translatable strings (aprox) Flatpak Software has?
> >
> > 2. Are those translatable strings in a PO file format? If answer is
> > no, which format does it use and which tool is recommended for it?
> >
> > 3 - If finally DL is not able to directly commit translations, how
> > will be the workflow to send and commit them?
> >
> > In a first stage I would not opposite to this idea, but I would like
> > to solve these questions before giving a final vote (just my personal
> > opinion about this, it would be necessary other coordinator's
> > opinion).
> >
> > Thanks in advance
> >
> > El vie., 9 oct. 2020 a las 14:22, Thibault Martin
> > () escribió:
> >> Hello,
> >>
> >>  Thanks for this quick answer Claude. So that solves the technical
> >>  feasibility.
> >>
> >>  Now the audience for this question would probably be the translation
> >>  coordinators: would we accept to take the responsibility of
> >> translating
> >>  flatpak software?
> >>
> >>  Best,
> >>
> >>  Le jeu. 8 oct. 2020 à 23:12, Claude Paroz  a
> >>  écrit :
> >>  > Le 08.10.20 à 14:13, Thibault Martin a écrit :
> >>  >> Hello,
> >>  >>
> >>  >> Flatpak doesn't have a proper translation platform. So far people
> >>  >>  retrieve and submit po files manually.
> >>  >>
> >>  >> I know Flatpak doesn’t necessarily want to be too associated
> >> with
> >>  >> GNOME  so it doesn’t shy out other systems.
> >>  >> Still, a translation provided by one of the major DE could be an
> >>  >> huge  improvement to today’s situation.
> >>  >>
> >>  >> I have two questions here:
> >>  >> * Would we accept to take responsibility of Flatpak’s
> >> translations?
> >>  >> * Is it technically feasible for DL to handle the translations
> >> of a
> >>  >>  project stored on GitHub?
> >>  >>
> >>  >> If we answer "yes" to both, I would offer to Flatpak’s team to
> >>  >> take care  of their translations, which they may or may not
> >> accept.
> >>  >
> >>  > Hi Thibault,
> >>  >
> >>  > There is more or less two level of translation supports in D-L.
> >>  > The first one is "simply" a status of current module translations
> >> +
> >>  > updated pot and merged po files ready for translators to use.
> >>  > That's the case for all freedesktop modules.
> >>  >
> >>  > The second is ability to commit translations from the Web
> >> interface.
> >>  > We do not support Github currently for this feature.
> >>  >
> >>  > So I would say that hosting translation stats would be fine IMHO.
> >>  > Adding commit support is another story, even if it should not be
> >> so
> >>  > much effort (to be evaluated, still).
> >>  >
> >>  > Claude
> >>  > --
> >>  > www.2xlibre.net
> >>  > ___
> >>  > 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
>
>
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Technical feasibility to translate a project on Github

[Daniel Mustieles García via gnome-i18n]

Hi Thibault,

I have some questions about this, hope you can help us with them

1 .To have a better idea about the necessary work for this, how many
translatable strings (aprox) Flatpak Software has?

2. Are those translatable strings in a PO file format? If answer is no,
which format does it use and which tool is recommended for it?

3 - If finally DL is not able to directly commit translations, how will be
the workflow to send and commit them?

In a first stage I would not opposite to this idea, but I would like to
solve these questions before giving a final vote (just my personal opinion
about this, it would be necessary other coordinator's opinion).

Thanks in advance

El vie., 9 oct. 2020 a las 14:22, Thibault Martin ()
escribió:

> Hello,
>
> Thanks for this quick answer Claude. So that solves the technical
> feasibility.
>
> Now the audience for this question would probably be the translation
> coordinators: would we accept to take the responsibility of translating
> flatpak software?
>
> Best,
>
> Le jeu. 8 oct. 2020 à 23:12, Claude Paroz  a
> écrit :
> > Le 08.10.20 à 14:13, Thibault Martin a écrit :
> >> Hello,
> >>
> >> Flatpak doesn't have a proper translation platform. So far people
> >>  retrieve and submit po files manually.
> >>
> >> I know Flatpak doesn’t necessarily want to be too associated with
> >> GNOME  so it doesn’t shy out other systems.
> >> Still, a translation provided by one of the major DE could be an
> >> huge  improvement to today’s situation.
> >>
> >> I have two questions here:
> >> * Would we accept to take responsibility of Flatpak’s translations?
> >> * Is it technically feasible for DL to handle the translations of a
> >>  project stored on GitHub?
> >>
> >> If we answer "yes" to both, I would offer to Flatpak’s team to
> >> take care  of their translations, which they may or may not accept.
> >
> > Hi Thibault,
> >
> > There is more or less two level of translation supports in D-L.
> > The first one is "simply" a status of current module translations +
> > updated pot and merged po files ready for translators to use.
> > That's the case for all freedesktop modules.
> >
> > The second is ability to commit translations from the Web interface.
> > We do not support Github currently for this feature.
> >
> > So I would say that hosting translation stats would be fine IMHO.
> > Adding commit support is another story, even if it should not be so
> > much effort (to be evaluated, still).
> >
> > Claude
> > --
> > www.2xlibre.net
> > ___
> > 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
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Fwd: Submit Help Translation on GNOME Terminal

[Daniel Mustieles García via gnome-i18n]

Ok, hope you feel better soon.

Regards

El sáb., 10 oct. 2020 4:59, Andika Triwidada  escribió:

> Sorry I'm sick, can not explain right now. Will continue discussion after
> I have recovered.
>
> On Tue, Oct 6, 2020 at 6:11 PM Daniel Mustieles García <
> daniel.mustie...@gmail.com> wrote:
>
>> Mmmm... that's very strange. Does it happens only in this module or are
>> other modules affected by this behaviour?
>>
>> I have no problem to directly commit gnome-terminal's PO file into git,
>> but if something in DL is not working properly then we should ask Claude to
>> review it
>>
>> El mar., 6 oct. 2020 a las 12:56, Andika Triwidada ()
>> escribió:
>>
>>> Problem is, no option exist (on DL's pulldown) to submit it
>>>
>>> On Tue, Oct 6, 2020 at 12:18 PM Daniel Mustieles García <
>>> daniel.mustie...@gmail.com> wrote:
>>>
>>>> I don't think so... just see PO file is not committed, just reserved to
>>>> submit. Please submit it and will see if it works. If it doesn't just let
>>>> me know and will help you with it.
>>>>
>>>> Regards
>>>>
>>>> El lun., 5 oct. 2020 a las 17:15, Andika Triwidada ()
>>>> escribió:
>>>>
>>>>>
>>>>>
>>>>> On Mon, Oct 5, 2020 at 2:20 PM Daniel Mustieles García via gnome-i18n <
>>>>> gnome-i18n@gnome.org> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I've added the "id" language to both 3.38 and master branches so now
>>>>>> you should be able to add your translations (and also reuse the 3.38 PO
>>>>>> file in master to save some time).
>>>>>>
>>>>>
>>>>> maybe we need to create "id" subdirectory too?
>>>>> or even an empty help/id/id.po?
>>>>>
>>>>>
>>>>>>
>>>>>> It seems that DL it not taking this change and trying to manually
>>>>>> update branches page gives a Timeout.
>>>>>>
>>>>>> @Claude Paroz  could you please review this?
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> El lun., 5 oct. 2020 a las 8:51, Claude Paroz ()
>>>>>> escribió:
>>>>>>
>>>>>>> Le 05.10.20 à 05:17, Kukuh Syafaat via gnome-i18n a écrit :
>>>>>>> > Hi all,
>>>>>>> >
>>>>>>> > The Indonesian team has recently submitted gnome-terminal help
>>>>>>> > translation to damned-lies, but the po statistics is still 0% [0].
>>>>>>> > I checked on gnome-terminal repository in GitLab [0] and there is
>>>>>>> no
>>>>>>> > `id` folder on help.
>>>>>>> > Why damned-lies did not create automatically when the translator
>>>>>>> > submit po for the first time?
>>>>>>> > Is there any workaround for this?
>>>>>>> >
>>>>>>> > Best Regards.
>>>>>>> >
>>>>>>> > [0]
>>>>>>> https://l10n.gnome.org/vertimus/gnome-terminal/gnome-3-38/help/id/level1/
>>>>>>> > [1]
>>>>>>> https://gitlab.gnome.org/GNOME/gnome-terminal/-/tree/master/help
>>>>>>>
>>>>>>> Hi Kukuh Syafaat,
>>>>>>>
>>>>>>> I guess the issue is due to using the "Inform of submission" action
>>>>>>> instead of the "Submit to repository" action. The former is for those
>>>>>>> having committed the file by an other mean that DL itself (e.g. by
>>>>>>> command line).
>>>>>>>
>>>>>>> However, it may be that DL didn't proposed the action because adding
>>>>>>> new
>>>>>>> translations for modules help without LINGUAS files have to be done
>>>>>>> "by
>>>>>>> hand", as machine-editing Makefiles is too brittle to be automated.
>>>>>>>
>>>>>>> I'm sure someone with GNOME Gitlab commit rights will do the action
>>>>>>> for
>>>>>>> you soon!
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Claude
>>>>>>> --
>>>>>>> www.2xlibre.net
>>>>>>> ___
>>>>>>> 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
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> --
>>>>> andika
>>>>>
>>>>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Fwd: Submit Help Translation on GNOME Terminal

[Daniel Mustieles García via gnome-i18n]

Hi,

I've added the "id" language to both 3.38 and master branches so now you
should be able to add your translations (and also reuse the 3.38 PO file in
master to save some time).

It seems that DL it not taking this change and trying to manually update
branches page gives a Timeout.

@Claude Paroz  could you please review this?

Thanks!

El lun., 5 oct. 2020 a las 8:51, Claude Paroz ()
escribió:

> Le 05.10.20 à 05:17, Kukuh Syafaat via gnome-i18n a écrit :
> > Hi all,
> >
> > The Indonesian team has recently submitted gnome-terminal help
> > translation to damned-lies, but the po statistics is still 0% [0].
> > I checked on gnome-terminal repository in GitLab [0] and there is no
> > `id` folder on help.
> > Why damned-lies did not create automatically when the translator
> > submit po for the first time?
> > Is there any workaround for this?
> >
> > Best Regards.
> >
> > [0]
> https://l10n.gnome.org/vertimus/gnome-terminal/gnome-3-38/help/id/level1/
> > [1] https://gitlab.gnome.org/GNOME/gnome-terminal/-/tree/master/help
>
> Hi Kukuh Syafaat,
>
> I guess the issue is due to using the "Inform of submission" action
> instead of the "Submit to repository" action. The former is for those
> having committed the file by an other mean that DL itself (e.g. by
> command line).
>
> However, it may be that DL didn't proposed the action because adding new
> translations for modules help without LINGUAS files have to be done "by
> hand", as machine-editing Makefiles is too brittle to be automated.
>
> I'm sure someone with GNOME Gitlab commit rights will do the action for
> you soon!
>
> Regards,
>
> Claude
> --
> www.2xlibre.net
> ___
> 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: Making my application international

[Daniel Mustieles García via gnome-i18n]

Hi Gustavo,

You can ask in gnome-devel list, there there are many developers that will
help you better than us.

Good luck!

El lun., 28 sept. 2020 a las 14:57, Gustavo Peredo via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> Thank you for your response! Unfortunately this didn't make the trick, but
> helped me gather some information. When running: $ strace -o file.log
> flatpak run , I'm able to see some output referring to the locale
> I'm currently using:
>
> openat(AT_FDCWD, "/usr/share/locale/en_GB.UTF-8/LC_MESSAGES/libc.mo",
> O_RDONLY) = -1 ENOENT (No such file or directory)
> openat(AT_FDCWD, "/usr/share/locale/en_GB.utf8/LC_MESSAGES/libc.mo",
> O_RDONLY) = -1 ENOENT (No such file or directory)
> openat(AT_FDCWD, "/usr/share/locale/en_GB/LC_MESSAGES/libc.mo", O_RDONLY)
> = 3
> openat(AT_FDCWD, "/usr/share/locale/en_GB.UTF-8/LC_MESSAGES/flatpak.mo",
> O_RDONLY) = -1 ENOENT (No such file or directory)
> openat(AT_FDCWD, "/usr/share/locale/en_GB.utf8/LC_MESSAGES/flatpak.mo",
> O_RDONLY) = -1 ENOENT (No such file or directory)
> openat(AT_FDCWD, "/usr/share/locale/en_GB/LC_MESSAGES/flatpak.mo",
> O_RDONLY) = 4
> openat(AT_FDCWD, "/usr/share/locale/en_GB.UTF-8/LC_MESSAGES/glib20.mo",
> O_RDONLY) = -1 ENOENT (No such file or directory)
> openat(AT_FDCWD, "/usr/share/locale/en_GB.utf8/LC_MESSAGES/glib20.mo",
> O_RDONLY) = -1 ENOENT (No such file or directory)
> openat(AT_FDCWD, "/usr/share/locale/en_GB/LC_MESSAGES/glib20.mo",
> O_RDONLY) = 4
>
> While using a locale I didn't translate, the output is similar:
>
> openat(AT_FDCWD, "/usr/share/locale/ja_JP.UTF-8/LC_MESSAGES/libc.mo",
> O_RDONLY) = -1 ENOENT (そのようなファイルやディレクトリはありません)
> openat(AT_FDCWD, "/usr/share/locale/ja_JP.utf8/LC_MESSAGES/libc.mo",
> O_RDONLY) = -1 ENOENT (そのようなファイルやディレクトリはありません)
> openat(AT_FDCWD, "/usr/share/locale/ja_JP/LC_MESSAGES/libc.mo", O_RDONLY)
> = -1 ENOENT (そのようなファイルやディレクトリはありません)
> openat(AT_FDCWD, "/usr/share/locale/ja_JP.UTF-8/LC_MESSAGES/flatpak.mo",
> O_RDONLY) = -1 ENOENT (そのようなファイルやディレクトリはありません)
> openat(AT_FDCWD, "/usr/share/locale/ja_JP.utf8/LC_MESSAGES/flatpak.mo",
> O_RDONLY) = -1 ENOENT (そのようなファイルやディレクトリはありません)
> openat(AT_FDCWD, "/usr/share/locale/ja_JP/LC_MESSAGES/flatpak.mo",
> O_RDONLY) = -1 ENOENT (そのようなファイルやディレクトリはありません)
>
> Unfortunately, I don't know how much this helps and the fact that it says
> "(No such file or directory)", doesn't help much... Do you know
> someone/somewhere else I can ask?
>
> Em dom., 27 de set. de 2020 às 18:39, Rafael Fontenelle <
> rafae...@gnome.org> escreveu:
>
>> Hello Gustavo,
>>
>> Consider setting the "gettext.bindtextdomain()" (in src/main.py, I
>> think) as mentioned in
>> https://docs.python.org/pt-br/3/library/gettext.html
>>
>> If the domain name is not set, the software will look for
>> "messages.mo" (the translation file in machine language) instead of
>> the proper e.g. "font-downloader.mo".
>>
>> You can verify if that's the case by searching for "messages.mo":
>>
>> $ strace -o file.log   (replace if the proper executable
>> name/path)
>> $ grep messages.mo file.log
>>
>> Best regards,
>> Rafael Fontenelle
>>
>> On Sat, Sep 26, 2020 at 7:29 PM Gustavo Peredo via gnome-i18n
>>  wrote:
>> >
>> > Thank you for your answer!
>> >
>> > After reading xgettext documentation I was able to generate my .po
>> files, I created and edited two of them: en_GB and pt_BR. I added them to
>> my /po directory and added en_GB and pt_BR to my LINGUAS file, no errors
>> were shown during compilation nor when exporting the package. I installed
>> the app on my machine but no translations were applied (My system locale is
>> pt_BR)!
>> >
>> > Any clues on what I should do?
>> >
>> > Do you know somewhere else I can ask this question?
>> >
>> > PS: Also, you were right, many pages were outdated (were talking about
>> GTK 2)
>> > Gustavo
>> >
>> > Em sáb., 26 de set. de 2020 às 13:02, Andre Klapper 
>> escreveu:
>> >>
>> >> Hi,
>> >>
>> >> On Sat, 2020-09-26 at 09:05 -0300, Gustavo Peredo via gnome-i18n wrote:
>> >> > TL; DR: How to begin translating a GTK Application using po?
>> >>
>> >> In theory: https://wiki.gnome.org/TranslationProject/DevGuidelines
>> >>
>> >> In practice I'm not sure how heavily outdated some of those wiki pages
>> >> might be (meson etc). So this email might be useless in the end. :)
>> >>
>> >> andre
>> >> --
>> >> Andre Klapper  |  ak...@gmx.net
>> >> https://blogs.gnome.org/aklapper/
>> >>
>> >>
>> > ___
>> > 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
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: String freeze break request for Epiphany

[Daniel Mustieles García via gnome-i18n]

2/2 from i18n

Thanks!

El lun., 14 sept. 2020 17:59, Piotr Drąg via gnome-i18n <
gnome-i18n@gnome.org> escribió:

> pon., 14 wrz 2020 o 17:09 Michael Catanzaro 
> napisał(a):
> >
> > Hi, I'd like to request a string freeze break to fix the title of the
> > Add Language dialog in Epiphany 3.38. We accidentally added an
> > underscore (as if for a mnemonic) and it looks rather stupid:
> >
> https://gitlab.gnome.org/GNOME/epiphany/-/commit/41881f343358fdd5953382d52520a82e4ae59ccf
> .
> > If approved, I'll backport that commit to the 3.38 branch. Epiphany
> > 3.38.0 is already released, so you would have until 3.38.1 to update
> > translations.
> >
>
> Aah, I did wonder what was up with that underscore. Sorry I didn’t
> report it then, so it wouldn’t have ended up in .0.
>
> 1/2 from i18n for .1.
>
> --
> Piotr Drąg
> https://piotrdrag.fedorapeople.org
> ___
> 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 break request for Glade

[Daniel Mustieles García via gnome-i18n]

Hi Juan!

You will be welcome to collaborate with us ;-)

Just subscribe and write to team's mailing list (gnome-es-l...@gnome.org)
or write me directly and will talk about it.

Many thanks!

El dom., 13 sept. 2020 a las 20:03, Juan Pablo Ugarte via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

>
> You are right it was rude, I was under the wrong impression of how the
> string break actually works and did not take the time to learn about.
> I thought it was a way to let translators know there were going to be
> untranslated "broken" strings, but now that you mention it does make more
> sense to introduce the break in the point release.
> I am sorry I had to learn the hard way and cause other people trouble.
>
> I am going to try to get more involved in the process in the future so
> this does not happen again.
> Would it be ok if I start helping with the spanish translation?
>
> thanks
>
> Juan Pablo
> ___
> 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 break request for Glade

[Daniel Mustieles García via gnome-i18n]

2/2 from i18n

Thanks!

El sáb., 12 sept. 2020 11:10, Claude Paroz  escribió:

> I18n approval 1 of 2 for GNOME 3.38.*1*
>
> Claude
>
> Le 12.09.20 à 00:13, Juan Pablo Ugarte via gnome-i18n a écrit :
> > This is how it would look like
> >
> > imagen.png
> >
> >
> > On Thu, Sep 10, 2020 at 8:15 PM Juan Pablo Ugarte
> > mailto:juanpablouga...@gmail.com>> wrote:
> >
> > Hello, sorry for this last minute request
> >
> > Last year a beloved professor passed away and I would like to do
> > something in commemoration.
> >
> > Add a simple string like "In memory of an extraordinaire \n person
> > and professor \n R.I.P Guido Macchi" either in the main window or
> > about dialog and a small explanation of who he was to me
> >
> > Since this wont affect the program at all, there would be no issue
> > if its not translated
> >
> > thanks
> >
> > Juan Pablo
> ___
> 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: msgfmt check not pass

[Daniel Mustieles García via gnome-i18n]

@Claude, I didn't mean you to fix it, I know we should not touch other
team's PO files 

@Afranke, I visited NetworkManager to check a translation for gnome-help
and saw it (there is a warning icon in the affected languages). I wrote to
both i18n and teams coordinators to notice them about the issue. Sorry for
that.


El jue., 3 sept. 2020 19:44, Alexandre Franke  escribió:

> On Thu, Sep 3, 2020 at 6:05 PM Daniel Mustieles García
>  wrote:
> > Hi all,
>
> Hi,
>
> > I've detected some msgfmt errors in NetworkManager in Damned Lies [1].
>
> How?
>
> > Affected languages are French, Chinese and Japanese.
> >
> > Could you please review and fix them?
>
> Please don’t rely on individuals to do such tasks. Next time, send an
> email to the relevant teams.
>
> --
> Alexandre Franke
> GNOME Hacker
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

msgfmt check not pass

[Daniel Mustieles García via gnome-i18n]

Hi all,

I've detected some msgfmt errors in NetworkManager in Damned Lies [1].

Affected languages are French, Chinese and Japanese.

Could you please review and fix them?

Thanks in advance!

[1] https://l10n.gnome.org/module/NetworkManager/
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: gnome-settings-daemon | usb-protection: Relax the whitelist to all HIDs and HUBs (!192)

[Daniel Mustieles García via gnome-i18n]

Hi Enrico,

Freeze break approvals can only be emitted by i18n admins, not from
translation teams ;-)

So this request, at this moment, has only 1/2 from i18n

Regards!

El jue., 3 sept. 2020 a las 17:14, Enrico () escribió:

> +1 from pt_BR l10n team :)
>
> Kind regards
> --
>
> Em qui, 3 de set de 2020 11:50, Daniel Mustieles García via gnome-i18n <
> gnome-i18n@gnome.org> escreveu:
>
>>  +1 from i18n team. Lets help developers to reduce the number of
>> frustrated users :-P
>>
>> Regards
>>
>> El jue., 3 sept. 2020 a las 16:46, Tobias Mueller ()
>> escribió:
>>
>>> Dear translations team,
>>>
>>> we're seeking for a string freeze exception for in gnome-settings-
>>> daemon.
>>> Details can be found here:
>>>
>>> https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/192/diffs#b2656164d97e5e60c50fd14cf5c149c5a8e30904_591_589
>>>
>>> and the affected two strings are:
>>>
>>> "New keyboard detected" which ought to be "New device detected"
>>>
>>> And:
>>> "Either your keyboard has been reconnected or a new one has been plugged
>>> in. "
>>>
>>> which will become:
>>> "Either one of your existing devices has been reconnected or a new one
>>> has been plugged in. "
>>>
>>>
>>> The patch will be merged if or rather when the exception is granted.
>>>
>>> In fairness, it is not absolutely necessary to push it to 3.38, but it
>>> would be nice as it will most likely lessen the number of frustrated users
>>> asking for help ;-)
>>>
>>> Thanks,
>>>   Tobi
>>>
>>> ___
>>> 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
>>
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: gnome-settings-daemon | usb-protection: Relax the whitelist to all HIDs and HUBs (!192)

[Daniel Mustieles García via gnome-i18n]

 +1 from i18n team. Lets help developers to reduce the number of frustrated
users :-P

Regards

El jue., 3 sept. 2020 a las 16:46, Tobias Mueller ()
escribió:

> Dear translations team,
>
> we're seeking for a string freeze exception for in gnome-settings-
> daemon.
> Details can be found here:
>
> https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/192/diffs#b2656164d97e5e60c50fd14cf5c149c5a8e30904_591_589
>
> and the affected two strings are:
>
> "New keyboard detected" which ought to be "New device detected"
>
> And:
> "Either your keyboard has been reconnected or a new one has been plugged
> in. "
>
> which will become:
> "Either one of your existing devices has been reconnected or a new one has
> been plugged in. "
>
>
> The patch will be merged if or rather when the exception is granted.
>
> In fairness, it is not absolutely necessary to push it to 3.38, but it
> would be nice as it will most likely lessen the number of frustrated users
> asking for help ;-)
>
> Thanks,
>   Tobi
>
> ___
> 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: Connections POTFILES.in

[Daniel Mustieles García via gnome-i18n]

Hi Rafael,

Yes, I modified POTFILES.in to fix some errors DL was showing about missing
files (and a non-existant file) in the file.

If strings are marked as translatable but not included in POTFILES it's not
a freeze break (please let me know if I'm wrong... this is sometimesa bit
confusing).

But now we have done the initial setup for having this module in DL I'd ask
Felipe to review and fix this. We can do it but maybe we should let him
this task ;-)

Thanks!

El mar., 1 sept. 2020 a las 14:14, Rafael Fontenelle ()
escribió:

> Hey there,
>
> I notice you added some files to POTFILES.in in gnome-3-38 branch[1],
> but the gnome-3-38's list differs from master branch's[2]. Some
> important strings were not included in 3.38's translation, like CLI
> options descriptions and the "translator-credits". See my diff between
> gnome-3-38 and master for the obsolete strings[3] -- this translation
> started in master branch, but I had to redo it when branched on Damned
> Lies.
>
> Is it OK to have POTFILES.in contents synced, or this would be somehow
> considered string freeze break?
>
> [1]
> https://gitlab.gnome.org/GNOME/connections/-/blob/gnome-3-38/po/POTFILES.in
> [2]
> https://gitlab.gnome.org/GNOME/connections/-/blob/master/po/POTFILES.in
> [3] https://l10n.gnome.org/vertimus/diff/670111/0/0/
>
> Best regards,
> Rafael Fontenelle
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Enroll gnome-connections in the translation project

[Daniel Mustieles García via gnome-i18n]

I've been able to commit from both DL and command line directly into git.

Matej, are you trying to upload translations throught Damned Lies? Which
branch are you trying?

Regards

El mar., 1 sept. 2020 a las 10:05, Felipe Borges ()
escribió:

> Hi Matej,
>
> I did set the gitlab permissions to the gnome-3-38 and master branches to
> "Developers + Maintainers". It's exactly what I have for gnome-boxes too.
>
> Is there some other permission I should change for you to be able to
> commit?
>
> Cheers,
> Felipe.
>
>
> On Tue, 1 Sep 2020, 09:41 Matej Urban,  wrote:
>
>> Daniel,
>> thank you, I'll wait for Felipe raply.
>>
>> Best,
>> Matej
>>
>> On Mon, Aug 31, 2020 at 10:59 PM Daniel Mustieles García via gnome-i18n <
>> gnome-i18n@gnome.org> wrote:
>>
>>> Done. I've also fixed Potfiles file, renaming it to Potfiles.in and
>>> adding some missing files. Now stats in DL are working properly.
>>>
>>> About perms you should ask Felipe directly as he is the maintainer and
>>> and review and fix them.
>>>
>>> Regards
>>>
>>> El lun., 31 ago. 2020 20:44, Alexandre Franke 
>>> escribió:
>>>
>>>> Hey,
>>>>
>>>> it seems Felipe unfortunately already branched for 3.38. Can someone
>>>> please add the branch on Damned lies and switch from master to that
>>>> branch in the 3.38 releaseset?
>>>>
>>>> Cheers,
>>>>
>>>> --
>>>> Alexandre Franke
>>>> GNOME Hacker
>>>> ___
>>>> 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
>>>
>>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Enroll gnome-connections in the translation project

[Daniel Mustieles García via gnome-i18n]

Done. I've also fixed Potfiles file, renaming it to Potfiles.in and adding
some missing files. Now stats in DL are working properly.

About perms you should ask Felipe directly as he is the maintainer and and
review and fix them.

Regards

El lun., 31 ago. 2020 20:44, Alexandre Franke  escribió:

> Hey,
>
> it seems Felipe unfortunately already branched for 3.38. Can someone
> please add the branch on Damned lies and switch from master to that
> branch in the 3.38 releaseset?
>
> Cheers,
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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: Enroll gnome-connections in the translation project

[Daniel Mustieles García via gnome-i18n]

Many thanks! Now it's working properly and added into Core moduleset.

Thanks!

El lun., 31 ago. 2020 a las 11:55, Felipe Borges ()
escribió:

> Hi Daniel, thank you very much for your quick reply.
>
> I have now pushed a commit renaming the POTFILES file to POTFILES.in
>
> https://gitlab.gnome.org/GNOME/connections/-/commit/496a4f3b1797997a80bf0c102997921e6c3aa8cf
>
> Cheers,
> Felipe.
>
> On Mon, Aug 31, 2020 at 11:41 AM Daniel Mustieles García
>  wrote:
> >
> > Hi Felipe,
> >
> > I've added your module to Damned Lies but got some errors generating POr
> files due to the name of po/POTFILEs file. It should be POTFILEs.in. I
> tried to fix it but I don't have commit rights in this repo.
> >
> > Could you please fix it?
> >
> > Another issue is I don't know which moduleset should this module belong.
> @Claude Paroz should we add it To Extra applications until it gets promoted
> to Core or should we add it directly to Core moduleset?
> >
> > Thanks!
> >
> > El lun., 31 ago. 2020 a las 10:04, Felipe Borges (<
> felipebor...@gnome.org>) escribió:
> >>
> >> Hi everyone,
> >>
> >> The release-team has decided to promote Connections to the GNOME
> >> namespace in Gitlab and promote it as a core app in our future
> >> releases.
> https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/405
> >>
> >> Please, let me know how I can go about enrolling this app into the
> >> GNOME translation project.
> >>
> >> Thank you very much,
> >> Felipe.
> >> ___
> >> 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: Enroll gnome-connections in the translation project

[Daniel Mustieles García via gnome-i18n]

Great! I've already added it, into the Utils category.

Thanks!

El lun., 31 ago. 2020 a las 11:59, Rafael Fontenelle ()
escribió:

> Hi Daniel,
>
> It seems Connections was approved as Core app, according to
> mcantazaro's reply in
>
> https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/405#note_899412
>
> Best regards,
> Rafael Fontenelle
>
> On Mon, Aug 31, 2020 at 6:41 AM Daniel Mustieles García via gnome-i18n
>  wrote:
> >
> > Hi Felipe,
> >
> > I've added your module to Damned Lies but got some errors generating POr
> files due to the name of po/POTFILEs file. It should be POTFILEs.in. I
> tried to fix it but I don't have commit rights in this repo.
> >
> > Could you please fix it?
> >
> > Another issue is I don't know which moduleset should this module belong.
> @Claude Paroz should we add it To Extra applications until it gets promoted
> to Core or should we add it directly to Core moduleset?
> >
> > Thanks!
> >
> > El lun., 31 ago. 2020 a las 10:04, Felipe Borges (<
> felipebor...@gnome.org>) escribió:
> >>
> >> Hi everyone,
> >>
> >> The release-team has decided to promote Connections to the GNOME
> >> namespace in Gitlab and promote it as a core app in our future
> >> releases.
> https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/405
> >>
> >> Please, let me know how I can go about enrolling this app into the
> >> GNOME translation project.
> >>
> >> Thank you very much,
> >> Felipe.
> >> ___
> >> 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
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Enroll gnome-connections in the translation project

[Daniel Mustieles García via gnome-i18n]

I forgot this in my previous mail...

here is the link to the recently created module in DL:
https://l10n.gnome.org/module/gnome-connections/

El lun., 31 ago. 2020 a las 11:41, Daniel Mustieles García (<
daniel.mustie...@gmail.com>) escribió:

> Hi Felipe,
>
> I've added your module to Damned Lies but got some errors generating POr
> files due to the name of po/POTFILEs file. It should be POTFILEs.in. I
> tried to fix it but I don't have commit rights in this repo.
>
> Could you please fix it?
>
> Another issue is I don't know which moduleset should this module belong. 
> @Claude
> Paroz  should we add it To Extra applications until
> it gets promoted to Core or should we add it directly to Core moduleset?
>
> Thanks!
>
> El lun., 31 ago. 2020 a las 10:04, Felipe Borges ()
> escribió:
>
>> Hi everyone,
>>
>> The release-team has decided to promote Connections to the GNOME
>> namespace in Gitlab and promote it as a core app in our future
>> releases.
>> https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/405
>>
>> Please, let me know how I can go about enrolling this app into the
>> GNOME translation project.
>>
>> Thank you very much,
>> Felipe.
>> ___
>> 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: Evolution: String freeze break approval plea

[Daniel Mustieles García via gnome-i18n]

Hi Milan,

1/2 from i18n team

Thanks!

El lun., 31 ago. 2020 a las 9:14, Milan Crha via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> Hello,
> there is opened a merge request [1] against Evolution from a
> contributor, which is quite simple (code wise speaking), but it
> contains two translatable strings. One for an option name ("Started
> Tasks"), the other for its tooltip (might be something along these
> lines, even we are still discussing the final version "Filters for
> tasks that either do not have a start date or the start date is earlier
> than the time the filter is selected at").
>
> I'd like to include the change in the 3.38.0, especially because it's
> the contributor's effort, though the contributor filled the merge
> request "too late".
>
> Would you mind to approve it, please?
>
> Thanks and bye,
> Milan
>
> [1] https://gitlab.gnome.org/GNOME/evolution/-/merge_requests/63
>
> ___
> 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: Enroll gnome-connections in the translation project

[Daniel Mustieles García via gnome-i18n]

Hi Felipe,

I've added your module to Damned Lies but got some errors generating POr
files due to the name of po/POTFILEs file. It should be POTFILEs.in. I
tried to fix it but I don't have commit rights in this repo.

Could you please fix it?

Another issue is I don't know which moduleset should this module
belong. @Claude
Paroz  should we add it To Extra applications until it
gets promoted to Core or should we add it directly to Core moduleset?

Thanks!

El lun., 31 ago. 2020 a las 10:04, Felipe Borges ()
escribió:

> Hi everyone,
>
> The release-team has decided to promote Connections to the GNOME
> namespace in Gitlab and promote it as a core app in our future
> releases.
> https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/405
>
> Please, let me know how I can go about enrolling this app into the
> GNOME translation project.
>
> Thank you very much,
> Felipe.
> ___
> 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: [gnome-music] string freeze break request

[Daniel Mustieles García via gnome-i18n]

1/2 from i18n

Thanks!

El vie., 28 ago. 2020 a las 22:13, Marinus () escribió:

> Hey translator folks,
>
> Music accidentally broke string freeze with a user facing message
> containing a version number. See
> https://gitlab.gnome.org/GNOME/gnome-music/-/merge_requests/760#note_900702
> .
>
> It is kind of important to report the correct needed tracker version to
> the user if we display an error screen.
>
> Apologies for the inconvenience.
>
> Regards,
> Marinus Schraal
> ___
> 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: Upcoming Geary release

[Daniel Mustieles García via gnome-i18n]

Sorry, I thought we were in string change announcement.

Thanks Alexandre!

El jue., 27 ago. 2020 a las 9:58, Alexandre Franke ()
escribió:

> On Thu, Aug 27, 2020 at 7:32 AM Daniel Mustieles García via gnome-i18n
>  wrote:
> > El jue., 27 ago. 2020 a las 0:22, Michael Gratton via gnome-i18n (<
> gnome-i18n@gnome.org>) escribió:
> >> It was just pointed out Geary has a missing plural form, is it okay if
> >> I land a fix for this?
> >> <https://gitlab.gnome.org/GNOME/geary/-/issues/949>
> >
> > Sure, go ahead.
>
> Ahem, Technically that is affected by string freeze, so you need two
> approvals from i18n to be granted an exception. Here’s the second one.
>
> --
> Alexandre Franke
> GNOME Hacker
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Upcoming Geary release

[Daniel Mustieles García via gnome-i18n]

El jue., 27 ago. 2020 a las 0:22, Michael Gratton via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> On Wed, 26 Aug, 2020 at 09:59, Thibault Martin 
> wrote:
> > A friendly reminder that Geary, the mail app, is following the Core
> > release cycle. Its maintainers froze the UI and the strings so we can
> > translate it.
> >
> > Although this application is filed under "Extras" in DL, you may want
> > to prioritize its translation and proofreading once you are done with
> > Core applications.
>
>
> It was just pointed out Geary has a missing plural form, is it okay if
> I land a fix for this?
> 
>

Sure, go ahead.

Thanks!


> //Mike
>
> PS Thanks for the email Thibault!
>
> --
> Michael Gratton.
> 
>
>
> ___
> 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: GTK master and gnome 3.38 in D-L

[Daniel Mustieles García via gnome-i18n]

Hi Rafael!

I see both master and 3.24 are shown in core moduleset. Maybe we can remove
master branch to avoid translator waste time working on it for now.

@Claude: it's ok to remove GTK's master branch until the new release?

Thanks!

El mié., 19 ago. 2020 a las 14:18, Rafael Fontenelle ()
escribió:

> Hi Matthias,
>
> On Tue, Aug 18, 2020 at 10:42 AM Matthias Clasen
>  wrote:
> >
> >
> >
> > On Tue, Aug 18, 2020 at 8:37 AM Rafael Fontenelle 
> wrote:
> >>
> >> Hi translation coordinators,
> >>
> >> I see that GTK master in the GNOME 3.38 core apps page in Damned Lies.
> >> Can GTK master be translated, or should we stick with its previous
> >> version (3.24.x) ?
> >>
> >
> > GTK master will turn into GTK4 soon. Ideally, both should be translated,
> but
> > if you need to prioritize, GTK 3.24 has more immediate impact, since
> that is
> > what apps use in 3.38
>
> Thanks for the reply! Yes, I asked mostly because of prioritization.
> I'll ignore GTK master for now then.
>
> (GTP coordinators:) It would be nice to link GTK 3.24 in Damned Lies's
> GNOME 3.38 core apps page instead of GTK master, if it is not going to
> be released for GNOME 3.38.
>
> Regards,
> Rafael Fontenelle
> ___
> 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: Ignoring source files with strings that will never be presented in the UI

[Daniel Mustieles García via gnome-i18n]

Hi Michael,

I think you're right: if those strings will neve be shown in the GUI and
adding them to POTFILES.skip does the trick, I don't see any problem with
it.

If I'm wrong with this please let me/us know.

Regards

El mar., 18 ago. 2020 a las 14:24, Michael Gratton via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> Hi all,
>
> Just wanted to check some rationale regarding ignoring some
> translatable files that contain strings that will never show up in the
> UI.
>
> Geary is using libpeas for plugins, which uses a desktop-file format
> for plugin metadata such as human-readable names and descriptions.
> Geary has both internal and optional plugins. The internal ones are
> always loaded and are never presented in the UI, however libpeas
> requires them to have a Name key in their desktop file regardless, and
> hence this is showing up as a translatable string.
>
> See this for example:
> <
> https://gitlab.gnome.org/GNOME/geary/-/blob/462edf7eb8f07014f5f160f49e9e217812f3c05e/src/client/plugin/special-folders/special-folders.plugin.desktop.in>
>
> - currently it has a comment for translators to avoid translating it.
>
> These files are currently listed in POTFILES.in since it's best
> practice for all source files to be present there, but on the one hand
> surely it would be better for these files to be skipped. So I'm not
> sure what to do.
>
> Can I just remove them from POTFILES.in and put them in POTFILES.skip
> instead?
>
> //Mike
>
> --
> Michael Gratton.
> 
>
>
> ___
> 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: Portuguese Translation Team (pt)

[Daniel Mustieles García via gnome-i18n]

Mmmm... I'm not sure about this. If Portuguese is different from Brazilian
and you don't have a full knowledge about it I don't think it's a good idea
to coordinate that team.

I don't know how deep are the differences between both languages, but maybe
a Portuguese people might get confused reading some Brazilian terms.

Regards

El mar., 18 ago. 2020 a las 13:24, Rafael Fontenelle ()
escribió:

> Hi, Juliano
>
> On Tue, Aug 18, 2020 at 8:17 AM Juliano Camargo via gnome-i18n
>  wrote:
>
> > It depends on what you believe is "ready". Let make me clear, I am not a
> Portuguese, I am Brazilian. I speak Portuguese but not as they do in
> Portugal. Still, I am kind of learning how to speak like they do and I use
> Linux as OS so "why not merge the two things?" I was asking myself.
>
> Have you considered joining Brazilian Portuguese translation team in
> https://l10n.gnome.org/teams/pt_BR/ ?
>
> Best regards,
> Rafael Fontenelle
> ___
> 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: New procedure for freeze break requests

[Daniel Mustieles García via gnome-i18n]

El mié., 12 ago. 2020 a las 9:53, Alexandre Franke ()
escribió:

> On Tue, Aug 11, 2020 at 9:16 PM Michael Catanzaro 
> wrote:
> > Hi,
>
> Hi,
>
> > I'm fed up with mailman and am trying to decommission the release team
> > mailing list. That means we need a new procedure for handling freeze
> > break requests that's not based on email. We've created:
> >
> > https://gitlab.gnome.org/Teams/Releng/freeze-breaks
>
> I like the idea, but I am concerned. Gitlab has notoriously bad
> notification handling, and people miss things because of it. Aren’t
> you afraid of that, especially with freeze exception requests, which
> are time sensitive?
>
> > That should work fine for everything that only requires approval from
> > release team: UI freeze, feature freeze, and hard code freeze. (And
> > docs team can watch the repo if interested.)
>
> Tentative nod. Do note that some of these changes might affect strings
> which are not frozen yet, but the start of The Freeze also marks the
> start of the string change announcement period. Therefore, in those
> cases, developers would still need to tell us about it (which could
> “just” have been a CC before, now it would require a separate email in
> addition to the gitlab issue).
>
> >  * i18n team could watch this repo's issue tracker for string break
> > requests and approve them there, alongside other freeze break requests;
>
> I’m worried about signal to noise ratio here. Watching activity on a
> whole gitlab project when you’re only interested in a subset of if
> does not seem very compelling. Unless there’s a way for i18n team
> members to only watch a label or something similar?
>
> >  * We could continue to use email to gnome-i18n@ for string break
> > requests and just say that release team no longer needs to be involved
> > in string freeze breaks
>
> That makes me wonder why the release team was involved at all so far.
> Not that it changes anything for me personally, but there may have
> been a reason, wasn’t there?
>
> > Do you have a preference (or alternative proposal) for how this would
> > work?
>
> I may need a bit of time to think this through. All the proposals,
> apart from the first one, make sense to me and I’m not sure what would
> be the best. Making such a decision 10 days before entering the string
> freeze also looks like bad timing, so maybe we should stick to the
> current method for this release and make a decision early in the next
> cycle?
>

Agree, I don't think the idea was to change it for this cycle, but it's a
good point to put it on the table ;-)

>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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: New procedure for freeze break requests

[Daniel Mustieles García via gnome-i18n]

Hi Michael!

El mar., 11 ago. 2020 a las 21:16, Michael Catanzaro ()
escribió:

> Hi,
>
> I'm fed up with mailman and am trying to decommission the release team
> mailing list. That means we need a new procedure for handling freeze
> break requests that's not based on email. We've created:
>
> https://gitlab.gnome.org/Teams/Releng/freeze-breaks
>
> where developers can report issues to request a freeze break. That
> should work fine for everything that only requires approval from
> release team: UI freeze, feature freeze, and hard code freeze. (And
> docs team can watch the repo if interested.)
>
> Now, for issues that require string freeze breaks, I see a few
> different options:
>
>  * i18n team could watch this repo's issue tracker for string break
> requests and approve them there, alongside other freeze break requests;
> or
>

Personally I don't like this option because watching request not directly
related to i18n is useless for us and might create unnecessary noise.


>  * We could continue to use email to gnome-i18n@ for string break
> requests and just say that release team no longer needs to be involved
> in string freeze breaks
>

Good, but I have one question here: would Release team made a first
approval of a change before us? I mean, if a developer requests a break
that adds several source code lines but only changes one string, both
Release and i18n team should approve it. How would it be done? If i18n
gives 2 votes but R-T rejects it, how would we notice it?

 * We could create a separate repo under
> https://gitlab.gnome.org/Teams/Translation just for string freeze
> breaks.
>

Same above questions bus I guess Gitlab would allow to add R-T comments in
the thread, so both teams could be notice about the changes in the
discussion.

My 2 cents ;-)

Regards!

>
> Do you have a preference (or alternative proposal) for how this would
> work?
>
> Happy Tuesday!
>
> Michael
>
>
> ___
> 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: Upcoming release of App Icon Preview

[Daniel Mustieles García via gnome-i18n]

Completely agree with Alexandre. This mailing list is not the proper place
to discuss your disagrees with your team coordinator.

Please do not use this list for that.

El mié., 29 jul. 2020 15:56, Alexandre Franke  escribió:

> Milo,
>
> Hijacking threads to make them about your situation and harassing
> people like you do reflects poorly on you. You have to stop that now.
>
> --
> Alexandre Franke
> GNOME Hacker
> ___
> 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: What to do with inactive GNOME language translation teams?

[Daniel Mustieles García via gnome-i18n]

Yes, I agree this is sad and if we can do something to fix or improve it,
we should do it.

The first step should be contact team coordinators to wonder if they are
still interested in the project. Obviously they are not but we can use this
as an introduction to ask about a general request for a new team
coordinator.

Once done this we can spread the word about the need of a new team
coordinator for the XX team. Maybe here we could contact recent
collaborators in each team, make a post in Planet GNOME or even make a
public announce (Engagement Team could help?) to try to reach more public.

@Claude: could we get a list of coordinators' email directly from DL's
database? that could ease the work.

Andre, I can help with this task so just let me know what can I do ;-)

Thanks for taking care of this!

El mar., 28 jul. 2020 a las 15:18, Andre Klapper () escribió:

> https://l10n.gnome.org/teams/ lists 142 language teams.
>
> 8 of them state "No coordinator".
>
> For the 134 remaining language teams with a coordinator listed, I ran a
> bash script (attached) on a local git checkout of git master branches
> under "GNOME", to list how many updates have been made by each team in
> the last 24 months. (See complete output below.)
>
> The script queries for .po files with the language team abbreviation,
> for example "no.po" files for the "no" language team.
> NOTE: This is not always correct.
> There are definitely false positives, e.g. "no" team means "nb" and
> "nn" languages, or "zh_trad" team might mean "zh_TW" language?
>
> Of these 134 teams, 36 had no activity in the last 24 months:
>
> * https://l10n.gnome.org/teams/ak - Akan — Coordinated by Lawrence Aberba
> * https://l10n.gnome.org/teams/en_AU - Australian English — Coordinated
> by Michael Findlay
> * https://l10n.gnome.org/teams/bal - Balochi — Coordinated by Mostafa
> Daneshvar
> * https://l10n.gnome.org/teams/bem - Bemba — Coordinated by Anthony
> Musaluke
> * https://l10n.gnome.org/teams/brx - Bodo — Coordinated by Sanjib Narzary
> * https://l10n.gnome.org/teams/nhn - Central Nahuatl — Coordinated by
> jorge becerril
> * (false?) https://l10n.gnome.org/teams/zh_trad - Chinese Traditional —
> Coordinated by Chao-Hsiung Liao
> * https://l10n.gnome.org/teams/dv - Divehi — Coordinated by Inash Zubair
> * https://l10n.gnome.org/teams/fo - Faroese — Coordinated by Niels John
> Andreasen
> * https://l10n.gnome.org/teams/fy - Frisian — Coordinated by Sense
> Hofstede
> * https://l10n.gnome.org/teams/ff - Fula — Coordinated by Ibrahima Sarr
> * https://l10n.gnome.org/teams/gn - Guarani — Coordinated by Moreno
> Saraiva Martins
> * https://l10n.gnome.org/teams/az_IR - Iranian Azerbaijani — Coordinated
> by Amir Hedayaty
> * https://l10n.gnome.org/teams/ks - Kashmiri — Coordinated by Rakesh
> Pandit
> * https://l10n.gnome.org/teams/kg - Kikongo — Coordinated by Kibavuidi
> NSIANGANI
> * https://l10n.gnome.org/teams/ky - Kirghiz — Coordinated by Timur
> Zhamakeev
> * https://l10n.gnome.org/teams/la - Latin — Coordinated by Paul Norton
> * https://l10n.gnome.org/teams/li - Limburgian — Coordinated by Kenneth
> Rohde Christiansen
> * https://l10n.gnome.org/teams/ln - Lingala — Coordinated by René Manassé
> GALEKWA
> * https://l10n.gnome.org/teams/lg - Luganda — Coordinated by Kizito
> Birabwa
> * https://l10n.gnome.org/teams/mi - Maori — Coordinated by John C Barstow
> * https://l10n.gnome.org/teams/nap - Neapolitan — Coordinated by Sabine
> Emmy Eller
> * https://l10n.gnome.org/teams/nso - Northern Sotho — Coordinated by
> Dwayne Bailey
> * (false!) https://l10n.gnome.org/teams/no - Norwegian (Bokmål and
> Nynorsk) — Coordinated by Kjartan Maraas
> * https://l10n.gnome.org/teams/ang - Old English — Coordinated by James
> R. Johnson
> * https://l10n.gnome.org/teams/szl - Silesian — Coordinated by Grzegorz
> Kulik
> * https://l10n.gnome.org/teams/so - Somali — Coordinated by Ismael Omar
> * https://l10n.gnome.org/teams/tl - Tagalog — Coordinated by Eric Pareja
> * https://l10n.gnome.org/teams/tt - Tatar — Coordinated by Ainur Shakirov
> * https://l10n.gnome.org/teams/bo - Tibetan — Coordinated by Tennom Bo
> * https://l10n.gnome.org/teams/ts - Tsonga — Coordinated by Ernest Mashele
> * https://l10n.gnome.org/teams/tk - Turkmen — Coordinated by Ghorban M.
> Tavakoly
> * https://l10n.gnome.org/teams/uz - Uzbek — Coordinated by Bahodir
> Mansurov
> * https://l10n.gnome.org/teams/guc - Wayuu — Coordinated by Michael
> Ramírez
> * https://l10n.gnome.org/teams/yi - Yiddish — Coordinated by Raphael
> Finkel
> * https://l10n.gnome.org/teams/yo - Yoruba — Coordinated by Abayomi
> Mobolaji Onibudo
>
> Does someone agree that this is an unfortunate state?
>
> If so, any ideas what to do?
> Contact those team coordinators via email and ask... something?
> And/or a public call for new coordinators?
> Any volunteers?
>
> Open questions, I know. :)
>
> Cheers,
> andre
>
>
>
> == Full script output, FYI: ==
>
> Since 2018-07-28:
> 38 code repos updated by af team in 67 commits

Re: Gnome Clocks split cases for Tuesday Thursday

[Daniel Mustieles García via gnome-i18n]

Hi Fabio,

Yes, but please report it at Gitlab, so maintainers can review it. They
might not be aware of messages in this list, but Gitlab will sure be the
place to warn them about this.

Thanks for notifying!

El mar., 14 jul. 2020 14:22, Fabio Tomat via gnome-i18n <
gnome-i18n@gnome.org> escribió:

> Hello,
> I noticed that the string “T” (referred to Alarm|Repeat-On) is used to
> display both Tuesday and Thursday (as explained in string comments). This
> is true for English but in other languages those days uses different
> letters (such as M for martars and J joibe in friulian or Martedì e Giovedì
> in italian and so on...)
> the same happens for Sunday and Saturday.
>
> I think it should be fixed
>
> Regards
>
> Fabio Tomat
> ___
> 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: Problems commiting damned-lies package

[Daniel Mustieles García via gnome-i18n]

 fact that you
> reference "commit hooks" makes me think you're basically thinking that
> we're using Git by itself, like this is still 2009. We don't. We switched
> to GitLab because it offers us a lot more tools that "hooks". We have CI
> pipelines that run on branches; merge requests; an entire API to construct
> tools on top of our infrastructure.
>
> We don't want special snowflakes, we just want to be able to do our work
>> in the best way.
>>
>
> Your "best way" has a high chance to make me waste my time, when we have
> perfectly functional tools to avoid that.
>
> I'm grateful for the work done by localisation teams; lowering the bar of
> contribution makes it better for everyone, but that should never come at
> the cost of the stability of the platform.
>
> The solution to making GNOME software better is not to make everyone
> expert developers, but to make sure our infrastructure is automated and
> safe to contribute to—and "safe" doesn't mean "I can revert broken stuff
> after the fact". That principle has been one of the driving force of a lot
> of the changes in our infrastructure over the years.
>
> Ciao,
>  Emmanuele.
>
> Regards
>>
>> El lun., 22 jun. 2020 a las 12:30, Emmanuele Bassi ()
>> escribió:
>>
>>> Hi;
>>>
>>> to be brutally honest, as a maintainer I don't want any translator to
>>> commit directly to Git—unless it's done to a separate branch and/or through
>>> merge requests.
>>>
>>> Translators do not build the projects they translate, and they don't (or
>>> cannot) know when they break things. The only way maintainers know that a
>>> broken translation happened is that suddenly the CI mails us, and then we
>>> have to hunt down what happened behind out backs. This is even worse when
>>> you realise something has broken a long time ago because the release
>>> process is now impossible.
>>>
>>> I'd rather have an automated, web UI tool that pushed changes to a
>>> branch and opened a merge request that ran the CI pipeline (and maybe the
>>> dist process), than allowing translators to commit to Git directly. I don't
>>> really care if some translator is an old hand that was around when GNOME
>>> used CVS and scripted their way to push to dozens of repositories at once;
>>> we started using a lot of tooling to ensure things don't break, and even
>>> developers have started pushing things to development branches instead of
>>> committing directly to master. I don't see why translators have to be the
>>> special snowflakes of the whole GNOME project, and break stuff for everyone
>>> else just because of their 20 years old workflow.
>>>
>>> Ciao,
>>>  Emmanuele.
>>>
>>> On Mon, 22 Jun 2020 at 11:03, Daniel Mustieles García via gnome-i18n <
>>> gnome-i18n@gnome.org> wrote:
>>>
>>>> Some time ago I talked about this with +Carlos Soriano
>>>>  . I asked him about the possibility of creating a
>>>> user's group in Gitlab, formed by some team coordinators, which will have
>>>> commit rights to be able to commit a bunch of translations due to the heavy
>>>> clickwork must be done in DL. Still waiting...
>>>>
>>>> Me (and some other team coordinators) got Git access before migration
>>>> to Gitlab, and it was not a problem. Having such rights will help us a lot
>>>> to be more agile maintaining and commiting translations. Yes, I currently
>>>> have those rights and can use an automated script [1] to ease my life, but
>>>> I don't have commit rights in some new modules (app-icon-preview,
>>>> shortwave...). I'd like to formerly request this feature/rigths. If we
>>>> found any problem with a wrong commit or something like that is quick and
>>>> easy to revert that commit; if a user with rights uses them for other
>>>> things that translations is quick and easy to revoke those privileges.
>>>> Advantages for us to maintain and keep translations up-to-date are huge.
>>>>
>>>> Please consider this request and let's work together to make it
>>>> possible in the best way.
>>>>
>>>> Best regards.
>>>>
>>>> [1]https://github.com/dmustieles/gnome_scripts/blob/master/gttk.sh
>>>>
>>>> El dom., 21 jun. 2020 a las 20:43, Matej Urban via gnome-i18n (<
>>>> gnome-i18n@gnome.org>) escribió:
>>>>
>>>>> Hello,
>>>>> some time ago

Re: Problems commiting damned-lies package

[Daniel Mustieles García via gnome-i18n]

Hi Emmanuele,

Just a quick question: which is the difference between commiting directly
into Git and commiting through DL? PO file checks are the same (or should
be), so commiting directly is not more dangerous than using DL. the same
checks DL makes into a PO file are done in my script, for example. If a PO
file breaks your module's building it doesn't matter if I committed it
directly into git or usind DL.

Also, note that not all translators will have commit rights: only a reduced
group of them. Breaking things in git is possible for both translators and
developers: that's one of the reasons we use Git, to be able to revert
commits and even revoke commit access to a person who breaks things several
times.

Of course, having a tool or a feature in DL to upload a bunch of PO files
and commit them directly would be the best option, but we currently don no
have it.

This is not a question of being 20 years o 20 days in the project: this is
a question of helping us with our work, because that work is as valid as
yours, and we all are responsible with it. pre-commit hooks can be
implemented (they are already, but we could study if are enough or not) to
avoid breaking things, but its really discouraging to follow DL's workflow
to commit a 1-modified string in a PO file. Multiply it by 20...

We don't want special snowflakes, we just want to be able to do our work in
the best way.

Regards

El lun., 22 jun. 2020 a las 12:30, Emmanuele Bassi ()
escribió:

> Hi;
>
> to be brutally honest, as a maintainer I don't want any translator to
> commit directly to Git—unless it's done to a separate branch and/or through
> merge requests.
>
> Translators do not build the projects they translate, and they don't (or
> cannot) know when they break things. The only way maintainers know that a
> broken translation happened is that suddenly the CI mails us, and then we
> have to hunt down what happened behind out backs. This is even worse when
> you realise something has broken a long time ago because the release
> process is now impossible.
>
> I'd rather have an automated, web UI tool that pushed changes to a branch
> and opened a merge request that ran the CI pipeline (and maybe the dist
> process), than allowing translators to commit to Git directly. I don't
> really care if some translator is an old hand that was around when GNOME
> used CVS and scripted their way to push to dozens of repositories at once;
> we started using a lot of tooling to ensure things don't break, and even
> developers have started pushing things to development branches instead of
> committing directly to master. I don't see why translators have to be the
> special snowflakes of the whole GNOME project, and break stuff for everyone
> else just because of their 20 years old workflow.
>
> Ciao,
>  Emmanuele.
>
> On Mon, 22 Jun 2020 at 11:03, Daniel Mustieles García via gnome-i18n <
> gnome-i18n@gnome.org> wrote:
>
>> Some time ago I talked about this with +Carlos Soriano
>>  . I asked him about the possibility of creating a
>> user's group in Gitlab, formed by some team coordinators, which will have
>> commit rights to be able to commit a bunch of translations due to the heavy
>> clickwork must be done in DL. Still waiting...
>>
>> Me (and some other team coordinators) got Git access before migration to
>> Gitlab, and it was not a problem. Having such rights will help us a lot to
>> be more agile maintaining and commiting translations. Yes, I currently have
>> those rights and can use an automated script [1] to ease my life, but I
>> don't have commit rights in some new modules (app-icon-preview,
>> shortwave...). I'd like to formerly request this feature/rigths. If we
>> found any problem with a wrong commit or something like that is quick and
>> easy to revert that commit; if a user with rights uses them for other
>> things that translations is quick and easy to revoke those privileges.
>> Advantages for us to maintain and keep translations up-to-date are huge.
>>
>> Please consider this request and let's work together to make it possible
>> in the best way.
>>
>> Best regards.
>>
>> [1]https://github.com/dmustieles/gnome_scripts/blob/master/gttk.sh
>>
>> El dom., 21 jun. 2020 a las 20:43, Matej Urban via gnome-i18n (<
>> gnome-i18n@gnome.org>) escribió:
>>
>>> Hello,
>>> some time ago I complained about inability to commit damned-lies package
>>> due to wrong access rights. Ok, I can live with that, but lately I get this
>>> error on many, many packages, especially new ones, like:
>>>
>>> app-icon-preview, authenticator, fractal, fragments, gnome-keysign,
>>> obfuscate, shortwave ... list goes on
>>>
>>>

Re: Problems commiting damned-lies package

[Daniel Mustieles García via gnome-i18n]

Some time ago I talked about this with +Carlos Soriano 
. I asked him about the possibility of creating a user's group in Gitlab,
formed by some team coordinators, which will have commit rights to be able
to commit a bunch of translations due to the heavy clickwork must be done
in DL. Still waiting...

Me (and some other team coordinators) got Git access before migration to
Gitlab, and it was not a problem. Having such rights will help us a lot to
be more agile maintaining and commiting translations. Yes, I currently have
those rights and can use an automated script [1] to ease my life, but I
don't have commit rights in some new modules (app-icon-preview,
shortwave...). I'd like to formerly request this feature/rigths. If we
found any problem with a wrong commit or something like that is quick and
easy to revert that commit; if a user with rights uses them for other
things that translations is quick and easy to revoke those privileges.
Advantages for us to maintain and keep translations up-to-date are huge.

Please consider this request and let's work together to make it possible in
the best way.

Best regards.

[1]https://github.com/dmustieles/gnome_scripts/blob/master/gttk.sh

El dom., 21 jun. 2020 a las 20:43, Matej Urban via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> Hello,
> some time ago I complained about inability to commit damned-lies package
> due to wrong access rights. Ok, I can live with that, but lately I get this
> error on many, many packages, especially new ones, like:
>
> app-icon-preview, authenticator, fractal, fragments, gnome-keysign,
> obfuscate, shortwave ... list goes on
>
> Is there any special reason why not even coordinators are able to do that
> the usual way? Yes, I know, there is another way to do it, but it is
> cumbersome and takes a lot, lot, lot time to do it and what is more
> important, each project has some specifics. For this reasons I do not push
> these ...
>
> Please advise or better, please bend at least for coordinators these rules.
>
> Thank you,
> Matej
>
>
> ___
> 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: Show danish translation of release notes

[Daniel Mustieles García via gnome-i18n]

Many thanks!

El lun., 15 jun. 2020 a las 13:47, Andrea Veri () escribió:

> Bart will be having a look soonish.
>
> Thanks,
>
> Il giorno lun 15 giu 2020 alle ore 12:07 Daniel Mustieles García <
> daniel.mustie...@gmail.com> ha scritto:
>
>> I've reopened the issue and Cc'ed Infrastructure.
>>
>> I've not been able to tag Andrea Veri in the issue. Cc'ing him here to
>> ask him if he can see any error in the server side.
>>
>> Thanks!
>>
>> El lun., 15 jun. 2020 a las 8:47, Claude Paroz ()
>> escribió:
>>
>>> Le 14.06.20 à 17:10, Andre Klapper a écrit :
>>> > Hi,
>>> >
>>> > On Sun, 2020-06-14 at 15:21 +0200, scootergrisen via gnome-i18n wrote:
>>> >> I would like to be able to see the danish translation of the release
>>> >> notes on https://help.gnome.org/misc/release-notes/3.36/ but i can't.
>>> >
>>> >
>>> https://gitlab.gnome.org/Teams/Engagement/release-notes/-/commit/cb947c4fae307f6d4741bc3ca64cc564518156cf
>>> > exists but
>>> https://help.gnome.org/misc/release-notes/3.36/index.html.da
>>> >  shows a 404. That's strange. Please file a bug report in GNOME Gitlab:
>>> > https://gitlab.gnome.org/Infrastructure/damned-lies/issues/
>>>
>>> Was already reported here:
>>> https://gitlab.gnome.org/Teams/Engagement/release-notes/-/issues/21
>>>
>>> No answer after 3 weeks :-(
>>>
>>> Claude
>>> --
>>> www.2xlibre.net
>>> ___
>>> gnome-i18n mailing list
>>> gnome-i18n@gnome.org
>>> https://mail.gnome.org/mailman/listinfo/gnome-i18n
>>>
>>
>
> --
> Cheers,
>
> Andrea
>
> Red Hatter,
> Fedora / EPEL packager,
> GNOME Infrastructure Team Coordinator,
> Former GNOME Foundation Board of Directors Secretary,
> GNOME Foundation Membership & Elections Committee Chairman
>
> Homepage: https://www.gnome.org/~av
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Show danish translation of release notes

[Daniel Mustieles García via gnome-i18n]

I've reopened the issue and Cc'ed Infrastructure.

I've not been able to tag Andrea Veri in the issue. Cc'ing him here to ask
him if he can see any error in the server side.

Thanks!

El lun., 15 jun. 2020 a las 8:47, Claude Paroz ()
escribió:

> Le 14.06.20 à 17:10, Andre Klapper a écrit :
> > Hi,
> >
> > On Sun, 2020-06-14 at 15:21 +0200, scootergrisen via gnome-i18n wrote:
> >> I would like to be able to see the danish translation of the release
> >> notes on https://help.gnome.org/misc/release-notes/3.36/ but i can't.
> >
> >
> https://gitlab.gnome.org/Teams/Engagement/release-notes/-/commit/cb947c4fae307f6d4741bc3ca64cc564518156cf
> > exists but https://help.gnome.org/misc/release-notes/3.36/index.html.da
> >  shows a 404. That's strange. Please file a bug report in GNOME Gitlab:
> > https://gitlab.gnome.org/Infrastructure/damned-lies/issues/
>
> Was already reported here:
> https://gitlab.gnome.org/Teams/Engagement/release-notes/-/issues/21
>
> No answer after 3 weeks :-(
>
> Claude
> --
> www.2xlibre.net
> ___
> 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: How to make strings fuzzy without changing them

[Daniel Mustieles García via gnome-i18n]

Po files should not be directly modified by developers 

In this case, if you think original string can be confusing, you can add a
comment or context to it. Not sure about comment, but context will make it
be marked as fuzzy, so problem solved.

Regards

El mié., 3 jun. 2020 17:41, Yuri Chornoivan via gnome-i18n <
gnome-i18n@gnome.org> escribió:

> середа, 3 червня 2020 р. 17:37:22 EEST scootergrisen via gnome-i18n
> написано:
> > I want to change "Results must:" to "Options:" or something similar in:
> >
> https://gitlab.gnome.org/GNOME/orca/-/blob/master/src/orca/orca-find.ui#L327
> >
> > But at the same time i want the 2 strings "_Match case" and "Match
> > _entire word only" made fuzzy or cleared in the po files.
> >
> >
> https://gitlab.gnome.org/GNOME/orca/-/blob/master/src/orca/orca-find.ui#L291
> > -306
> >
> > So translators can have a fresh look at all three strings because i
> > think they might be incorrect translated with the way it is currently
> > written.
>
> Thanks. For making our lives interesting.
>
> I think that the easiest way is to use a PCRE in the git repo directly.
> Something like (not tested)
>
> perl -pi -e 's!foo!\#,\ fuzzy\nfoo!' if !(/\#,\ fuzzy\n!) po/*.po
>
> Please do not do it though if you do not want to ask how to disappear
> completely and never been found. ;)
>
> Best regards,
> Yuri
>
>
> ___
> 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: GIMP update

[Daniel Mustieles García via gnome-i18n]

El vie., 29 may. 2020 a las 20:17, Milo () escribió:

>
> We had this same conversation in the past and gogo explained us his
> reasons. You can read it here:
> https://mail.gnome.org/archives/gnome-i18n/2019-September/msg00095.html
>
> Yes, I know that … it was no help at all … because none of my 26
> translations was ever reviewed since july 2019!
>
> In one word: meritocracy. Unless you create a new translation team or
>> current coordinator in missing for a long time, is your team's leader who
>> can promote you to prrofreader, commiter or even coordinator.
>>
> I don't care much about meritocracy, mediocracy, autocracy, democracy or
> any other *-cy. My point is that the coordinator is not responding and is
> not supportive – missing for a long time is not the problem, because he
> keeps translating. If the policy of "Team Coordinator Responsibilities"
> https://wiki.gnome.org/TranslationProject/TeamCoordinatorResponsibilities 
> isn't
> important, then just drop it! Until then, I do insist on the coordinator's
> compliance to the existing policy …
>

Yo should, at least when you ask how things are done. if you want to
collaborate in a project you must know how it works, Expecting your
collaborations be accepted at any time is not the proper way.

>
> > If your team coordinator wants to use Ubuntu's terminology for Orca it's
>>> his own decision: it might be wrong or not, but i18n cannot say which
>>> option is correct. If you don't agree with it yuo have two options: assume
>>> it won't change and follow that policy or leave the project. Sorry if it
>>> sounds too hard, but it's what I think (and what I would do in your
>>> situation).
>>>
>> Sorry, but translators translate for users. Blind users certainly have
> special needs. Ignoring such translations is simply ignorant/autocratic!
>

This is a team's coordinator decission. You might disagree with it, but
i18n cannot take a decision here. you should discuss about it with your
coordinator

>
> Again, we only see one side of the problem. We'd like to hear gogo's
>> version about this problem. I have not background about previous
>> conversations between gogo and you.
>>
> Well, he promised he'l respond, but there is no answer until now …
>
> Milo
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: GIMP update

[Daniel Mustieles García via gnome-i18n]

Thanks, but please remember to Cc i18n... You send your message only to me


Thanks!

El vie., 29 may. 2020 19:50, gogo gogić  escribió:

>
> So as I read this, it seems gogo is some kind of evil coordinator dictator
> who eats poor little translators.
>
> I've merged gimp without reviewing because release day.
>
> Tonight and tomorrow I'll go throught your translation commits and
> tommorow I will write some my observations, explanations and minimal rules
> to avoid this kind of problems and I hope we resolve this problem.
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: GIMP update

[Daniel Mustieles García via gnome-i18n]

Ah! here is the mailing thread I was looking for.

We had this same conversation in the past and gogo explained us his
reasons. You can read it here:

https://mail.gnome.org/archives/gnome-i18n/2019-September/msg00095.html

Don't if now it's the same case, but at least this gives us more light
about it.

I won't drop mu opinion about it, just read and take your own conclusions

El vie., 29 may. 2020 a las 10:24, Daniel Mustieles García (<
daniel.mustie...@gmail.com>) escribió:

>
>
> El vie., 29 may. 2020 a las 1:01, Milo () escribió:
>
>>
>> > 28.05.2020., u 09:33, Daniel Mustieles García <
>> daniel.mustie...@gmail.com> je napisao:
>> > So here is the root of the problem :-)
>> > You don't agree your team coordinator's criteria about translationsand
>> ask us to override him.
>> No, the root of the problem is the ignorance of the coordinator to
>> respond/react whatsoever. Most of my translations – no matter if revised or
>> completely new ones – have never been reviewed/commented or whatever.
>> Please do take a look at my list of translations at
>> https://l10n.gnome.org/users/milotype/ … none of them have ever seen the
>> day of light!
>>
>> > Let me explain how this works with an example. In Spanish we have two
>> options to translate the word "Folder": "Directorio" and "Carpeta". Log
>> time ago we decided to use "Carpeta" instead of "Directorio". Some
>> translators might not like this option, but since there is a team
>> coordinator that has decided to use it, there is no more discussion about
>> it. This is an internal decision we took in our team an i18n cannot
>> interfere on it.
>> Specific wording is NOT the main problem in this issue … but having
>> coordinators who acknowledge better translations would be a much
>> appreciated "feature". As probably everyone knows, language is not static –
>> and not every translator knows the correct translation for specific terms.
>> As an contra-example to Daniel's example: Gogo's translation for "Font" is
>> "Slovo", which simply means a letter (alphabetic character). But the term
>> "font" is a completely legitimate modern typographic term in Croatian (I am
>> a typographer myself!).
>>
>
> Agree with you, but it's his decision... we cannot interfere in this
> questions.
>
>>
>> In one of his response to my proposed change was:
>> "… ali zbog dosljednosti se prevodi tako, zato jer je glupo sad
>> prepravljati na desetke aplikacija i zajedničkih GNOME biblioteka koje
>> imaju po par stotina tisuća izraza prijevoda.
>> Zato da je sve ujednačeno a ne po pet naziva za istu riječ/radnju, to je
>> zbunjujuće za GNOME korisnike posebno nove."
>>
>> Basically saying the following:
>> "… but for the sake of consistency we translates it that way, because
>> it's stupid now to redo dozens of applications and common GNOME libraries
>> that have a few hundred thousand translation terms each.
>> Just to keep it all the same and not have five names for the same
>> word/action, as it's confusing for GNOME users, especially new ones."
>>
>> THAT IS a very poor approach to translating!
>>
>>
>> > Also, i18n cannot decide whether a translator is valid or not: it
>> depends on your team coordinator (basically because we don't know your
>> team's policy and most of us don't speak Croatian ;-) )
>> So what is the procedure to become a Commiter/Coordinator?
>>
>
> In one word: meritocracy. Unless you create a new translation team or
> current coordinator in missing for a long time, is your team's leader who
> can promote you to prrofreader, commiter or even coordinator.
>
>>
>>
>> > If your team coordinator wants to use Ubuntu's terminology for Orca
>> it's his own decision: it might be wrong or not, but i18n cannot say which
>> option is correct. If you don't agree with it yuo have two options: assume
>> it won't change and follow that policy or leave the project. Sorry if it
>> sounds too hard, but it's what I think (and what I would do in your
>> situation).
>> No offense, but that is a very poor approach, as mentioned above.
>>
>
> No, it isn't. This is not a democracy. Think about Linux kernel's
> development. I disagree with the way a part of the kernel is being
> developed. Linus Torvarlds doesn't take into account my proposals nor
> answers my emails. Should I propose override him and take myself his
> current role? Think about it, it's the same case.
>
>>
>>
>> > We could help you only if your coordinator was missing for a long time.
>> His las commit in Gitlab was 2 months ago... ok, he won't be in top 10
>> contributors ranking but at leas is not completely missing :-).
>> He is not missing … but he simply does not the job he's supposed to do as
>> coordinator:
>> see paragraph "Being Responsive to Contributors" at
>> https://wiki.gnome.org/TranslationProject/TeamCoordinatorResponsibilities
>
>
> Again, we only see one side of the problem. We'd like to hear gogo's
> version about this problem. I have not background about previous
> conversations between gogo and 

Re: GIMP update

[Daniel Mustieles García via gnome-i18n]

El vie., 29 may. 2020 a las 1:01, Milo () escribió:

>
> > 28.05.2020., u 09:33, Daniel Mustieles García <
> daniel.mustie...@gmail.com> je napisao:
> > So here is the root of the problem :-)
> > You don't agree your team coordinator's criteria about translationsand
> ask us to override him.
> No, the root of the problem is the ignorance of the coordinator to
> respond/react whatsoever. Most of my translations – no matter if revised or
> completely new ones – have never been reviewed/commented or whatever.
> Please do take a look at my list of translations at
> https://l10n.gnome.org/users/milotype/ … none of them have ever seen the
> day of light!
>
> > Let me explain how this works with an example. In Spanish we have two
> options to translate the word "Folder": "Directorio" and "Carpeta". Log
> time ago we decided to use "Carpeta" instead of "Directorio". Some
> translators might not like this option, but since there is a team
> coordinator that has decided to use it, there is no more discussion about
> it. This is an internal decision we took in our team an i18n cannot
> interfere on it.
> Specific wording is NOT the main problem in this issue … but having
> coordinators who acknowledge better translations would be a much
> appreciated "feature". As probably everyone knows, language is not static –
> and not every translator knows the correct translation for specific terms.
> As an contra-example to Daniel's example: Gogo's translation for "Font" is
> "Slovo", which simply means a letter (alphabetic character). But the term
> "font" is a completely legitimate modern typographic term in Croatian (I am
> a typographer myself!).
>

Agree with you, but it's his decision... we cannot interfere in this
questions.

>
> In one of his response to my proposed change was:
> "… ali zbog dosljednosti se prevodi tako, zato jer je glupo sad
> prepravljati na desetke aplikacija i zajedničkih GNOME biblioteka koje
> imaju po par stotina tisuća izraza prijevoda.
> Zato da je sve ujednačeno a ne po pet naziva za istu riječ/radnju, to je
> zbunjujuće za GNOME korisnike posebno nove."
>
> Basically saying the following:
> "… but for the sake of consistency we translates it that way, because it's
> stupid now to redo dozens of applications and common GNOME libraries that
> have a few hundred thousand translation terms each.
> Just to keep it all the same and not have five names for the same
> word/action, as it's confusing for GNOME users, especially new ones."
>
> THAT IS a very poor approach to translating!
>
>
> > Also, i18n cannot decide whether a translator is valid or not: it
> depends on your team coordinator (basically because we don't know your
> team's policy and most of us don't speak Croatian ;-) )
> So what is the procedure to become a Commiter/Coordinator?
>

In one word: meritocracy. Unless you create a new translation team or
current coordinator in missing for a long time, is your team's leader who
can promote you to prrofreader, commiter or even coordinator.

>
>
> > If your team coordinator wants to use Ubuntu's terminology for Orca it's
> his own decision: it might be wrong or not, but i18n cannot say which
> option is correct. If you don't agree with it yuo have two options: assume
> it won't change and follow that policy or leave the project. Sorry if it
> sounds too hard, but it's what I think (and what I would do in your
> situation).
> No offense, but that is a very poor approach, as mentioned above.
>

No, it isn't. This is not a democracy. Think about Linux kernel's
development. I disagree with the way a part of the kernel is being
developed. Linus Torvarlds doesn't take into account my proposals nor
answers my emails. Should I propose override him and take myself his
current role? Think about it, it's the same case.

>
>
> > We could help you only if your coordinator was missing for a long time.
> His las commit in Gitlab was 2 months ago... ok, he won't be in top 10
> contributors ranking but at leas is not completely missing :-).
> He is not missing … but he simply does not the job he's supposed to do as
> coordinator:
> see paragraph "Being Responsive to Contributors" at
> https://wiki.gnome.org/TranslationProject/TeamCoordinatorResponsibilities


Again, we only see one side of the problem. We'd like to hear gogo's
version about this problem. I have not background about previous
conversations between gogo and you.

@gogo gogić  could you please give us your point of
view about this?

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

Re: GIMP update

[Daniel Mustieles García via gnome-i18n]

I think the question about quality Vs quantity should be treated in another
thread.

Here we are talking about the problem between a translator and a team
coordinator.

Please keep conversations separated to ease reading and comprehension of
those separated issues.

Thanks in advance

El jue., 28 may. 2020 a las 11:05, Marco Ciampa via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> On Wed, May 27, 2020 at 04:48:54PM -0300, Rafael Fontenelle wrote:
> > Em qua., 27 de mai. de 2020 às 15:56, Marco Ciampa via gnome-i18n
> >  escreveu:
> > >
> > > On Wed, May 27, 2020 at 03:18:59PM -0300, Rafael Fontenelle wrote:
> > > > Em qua., 27 de mai. de 2020 às 12:32, Andre Klapper 
> escreveu:
> > > > >
> > > > > On Wed, 2020-05-27 at 14:31 +0200, Marco Ciampa via gnome-i18n
> wrote:
> > > > > > Well, my 10 cent is that a bad translation is better than no
> > > > > > translation at all.
> > > > >
> > > > > I'd very much disagree. No documentation at all is still better
> than
> > > > > wrong, misleading, frustrating documentation which wasted my time.
> > > > >
> > > >
> > > > To share one personal unpleasant experience: accessing GitHub Actions
> > > > documentation will automatically give me Brazilian Portuguese
> > > > translation, which is incomplete and in some cases with bad
> > > > translation. Even some keywords are translated, when they should not
> > > > (e.g. 'job' and 'schedule' keywords were translated). I always end up
> > > > switching to English, which as a translator (not GitHub's though) is
> > > > very disappointing.
> > >
> > > 1) you know english
> > > 2) you are a translator
> > >
> > > Please stop thinking that all people are like us.
> >
> > Well, if the person can't read English, having a documentation that is
> > partially translated with important strings translated (when should
> > not) won't help much I think?
>
> It will help anyway. For the untranslated parts, as you wrote below,
> there are automatic tools that all agree to that they are useful, even if
> their translation is horrible and often completely wrong, right?
>
> How can be that google even when it fails miserably at translating is a
> useful tool and the human translations that are often much better are a
> mistake?
>
> > >
> > > > So, yes, quality translation is very important.
> > >
> > > I never said what quality is not important.
> > >
> > > I said that a bad translation, for people that do not understand
> English
> > > _at all_ is better than nothing (=English). Please think at some
> oriental
> > > or arabic user for a moment and try to be in their shoes for a moment.
> >
> > I am in those shoes in some cases when trying to read a site content
> > in a language I don't know, like Russian or Germany.  In cases like
> > these, one can use a machine translator like Google Translate.
>
> I agree, see above...
>
> --
>
> Saluton,
> Marco Ciampa
> ___
> 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: GIMP update

[Daniel Mustieles García via gnome-i18n]

So here is the root of the problem :-)

You don't agree your team coordinator's criteria about translationsand ask
us to override him. Let me explain how this works with an example. In
Spanish we have two options to translate the word "Folder": "Directorio"
and "Carpeta". Log time ago we decided to use "Carpeta" instead of
"Directorio". Some translators might not like this option, but since there
is a team coordinator that has decided to use it, there is no more
discussion about it. This is an internal decision we took in our team an
i18n cannot interfere on it.

Also, i18n cannot decide whether a translator is valid or not: it depends
on your team coordinator (basically because we don't know your team's
policy and most of us don't speak Croatian ;-) )

If your team coordinator wants to use Ubuntu's terminology for Orca it's
his own decision: it might be wrong or not, but i18n cannot say which
option is correct. If you don't agree with it yuo have two options: assume
it won't change and follow that policy or leave the project. Sorry if it
sounds too hard, but it's what I think (and what I would do in your
situation).

We could help you only if your coordinator was missing for a long time. His
las commit in Gitlab was 2 months ago... ok, he won't be in top 10
contributors ranking but at leas is not completely missing :-). I don't
know if you have had any conversation with your coordinator about this, I
don't know what your team's policy is... I know nothing about this, only
see one side of the problem so (at least me, I'd like to hear other i18n
members opinion) I cannot take an "invasive" decision about this (commiting
yout translations or granting you commiter role would be invasive
decisions).

I Cc'ed gogo in a previous message but someone removed him... please don't
do that, since we want him to be up-to-date about this discussion and hear
his opinion.

As I see, this is an internal problem in your transaltion team and we
cannot interfere for this momment. If your team coordinator was away for a
long time we could re-consider our intervention but for now I think we
should not.

Regards

El mié., 27 may. 2020 a las 23:30, Milo () escribió:

> I thank everybody's input … the only person not replying is gogo himself …
> so go figure!?
>
> As outlined before, I'm no novice/beginner. I'm trilingual (hr, de, en),
> bilingual natively (hr, de), with some knowledge of other european
> languages, which helps me a lot to compare translations … I've translated
> many open source software of different kinds in the past two years and have
> never experienced such obstrusion/ignorance.
>
> As a mater of fact, because of gogo's attitude, GNOME's Croatian
> translation team lately lost a Croatian native speaker as translator, who
> was translating "orca" (program for blind users). And yes, the person IS
> blind – so, who knows better? We are both translating "nvda" (screen reader
> for blind users). Unfortunately, while complaining about a gogo's reply on
> "orca" translation (which never got released), he responded only to my
> email address, so here is his response:
>
> *Od: *
> *Predmet: **RE: New release of GIMP planned for February 14*
> *Datum: *10. veljače 2020. u 22:48:29 CET
> *Za: *"'Milo Ivir'" 
>
> Hi,
> The same is for orca.
> Translation coordinator is here to help, not to reinforce their
> terminology and suggest the terminology from ubuntu.
> I want to be terminology independent and I want to use terminology
> familiar by users, written in a natural language.
>
>
> So, again, please let us find a solution! Presuming that my translations
> (or other) are incorrect and only gogo's are correct, is NOT the right way.
>
> Cheers,
> Milo
>
> P.S. Who decides and how, whether a translator has a certain quality?
>
>
> 27.05.2020., u 20:56, Marco Ciampa via gnome-i18n 
> je napisao:
>
> On Wed, May 27, 2020 at 03:18:59PM -0300, Rafael Fontenelle wrote:
>
> Em qua., 27 de mai. de 2020 às 12:32, Andre Klapper 
> escreveu:
>
>
> On Wed, 2020-05-27 at 14:31 +0200, Marco Ciampa via gnome-i18n wrote:
>
> Well, my 10 cent is that a bad translation is better than no
> translation at all.
>
>
> I'd very much disagree. No documentation at all is still better than
> wrong, misleading, frustrating documentation which wasted my time.
>
>
> To share one personal unpleasant experience: accessing GitHub Actions
> documentation will automatically give me Brazilian Portuguese
> translation, which is incomplete and in some cases with bad
> translation. Even some keywords are translated, when they should not
> (e.g. 'job' and 'schedule' keywords were translated). I always end up
> switching to English, which as a translator (not GitHub's though) is
> very disappointing.
>
>
> 1) you know english
> 2) you are a translator
>
> Please stop thinking that all people are like us.
>
> So, yes, quality translation is very important.
>
>
> I never said what quality is not important.
>
> I said that a bad translation, for people that do 

Re: GIMP update

[Daniel Mustieles García via gnome-i18n]

Note that a "bad translation" can be an "incorrect translation" and it can
confuse users or make them fall into mistakes when performing some
operations. I.e. imagine I translate "Delete file" as "Copy file"... it's a
mistake, not intentionated but it might cause a disaster in some
contexts... that's why translations must be reviewed ;-)

But since this a per-translation-team policy I have nothing to say... in
Spanish team we have harder policies than other teams might have... well,
that was our choice and do not expect other teams to follow them.

Regards!

El mié., 27 may. 2020 a las 14:32, Marco Ciampa via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> Well, my 10 cent is that a bad translation is better than no translation
> at all.
> 1) you can always disable the translation if you find it disturbing
> 2) a bad translation can be improved and it is simpler (IMHO) working on
> it than
>from scratch.
>
> --
>
> Saluton,
> Marco Ciampa
> ___
> 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: GIMP update

[Daniel Mustieles García via gnome-i18n]

Hi Milo,

I don't remember what I said in September and i18n archives only shows a
conversation in where you asked someone to commit your translations and I
wrote directly to Croatian coordinator but got no response.

Please note that we cannot give you commiter role directly because we
cannot evaluate if your translations are ok or not. If your team
coordinator is missing for a long time you can write us to explain the
problem and maybe we can try to find a solution for it (I say "maybe"
because I'm not sure about to deal with this).

Apart from this, about quality and quantity I can only talk about my team
(Spanish): we always prefer quality over quantity. Having a lot of strings
translated or modules with 100% in stats but a very low quality of
translations is bad for us. In this issue we only see one side of the
problem; we have not Goran's point of view about this so we (at least me)
cannot take a decision about this.

@Goran, we' d like to hear you about this issue. Could you please tell us
why Milo's translations are not being commited or even the possibility to
grant him commiter role?

Thanks

El mié., 27 may. 2020 a las 7:36, Milo () escribió:

> Can someone PLASE finally commit/release (or whatever the term may be)
> my Croatian translations of GNOME modules at
> https://l10n.gnome.org/users/milotype/!!?? Especially for GIMP, as they
> are updating the application!
>
> I'm really sick and tired of trying to get my Croatian translations in the
> GNOME translation project commited/released. The coordinator does not
> comment/correct anything. BTW, because of the ignorance of the Croatian
> coordinator, we actually lost a Croatian translator for the module "orca"
> (the person who was translating, is actually a blind person!!)
>
> As Daniel Mustieles replied on 16th september 2019 to my email, that my
> objection about translations " … are only "keep quality" thinks in our
> side" … it is simply not true! Uniformity/wrong translation is NOT the
> essence of translation …
>
> PLEASE help me solve this issue, as it's an issue since July 2019!!
>
> Thank you!
>
>
> 26.05.2020., u 16:06, Alexandre Prokoudine via gnome-i18n <
> gnome-i18n@gnome.org> je napisao:
>
> Hello,
>
> We are planning to release GIMP 2.10.20 and 2.99.2 later this week. This
> means you might want updating translations in both gimp-2-10 and master
> branches.
>
> Alex
> ___
> 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
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Evolution stats in DL are not updated

[Daniel Mustieles García via gnome-i18n]

The commits I did today (~3 hours ago) were made directly from command line
and they wen ok:

https://gitlab.gnome.org/GNOME/epiphany/-/commit/07f89a83001cf6a4e3970c99e96e817141d2b362

The problem is that DL is not updating stats. Following the same example
with Epiphany, last update was done "2020-05-16 10:32 a.m." so the commit I
did today is not being reflected in DL.

Anyway, if you need me to make another commit from command line I can do
it, just let me know ;-)

Thanks!

El lun., 18 may. 2020 a las 12:58, Andrea Veri () escribió:

> That was related as it was preventing the post receive hook to run
> properly. It was fixed this morning, if any of you could send in a commit
> and confirm it'd be lovely.
>
> Thanks!
>
> Il giorno lun 18 mag 2020 alle ore 12:54 Jordi Mas 
> ha scritto:
>
>> Hello,
>>
>> When you commit from command line (at least last night) you got this
>> error:
>>
>>
>>
>>
>>
>>
>>
>> *remote:
>> /opt/gitlab/embedded/service/gitlab-shell/hooks/post-receive.d/post-receive:
>> line 35: /home/admin/bin/git/gnome-post-receive-email: Permission
>> deniedremote: Traceback (most recent call last):remote:   File
>> "/home/admin/bin/git/post-receive-notify-l10n", line 34, in remote:
>> main()remote:   File "/home/admin/bin/git/post-receive-notify-l10n",
>> line 25, in mainremote: branch_name =
>> get_branch_name(sys.stdin.readline().split()[2])remote: IndexError: list
>> index out of range*
>>
>> It may be related
>>
>> Hopefully it helps 
>>
>> Jordi,
>>
>> On Mon, May 18, 2020 at 10:25 AM Daniel Mustieles García via gnome-i18n <
>> gnome-i18n@gnome.org> wrote:
>>
>>> Hi Claude,
>>>
>>> Sorry to bother you again with the same issue, but it DL is not updating
>>> statistics... I've committed some translations (epiphany, swell-foop, for
>>> example) and stats are not updated.
>>>
>>> For example, DL says that Epiphany las update was on 2020-05-16 10:32 a.m
>>>
>>> Thanks in advance for your help
>>>
>>> El sáb., 16 may. 2020 a las 11:32, Daniel Mustieles García (<
>>> daniel.mustie...@gmail.com>) escribió:
>>>
>>>> Don't worry, it seems to be working properly now :-)
>>>>
>>>> Thanks!
>>>>
>>>> El vie., 15 may. 2020 12:08, Andrea Veri  escribió:
>>>>
>>>>> Daniel,
>>>>>
>>>>> forgot to mention the API came back up after a few minutes since your
>>>>> original email yesterday.
>>>>>
>>>>> Please let me know if you see anything else not being functional.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Il giorno gio 14 mag 2020 alle ore 17:25 Daniel Mustieles García
>>>>>  ha scritto:
>>>>> >
>>>>> > Hi Andrea,
>>>>> >
>>>>> > I've just notice the API section in Damned Lies it's not working:
>>>>> >
>>>>> > https://l10n.gnome.org/api/v1/modules/pitivi
>>>>> >
>>>>> > Could you please review it? It is needed by Gtranslator to be able
>>>>> to select and download PO files into the application.
>>>>> >
>>>>> > Thanks in advance for your help
>>>>> >
>>>>> > El jue., 14 may. 2020 a las 15:41, Daniel Mustieles García (<
>>>>> daniel.mustie...@gmail.com>) escribió:
>>>>> >>
>>>>> >> It seems that GIMP-help now works properly (this moduleset was the
>>>>> biggest problem due to timeouts when commiting PO files).
>>>>> >>
>>>>> >> I will test it in the following days and if I see something wrong I
>>>>> will notice you.
>>>>> >>
>>>>> >> Many thanks for your help!
>>>>> >>
>>>>> >> El jue., 14 may. 2020 a las 15:29, Yuri Chornoivan via gnome-i18n (<
>>>>> gnome-i18n@gnome.org>) escribió:
>>>>> >>>
>>>>> >>> четвер, 14 травня 2020 р. 15:49:26 EEST Andrea Veri написано:
>>>>> >>> > Translators,
>>>>> >>> >
>>>>> >>> > we just completed the migration to a different storage backend,
>>>>> please
>>>>> >>> > let us know whether how that contributed to speed up your
>>>>> day

Re: Evolution stats in DL are not updated

[Daniel Mustieles García via gnome-i18n]

 > no interest from your side. We keep mentioning on IRC and other
>> mediums
>> >>> > > we're around to offer our knowledge in order to fullfil your
>> needs when
>> >>> > > it comes to maintaining this service properly.
>> >>> > >
>> >>> > > That said, we'll look into moving that volume into Ceph late next
>> week.
>> >>> > >
>> >>> > > [1]
>> >>> > >
>> https://www.dragonsreach.it/2020/03/30/2020-03-30-gnome-infrastructure-up
>> >>> > > dates>
>> >>> > > Il gio 30 apr 2020, 22:24 Claude Paroz  ha
>> scritto:
>> >>> > >> Hi Daniel,
>> >>> > >>
>> >>> > >> Looks like the stats ar now OK again.
>> >>> > >> I'm sorry for that (it also happened for gtk recently). There is
>> a major
>> >>> > >> problem right now with the D-L hosting. The disk performance of
>> the
>> >>> > >> hosting platform is not sufficient for D-L needs (much slower
>> than my
>> >>> > >> 9-year old personal machine!).
>> >>> > >>
>> >>> > >> I'm convinced the GNOME sysadmin team is working hard on the
>> >>> > >> infrastructure, but since D-L moved to the OpenShift platform, it
>> >>> > >> occasioned a lot of issues and I spent more time on it that I
>> would want.
>> >>> > >> I'm pleading to get back to a traditional VM infrastructure, but
>> I'm not
>> >>> > >> the one who can decide this currently.
>> >>> > >> So sorry for you translators, hopefully we can find a solution
>> in a not
>> >>> > >> too far future.
>> >>> > >>
>> >>> > >> Claude
>> >>> > >>
>> >>> > >> Le 30.04.20 à 11:40, Daniel Mustieles García via gnome-i18n a
>> écrit :
>> >>> > >> > Hi Claude,
>> >>> > >> >
>> >>> > >> > I've noticed Evolution stats in DL are not being updated.
>> Doing it
>> >>> > >> > manually also doesn't work.
>> >>> > >> >
>> >>> > >> > Last update was done 2 days ago so changes done yesterday are
>> not
>> >>> > >> > reflected.
>> >>> > >> >
>> >>> > >> > Could you please review it.
>> >>> > >> >
>> >>> > >> > Thanks in advance!
>> >>> > >> >
>> >>> > >> > https://l10n.gnome.org/module/evolution/
>> >>> >
>> >>> > --
>> >>> > Cheers,
>> >>> >
>> >>> > Andrea
>> >>> >
>> >>> > Red Hatter,
>> >>> > Fedora / EPEL packager,
>> >>> > GNOME Infrastructure Team Coordinator,
>> >>> > Former GNOME Foundation Board of Directors Secretary,
>> >>> > GNOME Foundation Membership & Elections Committee Chairman
>> >>> >
>> >>> > Homepage: https://www.gnome.org/~av
>> >>> > ___
>> >>> > 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
>>
>>
>>
>> --
>> Cheers,
>>
>> Andrea
>>
>> Red Hatter,
>> Fedora / EPEL packager,
>> GNOME Infrastructure Team Coordinator,
>> Former GNOME Foundation Board of Directors Secretary,
>> GNOME Foundation Membership & Elections Committee Chairman
>>
>> Homepage: https://www.gnome.org/~av
>>
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Evolution stats in DL are not updated

[Daniel Mustieles García via gnome-i18n]

Don't worry, it seems to be working properly now :-)

Thanks!

El vie., 15 may. 2020 12:08, Andrea Veri  escribió:

> Daniel,
>
> forgot to mention the API came back up after a few minutes since your
> original email yesterday.
>
> Please let me know if you see anything else not being functional.
>
> Thanks!
>
> Il giorno gio 14 mag 2020 alle ore 17:25 Daniel Mustieles García
>  ha scritto:
> >
> > Hi Andrea,
> >
> > I've just notice the API section in Damned Lies it's not working:
> >
> > https://l10n.gnome.org/api/v1/modules/pitivi
> >
> > Could you please review it? It is needed by Gtranslator to be able to
> select and download PO files into the application.
> >
> > Thanks in advance for your help
> >
> > El jue., 14 may. 2020 a las 15:41, Daniel Mustieles García (<
> daniel.mustie...@gmail.com>) escribió:
> >>
> >> It seems that GIMP-help now works properly (this moduleset was the
> biggest problem due to timeouts when commiting PO files).
> >>
> >> I will test it in the following days and if I see something wrong I
> will notice you.
> >>
> >> Many thanks for your help!
> >>
> >> El jue., 14 may. 2020 a las 15:29, Yuri Chornoivan via gnome-i18n (<
> gnome-i18n@gnome.org>) escribió:
> >>>
> >>> четвер, 14 травня 2020 р. 15:49:26 EEST Andrea Veri написано:
> >>> > Translators,
> >>> >
> >>> > we just completed the migration to a different storage backend,
> please
> >>> > let us know whether how that contributed to speed up your day-to-day
> >>> > operations.
> >>> >
> >>> > Thanks!
> >>>
> >>> Hi,
> >>>
> >>> Works much faster. Many thanks for your work.
> >>>
> >>> Best regards,
> >>> Yuri
> >>>
> >>> > Il giorno ven 1 mag 2020 alle ore 14:07 Andrea Veri 
> ha
> >>> scritto:
> >>> > > Claude,
> >>> > >
> >>> > > Your statements are pretty unfair I have to be honest. The current
> issue
> >>> > > is that glusterfs doesn't seem to perform well when trying to cope
> with
> >>> > > big repositories such as gtk or gimp. The solution there is mainly
> moving
> >>> > > this data out of it into the brand new Ceph cluster we deployed and
> >>> > > blogged about [1] recently.
> >>> > >
> >>> > > Openshift is a platform that we introduced for the community and
> used /
> >>> > > loved by multiple contributors as of today. It introduced, as
> every new
> >>> > > technology, a learning curve that has to be filled before the
> actual
> >>> > > features can become of good use. Saying I want to go back to a
> plain VM
> >>> > > is the old please give me back a bare metal because I want all the
> >>> > > performances for myself when the world transitioned off to virtual
> >>> > > machines ages ago. It doesn't scale, adds maintenance burdens, and
> it's
> >>> > > definitely unnecessary.
> >>> > >
> >>> > > The GNOME Infrastructure Team has made sure l10n runs beautifully
> with the
> >>> > > new platform with a service degradation that only happened during
> the
> >>> > > datacenter migration we recently performed and fixed right
> afterwards. On
> >>> > > top of that we made sure the entire VM to container migration was
> >>> > > performed in its *entirety* by us, we offered our help to let you
> >>> > > understand how the platform works to get you up to speed with
> little to
> >>> > > no interest from your side. We keep mentioning on IRC and other
> mediums
> >>> > > we're around to offer our knowledge in order to fullfil your needs
> when
> >>> > > it comes to maintaining this service properly.
> >>> > >
> >>> > > That said, we'll look into moving that volume into Ceph late next
> week.
> >>> > >
> >>> > > [1]
> >>> > >
> https://www.dragonsreach.it/2020/03/30/2020-03-30-gnome-infrastructure-up
> >>> > > dates>
> >>> > > Il gio 30 apr 2020, 22:24 Claude Paroz  ha
> scritto:
> >>> > >> Hi Daniel,
> >>> > >>
> >>> > >> Looks like the sta

Re: Evolution stats in DL are not updated

[Daniel Mustieles García via gnome-i18n]

Hi Andrea,

I've just notice the API section in Damned Lies it's not working:

https://l10n.gnome.org/api/v1/modules/pitivi

Could you please review it? It is needed by Gtranslator to be able to
select and download PO files into the application.

Thanks in advance for your help

El jue., 14 may. 2020 a las 15:41, Daniel Mustieles García (<
daniel.mustie...@gmail.com>) escribió:

> It seems that GIMP-help now works properly (this moduleset was the biggest
> problem due to timeouts when commiting PO files).
>
> I will test it in the following days and if I see something wrong I will
> notice you.
>
> Many thanks for your help!
>
> El jue., 14 may. 2020 a las 15:29, Yuri Chornoivan via gnome-i18n (<
> gnome-i18n@gnome.org>) escribió:
>
>> четвер, 14 травня 2020 р. 15:49:26 EEST Andrea Veri написано:
>> > Translators,
>> >
>> > we just completed the migration to a different storage backend, please
>> > let us know whether how that contributed to speed up your day-to-day
>> > operations.
>> >
>> > Thanks!
>>
>> Hi,
>>
>> Works much faster. Many thanks for your work.
>>
>> Best regards,
>> Yuri
>>
>> > Il giorno ven 1 mag 2020 alle ore 14:07 Andrea Veri  ha
>> scritto:
>> > > Claude,
>> > >
>> > > Your statements are pretty unfair I have to be honest. The current
>> issue
>> > > is that glusterfs doesn't seem to perform well when trying to cope
>> with
>> > > big repositories such as gtk or gimp. The solution there is mainly
>> moving
>> > > this data out of it into the brand new Ceph cluster we deployed and
>> > > blogged about [1] recently.
>> > >
>> > > Openshift is a platform that we introduced for the community and used
>> /
>> > > loved by multiple contributors as of today. It introduced, as every
>> new
>> > > technology, a learning curve that has to be filled before the actual
>> > > features can become of good use. Saying I want to go back to a plain
>> VM
>> > > is the old please give me back a bare metal because I want all the
>> > > performances for myself when the world transitioned off to virtual
>> > > machines ages ago. It doesn't scale, adds maintenance burdens, and
>> it's
>> > > definitely unnecessary.
>> > >
>> > > The GNOME Infrastructure Team has made sure l10n runs beautifully
>> with the
>> > > new platform with a service degradation that only happened during the
>> > > datacenter migration we recently performed and fixed right
>> afterwards. On
>> > > top of that we made sure the entire VM to container migration was
>> > > performed in its *entirety* by us, we offered our help to let you
>> > > understand how the platform works to get you up to speed with little
>> to
>> > > no interest from your side. We keep mentioning on IRC and other
>> mediums
>> > > we're around to offer our knowledge in order to fullfil your needs
>> when
>> > > it comes to maintaining this service properly.
>> > >
>> > > That said, we'll look into moving that volume into Ceph late next
>> week.
>> > >
>> > > [1]
>> > >
>> https://www.dragonsreach.it/2020/03/30/2020-03-30-gnome-infrastructure-up
>> > > dates>
>> > > Il gio 30 apr 2020, 22:24 Claude Paroz  ha
>> scritto:
>> > >> Hi Daniel,
>> > >>
>> > >> Looks like the stats ar now OK again.
>> > >> I'm sorry for that (it also happened for gtk recently). There is a
>> major
>> > >> problem right now with the D-L hosting. The disk performance of the
>> > >> hosting platform is not sufficient for D-L needs (much slower than my
>> > >> 9-year old personal machine!).
>> > >>
>> > >> I'm convinced the GNOME sysadmin team is working hard on the
>> > >> infrastructure, but since D-L moved to the OpenShift platform, it
>> > >> occasioned a lot of issues and I spent more time on it that I would
>> want.
>> > >> I'm pleading to get back to a traditional VM infrastructure, but I'm
>> not
>> > >> the one who can decide this currently.
>> > >> So sorry for you translators, hopefully we can find a solution in a
>> not
>> > >> too far future.
>> > >>
>> > >> Claude
>> > >>
>> > >> Le 30.04.20 à 11:40, Daniel Mustieles