[Bug 797421] Remove translations ("Icon[LL]=" ) for .desktop files from all GNOME software

[l10n]

https://bugzilla.gnome.org/show_bug.cgi?id=797421

Piotr Drąg  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||piotrd...@gmail.com
 Resolution|--- |NOTGNOME

--- Comment #1 from Piotr Drąg  ---
This is a bug in gettext — https://savannah.gnu.org/support/?108887

The issue started showing up in GNOME as we started porting from intltool to
gettext. The comment is obviously a stop-gap solution that only slightly
alleviated the pain, but we can’t do much more until gettext upstream fixes it,
releases a new version, and that version gets propagated to major distros.

I try to fix broken “translations” before every GNOME release, but I don’t
always have time, and I might miss some. I’m closing your report, as it’s not
actionable from our side, but I do appreciate your concern.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

[Bug 797421] New: Remove translations ("Icon[LL]=" ) for .desktop files from all GNOME software

[l10n]

https://bugzilla.gnome.org/show_bug.cgi?id=797421

Bug ID: 797421
   Summary: Remove translations ("Icon[LL]=" ) for .desktop files
from all GNOME software
Classification: Infrastructure
   Product: l10n
   Version: git master
OS: All
Status: NEW
  Severity: enhancement
  Priority: Normal
 Component: other
  Assignee: gnome-i18n@gnome.org
  Reporter: scootergri...@gmail.com
QA Contact: ment...@menthos.com
 GNOME version: ---

For some GNOME software i see in the .desktop files in /usr/share/applications/
that some files have translations for "Icon=" which should not be translated so
the comment in both the .desktop file and the pot/po says:

Translators: Do NOT translate or transliterate this text (this is an icon
file name)!

One example from Tails where "network-workgroup" have been translated to
something else despite the comment (its properly an old version so it might be
fixed alreay but just as example):

# Translators: Do NOT translate or transliterate this text (this is an icon
file name)!
Icon[ar]=network-workgroup
Icon[cs]=network-workgroup
Icon[da]=network-workgroup
Icon[de]=network-workgroup
Icon[el]=network-workgroup
Icon[en_GB]=network-workgroup
Icon[es]=network-workgroup
Icon[eu]=sareko lantadea
Icon[fa]=network-workgroup
Icon[fi]=network-workgroup
Icon[fr]=network-workgroup
Icon[fur]=network-workgroup
Icon[gd]=network-workgroup
Icon[gl]=network-workgroup
Icon[he]=network-workgroup
Icon[hr]=mreža-radnagrupa
Icon[hu]=network-workgroup
Icon[id]=network-workgroup
Icon[it]=network-workgroup
Icon[kk]=network-workgroup
Icon[ko]=network-workgroup
Icon[lt]=network-workgroup
Icon[lv]=network-workgroup
Icon[nl]=network-workgroup
Icon[pa]=network-workgroup
Icon[pl]=network-workgroup
Icon[pt]=Grupo de Trabalho na Rede
Icon[pt_BR]=network-workgroup
Icon[ru]=network-workgroup
Icon[sk]=network-workgroup
Icon[sl]=network-workgroup
Icon[sr]=мрежна-раднагрупа
Icon[sr@latin]=mrežna-radnagrupa
Icon[sv]=network-workgroup
Icon[tr]=network-workgroup
Icon[uk]=network-workgroup
Icon[uz@cyrillic]=network-workgroup
Icon[vi]=network-workgroup
Icon[zh_CN]=network-workgroup
Icon[zh_TW]=network-workgroup
Icon=network-workgroup


Here is a pot file as example:
https://l10n.gnome.org/POT/nautilus.master/nautilus.master.pot

With:

#. Translators: Do NOT translate or transliterate this text (this is an
icon file name)!
#: data/nautilus-autorun-software.desktop.in:7
msgid "application-x-executable"
msgstr ""

If the string should never be translated i suggest not having them available
for translation in the pot/po file so translators cant make the mistake of
changing the string.

Also there is no need for the comment about not translating the icon string in
the .desktop file so i suggest removing it.

Dont know if this is some old stuff that might/might not have been fixed in all
the GNOME software but i at least see it in the pot file still so its not fully
fixed yet.

