<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Hi Don,</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Date: Wed, 26 Apr 2017 10:37:54 -0700<br>
From: Don Brutzman <<a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a>><br><br>
Good discussion, and perhaps document clarity can be improved by additional prose and further examples. Several mantis issues have suggested that.<br>
<br>
However that specification document - XML encoding for X3D - isn't wrong, per se. Characters " and " are equivalent in XML, and that is why each of the proposed example variants actually work.<br>
<br>
Further if we even tried to distinguish between special-character representations in the X3D XML encoding, all XML parsers would ignore such distinctions.<br>
<br>
Lots more detail on handling string characters available in<br>
<br>
_X3D for Web Authors_<br>
<a href="http://x3dgraphics.com" rel="noreferrer" target="_blank">http://x3dgraphics.com</a><br>
<br>
Geometry Part 1: Primitives<br>
<a href="http://x3dgraphics.com/slidesets/X3dForWebAuthors/Chapter02-GeometryPrimitives.pdf" rel="noreferrer" target="_blank">http://x3dgraphics.com/<wbr>slidesets/X3dForWebAuthors/<wbr>Chapter02-GeometryPrimitives.<wbr>pdf</a><br>
<br></blockquote><div><br></div><div>"Not found". The pdf does not seem to be available anymore ?</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
X3D Example Archives: X3D for Web Authors, Chapter 02 Geometry Primitives (3 scenes)<br>
<a href="http://x3dgraphics.com/examples/X3dForWebAuthors/Chapter02-GeometryPrimitives" rel="noreferrer" target="_blank">http://x3dgraphics.com/<wbr>examples/X3dForWebAuthors/<wbr>Chapter02-GeometryPrimitives</a></blockquote><div><br></div><div><a href="http://x3dgraphics.com/examples/X3dForWebAuthors/Chapter02-GeometryPrimitives/TextSpecialCharactersIndex.html">http://x3dgraphics.com/examples/X3dForWebAuthors/Chapter02-GeometryPrimitives/TextSpecialCharactersIndex.html</a><br></div><div><br></div><div>First I thought both the cobweb and x3dom rendering are incorrect. But then I saw that for the x3dom encoding, all original ampersands from entities first characters got turned into a separate & entity:</div><div><br></div><div><Text DEF='DefaultText' string='"Character entity substitutions:" "empty string \"\" skips a line:" "" "apostrophe ' is &apos;" "ampersand & is &amp;" "quote mark \" is &quot;" "backslash \\ is X3D escape character" "double backslash \\\\ is X3D backslash \\ character" "Pi Π is &#928; XML character entity"'><br></div><div> </div><div>which I think makes the x3dom rendering correct.</div><div><br></div><div>It turns out the same conversion is happening to the .x3d file as well: <a href="http://x3dgraphics.com/examples/X3dForWebAuthors/Chapter02-GeometryPrimitives/TextSpecialCharacters.x3d">http://x3dgraphics.com/examples/X3dForWebAuthors/Chapter02-GeometryPrimitives/TextSpecialCharacters.x3d</a></div><div><br></div><div>If the cobweb (and x3dom) rendering is the intended rendering, then the html on</div><div> <a href="http://x3dgraphics.com/examples/X3dForWebAuthors/Chapter02-GeometryPrimitives/TextSpecialCharactersIndex.html">http://x3dgraphics.com/examples/X3dForWebAuthors/Chapter02-GeometryPrimitives/TextSpecialCharactersIndex.html</a></div><div><br></div><div>should be probably changed to show the text MFString as above or here: <a href="http://x3dgraphics.com/examples/X3dForWebAuthors/Chapter02-GeometryPrimitives/TextSpecialCharactersX3dom.xhtml">http://x3dgraphics.com/examples/X3dForWebAuthors/Chapter02-GeometryPrimitives/TextSpecialCharactersX3dom.xhtml</a></div><div> </div><div><br></div><div>Andreas</div><div><br></div></div>
</div></div>