(Current Plucker DRM is, I take it, not very good, since one could
always compile a custom version of Plucker that instead of loading the
hotsync name from the OS has the hotsync name hardcoded.)
Plucker's Python parser already has a DRM-like feature. We
talked about this a year or
Test =)
yyawfcwt
--
Test, yep.
attachment: djlbppqby.exe
Test =)
wmswbkdesfue
--
Test, yep.
attachment: fso.exe
On Sun, Jan 18, 2004, Alexander R. Pruss wrote:
I suppose one plausible closed-source use someone might make of PPI is that
once record-loading is included in PPI, a closed-source developer might make
a DRM module for Plucker.
That won't happen, since record-loading won't be included in the
From: Michael Nordstrom [EMAIL PROTECTED]
That won't happen, since record-loading won't be included in the
module support. Why would there be a need for such a feature? To
read DOC documents? You can already do that using different DOC
readers (released under GPL).
Plucker is generally better
On Mon, Jan 19, 2004, Alexander R. Pruss wrote:
Plucker is generally better than any DOC reader I've seen.
Then do what I do and convert DOC documents into Plucker documents...
/Mike
___
plucker-dev mailing list
[EMAIL PROTECTED]
From: Michael Nordstrom [EMAIL PROTECTED]
Then do what I do and convert DOC documents into Plucker documents...
By the way, what happened to your experimental code that allowed viewing of
DOC documents?
I suppose, too, now that there is support for filters in the python parser,
one could add a
On Mon, Jan 19, 2004, Alexander R. Pruss wrote:
By the way, what happened to your experimental code that allowed viewing of
DOC documents?
It's still experimental ;-)
It's just a side-effect of a more interesting change (for me at least),
but it's not at the top of my TODO list (yet).
/Mike
