Unicode strings: Difference between revisions
Content added Content deleted
m (added whitespace before the TOC (table of contents), added a ;Task: (bold) header, added other whitespace to the task's preamble, added more bullet points (from existing compound questions).) |
|||
Line 1: | Line 1: | ||
{{task}} |
{{task}} |
||
As the world gets smaller each day, internationalization becomes more and more important. For handling multiple languages, [[Unicode]] is your best friend. |
As the world gets smaller each day, internationalization becomes more and more important. For handling multiple languages, [[Unicode]] is your best friend. |
||
It is a very capable tool, but also quite complex compared to older single- |
It is a very capable tool, but also quite complex compared to older single- and double-byte character encodings. |
||
and double-byte character encodings. How well prepared is your programming language for Unicode? Discuss and demonstrate its unicode awareness and capabilities. |
|||
How well prepared is your programming language for Unicode? |
|||
;Task: |
|||
Discuss and demonstrate its unicode awareness and capabilities. |
|||
Some suggested topics: |
Some suggested topics: |
||
⚫ | |||
:* Can Unicode literals be written directly, or be part of identifiers/keywords/etc? |
|||
⚫ | |||
:* Is it good at input/output with Unicode? |
|||
⚫ | |||
⚫ | |||
:* What encodings (e.g. UTF-8, UTF-16, etc) can be used? |
|||
:* Does it support normalization? |
|||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
;Note: |
|||
'''Note''' This task is a bit unusual in that it encourages general discussion |
|||
rather than clever coding. |
This task is a bit unusual in that it encourages general discussion rather than clever coding. |
||
⚫ | |||
⚫ | |||
* [[Unicode variable names]] |
* [[Unicode variable names]] |
||
* [[Terminal control/Display an extended character]] |
* [[Terminal control/Display an extended character]] |
||
<br><br> |
|||
=={{header|80386 Assembly}}== |
=={{header|80386 Assembly}}== |