Unicode strings: Difference between revisions
Content added Content deleted
m (If there is a "Task" heading like that then it ends up on the TOC eventually and looks weird) |
({{header|ZX Spectrum Basic}}) |
||
| Line 23: | Line 23: | ||
PicoLisp can directly handle _only_ Unicode (UTF-8) strings. So the problem is rather how to handle non-Unicode strings: They must be pre- or post-processed by external tools, typically with pipes during I/O. For example, to read a line from a file in 8859 encoding: |
PicoLisp can directly handle _only_ Unicode (UTF-8) strings. So the problem is rather how to handle non-Unicode strings: They must be pre- or post-processed by external tools, typically with pipes during I/O. For example, to read a line from a file in 8859 encoding: |
||
<lang PicoLisp>(in '(iconv "-f" "ISO-8859-15" "file.txt") (line))</lang> |
<lang PicoLisp>(in '(iconv "-f" "ISO-8859-15" "file.txt") (line))</lang> |
||
=={{header|ZX Spectrum Basic}}== |
|||
The ZX Spectrum does not have native Unicode support. However, it does support user defined graphics, which makes it is possible to create custom characters in the UDG area. However, there is only 48k of memory available on a traditional rubber key ZX Spectrum, (or 128k on some of the plus versions), and 510k would be needed to store the Unicode characters for display, so Unicode is not really viable on this platform. |
|||