[DL] String additions to 'gnome-builder.master'

2019-02-26 Thread GNOME Status Pages
This is an automatic notification from status generation scripts on:
https://l10n.gnome.org.

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

+ "Keywords"::"editor line spacing font monospace"
+ "Line Spacing"
+ "Number of pixels above and below editor lines"
+ "The number of pixels to include above and below lines in the editor."

Note that this doesn't directly indicate a string freeze break, but it
might be worth investigating.
https://gitlab.gnome.org/GNOME/gnome-builder/commits/master
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


[DL] String additions to 'epiphany.gnome-3-32'

2019-02-26 Thread GNOME Status Pages
This is an automatic notification from status generation scripts on:
https://l10n.gnome.org.

There have been following string additions to module 'epiphany.gnome-3-32':

+ "Maximum number of web processes created at the same time when using 
“one-secondary-process-per-web-view” model"
+ "Process model"
+ "This option allows to set the process model used. Use 
“shared-secondary-process” to use a single web process shared by all the tabs 
and “one-secondary-process-per-web-view” to use a different web process for 
each tab."
+ "This option sets a limit to the number of web processes that will be 
used at the same time for the “one-secondary-process-per-web-view” model. The 
default value is “0” and means no limit."

Note that this doesn't directly indicate a string freeze break, but it
might be worth investigating.
https://gitlab.gnome.org/GNOME/epiphany/commits/gnome-3-32
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


[DL] String additions to 'gnome-control-center.master'

2019-02-26 Thread GNOME Status Pages
This is an automatic notification from status generation scripts on:
https://l10n.gnome.org.

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

+ "Adjust for TV"
+ "Refresh Rate"
+ "display setting"::"Orientation"
+ "display setting"::"Resolution"

Note that this doesn't directly indicate a string freeze break, but it
might be worth investigating.
https://gitlab.gnome.org/GNOME/gnome-control-center/commits/master
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


[DL] String additions to 'gnome-control-center.master'

2019-02-26 Thread GNOME Status Pages
This is an automatic notification from status generation scripts on:
https://l10n.gnome.org.

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

+ "printing option"::"Resolution"

Note that this doesn't directly indicate a string freeze break, but it
might be worth investigating.
https://gitlab.gnome.org/GNOME/gnome-control-center/commits/master
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Strings in display panel marked for translation and added context in g-c-c

2019-02-26 Thread Daniel Mustieles García via gnome-i18n
2/2 from i18n

Thanks!

El mar., 26 feb. 2019 20:17, Piotr Drąg via gnome-i18n 
escribió:

