Last modified: 2014-01-15 18:38:45 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T62038, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 60038 - export format icalendar: escape and new line replacement?
export format icalendar: escape and new line replacement?
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
SemanticResultFormats (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-14 13:27 UTC by Andreas Plank
Modified: 2014-01-15 18:38 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Andreas Plank 2014-01-14 13:27:29 UTC
Is it possibel to improve the export of format=icalendar to replace line breaks by new line and escape , ; to \; \, ?

I tested an http://icalvalid.cloudapp.net/ icalendar validator and it complains about missing escaping of comma semicolon and when there is a line break it causes also an error in the exported ical file. 

Hope that can be adjusted.

Thanks,
Andreas
Comment 1 Andreas Plank 2014-01-14 15:19:57 UTC
Help how to escape what, details on escaping of field types and wrapping of long lines etc. see http://www.ietf.org/rfc/rfc5545.txt

E.g. value type text see section 3.3.11. page 44f. writes:

 escape \ to \\
 escape , to \,
 escape ; to \;
 escape newline to \n
 escape " to DQUOT

etc.
Comment 2 MWJames 2014-01-15 18:38:45 UTC
Feel free to add a patch set to [1] or ask on the smw-mailinglist for a volunteer developer who is willing to implement such feature.

[1] https://github.com/SemanticMediaWiki/SemanticResultFormats

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links