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 85289 - external editor must use utf-8 or whole article is lost
external editor must use utf-8 or whole article is lost
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
pre-0.12.0 betas
Other Linux
: Normal critical
: 0.13.0
Assigned To: Charles Kerr
Charles Kerr
Depends on:
Blocks:
 
 
Reported: 2002-06-14 15:19 UTC by Martin Tomasek
Modified: 2006-06-18 05:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Martin Tomasek 2002-06-14 15:19:22 UTC
my locales:
LANG=en_US.UTF-8
LC_CTYPE=cs_CZ (iso-8859-2)

external editor must use UTF-8, if not, pan writes "Gtk-CRITICAL **: file
gtktextbuffer.c: line 476 (gtk_text_buffer_emit_insert): assertion
`g_utf8_validate (text, len, NULL)' failed" and forget whole article. file
in /tmp is not removed.

I suggest to use /dev/urandom for generating testing data for this.

anyway, there should be way for setting external editor encoding. I thought
that default for this is LC_CTYPE, but it seems it isn't. (or maybe I'm
doing something completely wrong)
Comment 1 Charles Kerr 2002-07-24 21:51:32 UTC
88670 is closely related to this bug, and has some 
possibly-useful comments.
Comment 3 Charles Kerr 2002-07-25 23:13:11 UTC
Chris:

  * the ArgSet leaks in this patch.

  * do we really want the charset picker to return a
    const char* charset?  Won't this be a dangling pointer
    as soon as the charset dialog picker widget is destroyed?
Comment 4 Christophe Lambin 2002-07-26 22:26:38 UTC
1. Fixed. Thanks for reviewing my hasty commit.

2. Not that I could see: the charset picker doesn't own the strings.
They're globals in the pan-charset-picker.c module.