Hi,
On Wed, 2006-04-26 at 18:53 +0200, Tomasz Torcz wrote:
> On Tue, Apr 25, 2006 at 02:12:29PM -0400, D Bera wrote:
> > Or if someone wants to write a managed PDF parser (in C#), that would
> > be cool too :). There are some C# pdf libraries out there that can be
> > used e.g. itextsharp (its und
On Tue, Apr 25, 2006 at 02:12:29PM -0400, D Bera wrote:
> > On Mon, 2006-04-24 at 21:11 +0200, Jan Falkenhagen wrote:
> > > i've got a problem with beagle indexing pdf documents. Sometimes pdf
> > > indexing causes very high cpu and memory consumption of the pdftotext
> > > process (>1.5 GB of RAM)
> "ps aux | grep pstotext" doesn't show the filename?
thanks, simply didn't knew about this command.
jan
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers
itextsharp cannot do what we need. Some extensive searching has turned
up PdfSharp, a lib which shows promise. It can do what we need, but
has not undergone and Linux/Mono testing. While the project imports
into Monodevelop without issue, building seems to use some Windows
build system specific pre
Hi,
On Tue, 2006-04-25 at 21:51 +0200, Jan Falkenhagen wrote:
> well thats certainly true, but my problem is that i don't know which
> pdffiles are damaged because beagle-status doesn't show this kind of
> information and when im trying to use beagled --fg --debug in this case
> the log fills with
hi
> This is a bug in the xpdf software (from which pdftotext comes), and I'd
> suggest you report a bug to their developers.
well thats certainly true, but my problem is that i don't know which
pdffiles are damaged because beagle-status doesn't show this kind of
information and when im trying to
> On Mon, 2006-04-24 at 21:11 +0200, Jan Falkenhagen wrote:
> > i've got a problem with beagle indexing pdf documents. Sometimes pdf
> > indexing causes very high cpu and memory consumption of the pdftotext
> > process (>1.5 GB of RAM). however i guess that this occurs only with
> > some broken pdf
Hi,
On Mon, 2006-04-24 at 21:11 +0200, Jan Falkenhagen wrote:
> i've got a problem with beagle indexing pdf documents. Sometimes pdf
> indexing causes very high cpu and memory consumption of the pdftotext
> process (>1.5 GB of RAM). however i guess that this occurs only with
> some broken pdf file
hi,
i've got a problem with beagle indexing pdf documents. Sometimes pdf
indexing causes very high cpu and memory consumption of the pdftotext
process (>1.5 GB of RAM). however i guess that this occurs only with
some broken pdf files. is there any simple way to track down this
behaviour to the fil
