vlion: (wizard)
vlion ([personal profile] vlion) wrote in [site community profile] dw_dev2009-12-07 09:06 pm
Entry tags:

Export Journal

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.
mark: A photo of Mark kneeling on top of the Taal Volcano in the Philippines. It was a long hike. (Default)

[staff profile] mark 2009-12-08 05:32 am (UTC)(link)
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.
peoppenheimer: A photo of Paul Oppenheimer at the Australasian Association of Philosophy meeting. (Default)

[personal profile] peoppenheimer 2009-12-08 05:59 am (UTC)(link)
Usually encapsulated postscript, which tells TeX where to put the thing, how big it is, and so on.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)

[staff profile] denise 2009-12-08 05:51 am (UTC)(link)
I think it should be a combination paid user/non-paid user feature: "export all contents in the journal in a single format (.pdf) once per year" should be something everyone can do, while "export more frequently/whenever you want", "export in html/latex/other esoteric formats", "export by privacy level", "export by tag", etc etc, should be a paid user feature.

zvi: self-portrait: short, fat, black dyke in bunny slippers (Default)

[personal profile] zvi 2009-12-08 06:18 am (UTC)(link)
Er, do you mean that whoever is running the site should be able to peg how often exports of what kind are done by each account level? Dreamwidth really needs to keep heavy use cases to paid (although I do think an annual free export is an awesome idea!), but somebody's special purpose install may not need to be that restrictive and somebody's completely hobbyist site may want to forbid it all together.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)

[staff profile] denise 2009-12-08 06:41 am (UTC)(link)
Yeah, sorry, that was what I meant -- controlled by config options, with dual "how many times per {month/year} someone could export" and "can use advanced export tools" caps.
foxfirefey: A fox colored like flame over an ornately framed globe (Default)

[personal profile] foxfirefey 2009-12-15 09:55 pm (UTC)(link)
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