> wt., 26 lut 2019 o 19:56 Benjamin Berg 
> napisał(a):
> >
> > Hi,
> >
> > during the port of the display panel to use UI files and the new
> > libhandy widgets, a few strings were not marked as translatable. Also,
> > these strings and the printer panel strings need more context.
> >
> > The requested changes are:
> >  * Mark display setting strings as translatable (regression)
> >  * Add context to the above strings (#393, not a regression)
> >  * Add context to printer options (#394, not a regression)
> >
> > See
> >   https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/414
> >
> > Benjamin
> >
> > PS: The regression probably happened due to glade not allowing
> > translation of the libhandy widget, upstream fix for this is:
> > https://source.puri.sm/Librem5/libhandy/merge_requests/236
>
> 1/2 from i18n.
>
> Best regards,
>
> --
> 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


[DL] String additions to 'seahorse.master'

2019-02-26 Thread GNOME Status Pages
This is an automatic notification from status generation scripts on:
https://l10n.gnome.org.

There have been following string additions to module 'seahorse.master':

+ "_About Passwords and Keys"

Note that this doesn't directly indicate a string freeze break, but it
might be worth investigating.
https://gitlab.gnome.org/GNOME/seahorse/commits/master
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Strings in display panel marked for translation and added context in g-c-c

2019-02-26 Thread Piotr Drąg via gnome-i18n
wt., 26 lut 2019 o 19:56 Benjamin Berg  napisał(a):
>
> Hi,
>
> during the port of the display panel to use UI files and the new
> libhandy widgets, a few strings were not marked as translatable. Also,
> these strings and the printer panel strings need more context.
>
> The requested changes are:
>  * Mark display setting strings as translatable (regression)
>  * Add context to the above strings (#393, not a regression)
>  * Add context to printer options (#394, not a regression)
>
> See
>   https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/414
>
> Benjamin
>
> PS: The regression probably happened due to glade not allowing
> translation of the libhandy widget, upstream fix for this is:
> https://source.puri.sm/Librem5/libhandy/merge_requests/236

1/2 from i18n.

Best regards,

-- 
Piotr Drąg
https://piotrdrag.fedorapeople.org
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Strings in display panel marked for translation and added context in g-c-c

2019-02-26 Thread Benjamin Berg
Hi,

during the port of the display panel to use UI files and the new
libhandy widgets, a few strings were not marked as translatable. Also,
these strings and the printer panel strings need more context.

The requested changes are:
 * Mark display setting strings as translatable (regression)
 * Add context to the above strings (#393, not a regression)
 * Add context to printer options (#394, not a regression)

See
  https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/414

Benjamin

PS: The regression probably happened due to glade not allowing
translation of the libhandy widget, upstream fix for this is: 
https://source.puri.sm/Librem5/libhandy/merge_requests/236


signature.asc
Description: This is a digitally signed message part
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: String/UI Freeze Break (#2) - totem

2019-02-26 Thread Bastien Nocera
On Tue, 2019-02-26 at 18:34 +0100, Andre Klapper wrote:
> On Tue, 2019-02-26 at 15:58 +, Emmanuele Bassi via release-team
> wrote:
> > On Tue, 26 Feb 2019 at 15:32, Bastien Nocera 
> > wrote:
> > > On Mon, 2019-02-25 at 13:52 +0100, Piotr Drąg wrote:
> > > > pon., 25 lut 2019 o 13:44 Bastien Nocera 
> > > > napisał(a):
> > > > > Hey,
> > > > > 
> > > > > This removes some UI which isn't connected to anything
> > > > > anymore.
> > > > > There
> > > > > aren't any screenshots in the user documentation, and the
> > > > > removed
> > > > > paragraph would automatically be dropped from user docs
> > > > > translations:
> > > > > https://gitlab.gnome.org/GNOME/totem/merge_requests/79
> > > > > 
> > > > 
> > > > It doesn’t break the string freeze, but thanks a lot for the
> > > > notification!
> > > 
> > > Could the release team weigh in with some feedback, please?
> > 
> > Looks very low impact, so +1 from me (r-t).
> 
> r-t 2/2 - yes please.

Merged! Thanks for the replies.

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


Re: String/UI Freeze Break (#2) - totem

2019-02-26 Thread Andre Klapper
On Tue, 2019-02-26 at 15:58 +, Emmanuele Bassi via release-team
wrote:
> On Tue, 26 Feb 2019 at 15:32, Bastien Nocera 
> wrote:
> > On Mon, 2019-02-25 at 13:52 +0100, Piotr Drąg wrote:
> > > pon., 25 lut 2019 o 13:44 Bastien Nocera 
> > > napisał(a):
> > > > Hey,
> > > > 
> > > > This removes some UI which isn't connected to anything anymore.
> > > > There
> > > > aren't any screenshots in the user documentation, and the removed
> > > > paragraph would automatically be dropped from user docs
> > > > translations:
> > > > https://gitlab.gnome.org/GNOME/totem/merge_requests/79
> > > > 
> > > 
> > > It doesn’t break the string freeze, but thanks a lot for the
> > > notification!
> > 
> > Could the release team weigh in with some feedback, please?
> 
> Looks very low impact, so +1 from me (r-t).

r-t 2/2 - yes please.

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


Re: String/UI Freeze Break (#2) - totem

2019-02-26 Thread Emmanuele Bassi via gnome-i18n
On Tue, 26 Feb 2019 at 15:32, Bastien Nocera  wrote:

> On Mon, 2019-02-25 at 13:52 +0100, Piotr Drąg wrote:
> > pon., 25 lut 2019 o 13:44 Bastien Nocera 
> > napisał(a):
> > > Hey,
> > >
> > > This removes some UI which isn't connected to anything anymore.
> > > There
> > > aren't any screenshots in the user documentation, and the removed
> > > paragraph would automatically be dropped from user docs
> > > translations:
> > > https://gitlab.gnome.org/GNOME/totem/merge_requests/79
> > >
> >
> > It doesn’t break the string freeze, but thanks a lot for the
> > notification!
>
> Could the release team weigh in with some feedback, please?
>

Looks very low impact, so +1 from me (r-t).

Ciao,
 Emmanuele.

-- 
https://www.bassi.io
[@] ebassi [@gmail.com]
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: String/UI Freeze Break (#2) - totem

2019-02-26 Thread Bastien Nocera
On Mon, 2019-02-25 at 13:52 +0100, Piotr Drąg wrote:
> pon., 25 lut 2019 o 13:44 Bastien Nocera 
> napisał(a):
> > Hey,
> > 
> > This removes some UI which isn't connected to anything anymore.
> > There
> > aren't any screenshots in the user documentation, and the removed
> > paragraph would automatically be dropped from user docs
> > translations:
> > https://gitlab.gnome.org/GNOME/totem/merge_requests/79
> > 
> 
> It doesn’t break the string freeze, but thanks a lot for the
> notification!

Could the release team weigh in with some feedback, please?

Cheers

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


Freedesktop.org Transifex org management

2019-02-26 Thread Bastien Nocera
Hey,

[I know this isn't directly related to GNOME, but has there is an
overlap between the folks involved in GNOME and in Transifex's
Freedesktop.org org, and GNOME is a consumer of those translations,
here I go]

I maintain shared-mime-info on freedesktop.org:
https://gitlab.freedesktop.org/xdg/shared-mime-info/

shared-mime-info uses Transifex as the translation service from back
when it was a Fedora hosted/sponsored project.

Somebody contacted me recently about how to get approved as a
translator for shared-mime-info for their language, which means getting
accepted as a translator in the "freedesktop" group:
https://www.transifex.com/freedesktop/public/

The problem is translators have had problems getting accepted into that
group, there seems to be no list of people to contact on the above
page, and, in the end, translators contact the module maintainers
directly, and they (I) know nothing about how transifex works from the
translator/group management side.

This is an example of the communication I received after some emails
discussions:
https://gitlab.freedesktop.org/xdg/shared-mime-info/merge_requests/17

And I've also found 8 more messages in my Transifex inbox from
translators who were trying to get accepted there.

I've been told Claude was responsible for the group. Is he still
responsible for it? Is there documentation we can point translators to
about applying for a position in the group? Or should I start looking
at other ways to get shared-mime-info (and other modules I maintain)
translated?

Cheers

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


Re: gnome-software string freeze break request for 3.30

2019-02-26 Thread Daniel Mustieles García via gnome-i18n
It's OK for me to apply it in 3.30, so 1/2 from i18n.

Thanks!

El mar., 26 feb. 2019 a las 9:43, Kalev Lember via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

>
> Hi,
>
> I'd like to backport a few new error messages to gnome-software 3.30.x
> and looking for feedback whether to do this upstream or just backport it
> downstream in Fedora.
>
> This would fix a long standing issue where gnome-software shows 'Unable
> to update "(null)"' as an error. The fix is to split a bunch of error
> messages into two, e.g.:
>
> "Unable to update %s" would be replaced with "Unable to update %s" +
> "Unable to install updates" so that we can show the latter if we don't
> have the data to fill in %s.
>
> If I counted it right then it's 9 error strings changed along those lines.
>
> Would it be OK to backport this to 3.30 or should I do it downstream
> instead?
>
> Thanks,
> Kalev
> ___
> 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-software string freeze break request for 3.30

2019-02-26 Thread Kalev Lember via gnome-i18n



Hi,

I'd like to backport a few new error messages to gnome-software 3.30.x
and looking for feedback whether to do this upstream or just backport it
downstream in Fedora.

This would fix a long standing issue where gnome-software shows 'Unable
to update "(null)"' as an error. The fix is to split a bunch of error
messages into two, e.g.:

"Unable to update %s" would be replaced with "Unable to update %s" +
"Unable to install updates" so that we can show the latter if we don't
have the data to fill in %s.

If I counted it right then it's 9 error strings changed along those lines.

Would it be OK to backport this to 3.30 or should I do it downstream
instead?

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