After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 793931 - Newlines in GSettings descriptions are not preserved in .po files
Newlines in GSettings descriptions are not preserved in .po files
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gsettings
2.54.x
Other All
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2018-02-28 18:34 UTC by Piotr Drąg
Modified: 2018-05-24 20:16 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Piotr Drąg 2018-02-28 18:34:18 UTC
GSettings descriptions with newlines lose those newlines in .po files. Compare https://gitlab.gnome.org/GNOME/mutter/blob/master/data/org.gnome.mutter.wayland.gschema.xml.in#L78 with https://gitlab.gnome.org/GNOME/mutter/blob/master/po/pl.po#L515 . It might be a bug in https://gitlab.gnome.org/GNOME/glib/blob/master/gio/gschema.its or gettext or somewhere else.
Comment 1 Arnaud B. 2018-03-05 03:30:24 UTC
I was just preparing a string freeze break request for this exact problem (in “dconf-editor”). Using “
” (or “
”) in the schema works as expected from an XML file, is that the correct way to go? But I’m quite sure that previously, the new line was working (some translations have line breaks in them).
Comment 2 Piotr Drąg 2018-03-05 15:33:56 UTC
I’m pretty sure it was working correctly before the move from intltool to gettext. I think it should work without using entities as a workaround, but I don’t even know where the bug lies specifically.

(It doesn’t mean that you can’t use the workaround for 3.28. I’m talking long(er)-term here.)
Comment 3 GNOME Infrastructure Team 2018-05-24 20:16:31 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/1350.