See also 2.7 JSON Encoding in the glTF spec: "Non-ASCII characters stored in glTF JSON MAY be escaped. [...] [Two examples differing only in string escaping] represent the same glTF JSON data."
To Reproduce
Open EscapedUnicodeTest.glb.zip with bin/gltf_viewer from the latest release. Note that the node name is shown as \u4f60\u597d.
Do the same with UnicodeTest.glb.zip. Note that the node name is shown as ??. (Presumably this is because the font doesn't have the correct glyphs. This issue is just about the discrepancy though, not the font.)
Expected behavior
No difference between these persists beyond the JSON loading phase.
Screenshots
With "\u4f60\u597d"
With "你好"
Desktop (please complete the following information):
OS: Linux
GPU:
Backend:
Additional context
The Blender glTF exporter currently writes the escaped form (it's the default for Python's builtin JSON library). A user presumably noticed the difference in Filament and reported a bug to Blender: https://projects.blender.org/blender/blender/issues/121692
Describe the bug Escaped unicode characters in glTF are treated differently than unescaped ones.
See also 2.7 JSON Encoding in the glTF spec: "Non-ASCII characters stored in glTF JSON MAY be escaped. [...] [Two examples differing only in string escaping] represent the same glTF JSON data."
To Reproduce
bin/gltf_viewerfrom the latest release. Note that the node name is shown as\u4f60\u597d.??. (Presumably this is because the font doesn't have the correct glyphs. This issue is just about the discrepancy though, not the font.)Expected behavior No difference between these persists beyond the JSON loading phase.
Screenshots With
"\u4f60\u597d"With
"你好"Desktop (please complete the following information):
Additional context The Blender glTF exporter currently writes the escaped form (it's the default for Python's builtin JSON library). A user presumably noticed the difference in Filament and reported a bug to Blender: https://projects.blender.org/blender/blender/issues/121692