Re: Unauthorized translation changes in dconf-editor
Ühel kenal päeval, E, 18.03.2019 kell 20:35, kirjutas Claude Paroz: > Le 18.03.19 à 15:17, mcatanz...@gnome.org a écrit : > > Please keep gnome-i18n@gnome.org CCed > > > > On Mon, Mar 18, 2019 at 5:02 AM, Arnaud Bonatti > > wrote: > ... > > > If a translation contains a web link to what is currently an > > > hypnotherapist website, it’s my role to remove that link before > > > it > > > hits the stable release. Even if I didn’t had the time to join > > > the > > > translator or its team to fix it in l10n. (Yes, it’s a true > > > story. Not > > > a big issue, but a real life one.) > > Hello Arnaud, > > I'm sure you have good intentions and you want the better for you > released software. > However the example above is a typical example whete it would be > crucial > that gnome-i18n is aware of the issue, because the person that > committed > that is either malicious and his account should immediately be > blocked, > or his account has been hacked and he should be aware of that. > > So if you report a serious issue to a translator team and don't get > a > prompt answer, you should imemdiately escalate the issue to gnome- > i18n > so we can take proper action. Only things related to links I noticed was https://gitlab.gnome.org/GNOME/dconf-editor/commit/0e6f727e249f259939f65c44c70bc173cf214292 which is just a dead link. https://gitlab.gnome.org/GNOME/dconf-editor/commit/c34101ac613708fbd5bad3f4fe1ebb4574f3f29f which shows the same page. And various changes from http to https by Arnaud. So some commit I missed had an outdated translator-credits? I even checked git diff origin/gnome-3-32..origin/maintainer-only-3-32 |grep http Meanwhile I see stuff like this instead: https://gitlab.gnome.org/GNOME/dconf-editor/commit/cb0708fedc224ae9274645d8d8e377953f37c233 Breaks unicode typography for the language - this language team uses ”%s” kind of markup typography throughout the desktop, not the English specific “%s”, but this is broken by this commit from Arnaud. I would be very angry if he broke my strings like this; but unfortunately (or fortunately?) we are in such a state that dconf-editor isn't really translated. I'd use „%s“, as told by our NATIONAL language institute(!) which Arnaud would break. I bet this is a similar case with baski here for eu.po file. https://gitlab.gnome.org/GNOME/dconf-editor/commit/3704fbb76c70def8718da2a62de12958cd7c7248 Probably changes translation of "Creators" from slovenian "Creators" to "Created" instead https://gitlab.gnome.org/GNOME/dconf-editor/commit/20d7339d1cceab3f8e16cebf8a054740fd02dd95 And of course changes all over the place that copy phrases and strings over from somewhere else, presumably without knowing the language or grammar and other subtleties. In general there are real fixes and probable improvements in there, but I don't see why the language teams just get trampled over here. It is maybe theoretically beneficial to languages that can't keep up at all, and it's just a way to keep it (a bit more) up to date; but for active languages, it's actively stepping over the language teams and defeating the process. As far as I'm concerned, if it's a GNOME project, you don't touch the translations yourself. If a language has such trouble, I don't think it makes sense to go spend hours and hours of time without knowing the language on tweaking things in an application that frankly no regular user should end up running anyways. Meanwhile it's then supposedly not good in 100 other GNOME modules for the language that people are actually exposed to. Lets just say that dconf-editor at this point is not something I feel like I shall be translating anytime soon, as it'll not be what gets shipped anyways. If you want to be the translator for all languages, you also get to translate it all, not only improve and "improve" stuff. This is a two-way street. Mart ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Unauthorized translation changes in dconf-editor
Am Mo., 18. März 2019 um 20:36 Uhr schrieb Claude Paroz : > > Le 18.03.19 à 15:17, mcatanz...@gnome.org a écrit : > > Please keep gnome-i18n@gnome.org CCed > > > > On Mon, Mar 18, 2019 at 5:02 AM, Arnaud Bonatti > > wrote: > ... > >> If a translation contains a web link to what is currently an > >> hypnotherapist website, it’s my role to remove that link before it > >> hits the stable release. Even if I didn’t had the time to join the > >> translator or its team to fix it in l10n. (Yes, it’s a true story. Not > >> a big issue, but a real life one.) > > Hello Arnaud, > > I'm sure you have good intentions and you want the better for you > released software. > However the example above is a typical example whete it would be crucial > that gnome-i18n is aware of the issue, because the person that committed > that is either malicious and his account should immediately be blocked, > or his account has been hacked and he should be aware of that. > > So if you report a serious issue to a translator team and don't get a > prompt answer, you should imemdiately escalate the issue to gnome-i18n > so we can take proper action. I agree with this - also, reporting the smaller errors to the translation teams could mean that they are corrected elsewhere, as they are likely repeated in the 100+ GNOME modules. I wonder if that link is found in multiple modules? (Of course it is tedious to wait for the translation teams when there's a release deadline and you're doing the final polishing.) Best regards Ask > > Thanks for your understanding. > > 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: Unauthorized translation changes in dconf-editor
Le 18.03.19 à 15:17, mcatanz...@gnome.org a écrit : Please keep gnome-i18n@gnome.org CCed On Mon, Mar 18, 2019 at 5:02 AM, Arnaud Bonatti wrote: ... If a translation contains a web link to what is currently an hypnotherapist website, it’s my role to remove that link before it hits the stable release. Even if I didn’t had the time to join the translator or its team to fix it in l10n. (Yes, it’s a true story. Not a big issue, but a real life one.) Hello Arnaud, I'm sure you have good intentions and you want the better for you released software. However the example above is a typical example whete it would be crucial that gnome-i18n is aware of the issue, because the person that committed that is either malicious and his account should immediately be blocked, or his account has been hacked and he should be aware of that. So if you report a serious issue to a translator team and don't get a prompt answer, you should imemdiately escalate the issue to gnome-i18n so we can take proper action. Thanks for your understanding. Claude -- www.2xlibre.net ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Unauthorized translation changes in dconf-editor
schrieb am Mo., 18. März 2019, 15:17: > Please keep gnome-i18n@gnome.org CCed > > On Mon, Mar 18, 2019 at 5:02 AM, Arnaud Bonatti > wrote: > > Hi Jeremy and Michael, hi release-team, > > > > 2019-03-17 17:01 UTC+01:00, mcatanz...@gnome.org > > : > >> I see: > >> > >> > >> > https://gitlab.gnome.org/GNOME/dconf-editor/commits/maintainer-only-3-32/po > >> > >> which seems pretty excessive. You probably wouldn't be very happy if > >> translators starting introducing unexpected changes outside of po/, > >> right? In the same way, the translators would prefer you to not make > >> changes under po/. > > > > That’s my role as a maintainer to ensure that the product that is > > taggued as stable does not look broken. > > > Your role as a maintainer doesn't include unauthorized changes of po files, which aren't approved by the translation teams and get released secretly via a "maintainer only" Git branch. As I already wrote one year ago: Never touch po files, really never! If you don't stop with your willful "fixes" and "improvements", we should consider to remove dconf-editor (and any other software maintained by you) from the Damned Lies pages. Best Regards, Mario > If translations are breaking the application layout, by translating > > the word “Translators” as something crediting translators on a > > long > > multiline string (the said “translator-credits” string from the > > About > > dialog), it’s my role to not tag a stable release without these > > translations fixed. > > > > If a translation contains a web link to what is currently an > > hypnotherapist website, it’s my role to remove that link before it > > hits the stable release. Even if I didn’t had the time to join the > > translator or its team to fix it in l10n. (Yes, it’s a true story. > > Not > > a big issue, but a real life one.) > > > >> Why is this necessary? They can't maintain their translations if you > >> have your own separate translations that never make it into > >> l10n.gnome.org. > > > > My goal is of course to upstream these changes is l10n, not to > > maintain a out of tree patchset indefinitely. > > > > But this upstreaming takes time: sometimes translators do not answer > > (see > > > https://bugzilla.gnome.org/buglist.cgi?quicksearch=product:l10n%20dconf-editor > > for long-time bugs without answers), sometimes translators take time > > to understand the problem, and I have to tag a stable release by the > > time. > > > > But that should not be a surprise if the last commit before the 3.32 > > dconf-editor release (8d0fa918) is fixing in one translation a problem > > I discovered and temporarily fixed in other po files, that’s part of > > my work with translators on these issues. > > > > As opposed to what Jeremy Bicha says, my current workflow is not > > breaking the translators one; that was not the case with my previous > > attempts (sorry again with that). And it is fixing translations for > > real life users. And that’s the important part of this story. > > > > 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 > ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Unauthorized translation changes in dconf-editor
Please keep gnome-i18n@gnome.org CCed On Mon, Mar 18, 2019 at 5:02 AM, Arnaud Bonatti wrote: Hi Jeremy and Michael, hi release-team, 2019-03-17 17:01 UTC+01:00, mcatanz...@gnome.org : I see: https://gitlab.gnome.org/GNOME/dconf-editor/commits/maintainer-only-3-32/po which seems pretty excessive. You probably wouldn't be very happy if translators starting introducing unexpected changes outside of po/, right? In the same way, the translators would prefer you to not make changes under po/. That’s my role as a maintainer to ensure that the product that is taggued as stable does not look broken. If translations are breaking the application layout, by translating the word “Translators” as something crediting translators on a long multiline string (the said “translator-credits” string from the About dialog), it’s my role to not tag a stable release without these translations fixed. If a translation contains a web link to what is currently an hypnotherapist website, it’s my role to remove that link before it hits the stable release. Even if I didn’t had the time to join the translator or its team to fix it in l10n. (Yes, it’s a true story. Not a big issue, but a real life one.) Why is this necessary? They can't maintain their translations if you have your own separate translations that never make it into l10n.gnome.org. My goal is of course to upstream these changes is l10n, not to maintain a out of tree patchset indefinitely. But this upstreaming takes time: sometimes translators do not answer (see https://bugzilla.gnome.org/buglist.cgi?quicksearch=product:l10n%20dconf-editor for long-time bugs without answers), sometimes translators take time to understand the problem, and I have to tag a stable release by the time. But that should not be a surprise if the last commit before the 3.32 dconf-editor release (8d0fa918) is fixing in one translation a problem I discovered and temporarily fixed in other po files, that’s part of my work with translators on these issues. As opposed to what Jeremy Bicha says, my current workflow is not breaking the translators one; that was not the case with my previous attempts (sorry again with that). And it is fixing translations for real life users. And that’s the important part of this story. 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
[gnome-photos] (2 commits) Created branch gnome-3-32
The branch 'gnome-3-32' was created. Summary of new commits: fe0928c... Post-release version bump d0c0742... Remove Flatpak manifest from stable branch ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[adwaita-icon-theme] Created branch gnome-3-32
The branch 'gnome-3-32' was created pointing to: 0bfd292... prepare for 3.32.0 release ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New coordinator for en_GB
On Sun, 2019-03-17 at 02:11 +0100, Bastien Nocera wrote: > On Sat, 2019-03-16 at 22:52 +0100, Claude Paroz wrote: > > Le 16.03.19 à 21:05, Bastien Nocera a écrit : > > > Hey, > > > > > > Bruce Cowan, who does most of the en_GB translation work these > > > days, > > > has agreed to take over from the absentee en_GB coordinator, that > > > is > > > me. > > > > > > Could you i18n coordinators take care of changing this in Damned > > > Lies? > > > Bruce is a member of this list should this need confirmation. > > > > Done. Thanks Bastien for your involvment in all those years! > > Thanks for quick update! Apologies for the delay, but thank you for arranging this. -- Bruce Cowan ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: UI/String freeze break request for gnome-boxes
pt., 15 mar 2019 o 15:47 Felipe Borges napisał(a): > > Hi, > > Since the release of GNOME Boxes 3.32.0 this week, we started to get > reports from users having problems with our recent "auto enable 3D > acceleration" feature. For this small set of users (dual-GPU or > unconventional graphics drivers), Boxes has become unusable. > > That's why I have proposed the following merge request > https://gitlab.gnome.org/GNOME/gnome-boxes/merge_requests/133 > > These changes introduce a pop-up notification that shows up only at > the first time a user starts a machine that supports 3D acceleration. > The notification offers an user action to Disable 3D acceleration. > Other than UI, it introduces two new strings: > "Experiencing graphics problems?" and "Disable 3d acceleration". > > Screenshot -> https://i.imgur.com/EYC5IDa.jpg > (by the way, those glitches you see in the screenshot are the ones > worked-around by this). > > I have discussed the approach with both Jakub Steiner and Allan Day, > and their are onboard with the change. > > Thanks, and sorry for the inconvenience of making this request this > late in the release cycle. > Dear Felipe, You can’t add new strings and then immediately make a release. This is not how it’s supposed to work. 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
[DL] String additions to 'gnome-boxes.gnome-3-32'
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-3-32': + "Disable 3D acceleration" + "Experiencing graphics problems?" 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-3-32 ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[swell-foop] Created branch gnome-3-32
The branch 'gnome-3-32' was created pointing to: ba95307... snap: Add snap build configuration ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[lightsoff] Created branch gnome-3-32
The branch 'gnome-3-32' was created pointing to: 6f05d33... Prepared release 3.32.0 ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[gnome-mines] Created branch gnome-3-32
The branch 'gnome-3-32' was created pointing to: 1cc0b53... Update Catalan translation ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
