| Latest revision |
Your text |
| Line 1: |
Line 1: |
| This page is my attempt to document my research on unique or popular Unicode implementations supported in various languages and software, in order to get a good feel for the main page I'm writing. This is mostly in note form to avoid things getting out of control and only includes implementations I find interesting. | | This page is my attempt to document my research on unique Unicode implementations supported in various languages and software. This is mostly in note form to avoid things getting out of control. |
|
| |
|
| I apologize for not attaching sources to all of this, as always double check this in case things have changed. | | I apologize for not attaching sources to all of this, as always double check this in case things have changed. |
| Line 18: |
Line 18: |
| * Supports breaking by text boundaries: No | | * Supports breaking by text boundaries: No |
| * Supports encoding and decoding to other encodings: Yes | | * Supports encoding and decoding to other encodings: Yes |
| * Supports Unicode regex extensions: No (not applicable in C as it has no regex) | | * Supports Unicode regex extensions: Not applicable, no regex included |
| * Classifies by: Locale information, only supports single characters | | * Classifies by: Locale information, only supports single characters |
| * Collates by: Locale information, supports arbitrary strings | | * Collates by: Locale information, supports arbitrary strings |
| Line 31: |
Line 31: |
| * On POSIX, characters are usually 8-bit ASCII-compatible values | | * On POSIX, characters are usually 8-bit ASCII-compatible values |
| * On Windows, characters are 16-bit UTF-16-compatible values | | * On Windows, characters are 16-bit UTF-16-compatible values |
| Actual support for locales depends on your libc implementation, and this affects most languages that run on your computer. For example, on Linux glibc seems to be the only libc that supports uppercasing Unicode text.
| |
|
| |
|
| == Lua == | | == Lua == |
| Line 134: |
Line 133: |
|
| |
|
| == JavaScript == | | == JavaScript == |
| JavaScript follows Java's model but with a few less features. | | JavaScript is a bit like Java. |
| *Character type: 16-bit | | *Character type: 16-bit |
| * Byte strings: No | | * Byte strings: No |
| Line 154: |
Line 153: |
| * Locale tailoring is done by: Providing a locale object | | * Locale tailoring is done by: Providing a locale object |
| * Wraps operating system APIs with Unicode ones: Yes | | * Wraps operating system APIs with Unicode ones: Yes |
| | Similar to Java basically. |
| | |
| == Swift == | | == Swift == |
| Swift has an interesting idea about defining characters as extended grapheme clusters. | | Swift has an interesting idea about defining characters as extended grapheme clusters. |
| Line 180: |
Line 181: |
| == Go == | | == Go == |
| Go has a kind of unopinionated take here. | | Go has a kind of unopinionated take here. |
| *Character type: 32-bit integer, Unicode code point | | *Character type: 32-bit integer |
| * Byte strings: Yes | | * Byte strings: Yes |
| * Internal encoding: None | | * Internal encoding: None |
| Line 202: |
Line 203: |
| I would probably put this between Lua and C for bad interfaces. | | I would probably put this between Lua and C for bad interfaces. |
|
| |
|
| Bonus points for deciding shortening 'code point' to 'rune' is worth having to look up what a rune is.
| | == Tcl == |
|
| |
|
| == Ruby == | | == Squirrel == |
| Ruby hasn't really had a major refactoring for Unicode like contemporary languages.
| |
|
| |
|
| *Character type: Arbitrarily large integers, unspecified character set
| | == Perl == |
| * Byte strings: Yes
| |
| * Internal encoding: None
| |
| * String encoding: Any
| |
| * Supports bytes in strings: No for UTF-8/UTF-16/UTF-32 strings
| |
| * Supports surrogates in strings: No for UTF-8 strings
| |
| * Supports invalid code units in strings: No for UTF-8 strings
| |
| * Supports normalizing strings: Yes
| |
| * Supports querying character properties: Yes
| |
| * Supports breaking by code point: Yes for UTF-8 text
| |
| * Supports breaking by extended grapheme cluster: Yes
| |
| * Supports breaking by text boundaries: No
| |
| * Supports encoding and decoding to other encodings: Yes
| |
| * Supports Unicode regex extensions: Yes
| |
| * Classifies by: Unicode properties
| |
| * Collates by: Doesn't provide an API for this
| |
| * Converts case by: Unicode properties with Turkic language support
| |
| * Locale tailoring is done by: Doesn't provide an API for this
| |
| * Wraps operating system APIs with Unicode ones: No
| |
|
| |
|
| If you use UTF-8 strings only in Ruby then you might be able to have a good experience.
| | == Ruby == |
|
| |
|
| == Erlang == | | == Elixir == |
| Erlang is kind of an alien language compared to all the above.
| | - erlang too? |
|
| |
|
| *Character type: Integer, Unicode code point
| | == Raku == |
| * Byte strings: Yes
| |
| * Internal encoding: I don't know
| |
| * String encoding: A mix of integers or UTF-8 strings
| |
| * Supports bytes in strings: Yes
| |
| * Supports surrogates in strings: Yes
| |
| * Supports invalid code units in strings: Yes
| |
| * Supports normalizing strings: Yes
| |
| * Supports querying character properties: No
| |
| * Supports breaking by code point: Yes
| |
| * Supports breaking by extended grapheme cluster: Yes
| |
| * Supports breaking by text boundaries: No
| |
| * Supports encoding and decoding to other encodings: Yes
| |
| * Supports Unicode regex extensions: Yes
| |
| * Classifies by: Doesn't provide an API for this
| |
| * Collates by: Doesn't provide an API for this
| |
| * Converts case by: I don't know
| |
| * Locale tailoring is done by: Doesn't provide an API for this
| |
| * Wraps operating system APIs with Unicode ones: No
| |
| | |
| Unicode support seems fairly limited and confusing here.
| |
|
| |
|
| == Raku == | | == Haskell == |
| Raku seems to have had the most thought put in to its Unicode support.
| |
|
| |
|
| *Character type: 32-bit integer
| | == PHP == |
| * Byte strings: Yes
| | - narrow APIs |
| * Internal encoding: A mix of signed integers of various sizes
| |
| * String encoding: Normalized grapheme clusters
| |
| * Supports bytes in strings: Yes
| |
| * Supports surrogates in strings: I don't know
| |
| * Supports invalid code units in strings: I don't know
| |
| * Supports normalizing strings: Yes
| |
| * Supports querying character properties: Yes
| |
| * Supports breaking by code point: Yes
| |
| * Supports breaking by extended grapheme cluster: Yes
| |
| * Supports breaking by text boundaries: No
| |
| * Supports encoding and decoding to other encodings: Yes
| |
| * Supports Unicode regex extensions: Yes
| |
| * Classifies by: Unicode properties
| |
| * Collates by: Unicode properties
| |
| * Converts case by: I don't know
| |
| * Locale tailoring is done by: Doesn't provide an API for this
| |
| * Wraps operating system APIs with Unicode ones: Yes, with UTF-C8 to escape bytes
| |
|
| |
|
| Interesting it doesn't contain wrappers like isalpha, isupper, etc.
| | - mbstring |
| [[Category:Research]] | | [[Category:Research]] |