On 7/30/07, David Sanders <[EMAIL PROTECTED]> wrote: > > To resolve this, I need to calculate MANUALLY what could be the length > of > the value with this special characters, and make the field bigger... > > Correct. AR System developers tend to triple the number of single-byte > characters needed in fields to enable multi-byte or unicode data. In > other > words, if you expect 20 "characters" in English, you should allocate 60 > bytes to the field if the field may contain multi-byte languages.
Well, that's my point. First of all you'd have to manually check the fields (didn't we have input length for that?) and secondly you need to make your fields 4 times bigger (to hold 25 chars, size to 100 bytes) because an unicode character can be 4 bytes wide at most. This won't always work, for example for a field that should have a limit of 100 characters. BMC can document this all they want, and change the tool tips of the usertool to "this field can hold up to x bytes", but again, my users are not thinking bytes, they are thinking characters. So if you'd ask me if that's proper unicode support, I'd say "no sir" :) But my bets are on the RFE that we've filed regarding unicode support, it's "under consideration" for a next major release. Hugo _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
