Re: String freeze break for gnome-software for 42.1

2022-04-25 Thread Alexandre Franke
On Wed, Apr 13, 2022 at 10:59 PM Philip Withnall 
wrote:

> Hi all,
>

Hey!

I had a draft ready on the same day you sent your request, but needed
clarification. Pinged you in the Hackers room but didn’t get any response
and then forgot about it.


> Can we have a string freeze break for gnome-software to add more
> information about file system permissions required by flatpak apps?
> […]
>
I realise you’re probably not going to be happy about this!


I’m actually happy that you approached this the right way and took us into
account. Bonus points for the clear presentation and listing the strings so
we don’t have to hunt them down. The timing is also not the worst, so not
much to be unhappy about!


>  1. Add these new translatable strings now, in time for the 42.1
> release (this week). This means the bug will be fixed, but the strings
> will likely not be translated in many languages.
>

That would have been 10 days for three strings that are not too complex, at
a time when there isn’t much other activity in other modules. Looked
relatively reasonable. I would not have beent against landing this right
after you requested it. You said “this week” though, which threw me off.
Considering you just bumped, I supposed you indeed meant 10 days from that
date. Anyway, it’s too late for this.


>  2. Add these new translatable strings after the 42.1 release, to give
> more time for them to be translated ready for 42.2.
>

This one definitely looks great now.


>  3. Don’t add these new strings on 42.x at all, and use the
> inappropriate-but-already-existing “can read/write all your data”
> string instead.
>

No, I don’t think this option is necessary at all. Worst case, we can go
with option 2.

So here is approval 1/2 from i18n for option 2.

Cheers.

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


Re: gnome-shell.main.pot is incorrect

2022-04-25 Thread Guillaume Bernard
Hi,

I updated the Dockerfile on oscp-testing but it seems we cannot replace the FROM
instruction. Below is a extract of the first lines of the Docker build log.

Replaced Dockerfile FROM image fedora:34
Step 1/17 : FROM
quay.io/centos/centos@sha256:fc196b0e96ca8d0a7a06d768f1f6288478e5ae064c26c3626b2
e6e9b6e6ebcf4

I suppose there’s something in OpenShift that forces some images that can be
used as base image, I don’t find anything in the options I can change. I suppose
that I can only use the images located in Builds → Images. 

So, without help from Infrastructure team, I think I’m stuck there. I opened an
issue on infrastructure:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/816
-- 
Guillaume Bernard


Le lundi 25 avril 2022 à 08:49 +0200, Claude Paroz a écrit :
> Le 24.04.22 à 23:47, Michael Catanzaro a écrit :
> > 
> > Reading through the linked issues, nobody has bisected gettext yet to 
> > identify what changed. That's probably the next step towards getting 
> > this fixed.
> 
> I don't agree with that, we really need a full gettext 0.21 version, not 
> a patched 0.19.x version, as there are potentially other improvements.
> 
> Claude


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 freeze break for gnome-software for 42.1

2022-04-25 Thread Philip Withnall
*bump* 

On Wed, 2022-04-13 at 21:59 +0100, Philip Withnall wrote:
> Hi all,
> 
> Can we have a string freeze break for gnome-software to add more
> information about file system permissions required by flatpak apps?
> 
> Currently when flatpak apps request custom or unusual file system
> permissions, gnome-software incorrectly says the app “has access to
> no
> files”. The existing translatable strings we have in gnome-software
> 42.0 only give us the option of instead saying the app “can
> read/write
> all your data”, which is a bit wide.
> 
> We’d like to add three more strings to provide a middle ground,
> saying
> the app “can access arbitrary files”.
> 
> The change is here:
> https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/1317
> 
> The new strings are listed here:
> https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/1317#note_1429466
> 
> I realise you’re probably not going to be happy about this! There are
> a
> few options, and we’ll go with whatever the i18n team prefer:
> 
>  1. Add these new translatable strings now, in time for the 42.1
> release (this week). This means the bug will be fixed, but the
> strings
> will likely not be translated in many languages.
> 
>  2. Add these new translatable strings after the 42.1 release, to
> give
> more time for them to be translated ready for 42.2.
> 
>  3. Don’t add these new strings on 42.x at all, and use the
> inappropriate-but-already-existing “can read/write all your data”
> string instead.
> 
> Thanks,
> Philip

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


[DL]String additions to 'gnome-boxes.gnome-42'

2022-04-25 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-boxes.gnome-42':

+ "Screenshots"

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


Upcoming Rhythmbox release

2022-04-25 Thread Jonathan Matthew via gnome-i18n
Hi,

I will make a new Rhythmbox release on Sunday May 1st around 09:00 UTC.
Strings are frozen until then.

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


Re: gnome-shell.main.pot is incorrect

2022-04-25 Thread Claude Paroz

Le 24.04.22 à 23:47, Michael Catanzaro a écrit :


Reading through the linked issues, nobody has bisected gettext yet to 
identify what changed. That's probably the next step towards getting 
this fixed.


I don't agree with that, we really need a full gettext 0.21 version, not 
a patched 0.19.x version, as there are potentially other improvements.


Claude
--
www.2xlibre.net
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n