Hello! I'm new to these forums, so sorry if this is the wrong place. I'm working on code to load ldraw files and noticed that not all parts seem to use valid utf8. The file "LDraw\parts\s\2902s01.dat" contains comment lines that don't decode properly as utf8 in programming languages like Python or Rust due to a missing continuation byte. The comment renders in some editors as "0 Cran creus�". I would expect the e with an accent to be C3A9 in hex, but the file is only using the single byte E9. The entire phrase appears in the file as 3020 4372616E 20637265 7573E9. LDView displays the text just fine as "0 Cran creusé". Is this part valid? Should programs match the behavior of LDView?
invalid utf8 in part 2902 (2902s1.dat)
« Next Oldest | Next Newest »
Messages In This Thread |
invalid utf8 in part 2902 (2902s1.dat) - by Jonathan N - 2023-02-21, 23:44
RE: invalid utf8 in part 2902 (2902s1.dat) - by Orion Pobursky - 2023-02-21, 23:50
RE: invalid utf8 in part 2902 (2902s1.dat) - by Jonathan N - 2023-02-22, 0:03
RE: invalid utf8 in part 2902 (2902s1.dat) - by Orion Pobursky - 2023-02-22, 1:00
RE: invalid utf8 in part 2902 (2902s1.dat) - by Travis Cobbs - 2023-02-22, 22:10
|
Users browsing this thread: 1 Guest(s)