Displaying 1 result from an estimated 1 matches for "internationalizable".
2000 May 12
9
comment field proposal
...0x3D is followed by 8 bit clean field contents to the end of the field.
Implications: field names should not be 'internationalized'; this is a
concession to simplicity not an attempt to piss off the majority of the world
that doesn't speak English. Field *contents*, however, should be
internationalizable... suggestions on the proper encoding for that?
We have the length of the entirety of the field and restrictions on the field
name so that the field name is bounded in a known way. Thus we also have the
length of the field contents.
Individual 'vendors' may use non-standard field names w...