obj_encoder functions produce invalid OBJ files when using a non-english numeric locale about draco HOT 2 CLOSED

I believe this should be fixed in the latest release, please give it a try.

from draco.

This is still an issue in the latest release (1.5.7). I must still use the work around outlined above to ensure I get period decimal separators when my system is set to a region that uses a comma decimal separator.

Looking at the OBJ encoder code, I see the following in obj_encoder.cc

void ObjEncoder::EncodeFloat(float val) {
  // Use %F instead of %f to make the floating point non-locale aware.
  snprintf(num_buffer_, sizeof(num_buffer_), "%F", val);
  buffer()->Encode(num_buffer_, strlen(num_buffer_));
}

Both of these sources do not mention anything about the uppercase F vs lowercase f having anything to do with locale, but rather whether or not to print things like infinity or NAN in upper or lower case.

from draco.