Benito van der Zander

> All the specs seem to agree that if you're writing, the most important thing is to include a BOM so that the reader knows what the endianness actually is....

I found another unicode library, and removed everything not normalization related to make their tables smaller. Now I have a normalization-only library: https://github.com/benibela/internettools/blob/master/data/bbnormalizeunicode.pas You could test if that works better...

or in one line: fpc -B PUCUConvertUnicode.dpr && ./PUCUConvertUnicode && fpc -Twin32 -Pi386 -B PUCUGenCodePages.dpr && wine ./PUCUGenCodePages.exe && fpc -B PUCUBuild.dpr && ./PUCUBuild but it gives different codepage arrays....

This is like the static type checking all over again. What if it the query is: if (false()) then {"a": 1, "a": 2} else ()

I always use `url`. everyone has heard of urls. But I guess url is not used in Xpath

>renaming fn:intersperse to fn:join; Could also call it `sequence-join` or `items-join`, then it is more consistent with `string-join` `items-join` variant would also be consistent with `items-after` >adding a parameter to...

An index argument is extremely useful I need it all the time But too many variables make the code hard too read. And the implementation becomes slow, when it has...

I have an [extract function](https://www.benibela.de/documentation/internettools/xpath-functions.html#x-extract) in Xidel that only returns the matched text and the third parameter lets one choose the returned capture groups (I always thought it to be...

> think your function would be fine, although maybe 0 or -1 would be better than "", so that the argument could be specified as xs:integer there is more All...

It does not parse in Xidel > Michael D's reasoning is at >https://lists.w3.org/Archives/Public/public-xsl-query/2016Mar/0037.html >>I'm reminded of Benito van der Zander's post in xquery-talk a while ago: My post?? I am...