> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Jewett, Jim J > Sent: Thursday, May 20, 2004 8:26 AM > To: '[EMAIL PROTECTED]' > Subject: Re: Progress note (other formats) > > 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.) >
The site that made tables painful for me was the Wheel of Time FAQ (http://www.steelypips.org/wotfaq/) and try the section 2.7.5. I am using font NimbusSans15. > > 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? > Yes > > 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? > Decryption routine. It is actually available in the public domain at http://membres.lycos.fr/pc1/ > 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?) > This was mentioned before and it might suffice. I would hesitate to include the CC information though. It would deter copying, but it would also get left around because of backups, etc. and I am very wary of identity and CC theft. Mark E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized. _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
