[x3d-public] illegal characters in X3D Architecture Table 41.5

[vmarchetti at kshell.com]

John

Good call on the git logs, but it's even simpler than that.
If you look at our published spec at https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/volume.html
we can see that the intended symbol is a left-pointing-arrow. In the near future I will look at the source
to see what got corrupted.

Vince Marchetti



> On Sep 8, 2021, at 10:28 AM, John Carlson <yottzumm at gmail.com> wrote:
> 
> 1) Would it be possible to go back in the git logs?
> 
> 2) if the first 8-bits were 0xFF, what would the UTF-8 be?  Assuming some random bit flip.
> 
> On Wed, Sep 8, 2021 at 5:43 AM vmarchetti at kshell.com <mailto:vmarchetti at kshell.com> <vmarchetti at kshell.com <mailto:vmarchetti at kshell.com>> wrote:
> I examined   file X3D/ISO-IEC19775/ISO-IEC19775-1/ISO-IEC19775-1v4.0/ISO-IEC19775-1v4-CD1/Part01/components/volume.html from github.
> The xml header line declares the encoding of utf-8, as does the html meta tag, charset field
> 
> Line 904 is the first data row of table 41.5
> <td>S ???? luminance (L)</td>
> where ???? denotes the garbled bytes.
> 
> Examining a hex dump, the 4 bytes between the space following 'S' and the space preceding 'l' are:
> 0xEF 0xBF 0xBD 0x3F
> 
> 0xEF is a byte used in byte-order-marks in different encodings, but it is incorrect to have it in the middle of a file.
> I have tried without success to decode these 4 bytes and portions of this byte-list in utf-8 and utf-16 ; the only success is that
> the final byte, 3F, is the question mark in ascii.
> 
> I propose the way forward is to decide what character we want to put in these table rows , and a dash would be fine, and make the edit.
> 
> Vince Marchetti
> 
> 
> 
>> On Sep 7, 2021, at 10:07 PM, Brutzman, Donald (Don) (CIV) <brutzman at nps.edu <mailto:brutzman at nps.edu>> wrote:
>> 
>> For Mantis 899, hoping someone can discern correct values for garbled characters in
>>  
>> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/volume.html#t-transferFunctionTextureCoordinateMapping <https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/volume.html#t-transferFunctionTextureCoordinateMapping>
>> Table 41.5 — Transfer function mapping from texture type to texture coordinate
>>  
>> Am thinking they might be quite simple, mdash or hyphen perhaps…
>>  
>> all the best, Don
>> -- 
>> Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu <mailto:brutzman at nps.edu>
>> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
>> X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman <http://faculty.nps.edu/brutzman>
>>  
>> _______________________________________________
>> x3d-public mailing list
>> x3d-public at web3d.org <mailto:x3d-public at web3d.org>
>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org <http://web3d.org/mailman/listinfo/x3d-public_web3d.org>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org <mailto:x3d-public at web3d.org>
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org <http://web3d.org/mailman/listinfo/x3d-public_web3d.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20210908/218c5650/attachment.html>