[x3d-public] can SFString contain newline, carriage return?

[John Carlson]

For example, in values= and point= attributes in:

www.web3d.org/x3d/content/examples/HumanoidAnimation/HAnimSpecificationV2/KoreanCharacterAnnexD01Jin.x3d

(from the standard),

I see a leading line break after the leading " in the .x3d file.  I will
basically have to change ALL my code to expect this. This is NOT funny, and
will require me to redo ALL my testing.

Giggle!

John

On Mon, May 4, 2020 at 9:42 PM John Carlson <yottzumm at gmail.com> wrote:

> Would this ultimately, apply to ALL XML attributes?  Need some help here!
>
> On Sun, May 3, 2020 at 1:06 PM John Carlson <yottzumm at gmail.com> wrote:
>
>> I found some suggestions in the standards that one use &#xA; and &#xD;,
>> but no requirement???
>>
>> The reason I mention this is because in the HAnim motion standard,
>> there's examples that certainly look like a SFStrings that cover more than
>> one line, without newline and carriage return encoding, as above.  Plus the
>> Motion interface has joints and channels as "string"s, not
>> "sequence<string>"
>>
>> I think the standard is correct, we just need to modify our schemas and
>> X3DUOM to change MFString to SFString for joints and channels, if not
>> already done.
>>
>> I think I have heard from at least a couple of people that the standard
>> is correct, but from one person, a negative.
>>
>> I am not sure if this is a difference between HTML and XML?
>>
>> This is timely, because people are implementing the new HAnim motion
>> standard.
>>
>> Comments?   Corrections?
>>
>> Thanks,
>>
>> John
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200504/d39984fd/attachment.html>