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 591676 - EDS sould support richer memo text
EDS sould support richer memo text
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: Memos
2.28.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-08-13 11:39 UTC by Marcus Beyer
Modified: 2021-05-19 11:03 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Marcus Beyer 2009-08-13 11:39:58 UTC
Currently, EDS stores memos as VJOURNAL objects. This format is by itself very limited. Richer notes would be more usefull for users and also enable a better integration of other GNOME tools like Tomboy (see #347669).
Comment 1 Matthew Barnes 2010-01-08 22:09:36 UTC
iCalender's ALTREP property may be the key to getting this working, as it's essentially the same idea as "multipart/alternative" MIME types.

The comment field in Evolution's iCalendar component editor could then allow rich-text editing, which would be converted to plain text for the COMMENT property, with an ALTREP parameter pointing to the "text/richtext" content portion.  (I think we want to stay away from HTML here, as that would open up a nasty can of worms for the editor.)

I assume Tomboy/GNote can readily import and export "text/richtext" content.

From RFC 2445:

4.2.1 Alternate Text Representation

   Parameter Name: ALTREP

   Purpose: To specify an alternate text representation for the property
   value.

   Format Definition: The property parameter is defined by the following
   notation:

     altrepparam        = "ALTREP" "=" DQUOTE uri DQUOTE

   Description: The parameter specifies a URI that points to an
   alternate representation for a textual property value. A property
   specifying this parameter MUST also include a value that reflects the
   default representation of the text value. The individual URI
   parameter values MUST each be specified in a quoted-string.

   Example:

     DESCRIPTION;ALTREP="CID:<part3.msg.970415T083000@host.com>":Project
       XYZ Review Meeting will include the following agenda items: (a)
       Market Overview, (b) Finances, (c) Project Management

   The "ALTREP" property parameter value might point to a "text/html"
   content portion.

     Content-Type:text/html
     Content-Id:<part3.msg.970415T083000@host.com>

     <html><body>
     <p><b>Project XYZ Review Meeting</b> will include the following
     agenda items:<ol><li>Market
     Overview</li><li>Finances</li><li>Project Management</li></ol></p>
     </body></html>
Comment 2 Alexánder Alzate 2017-03-02 01:59:29 UTC
Wouldn't it be better if we use markdown instead any rich text format?
Comment 3 André Klapper 2021-05-19 11:03:31 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/

Thank you for your understanding and your help.