basex | Arbitrary base encoding in GO

XSLT 2

Remove targetNamespace="http://www.ipp.estg.pt/Dados_clientess" from the root element of your XML document.

A targetNamespace attribute does not belong on the root element of an XML instance document; it belongs on the root element of an XSD root element.

• xmlns, xmlns:xsi, xsi:schemaLocation, and targetNamespace?
• How to link XML to XSD using schemaLocation or noNamespaceSchemaLocation?

I assume you shorted the code for us, so ignoreing the missing ] on line 150 and the missing page number 41 in the pages constant on line 141+.

I would say the problem is not the this.scene.stop("game"), although I would just use this.scene.stop(), if you want the stop the current scene (in to a Reference ).

You can see the problem, if you uncomment the code and check the browser console, an error like:

"...Uncaught ReferenceError: optionText is not defined..."

should be visible. That indicates the real issue, it is that optionText ist not defined. Without diving to deep into your code here are some fixes to get it to work:

• Move the whole block into the for loop. (just above the } on line 115)

• change if(optionText=== "Play again") to if(optionText.text === "Play again")since optionText is a text object not a string.

• Add a the scene object as context to the optionBox.on('pointerup',... eventlistener like this:

Is the convert part of GAME_SPRITE['background'] = pygame.image.load(BACKGROUND).convert a function or method? If so you are missing the () after it.

Change that line to

Use .. to navigate up e.g.

If I add opt(writer, "encoding", Strings.UTF8); as line 156 in HtmlParser.java (https://github.com/martin-honnen/basex/commit/4711a390e4069d363243f48c95456544916f40f7) of BaseX the problems seems to go away. I am not sure, however, this is the right way to fix it.

The root of the problem seems to be two issues, TagSoup, without having the output encoding of the XMLWriter set to any Unicode encoding like UTF-8 or UTF-16, outputs two numeric character references representing an Unicode character outside of the BMP.

So you have to set UTF-8 or UTF-16 as the output encoding of TagSoup's XMLWriter as then it switches to Unicode mode and just outputs characters and not character references, with both encodings the XMLWriter of TagSoup seems to feed the right characters to the StringWriter BaseX sets up.

Furthermore, BaseX's internal String to byte[] conversion seems to expect UTF-8 encoded strings, not sure why that is the case on the Java platform, but the token function delegates work to an utf8 function.

So that way the fix in the HtmlParser seems to be to set opt(writer, "encoding", Strings.UTF8).

Due to the grouping you already have, count($elems) will have the right value in the return clause.

I think you original use of the let $sep is causing problems, the grouping count($elems) I suggested works fine for me at https://xqueryfiddle.liberty-development.net/bFDbxm7 where I have moved the $sep to a declared variable.

similar to my answer for https://www.biostars.org/p/280581/ using my tool xsltstream:

The solution is to add @method="text" to the element.

This attribute is documented in the EXPath HTTP Client spec, section 3.2 Serializing the request content:

The default value of the serialization method depends on the media-type: it is xml if it is an XML media type, html if it is an HTML media type, xhtml if it is application/xhtml+xml, text if it is a textual media type, and binary for any other case.

What this means is that the EXPath HTTP Client doesn't have a built-in mapping for the media-type of application/json—i.e., it falls back on binary. But JSON is a textual media type, and you've already performed the serialization of your XDM map into text via the fn:serialize() function. So you have to override the EXPath HTTP Client default of method="binary" and set method="text" on the element.

The draft v2 spec, simplifies sending JSON; by default, when it detects that the body contains a map() or array(), it will serialize the item as JSON, with the appropriate media-type.

But for now with v1, we still need to explicitly (1) serialize maps and arrays using the JSON serialization method and (2) specify method="text" on the element.