Re: database version problem

[Jean Jordaan <jean jordaan gmail com>]

Hi there

> Probably this is because "%20" is not recognized as blank (" ").

Indeed.

> (quick and dirty) fix,

Running right now, looks like it's working :-)
With an added bonus that apparently the metadata is being synced to
the versions:

Syncing metadata to file...
old = "" new = "" heading = "ASCII"
value = 2008:08:12 08:28:26 len = 19
_:bnode287220736 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type>
<http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag> .
_:bnode287220736 <http://www.w3.org/1999/02/22-rdf-syntax-ns#li> "flickr" .
_:bnode287220736 <http://www.w3.org/1999/02/22-rdf-syntax-ns#li> "Bangkok" .
_:bnode287220736 <http://www.w3.org/1999/02/22-rdf-syntax-ns#li> "temple" .
_:bnode287220736 <http://www.w3.org/1999/02/22-rdf-syntax-ns#li> "Wat Pho" .
<http://fakebase.f-spot.org/internal/>
<http://purl.org/dc/elements/1.1/subject> _:bnode287220736 .
value = f-spot version 0.5.0.3 len = 22
value = 2009:09:08 11:15:17 len = 19
value = f-spot version 0.5.0.3 len = 22
value = 2009:09:08 11:15:17 len = 19
Saved 10229 bytes

> This should probably be better done using regular expressions. Is on the
> todo list for the next version ;).

Rather than munging the character escapes manually, I would expect
that there are encoding/decoding methods that will give you the path
in a usable form.

-- 
jean                                              . .. .... //\\\oo///\\