Re: [basex-talk] Decode a RESTXQ path

2015-08-28 Thread Dirk Kirsten
Hello Kristian, I guess you are correct and Tomcat or nginx. I would guess that Tomcat is the culprit (but that might be totally biased, just because I had lots of trouble with Tomcat). However, you might want to follow the advice given at https://stackoverflow.com/questions/138948/how-to-get-utf-

Re: [basex-talk] Decode a RESTXQ path

2015-08-28 Thread Kristian Kankainen
Hello! I'll try to elaborate. :-) My search function is as basic as is in your test. But you can see the output at: http://tomcat.eki.ee/vadja/korpus/%F0%9F%98%83 Can it be a problem or setting of Tomcat or anything in between the browser and BaseX, for example Nginx? Thank you for working

Re: [basex-talk] Decode a RESTXQ path

2015-08-28 Thread Dirk Kirsten
Hello Kristian, could you please elaborate what you mean by "decode"? Normally, you should not have to do anything, this is just an encoding and your $query variable should be able to handle UTF-8. I just tested this to see if there might be a bug, but if I do e.g. declare %rest:GET %rest:path

[basex-talk] Decode a RESTXQ path

2015-08-28 Thread Kristian Kankainen
Hello! I have a simplistic search path as %rest:GET %rest:path("search/{$query}") for an application. It all works fine with ASCII query string, but I can't figure out how to decode the string when It contains utf-8 characters. Best wishes Kristian K