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 605987 - Add possibility of exporting logged conversations to HTML or other format
Add possibility of exporting logged conversations to HTML or other format
Status: RESOLVED DUPLICATE of bug 624529
Product: empathy
Classification: Core
Component: Archives
2.28.x
Other Linux
: Low enhancement
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2010-01-03 23:30 UTC by Fanen Ahua
Modified: 2011-06-22 15:29 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Fanen Ahua 2010-01-03 23:30:03 UTC
It would be useful if there is a possibility of exporting logged conversations in empathy into HTML or other format. This is useful if you wish to send a previous conversation to someone via email.

Copy-paste doesn't get all the formatting, and seems to discard some information.
Comment 1 soloturn 2010-04-05 18:21:39 UTC
is this a duplicate of #590033
Comment 2 soloturn 2010-04-05 18:21:59 UTC
(In reply to comment #1)
> is this a duplicate of #590033
bug590033
Comment 3 Jean-François Fortin Tam 2010-12-06 16:26:50 UTC
+1, I'll simply mention that copy-paste is a pain to use because it is heavily theme-dependent, so you get stuff like timestamps randomly inserted around depending on the theme, duplicate user names depending on the theme, etc.

A log export feature that allows to set whether or not I want to see the timestamps and duplicate usernames (when somebody sends multiple successive messages) in the output would be great.
Comment 4 Emilio Pozuelo Monfort 2011-06-22 15:29:21 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 624529 ***