XTCE String types should not have ByteOrderList #701
Comments
Some kinds of char encodings are multi-byte. I wouldn't necessarily say all strings then can't have a byte order. However XTCE 1.1 is a little broken or at least poor in this area, there's an attempt to clean it up in XTCE 1.2 -- but its not out yet. |
COSMOS doesn't currently support character encodings, so for now, endianness of strings has no meaning or effect within COSMOS. |
I'm trying to decide how this should be handled. I suppose if it appears, you could either totally stop or issue a warning. Should the element be pre-filtered it out so the file can be accepted? |
If you have a pull request we'll be happy to take a look at it once you sign the Contributor License Agreement. |
Strings are always single byte values so don't do anything with endianness.
The text was updated successfully, but these errors were encountered: