Closed
Bug 245750
Opened 20 years ago
Closed 20 years ago
Fixup formatting of export HTML or RTF (date range, description)
Categories
(Calendar :: Sunbird Only, defect)
Calendar
Sunbird Only
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gekacheka, Assigned: mostafah)
References
Details
Attachments
(1 file)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040514 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040514 The date range format from Email Selected Events (bug 244400) can also be applied to exporting events to HTML and to RTF. Reproducible: Always Steps to Reproduce: 1. Select multiple events in search unifinder. 2a. Copy, then Paste into HTML Composer, or OOo Writer. 2b. Export Selected events to Rich Text Format. Actual Results: "When" text has two dates and times with redundant info. If description is more than one line, it doesn't fit in current format. If description is preformatted (e.g., an outline), format is lost. Expected Results: Omit repeated date if same date. Omit repeated time if same time. Omit times if all day event. Show description like 'body' of message, in paragraph below headers. Preserve line breaks. Preserve indentation.
dateUtils.js: add formatInterval (extracted from calendarMail.js) calendarMail.js: formatInterval functionality moved, now calls dateUtils. importExport.js: use formatInterval in eventArrayToHTML, eventArrayToRTF. Adjust formatting to accomodate multiline and preformatted descriptions in body. wizard.xul: add dateUtils.js, as importExport.js now depends on it.
Depends on: 244400
Summary: Apply date range fixes to export HTML or RTF → Fixup formatting of export HTML or RTF (date range, description)
Assignee | ||
Comment 2•20 years ago
|
||
Checked in. Thanks
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Comment 3•18 years ago
|
||
The bugspam monkeys have been set free and are feeding on Calendar :: Sunbird Only. Be afraid for your sanity!
QA Contact: gurganbl → sunbird
You need to log in
before you can comment on or make changes to this bug.
Description
•