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 120584 - Can replace "\n" in msgid or msgstr as newline, similar to replacing space with middledot
Can replace "\n" in msgid or msgstr as newline, similar to replacing space wi...
Status: RESOLVED FIXED
Product: gtranslator
Classification: Other
Component: Interface
HEAD
Other All
: Normal enhancement
: 1.0
Assigned To: Ross Golder
Fatih Demir
Depends on:
Blocks:
 
 
Reported: 2003-08-24 08:49 UTC by Abel Cheung
Modified: 2007-08-28 17:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Abel Cheung 2003-08-24 08:49:51 UTC
Currently, "\n" in msgid and msgstr are shown as is. It can be made more
intuitive by replacing "\n" with a symbol that denotes newline, then open a
new line for displaying remaining strings.
Comment 1 Alessio Dessi 2003-09-04 22:34:03 UTC
here we need to consider that is not only a visualization problem for
the "\n" but also that we need a simple way to put it in the string. 

I think that the best solution is to let the newline appear in the
messages as escape code and in the same way use the escape code to
insert the newline in the translated message. Another solution could
be using a special simbol but for this we need to add a special
shortcut to gtranslator. for me the first solution is the best one.

any other idea ?
Comment 2 Leonardo Ferreira Fontenelle 2006-10-27 06:24:00 UTC
See http://live.gnome.org/gtranslator for that. IMHO, when the user presses enter or tab then the escaped sequence should be added, but not displayed -- just display text with a new line or a tabulation. If the user chooses to show blank spaces as special characters, then show something like the return key or an right arrow.
Comment 3 Ignacio Casal Quinteiro (nacho) 2007-08-28 17:32:12 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.