Export Journal

[vlion]

I have a draft design for solving Bug 32 up here:

http://wiki.dwscoalition.org/notes/Export_Journal_Notes

It looks like it is a medium-sized project with three areas of expertise(DW server configuration, programming and graphic design).

There are several open questions about how an export should look, and I've left those for someone who is good at graphic design to write.

I would appreciate comments and review.

Comments

[mark]

1) Five minutes is unreasonable to expect. Doing a full dump of someone's journal is going to take much longer, especially since we'll have to prioritize it to run on the inactive slaves. If a lot of people do it, you can expect the wait to be up to hours.

2) You want to consider whether this is a paid user feature (probably) or if all users can do it.

3) I'm not familiar enough with LaTeX, so: how do you put images in it? Do we have to download them and include them in the zip file, or do they get embedded in the LaTeX file? Further, what are the copyright concerns with downloading and reproducing images that are merely linked on Dreamwidth?

Otherwise, I think this sounds fine. The biggest challenge will be coming up with the proper LaTeX output that will faithfully render the user's content in a way that is readable and useful. (Also, aren't there licensing concerns on using PDF?)

Another thing to consider is whether or not we want to try to partner with people who print books ... my gut says yes, but that's probably a business consideration that is not going to be part of this bug in particular.

[foxfirefey]

Note: we've just started putting Template Toolkit into the system, and it looks like it has some LaTeX hooks. This may interest you.

http://search.cpan.org/~andrewf/Template-Plugin-Latex-3.02/lib/Template/Latex.pm
http://search.cpan.org/~andrewf/Template-Plugin-Latex-3.02/lib/Template/Plugin/Latex.pm