|
![](/i/fill.gif) |
Mike Raiford <"m[raiford]!at"@gmail.com> wrote:
> The unicode thing to me is strange, though. Why is it capable of only
> displaying part of the string?
Possibly using UTF-8 to store the string, giving you a non-constant number of
bytes per character, which makes handling such strings (like, say, displaying
the substring starting from the 42th character) non-trivial.
Add limitations of the software design chosen before they decided to add Unicode
support at all, and pressure to finish the product on time, and you're there.
Post a reply to this message
|
![](/i/fill.gif) |