Also it seems if i look in the source code example:
https://gitlab.gnome.org/GNOME/nautilus/blob/master/data/org.gnome.Nautilus.desktop.in.in

I cant see the translations so hard for me to know if "Icon=" is being
translated. Are there any smart way to check this for all GNOME software in the
latest code?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

[evince] Created branch gnome-3-32

[Germán Poo-Caamaño]

The branch 'gnome-3-32' was created pointing to:

 af6f345... Update Polish translation

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

[release-notes] Created branch gnome-3-32

[Link Dupont]

The branch 'gnome-3-32' was created pointing to:

 81dc183... Updated Spanish translation

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

Re: Wrong context in 2 strings

[Jehan Pagès via gnome-i18n]

Ok thanks everyone for the quick answers.

Seeing the unanimous (well up to now) answer, I just committed and pushed
the quick fix.
Commits 7a5e5be35e9b20e494767726fc58216c74125a08 on master and
66803bc2b3705830cf2f262fdd42e994aa990008 on gimp-2-10 branch.

As for future events, I guess I'll use my best judgement, and (if such
things ever happen again) if really I see that's the same thing (no actual
context/usage change, just an error in the msgctxt), I guess I would just
push.
But I'll ask again the question if I have any doubt or if the issue is
slightly different. :-)

Thanks again.

Jehan


On Thu, Feb 7, 2019 at 5:32 PM Kolbjørn Stuestøl 
wrote:

