> And when looking at the parser code I saw that we still use a mix
> of tabs and spaces. To make it really messy the tab setting seems
> to be 8 (and to add to this mess this isn't true for all tabs:),
> while the used indentation in the file is 4 ;-) Since no one else
> seems interested in fixin
> Another thing I have found is that the explode program gets confused
> when you have a link in a long document that points to a part that is
> in a separate record because of the 32k split. For such links it will
> include a link in the document that points to a file that doesn't
> exists since
> -The variable
> void *private;
> may cause problems if you want to drop this wholesale into a C++ application, as
>"private" is a
> keyword. Changing all instance of the "private" like "prvate" allowed a C++
>compiler to go
> ahead and didn't seem to cause a noticable bad effect.
On Sat, May 18, 2002, Robert O'Connor wrote:
> -The outputted HTML doesn't seem to have an open/close HTML tag
> around the BODY tags. These may be the cause of the lynx/parser
> choking while some browsers still show it.
The problem was caused by the comments in the file. After removing
them it
On Fri, May 17, 2002, David A. Desrosiers wrote:
> Doesn't decode.py do this already?
Actually, Decode.py (alias plucker-dump) will dump the records
from a Plucker document in the cache dir. plucker-decode (alias
PluckerDocs.py) will allow you to get info about a record.
Confused by the n
I've took it for some test runs. Very impressive stuff!
Two small mentions that may be of benefit:
> Works quite well. The generated HTML code seems to be non-Plucker
> compatible, though ;-) That is, the parser won't parse it into a
> Plucker document. Neither can I read the created files in l
On Fri, May 17, 2002, Bill Janssen wrote:
> which is just an API to retrieve information from a Plucker document.
Works quite well. The generated HTML code seems to be non-Plucker
compatible, though ;-) That is, the parser won't parse it into a
Plucker document. Neither can I read the created f
On 17 May 2002 at 17:00, Bill Janssen wrote:
> I've put out a tar file,
> ftp://ftp.parc.xerox.com/transient/janssen/unpluck.tgz, which contains
> code for the 'unpluck' library, which is just an API to retrieve
> information from a Plucker document. Also included is a sample
> program, explode,
I've put out a tar file,
ftp://ftp.parc.xerox.com/transient/janssen/unpluck.tgz, which contains
code for the 'unpluck' library, which is just an API to retrieve
information from a Plucker document. Also included is a sample
program, explode, which will "explode" a Plucker document into a
director
