aboutsummaryrefslogtreecommitdiffstats
path: root/xml
Commit message (Collapse)AuthorAgeFilesLines
* be-mbox-to-xml passes attributes on to each part of multipart messages.W. Trevor King2009-07-122-15/+44
| | | | | | | | | | | | | | | | | | | | | | Previously "message[<some-attr>]" just returned None if it wasn't set for that message part, which overwrote anything passed in through fields. "from" and "date" added to list of attributes passed along. For be-xml-to-mbox, "alt-id" was added to Comment._attrs, and Comment.print_to_mbox was adjusted to handle the case where we have no information about the parent bug. With all of this, I can complete the loop be-mbox-to-xml example.mbox | be-xml-to-mbox > example2.mbox without errors :p. Finally, be-xml-to-mbox has been adjusted to also work on files (it had previously only handled data via stdin). We can't add stdin handling to be-mbox-to-xml though, because the mailbox package needs an actual file to work on, and I haven't setup a tmpfile workaround yet...
* Altered be-xml-to-mbox to work with non-ASCII input.W. Trevor King2009-07-121-72/+58
| | | | | | Now it runs off xml.etree instead of xml.sax. Removed "No matching bugs found" from "be list --xml" output.
* Added be-mbox-to-xml.W. Trevor King2009-07-121-0/+94
| | | | | | | | | | | | | | | | | | | | | | | Reworked to allow "be comment" to handle unicode strings (see bug e4ed63f6-9000-4d0b-98c3-487269140141). The solution was to escape all the unicode to produce and ASCII string before calling ElementTree.XML, and then converting back to unicode afterwards. Added a unicode-containing comment to the end of bug f7ccd916-b5c7-4890-a2e3-8c8ace17ae3a so that there's a handy unicode comment for testing. XML headers (e.g. '<?xml version="1.0" encoding="UTF-8" ?>') are now added to all xml output from be. Switched non-text/* encoding library to base64 instead of email.encoders, which makes that code in libbe/comment.py simpler. Changed libbe/mapfile.py error encoding from string_escape to unicode_escape so it can handle unicode. Everything's still untested, and be-xml-to-mbox doesn't handle unicode yet, but I felt this commit was getting a bit unwieldy ;).
* Updated copyright blurbs and AUTHORS and included script for future updatesW. Trevor King2009-07-011-1/+2
|
* Added ability to handle non text/* MIME types.W. Trevor King2009-06-261-4/+7
| | | | | | | | | | | | | | | | The main problem was the encoding/decoding that was happening to _all_ input/output. Now many I/O activities have a `binary' option to disable any encoding/decoding. The `binary' flag is set whenever the comment content-type is not a text/* type. In order to print valid XML (and make life easy on xml/be-xml-to-mbox), non text/* types are printed out as base64-encoded MIME messages, so be list --xml | be-xml-to-mbox | catmutt works as you'd expect. With the standard (non-XML) output from `be show', we just print a message telling the user that we can't reasonably display the MIME type and that they should use the XML output if they want to see it.
* Added extra_strings functionality to libbe.bug.xml and be-xml-to-mbox.W. Trevor King2009-06-251-8/+19
|
* Use Comment.content_type in xml output.W. Trevor King2009-06-221-2/+6
|
* Created be-xml-to-mbox.W. Trevor King2009-06-221-0/+181
| | | | | | Converts the output of `be list --xml` mbox format. For example: $ be list --xml | be-xml-to-mbox | catmutt
* Adjusted catmutt for portability following Mortiz' suggestions.W. Trevor King2009-06-221-5/+5
|
* Converted xml/grepm to xml/catmutt.W. Trevor King2009-06-222-65/+59
| | | | | | Now $ cat example.mbox | catmutt works. Onwards to be-xml-to-mbox!
* Added grepm as a template for an output-mbox-to-mutt script.Moritz Barsnick (at dot)2009-06-221-0/+65
The goal is to turn grepm into catmutt, and end up with $ be --xml list | be-xml-to-mbox | catmutt to browse current bugs and comments in mutt. Moritz has generously donated grepm under GPLv2. Not GPLv>=2 yet, so if the project decides to go to GLPv3 for example, this file will have to stay behind. Not that I see such a change coming, but I thought it was worth commenting on, so we don't forget.