[DL]String additions to 'gnome-maps.master'
This is an automatic notification from status generation scripts on: https://l10n.gnome.org. There have been following string additions to module 'gnome-maps.master': + "Show scale" + "Whether to show the scale." Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. https://gitlab.gnome.org/GNOME/gnome-maps/commits/master ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [DL]String additions to 'libgweather.main'
On Thu, Mar 3, 2022 at 6:03 PM Emmanuele Bassi wrote: > Well, it depends. Translating "Somewhere Airport" is likely needed, but > translating the name of a city isn't exactly what I'd consider necessary. In French (taking an example I can speak for), London (UK, not Ontario) is Londres, which is already fairly different. More extremely, Aachen (Germany) is Aix-la-Chapelle. I really do think translation is necessary. > There's also the issue that not everything is marked as translatable *today*, > for no apparent reason. I don’t why either. That doesn’t seem right. > In any case, as I said: I wanted to open the floor to the discussion, not ask > permission for the removal. Technically you need permission for the addition you did. Removal is up to you. I stand by my approval for them to stay in though, as it doesn’t seem like a huge issue. I’m confident you’ll get 2/2 soon and this will then be solved. > Sure, but at the end of the day you are still getting those strings counted > towards the overall coverage. I wish people (and by that I mostly mean our translators, not necessarily you) would understand that the stats we provide are just a means to know where we stand, a picture of the situation at a given time, and that it’s ok not to be at 100%. By the way, many of those places actually don’t have a localised name, and copying from the source string is pretty trivial with appropriate translation software, so I wouldn’t worry to much about the amount of work it represents. -- Alexandre Franke GNOME Hacker ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [DL]String additions to 'libgweather.main'
On Thu, 3 Mar 2022 at 16:54, Alexandre Franke wrote: > On Thu, Mar 3, 2022 at 5:48 PM Emmanuele Bassi via gnome-i18n > wrote: > > Hi all; > > Hi, > > > these are location names that did not exist in the database, so are > effectively newly translatable strings—but they are physical places, so > they can be left untranslated without any particular loss. > > Let’s call this a break request and here is approval 1/2. > I can revert at no particular loss. I honestly didn't really know the current status of the locations database with regards to translation. I mostly inherited the existing infrastructure, but there's no actual documentation on its contents and/or rules. > > As a side note: I'm not entirely sure most of the locations in the > libgweather database need to be translated in the first, so it would be > nice to have a discussion with the i18n teams at large, to see if we can > reduce the amount of translatable strings for the next cycle. > > I’m not sure I see the logic behind that. What makes you think > translations are not needed? A speaker of a given language surely has > a better chance of knowing a place by their localised names, don’t > they? Well, it depends. Translating "Somewhere Airport" is likely needed, but translating the name of a city isn't exactly what I'd consider necessary. There's also the issue that not everything is marked as translatable *today*, for no apparent reason. Of course, as Yuri pointed out: > Just my 2 cents. Surely, they are not translated, but commonly transliterated > (Cyrillic, Greek, CJK scripts). Please leave them translatable. transliteration is a perfectly valid use case. In any case, as I said: I wanted to open the floor to the discussion, not ask permission for the removal. Also, locations are using a separate domain, so it’s easy to > just translate `po` and leave `locations` out. > Sure, but at the end of the day you are still getting those strings counted towards the overall coverage. 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: [DL]String additions to 'libgweather.main'
On Thu, Mar 3, 2022 at 5:48 PM Emmanuele Bassi via gnome-i18n wrote: > Hi all; Hi, > these are location names that did not exist in the database, so are > effectively newly translatable strings—but they are physical places, so they > can be left untranslated without any particular loss. Let’s call this a break request and here is approval 1/2. > As a side note: I'm not entirely sure most of the locations in the > libgweather database need to be translated in the first, so it would be nice > to have a discussion with the i18n teams at large, to see if we can reduce > the amount of translatable strings for the next cycle. I’m not sure I see the logic behind that. What makes you think translations are not needed? A speaker of a given language surely has a better chance of knowing a place by their localised names, don’t they? Also, locations are using a separate domain, so it’s easy to just translate `po` and leave `locations` out. -- Alexandre Franke GNOME Hacker ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [DL]String additions to 'libgweather.main'
четвер, 3 березня 2022 р. 18:48:04 EET Emmanuele Bassi via gnome-i18n написано: > Hi all; > > these are location names that did not exist in the database, so are > effectively newly translatable strings—but they are physical places, so > they can be left untranslated without any particular loss. > > As a side note: I'm not entirely sure most of the locations in the > libgweather database need to be translated in the first, so it would be > nice to have a discussion with the i18n teams at large, to see if we can > reduce the amount of translatable strings for the next cycle. > > Ciao, > Emmanuele. Hi, Just my 2 cents. Surely, they are not translated, but commonly transliterated (Cyrillic, Greek, CJK scripts). Please leave them translatable. Best regards, Yuri > > On Thu, 3 Mar 2022 at 16:28, 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 'libgweather.main': > > > > + "Balneário Camboriú" > > > > + "Blumenau" > > + "Brusque" > > + "Chapecó" > > + "Criciúma" > > + "Jaraguá do Sul" > > + "Lages" > > + "Palhoça" > > + "São José" > > + "Tubarão" > > > > Note that this doesn't directly indicate a string freeze break, but it > > might be worth investigating. > > https://gitlab.gnome.org/GNOME/libgweather/commits/main > > ___ > > 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 'libgweather.main'
Hi all; these are location names that did not exist in the database, so are effectively newly translatable strings—but they are physical places, so they can be left untranslated without any particular loss. As a side note: I'm not entirely sure most of the locations in the libgweather database need to be translated in the first, so it would be nice to have a discussion with the i18n teams at large, to see if we can reduce the amount of translatable strings for the next cycle. Ciao, Emmanuele. On Thu, 3 Mar 2022 at 16:28, 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 'libgweather.main': > > + "Balneário Camboriú" > + "Blumenau" > + "Brusque" > + "Chapecó" > + "Criciúma" > + "Jaraguá do Sul" > + "Lages" > + "Palhoça" > + "São José" > + "Tubarão" > > Note that this doesn't directly indicate a string freeze break, but it > might be worth investigating. > https://gitlab.gnome.org/GNOME/libgweather/commits/main > ___ > 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
[DL]String additions to 'libgweather.main'
This is an automatic notification from status generation scripts on: https://l10n.gnome.org. There have been following string additions to module 'libgweather.main': + "Balneário Camboriú" + "Blumenau" + "Brusque" + "Chapecó" + "Criciúma" + "Jaraguá do Sul" + "Lages" + "Palhoça" + "São José" + "Tubarão" Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. https://gitlab.gnome.org/GNOME/libgweather/commits/main ___ 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
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
String freeze break request for gnome-control-center!1684
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