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.
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.
no subject
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.
no subject
(2)Noted.
(3)Standard procedure is that the images + Latex file are combined into an output file. Typical scientific procedure is to use Postscript images, I *think*. It can get gnarly.
(3b) Linked off dreamwidth copyrights: I don't know. It's a good question. How do other sites do that sort of thing?
(4) PDF is a published standard now from what I noticed this weekend on Wikipedia.
(5)Partnering: doesn't sound like a bug. :)
no subject
no subject
- PDF is an ISO standard now: http://blogs.adobe.com/insidepdf/2007/12/iso_ballot_for_pdf_17_passed.html
- Paid user feature. This sounds closer to a business decision than a code decision. In a technical analysis view, it seems to me that requiring it be a paid user feature would avoid exploiting the system by people from other places autoloading their blogs in, exporting, and nevermore touching DW. It would also reduce exporting load. Another option would be have it be a pay-per-export for non-paid users; that would accomplish similar avoidance of exploiting.
no subject
no subject
no subject
no subject
no subject
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
no subject