[Bugs] #2833 UNSP: add support for PDF export

[Sugar Labs Bugs]

#2833: add support for PDF export
------------------------------------------+---------------------------------
    Reporter:  godiard                    |          Owner:  lucian                     
        Type:  enhancement                |         Status:  new                        
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  Browse                     |        Version:  Git as of bugdate          
    Severity:  Unspecified                |       Keywords:                             
Distribution:                             |   Status_field:  New                        
------------------------------------------+---------------------------------

Comment(by lucian):

 Replying to [comment:7 godiard]:
 > Replying to [comment:5 lucian]:
 > > The way I see it, converting to PDF isn't ideal: 1) it's a lossy
 conversion and 2) it'll be opened by a different activity.
 > >
 > > As Sacha says, in Webified there's a proof of concept for saving
 complete web pages (just like firefox), putting them in a zip and later
 opening them with Browse:
 > >
 http://git.sugarlabs.org/browse/webified/commit/25450e1f18701402eb3bdba3a7c3297f61ac752a
 > >
 http://git.sugarlabs.org/browse/webified/commit/7005fb13a31f26704ec561d8e71bb4f82274fb3c
 > >
 > > I don't have time for it now, but it shouldn't be hard to port it to
 Browse mainline. The main problem with the patch(es) as it is now is that
 it doesn't clean up after it correctly.
 >
 > Yeah, probably you are right, and I think firefox already can open
 zipped media (jar support)

 At first I'd tried jar:, but it turns out it doesn't work as expected.
 Mozilla didn't intend it to be used for anything other than extensions and
 because of certain security features, they aren't usable for this.
 Unzipping files in Browse is a better choice, and it's not a big issue.


 Replying to [comment:4 sascha_silbe]:
 > The problem is that {{{print}}} is a reserved keyword in Python 2. XPCOM
 would need to rename {{{print}}} to something else, e.g. {{{print_}}}. I'm
 not sure how feasible it is to get that fix rolled out to the
 distributions that still ship a python-xpcom we can use in the first place
 (Ubuntu doesn't ship it at all and recent versions of Fedora are
 [ticket:2772 broken], too).

 For actually printing PDFs, a workaround like {{{setattr(self, 'print',
 print_)}}} should work.

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/2833#comment:8>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system