It looks like this behavior is intentional. In GLIB 2.6 (http://www.gtk.org/api/2.6/glib/glib-Key-value-file-parser.html) the documentation said "To preserve initial and final spaces, these can also be escaped as \s" while the current stable version says (https://developer.gnome.org/glib/stable/glib-Key-value-file-parser.html) "To preserve leading spaces in values, these can also be escaped as \s." The comment on the upstream bug report (https://bugzilla.gnome.org/show_bug.cgi?id=664740#c1) suggests they want to preserve trailing spaces in string values.
It looks like this behavior is intentional. In GLIB 2.6 (http:// www.gtk. org/api/ 2.6/glib/ glib-Key- value-file- parser. html) the documentation said "To preserve initial and final spaces, these can also be escaped as \s" while the current stable version says (https:/ /developer. gnome.org/ glib/stable/ glib-Key- value-file- parser. html) "To preserve leading spaces in values, these can also be escaped as \s." The comment on the upstream bug report (https:/ /bugzilla. gnome.org/ show_bug. cgi?id= 664740# c1) suggests they want to preserve trailing spaces in string values.