writing to STDOUT is inferior compared to writing to -f

[VladimirAlexiev]

I use the following JVM args to invoke xsparql (UTF-8 is important for proper Unicode handling):

java -Xmx6G -Dfile.encoding=UTF-8 -jar c:/prog/xsparql/xsparql-cli-jar-with-dependencies.jar ...

Writing to STDOUT is inferior compared to writing to -f file:

• it mangles Unicode
• prints out the Prova.txt crap (how to use WHERE VALUES for a lookup table? #41)

So one should always use -f to invoke xsparql, eg:

xsparql script.xsparql input=file.xml -f file.ttl

The inability to write properly to STDOUT is problematic if you want to post-process the output using a unix pipeline.
I tried this to no avail:

xsparql script.xsparql input=test.xml -f /dev/stdout > test1.ttl
File not found: script.xsparql

And this:

xsparql script.xsparql input=test.xml -f - > test1.ttl

It writes out ONLY the Prova.txt crap (Whaat?)

So I need to use a temp file in Makefile to do post-processing.

[VladimirAlexiev]

Combining with #42, here's what I use in Makefile:

%.ttl: xsparql.xsparql %.xml
	xsparql xsparql.xsparql input=$*.xml -f TEMP.ttl > /dev/null
	 riot --syntax ttl --formatted ttl --base "..." TEMP.ttl |\
	 perl -00e '@a=<>; print shift @a; print sort @a' > $*.ttl
	rm TEMP.ttl