Problems like these tend to crop up everywhere, until they eventually get
whittled away as SMW matures. The first thing you should probably do is work
out a plan for upgrading, and then do that. You may have to sacrifice
FCKeditor, but I've found the generic editor to be sufficient in my own use
Next, if you still have the same problem, it should go in a bug report so it
can be fixed in a future version of SMW. If you need help with that, let me
Finally, you have to do a workaround to serve your immediate needs until SMW
can do it without workarounds. How I approach a consistency problem like
this is to take control of formatting, with my own format scheme. For
example, you could encode your URL's in a deterministic way, so they can be
converted to and from SMW's own way of representing them. The problem here
appears to be an inconsistent way of encoding spaces and underscores in
URL's. That should be pretty easy to fix by coming up with your own way of
representing spaces and underscores, to guarantee you always get exactly
what you expect from a query result.
It looks to me that you're advanced enough with template programming to be
able to do this, but if you need help, let me know. It's more work, and not
the simple and elegant solution you're hoping for, but this approach
virtually guarantees you will be able to solve your problem, and later you
can remove the "cruft" code when SMW handles things the way you want it to.
Of course, it is likely that your code will work in any version of SMW,
perhaps without any modification, so you can always worry about removing
This method will work for your current version of SMW, so if you must, you
can skip the upgrades and the bug reports, and just do the custom encoding
work to fit your immediate needs, and be done with it for now.
View this message in context: http://wikimedia.7.x6.nabble.com/Problems-with-query-result-formats-tp5003805p5006721.html
Sent from the Semantic Mediawiki - User mailing list archive at Nabble.com.