Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionSatyabrata Maitra
2015-08-31 07:34:52 UTC
Description of problem:
While opening gedit in terminal on es_ES Locale, it is showing some parsing warning/error. May be some unwanted translation related issue that could not handled by gedit properly, resulting the warning throwing.
Version-Release number of selected component (if applicable):
gedit-3.14.3-7.el7
How reproducible:
Always
Steps to Reproduce:
1. In RHEl7.2 Beta compose, open gedit in es_ES locale from gnome-terminal
2. Click on "Preferences" and/or click on Fonts & Colors tab and try
to change the font. (either one action should show the warning in the g-t.
3. Observe the gnome-terminal warning message/error
Actual results:
It is showing the following warning/error :
Terminal output :
**************
[smaitra@localhost ~]$ LANG=es_ES.UTF-8 gedit
(gedit:29143): GLib-GIO-WARNING **: Failed to parse translated string ''Monospace 12'' for key 'editor-font' in schema 'org.gnome.gedit.preferences.editor': 0:expected value
(gedit:29143): GLib-GIO-WARNING **: Using untranslated default instead.
****************
Expected results:
It should not show any such warning/error
Additional info:
Comment 2Ray Strode [halfline]
2015-09-22 20:39:11 UTC
seems to be caused by using « instead of ' in the translation. upstream just switched it out. Not sure why the strings are marked for translation if their parsed.
I confused this bug with bug 1247999 and already built a fix. If we can't get the acks before tomorrow, i'll untag the build.
I can still see the same behaviour on gedit-3.14.3-9.el7
$ LANG=es_ES.UTF-8 gedit
(gedit:32075): GLib-GIO-WARNING **: Failed to parse translated string ''Monospace 12'' for key 'editor-font' in schema 'org.gnome.gedit.preferences.editor': 0:expected value
(gedit:32075): GLib-GIO-WARNING **: Using untranslated default instead.
sys:1: Warning: invalid cast from 'GeditPreferencesDialog' to 'GeditWindow'
Comment 5Ray Strode [halfline]
2015-09-30 15:28:40 UTC
looks like i only got 2 of the 4 instances. Oh, well, clearly too late for 7.2 at this point.
This is to
msgid "'Monospace 12'"
msgstr "«Monospace 12»"
in gedit-3.14.3/po/es.po.
Though arguable upstream should not be including the quotes in the translatable string.
Fix is simple to change the quoting in the translation.
Let me attach a patch.
(In reply to Jens Petersen from comment #8)
> This is to
>
> msgid "'Monospace 12'"
> msgstr "«Monospace 12»"
>
> in gedit-3.14.3/po/es.po.
>
> Though arguable upstream should not be including the quotes in the
> translatable string.
>
> Fix is simple to change the quoting in the translation.
> Let me attach a patch.
Why is that string translatable at all?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2424.html