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 106794 - Replacement text for images in buffer
Replacement text for images in buffer
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTextView
2.2.x
Other Linux
: Normal enhancement
: Small API
Assigned To: gtk-bugs
gtk-bugs
: 611642 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-02-22 15:44 UTC by Havoc Pennington
Modified: 2018-04-15 00:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Havoc Pennington 2003-02-22 15:44:35 UTC 
In GnomeChat if you cut-and-paste text containing a smiley image, 
the cut-and-pasted text should have the original ":-)" in it.

This is especially a problem because GnomeChat replaces the 
":/" in "http://" which it shouldn't do, but would be an 
issue anyway.

Should perhaps be a way to set some alternate text on an image 
which would be used when doing cut-and-paste, and could also 
be used for the "alt text" accessibility hint.

I'm not sure about the API/ABI implications for get_text(), get_slice(), 
etc. though. In general cut-and-paste should probably use get_text() ...
Comment 1 Sébastien Wilmet 2013-04-05 14:55:40 UTC 
*** Bug 611642 has been marked as a duplicate of this bug. ***
Comment 2 Matthias Clasen 2018-02-10 05:07:58 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 3 Matthias Clasen 2018-04-15 00:30:47 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new