Re: geary string freeze and upcoming release

[Michael Gratton]

Sounds like a good plan to me. Cheers!

--
⊨ Michael Gratton, Percept Wrangler.
⚙ 

On Tue, 12 Feb, 2019 at 6:41 PM, Daniel Mustieles 
=?iso-8859-1?q?Garc=EDa?=  wrote:

Sure, here is the second +1 from i18n ;-)

Thanks!


El mar., 12 feb. 2019 a las 8:22, Alexandre Franke 
() escribió:
On Mon, Feb 11, 2019 at 11:45 PM Michael Gratton  
wrote:

 > Sure thing. Per the original email in this thread, the plan is to
 > release 0.13 later this week. This is a feature release and will 
become

 > the new stable release, replacing 0.12 as such.
 >
 > Going forward, I plan to then quickly do a "UI refresh" release 
and
 > switch over to the GNOME release numbering, around the same time 
or

 > shortly after GNOME 3.32 comes out next month. This will have an
 > updated icon and app menu moved into the main window so as to 
match

 > GNOME 3.32 apps, and might be enhanced with libhandy so as to work
 > better on narrow, portrait displays, if that isn't too disruptive.
 >
 > I view this UI refresh release effectively as a point release 
(i.e.
 > 0.13.1), since I don't really plan on adding new features aside 
from
 > the above), but am bumping the version since its a noticeable 
change
 > from the perspective of a person using it, and it seems like a 
good
 > excuse as any to switch to GNOME's numbering. There will be a 
series
 > for point releases after that, too (i.e. 3.32.1, ...), for bug 
fix and

 > translation updates.
 >
 > After that I'd like to start following the GNOME release schedule
 > proper.
 >
 > Does that help?

 I think it does. Considering this, here’s my proposed solution:
 * we indeed consider Geary frozen and don’t make any breaking 
changes

 to strings in master
 * instead we stage them in a MR
 * changes that don’t break the freeze, like reusing an existing 
one,

 are fine for master
 * once 0.13 is released by the end of the week, we merge the staged
 fixes so they go in the next release

 This is similar to the situation where we have changes for GNOME
 modules right before the .0 release and we delay them to right after
 that release so they land in .1.

 Would that work for you, Michael?

 Can we have a +1 from a second i18n team member?

 --
 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: Strings additions in Nautilus

[Alexandre Franke]

On Tue, Feb 12, 2019 at 4:22 PM Carlos Soriano  wrote:
> Hello all,

Hi,

> Heads up we introduced a few strings in Nautilus, we added a plugin for totem 
> entirely
> inside Nautilus now. The strings are located for videos and audios in the 
> properties
> dialog and they are exactly the same as they were in Totem.

Thanks for letting us know.

> Here's the commit in case you want to see the added strings.

Just had a look and found an issue for which I reported
https://gitlab.gnome.org/GNOME/totem/issues/299 upstream. The fix will
need to be applied to both code bases.

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

Strings additions in Nautilus

[Carlos Soriano]

Hello all,

Heads up we introduced a few strings in Nautilus, we added a plugin for
totem entirely inside Nautilus now. The strings are located for videos and
audios in the properties dialog and they are exactly the same as they were
in Totem.

Here's the commit

in case you want to see the added strings.

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

“new” strings in dconf-editor

[Arnaud Bonatti via gnome-i18n]

Hello dear translators! I send you this mail to inform you that you
should see 4 “new” strings in dconf-editor. The story is that I’m
keeping a list of capitalized and non capitalized names of the various
types a simple gsettings/dconf value can have, but things were not
working correctly for types names starting with “D-Bus” in English, as
both capitalized and non-capitalized names were identical and so mixed
by gettext (that has been reported by Marek Černocký). It took me two
tries to get it right, but I think it’s correctly fixed now.

Also, I’ve done a bit of code moving in gnome-2048, so if you want to
have correct pointers to the code, you should refresh your potfiles.
But no change of strings there.

Regards,
Arnaud

-- 
Arnaud Bonatti

courriel : arnaud.bona...@gmail.com
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n