[x3d-public] summary of remaining JSON parse errors

[John Carlson]

I am a bit concerned that will add one more digit of precision, and will not be a faithful rendering of the number.  Thoughts?

In other words, it should be 1e2

John
> On Mar 1, 2016, at 10:06 AM, Don Brutzman <brutzman at nps.edu> wrote:
> 
> Last night's build went OK.
> 
> Found and amended code block (template output-reals) to insert missing 0 after decimal point, before scientific notation (e.g. 1.e2 converted to 1.0e2).
> 
> Marked ScriptSyntaxExample.x3d meta information as a test scene.
> 
> Many of your error cases in log file were test scenes or archived backups, not working scenes.  I'll keep scrutinizing and pursuing problems in the list.
> 
>> On 2/26/2016 2:18 PM, John Carlson wrote:
>>> Some number formatting issues (need digit after .)
>>> Escaping issues
>>> ContainerField naming or object attribute value braces missing.
>>> ‘,’ value is missing.
>>> Bad source documents (not X3D).
>>> -metadata should be an array or a containerField.
> 
> all the best, Don
> -- 
> Don Brutzman  Naval Postgraduate School, Code USW/Br       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