Talk:Terminal control/Display an extended character: Difference between revisions
Content added Content deleted
(Don't like this draft task at all) |
(we need more localization tasks like this) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
This is a poor candidate for a task, as it depends too much on the capabilities of the environment. (Crudely, writing a non-ASCII character is pretty much trivial as soon as I/O is supported by the language at all, but what that displays as depends on what the terminal does.) –[[User:Dkf|Donal Fellows]] 11:49, 25 November 2010 (UTC) |
This is a poor candidate for a task, as it depends too much on the capabilities of the environment. (Crudely, writing a non-ASCII character is pretty much trivial as soon as I/O is supported by the language at all, but what that displays as depends on what the terminal does.) –[[User:Dkf|Donal Fellows]] 11:49, 25 November 2010 (UTC) |
||
Unicode, other extended character sets, and localization in general are facts of life in this modern global era. I think it would be a fine task. Even better would be to show how to choose the output character set, if applicable. --[[User:IanOsgood|IanOsgood]] 19:08, 30 November 2010 (UTC) |
|||
Latest revision as of 19:08, 30 November 2010
This is a poor candidate for a task, as it depends too much on the capabilities of the environment. (Crudely, writing a non-ASCII character is pretty much trivial as soon as I/O is supported by the language at all, but what that displays as depends on what the terminal does.) –Donal Fellows 11:49, 25 November 2010 (UTC)
Unicode, other extended character sets, and localization in general are facts of life in this modern global era. I think it would be a fine task. Even better would be to show how to choose the output character set, if applicable. --IanOsgood 19:08, 30 November 2010 (UTC)