[x3d-public] MFString quoting [was: interesting sample]

[Andreas Plesch]

On Wed, Apr 26, 2017 at 3:55 PM, <yottzumm at gmail.com> wrote:

> It’s
>
>
>
> http://x3dgraphics.com/slidesets/X3dForWebAuthors/
> Chapter02GeometryPrimitives.pdf
>
>
>
> Got caught in the grand renaming.  Also the parent page is wrong.
>
>

Thanks.
Page 28 in the pdf shows the
http://x3dgraphics.com/examples/X3dForWebAuthors/Chapter02-GeometryPrimitives/TextSpecialCharactersIndex.html
example and confirms that cobweb and x3dom render as intended. However,
TextSpecialCharactersIndex.html needs to be adjusted so it displays
&amp instead of & , for example. So probably

ampersand & is &amp;

 in the html

needs to become

ampersand & is &amp;amp;

to show the correct x3d on the web page.

-Andreas



>
>
> John
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
>
> *From: *Andreas Plesch <andreasplesch at gmail.com>
> *Sent: *Wednesday, April 26, 2017 3:12 PM
> *To: *Don Brutzman <brutzman at nps.edu>
> *Cc: *X3D Graphics public mailing list <x3d-public at web3d.org>
> *Subject: *Re: [x3d-public] MFString quoting [was: interesting sample]
>
>
>
> Hi Don,
>
>
>
> Date: Wed, 26 Apr 2017 10:37:54 -0700
> From: Don Brutzman <brutzman at nps.edu>
>
> Good discussion, and perhaps document clarity can be improved by
> additional prose and further examples.  Several mantis issues have
> suggested that.
>
> 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.
>
> Further if we even tried to distinguish between special-character
> representations in the X3D XML encoding, all XML parsers would ignore such
> distinctions.
>
> Lots more detail on handling string characters available in
>
>         _X3D for Web Authors_
>         http://x3dgraphics.com
>
>         Geometry Part 1: Primitives
>         http://x3dgraphics.com/slidesets/X3dForWebAuthors/
> Chapter02-GeometryPrimitives.pdf
>
>
>
> "Not found". The pdf does not seem to be available anymore ?
>
>
>
>
>
>         X3D Example Archives: X3D for Web Authors, Chapter 02 Geometry
> Primitives (3 scenes)
>         http://x3dgraphics.com/examples/X3dForWebAuthors/
> Chapter02-GeometryPrimitives
>
>
>
> http://x3dgraphics.com/examples/X3dForWebAuthors/
> Chapter02-GeometryPrimitives/TextSpecialCharactersIndex.html
>
>
>
> 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:
>
>
>
> <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"'>
>
>
>
> which I think makes the x3dom rendering correct.
>
>
>
> It turns out the same conversion is happening to the .x3d file as well:
> http://x3dgraphics.com/examples/X3dForWebAuthors/
> Chapter02-GeometryPrimitives/TextSpecialCharacters.x3d
>
>
>
> If the cobweb (and x3dom) rendering is the intended rendering, then the
> html on
>
>  http://x3dgraphics.com/examples/X3dForWebAuthors/
> Chapter02-GeometryPrimitives/TextSpecialCharactersIndex.html
>
>
>
> should be probably changed to show the text MFString as above or here:
> http://x3dgraphics.com/examples/X3dForWebAuthors/
> Chapter02-GeometryPrimitives/TextSpecialCharactersX3dom.xhtml
>
>
>
>
>
> Andreas
>
>
>
>
>



-- 
Andreas Plesch
39 Barbara Rd.
Waltham, MA 02453
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170426/edf897a5/attachment-0001.html>