Lambert, Mark: > I would like to add my vote to somehow speed up table > rendering (i.e. font change or something).
Are all tables slow, or nested tables, or tables with a font different from the default, or ..? (I don't (currently) often read channels with tables, and never markup tables, so I don't see the problem myself ... which is why I'm asking for clarification.) > I am almost done with Mobi support and have started > Peanut document support. I am correct that this is a server- (PC-) side tranformation, rather than letting the viewer read the format natively? > It may be possible for me to include support for encrypted > Peanut files. The catch (both good and bad) is you will > have to somehow supply the Registration name and CC info to > convert it. Is this something that would be helpful or > something that I would be better left out? Supply it to what? To a Peanut webserver that your code verifies against, or supply it to a decryption routine as part of the key? In general, I would say yes, but I can understand reluctance to release code that lets people read (and copy) documents they haven't paid for. If the CC is part of the decryption key, that shouldn't be a problem; the number stays on their own machine, and you don't ask for anything more than the standard reader does. Also, IIRC, JPluck has a BSD license, so you *could* keep part of the source hidden, or even use a plugin, if that would satisfy Peanut Press. But once the document is decrypted, will you need to reencrypt the plucker format version? Would you need to include the CC information in that too somehow, to discourage beaming? (As part of the owner string? Just as text?) -jJ _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
