<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
This is my second take. Please review it (and disregard my previous
proposal).<br>
<br>
What I did is to enable the NCR decoding in YAXO, but if the result
is not a valid Cuis Character, then embed the NCR in the answer, as
the examples in the commet at String >> #asUtf8:<br>
<br>
Output looks reasonable, and as I said before, I suggest sending
#withCuisLineEndings prior to filing into Cuis.<br>
<br>
Thanks,<br>
<br>
On 9/27/2021 3:25 PM, Juan Vuletich via Cuis-dev wrote:
<blockquote cite="mid:61520CB0.8070004@jvuletich.org" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
On 9/27/2021 2:52 PM, Hilaire Fernandes via Cuis-dev wrote:
<blockquote
cite="mid:fad95c6d-19b1-1999-7cc3-9373ca67337e@drgeo.eu"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<p><font size="+1">Should not decoding the xml entity
	 etc. be done in the YAXO package.</font></p>
<p><font size="+1">Enabling entity decoding in the nextPCData
method make the xml entity correctly decoded:</font></p>
<p><font size="+1"> <font face="monospace"> nextChar == $&<br>
ifTrue: [<br>
self next.<br>
self peek == $#<br>
ifTrue: [<br>
nextPeek _ nil.<br>
nextChar _ self nextCharReference]</font><br>
</font></p>
<p><br>
</p>
<p>But it is disabled in YAXO, likely there is a reason for
that.<br>
</p>
<p>Hilaire<br>
</p>
</blockquote>
<br>
Oh. I wasn't aware of that code, at least not nowadays!<br>
<br>
I guess I disabled it when porting to Cuis. If this can be
enabled, the code I posted earlier today is not needed. But it
only should decode NCRs that can be represented in a Cuis
Character (as Cuis Character can not represent full Unicode). I'll
give it a try, and post some code later.<br>
<br>
<blockquote
cite="mid:fad95c6d-19b1-1999-7cc3-9373ca67337e@drgeo.eu"
type="cite">
<p> </p>
<div class="moz-cite-prefix">Le 27/09/2021 à 12:52, Juan
Vuletich a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:6151A286.7090804@jvuletich.org">I don't know the XML
spec in full detail, but it looks like the conversions in the
attach are needed. Anyone knows better?<br>
</blockquote>
<pre class="moz-signature" cols="72">--
GNU Dr. Geo
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://blog.drgeo.eu">http://blog.drgeo.eu</a></pre>
</blockquote>
<br>
Thanks,<br>
<pre class="moz-signature" cols="72">--
Juan Vuletich
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.cuis-smalltalk.org">www.cuis-smalltalk.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://github.com/jvuletich">https://github.com/jvuletich</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.linkedin.com/in/juan-vuletich-75611b3">https://www.linkedin.com/in/juan-vuletich-75611b3</a>
@JuanVuletich</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Juan Vuletich
<a class="moz-txt-link-abbreviated" href="http://www.cuis-smalltalk.org">www.cuis-smalltalk.org</a>
<a class="moz-txt-link-freetext" href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev</a>
<a class="moz-txt-link-freetext" href="https://github.com/jvuletich">https://github.com/jvuletich</a>
<a class="moz-txt-link-freetext" href="https://www.linkedin.com/in/juan-vuletich-75611b3">https://www.linkedin.com/in/juan-vuletich-75611b3</a>
@JuanVuletich</pre>
</body>
</html>