> Thank you for doing this this time and in the future for Norwegian nynorsk
> (language code nn).
> Kolbjørn
>
> Den 07.02.2019 17:17, skreiv Daniel Mustieles García via gnome-i18n:
>
> It is because of changing message context will cause DL to mark that
> string as fuzzy. This is why he is asking to apply the change directly into
> the PO files. These PO should be modified by developers, but in this case
> it is harmless because translated strings are not affected ;-)
>
> Cheers!
>
> El jue., 7 feb. 2019 a las 16:44, Snehalata Shirude via gnome-i18n (<
> gnome-i18n@gnome.org>) escribió:
>
>> Hi,
>>
>> If the meaning does not change, i think it can be directly changed using
>> find and replace. So it should not be directly related to the translation
>> process as such.
>>
>> Thanks
>>
>> Snehalata Shirude
>> Translator, for Marathi,
>> India
>>
>> On Thu 7 Feb, 2019, 8:42 PM Jehan Pagès via gnome-i18n, <
>> gnome-i18n@gnome.org> wrote:
>>
>>> Hi!
>>>
>>> In GIMP, we had a small bug in 2 strings: "Grow lighter areas of the
>>> image" and "Grow darker areas of the image".
>>>
>>> Basically in our code, we declared the strings with "drawable-action"
>>> context (hence that was the msgctx registered in po files) but called the
>>> translation with "filters-action" context so they were not translated.
>>> I fixed the code to use "filters-action" everywhere (the other was
>>> wrong), but the wrong context is now in various po/*.po files (43 files).
>>>
>>> Do you mind if I just do a massive search-and-replace for these 2
>>> context/strings to fix them? I mean, I actually already did it locally
>>> (took 20 secs), and I think that it is simpler than having everyone just
>>> edit manually for what was basically just a code bug. The actual context is
>>> the same (these strings are filter descriptions, same place in the GUI as
>>> what they were, nothing changed GUI-wise). So that looks harmless to me.
>>>
>>> Yet I have been told we should not touch the po files ourselves, if
>>> possible.
>>>
>>> So 2 questions:
>>> 1/ Is it ok if I just push this change?
>>>
>>> 2/ In the future, what should be our process as developers when we just
>>> see these kinds of code issues affecting the po files? Can we just push
>>> (making our own decision that this is not a translation issue) or we must
>>> ask case by case?
>>>
>>> Thanks for the awesome work, all!
>>>
>>> Jehan
>>>
>>> --
>>> ZeMarmot open animation film
>>> http://film.zemarmot.net
>>> Liberapay: https://liberapay.com/ZeMarmot/
>>> Patreon: https://patreon.com/zemarmot
>>> Tipeee: https://www.tipeee.com/zemarmot
>>> ___
>>> 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-i18n mailing 
> listgnome-i18n@gnome.orghttps://mail.gnome.org/mailman/listinfo/gnome-i18n
>
>
>
>
> 
>  Virusfri.
> www.avast.com
> 
> <#m_8868905255389087114_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Wrong context in 2 strings

[Kolbjørn Stuestøl]

Thank you for doing this this time and in the future for Norwegian 
nynorsk (language code nn).

Kolbjørn

Den 07.02.2019 17:17, skreiv Daniel Mustieles García via gnome-i18n:
It is because of changing message context will cause DL to mark that 
string as fuzzy. This is why he is asking to apply the change directly 
into the PO files. These PO should be modified by developers, but in 
this case it is harmless because translated strings are not affected ;-)


Cheers!

El jue., 7 feb. 2019 a las 16:44, Snehalata Shirude via gnome-i18n 
(mailto:gnome-i18n@gnome.org>>) escribió:


Hi,

If the meaning does not change, i think it can be directly changed
using find and replace. So it should not be directly related to
the translation process as such.

Thanks

Snehalata Shirude
Translator, for Marathi,
India

On Thu 7 Feb, 2019, 8:42 PM Jehan Pagès via gnome-i18n,
mailto:gnome-i18n@gnome.org>> wrote:

Hi!

In GIMP, we had a small bug in 2 strings: "Grow lighter areas
of the image" and "Grow darker areas of the image".

Basically in our code, we declared the strings with
"drawable-action" context (hence that was the msgctx
registered in po files) but called the translation with
"filters-action" context so they were not translated.
I fixed the code to use "filters-action" everywhere (the other
was wrong), but the wrong context is now in various po/*.po
files (43 files).

Do you mind if I just do a massive search-and-replace for
these 2 context/strings to fix them? I mean, I actually
already did it locally (took 20 secs), and I think that it is
simpler than having everyone just edit manually for what was
basically just a code bug. The actual context is the same
(these strings are filter descriptions, same place in the GUI
as what they were, nothing changed GUI-wise). So that looks
harmless to me.

Yet I have been told we should not touch the po files
ourselves, if possible.

So 2 questions:
1/ Is it ok if I just push this change?

2/ In the future, what should be our process as developers
when we just see these kinds of code issues affecting the po
files? Can we just push (making our own decision that this is
not a translation issue) or we must ask case by case?

Thanks for the awesome work, all!

Jehan

-- 
ZeMarmot open animation film

http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
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-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n




---
Denne e-posten har blitt sjekket for virus av antivirusprogramvare fra Avast
https://www.avast.com/antivirus
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Wrong context in 2 strings

[Sveinn í Felli]

Since it's a change in context and not in the translatable string, it 
would be awful to fuzzy all those translations just because there's a 
change in a path/pointer.


E.g. anything in a '#: ../src/aisleriot.schemas.in.h:1' comment could be 
altered as suits the programmer since it doesn't touch the string or the 
translation. And preferably via search-and-replace.


Just thoughts,

Sveinn í Felli

Þann 7.2.2019 15:32, skrifaði Daniel Mustieles García via gnome-i18n:

If the original string doesn't change and indeed it doesn't implies a
change in the translated one (and avoids translators to review a fuzzy
string) it's ok for me to apply the change directly in PO files.

Maybe other coordinators will disagree, but you have the OK to do it in the
Spanish PO file ;-)

About the second question... don't know how often this issues are, but I
would ask here before commiting, just to ensure you have the OK from the
i18n community.

Thanks!

El jue., 7 feb. 2019 a las 16:12, Jehan Pagès via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:


Hi!

In GIMP, we had a small bug in 2 strings: "Grow lighter areas of the
image" and "Grow darker areas of the image".

Basically in our code, we declared the strings with "drawable-action"
context (hence that was the msgctx registered in po files) but called the
translation with "filters-action" context so they were not translated.
I fixed the code to use "filters-action" everywhere (the other was wrong),
but the wrong context is now in various po/*.po files (43 files).

Do you mind if I just do a massive search-and-replace for these 2
context/strings to fix them? I mean, I actually already did it locally
(took 20 secs), and I think that it is simpler than having everyone just
edit manually for what was basically just a code bug. The actual context is
the same (these strings are filter descriptions, same place in the GUI as
what they were, nothing changed GUI-wise). So that looks harmless to me.

Yet I have been told we should not touch the po files ourselves, if
possible.

So 2 questions:
1/ Is it ok if I just push this change?

2/ In the future, what should be our process as developers when we just
see these kinds of code issues affecting the po files? Can we just push
(making our own decision that this is not a translation issue) or we must
ask case by case?

Thanks for the awesome work, all!

Jehan

--
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
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-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Wrong context in 2 strings

[Daniel Mustieles García via gnome-i18n]

It is because of changing message context will cause DL to mark that string
as fuzzy. This is why he is asking to apply the change directly into the PO
files. These PO should be modified by developers, but in this case it is
harmless because translated strings are not affected ;-)

Cheers!

El jue., 7 feb. 2019 a las 16:44, Snehalata Shirude via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> Hi,
>
> If the meaning does not change, i think it can be directly changed using
> find and replace. So it should not be directly related to the translation
> process as such.
>
> Thanks
>
> Snehalata Shirude
> Translator, for Marathi,
> India
>
> On Thu 7 Feb, 2019, 8:42 PM Jehan Pagès via gnome-i18n, <
> gnome-i18n@gnome.org> wrote:
>
>> Hi!
>>
>> In GIMP, we had a small bug in 2 strings: "Grow lighter areas of the
>> image" and "Grow darker areas of the image".
>>
>> Basically in our code, we declared the strings with "drawable-action"
>> context (hence that was the msgctx registered in po files) but called the
>> translation with "filters-action" context so they were not translated.
>> I fixed the code to use "filters-action" everywhere (the other was
>> wrong), but the wrong context is now in various po/*.po files (43 files).
>>
>> Do you mind if I just do a massive search-and-replace for these 2
>> context/strings to fix them? I mean, I actually already did it locally
>> (took 20 secs), and I think that it is simpler than having everyone just
>> edit manually for what was basically just a code bug. The actual context is
>> the same (these strings are filter descriptions, same place in the GUI as
>> what they were, nothing changed GUI-wise). So that looks harmless to me.
>>
>> Yet I have been told we should not touch the po files ourselves, if
>> possible.
>>
>> So 2 questions:
>> 1/ Is it ok if I just push this change?
>>
>> 2/ In the future, what should be our process as developers when we just
>> see these kinds of code issues affecting the po files? Can we just push
>> (making our own decision that this is not a translation issue) or we must
>> ask case by case?
>>
>> Thanks for the awesome work, all!
>>
>> Jehan
>>
>> --
>> ZeMarmot open animation film
>> http://film.zemarmot.net
>> Liberapay: https://liberapay.com/ZeMarmot/
>> Patreon: https://patreon.com/zemarmot
>> Tipeee: https://www.tipeee.com/zemarmot
>> ___
>> 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-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Wrong context in 2 strings

[Snehalata Shirude via gnome-i18n]

Hi,

If the meaning does not change, i think it can be directly changed using
find and replace. So it should not be directly related to the translation
process as such.

Thanks

Snehalata Shirude
Translator, for Marathi,
India

On Thu 7 Feb, 2019, 8:42 PM Jehan Pagès via gnome-i18n, <
gnome-i18n@gnome.org> wrote:

> Hi!
>
> In GIMP, we had a small bug in 2 strings: "Grow lighter areas of the
> image" and "Grow darker areas of the image".
>
> Basically in our code, we declared the strings with "drawable-action"
> context (hence that was the msgctx registered in po files) but called the
> translation with "filters-action" context so they were not translated.
> I fixed the code to use "filters-action" everywhere (the other was wrong),
> but the wrong context is now in various po/*.po files (43 files).
>
> Do you mind if I just do a massive search-and-replace for these 2
> context/strings to fix them? I mean, I actually already did it locally
> (took 20 secs), and I think that it is simpler than having everyone just
> edit manually for what was basically just a code bug. The actual context is
> the same (these strings are filter descriptions, same place in the GUI as
> what they were, nothing changed GUI-wise). So that looks harmless to me.
>
> Yet I have been told we should not touch the po files ourselves, if
> possible.
>
> So 2 questions:
> 1/ Is it ok if I just push this change?
>
> 2/ In the future, what should be our process as developers when we just
> see these kinds of code issues affecting the po files? Can we just push
> (making our own decision that this is not a translation issue) or we must
> ask case by case?
>
> Thanks for the awesome work, all!
>
> Jehan
>
> --
> ZeMarmot open animation film
> http://film.zemarmot.net
> Liberapay: https://liberapay.com/ZeMarmot/
> Patreon: https://patreon.com/zemarmot
> Tipeee: https://www.tipeee.com/zemarmot
> ___
> 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: Wrong context in 2 strings

[Daniel Mustieles García via gnome-i18n]

If the original string doesn't change and indeed it doesn't implies a
change in the translated one (and avoids translators to review a fuzzy
string) it's ok for me to apply the change directly in PO files.

Maybe other coordinators will disagree, but you have the OK to do it in the
Spanish PO file ;-)

About the second question... don't know how often this issues are, but I
would ask here before commiting, just to ensure you have the OK from the
i18n community.

Thanks!

El jue., 7 feb. 2019 a las 16:12, Jehan Pagès via gnome-i18n (<
gnome-i18n@gnome.org>) escribió:

> Hi!
>
> In GIMP, we had a small bug in 2 strings: "Grow lighter areas of the
> image" and "Grow darker areas of the image".
>
> Basically in our code, we declared the strings with "drawable-action"
> context (hence that was the msgctx registered in po files) but called the
> translation with "filters-action" context so they were not translated.
> I fixed the code to use "filters-action" everywhere (the other was wrong),
> but the wrong context is now in various po/*.po files (43 files).
>
> Do you mind if I just do a massive search-and-replace for these 2
> context/strings to fix them? I mean, I actually already did it locally
> (took 20 secs), and I think that it is simpler than having everyone just
> edit manually for what was basically just a code bug. The actual context is
> the same (these strings are filter descriptions, same place in the GUI as
> what they were, nothing changed GUI-wise). So that looks harmless to me.
>
> Yet I have been told we should not touch the po files ourselves, if
> possible.
>
> So 2 questions:
> 1/ Is it ok if I just push this change?
>
> 2/ In the future, what should be our process as developers when we just
> see these kinds of code issues affecting the po files? Can we just push
> (making our own decision that this is not a translation issue) or we must
> ask case by case?
>
> Thanks for the awesome work, all!
>
> Jehan
>
> --
> ZeMarmot open animation film
> http://film.zemarmot.net
> Liberapay: https://liberapay.com/ZeMarmot/
> Patreon: https://patreon.com/zemarmot
> Tipeee: https://www.tipeee.com/zemarmot
> ___
> 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

Wrong context in 2 strings

[Jehan Pagès via gnome-i18n]

Hi!

In GIMP, we had a small bug in 2 strings: "Grow lighter areas of the image"
and "Grow darker areas of the image".

Basically in our code, we declared the strings with "drawable-action"
context (hence that was the msgctx registered in po files) but called the
translation with "filters-action" context so they were not translated.
I fixed the code to use "filters-action" everywhere (the other was wrong),
but the wrong context is now in various po/*.po files (43 files).

Do you mind if I just do a massive search-and-replace for these 2
context/strings to fix them? I mean, I actually already did it locally
(took 20 secs), and I think that it is simpler than having everyone just
edit manually for what was basically just a code bug. The actual context is
the same (these strings are filter descriptions, same place in the GUI as
what they were, nothing changed GUI-wise). So that looks harmless to me.

Yet I have been told we should not touch the po files ourselves, if
possible.

So 2 questions:
1/ Is it ok if I just push this change?

2/ In the future, what should be our process as developers when we just see
these kinds of code issues affecting the po files? Can we just push (making
our own decision that this is not a translation issue) or we must ask case
by case?

Thanks for the awesome work, all!

Jehan

-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n