On 28/04/07, Johann Petrak <[EMAIL PROTECTED]> wrote:
> Is it possible to have multiple filters for a a group of files
> where each provides their own part of (meta)information about
> the files?
> For example, a user might have a collection of documents
> (e.g. PDF, plain text, OpenOffice) but the
On 27/04/07, Joe Shaw <[EMAIL PROTECTED]> wrote:
> We also have a repo which is stored in Novell Forge, which I run every
> now and then but mostly when I'm gearing up to do a release. It was
> originally put in Novell Forge because it was SVN and maintaining it
> in GNOME CVS would cause major pa
I'm sure someone has mentioned this before but it seems that a good
way of preventing all the bugs that people complain about (broken
filters, not all content indexed) might be caught more quickly if
beagle had a repository of various files that indexing can be tested
on every night.
Coupled with
On 17/03/07, Joe Shaw <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Alex Mac wrote:
> > checking for automake >= 1.8...
> >
> > testing automake-1.8...
> > found 1.8.5
>
> Try changing the REQUIRED_AUTOMAKE_VERSION in autogen.sh to 1.9 and
> rerun it.
On 16/03/07, Joe Shaw <[EMAIL PROTECTED]> wrote:
> Hi,
> This has been brought up before, but I thought it was fixed now.
> There's a bug in some versions of automake which build directories out
> of order.
>
> What versions of automake do you have installed, and which one is chosen
> by autogen.sh
if I do a clean checkout of the repository and run autogen.sh followed
by make it tries to build things in the wrong order and fails straight
away with the following error, I noticed this a while back but assumed
someone else might have noticed it by now so I didn't bother reporting
it. I'm running
dbera: I've posted a patch to the xslt filter in the bugzilla entry,
can you apply that please (just tidies up the code to use the
recommended xml parsing methods)
as I said in the bugzilla entry your file is not well-formed, fixing
that makes the error go away.
That said I have no idea why beagl
I've got a few improvements I want to make to some of the various
filters I've got in beagle, and dbera has just opened up another bug
on my svg filter. Getting these things done would be a lot quicker and
easier for me If I had an svn account, how do I go about getting one?
Alex
_
No not a filter that searches for water on mars, something much more
interesting than that! Mars is adobe's new PDF format:
"The Mars (code name) Project is an XML-friendly implementation of PDF syntax.
Already an open specification, PDF is the global standard for trusted, high
fidelity electronic
On 06/12/06, Richard Boulton <[EMAIL PROTECTED]> wrote:
> > A thought crossed my mind recently about having beagle search inside
> > subversion repos. Would I have to implement that as a backend? I've
> > only written fairly trivial filters so far so I'm not sure how much
> > work that would involv
On 06/12/06, Joe Shaw <[EMAIL PROTECTED]> wrote:
> Hi Alex,
>
> On Wed, 2006-12-06 at 20:38 +, Alex Mac wrote:
> > Any possible pitfalls or things that would make this not worth doing?
>
> The idea is to find .svn directories and deal with their contents,
> correc
A thought crossed my mind recently about having beagle search inside
subversion repos. Would I have to implement that as a backend? I've
only written fairly trivial filters so far so I'm not sure how much
work that would involve or if it would be practical but it would be
quite cool to be able to s
On 02/12/06, D Bera <[EMAIL PROTECTED]> wrote:
> > On further inspection it seems to be because I am using the .Net 1.0
> > method of creating an XmlTextReader which does not enable character
> > checking:
> >
> > XmlTextReader reader = new XmlTextReader(thestream);
> >
> > msdn says this is deprec
On 02/12/06, D Bera <[EMAIL PROTECTED]> wrote:
> > Thanks for the advice, although I just tried running the filter on an
> > old scribus file and it seems the XmlReader is quite happy to process
> > xml files that are malformed in this way so it looks like there's no
> > need for buffering.
>
> Are
er is quite happy to process
xml files that are malformed in this way so it looks like there's no
need for buffering.
I've attached a tweaked version of the filter to the bugzilla page
(http://bugzilla.gnome.org/show_bug.cgi?id=380950) which is now ready
to be committed by someone.
from that into the XmlReader and never load the
whole thing into ram?
Alex Mac
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers
16 matches
Mail list logo
