Mail Archives: djgpp/1999/11/08/07:32:14
Forsberg Sakari writes:
>> Recent versions of Allegro (the current WIP is 3.926) and later use
>> the Unicode UTF-8 encoding instead of ASCII.
>
> I have Allegro version 3.12. So I should upgrade mine?
If you want Unicode support, yes.
>> Try getting yourself a text editor
>> that supports UTF-8 and using it as your code editor.
>
> FED?
Nope. Like most code editors, FED just uses normal 8 bit chars,
which are displayed in whatever codepage your OS happens to be
using at the time.
There are some Unicode-aware editors around, but I don't know enough
to recommend any in particular. I found a dozen or so when I did a
quick web search a few months ago, though, so these aren't hard to
find. Alternatively there is a good chance that Emacs can do this
(I don't use it, but it seems to support just about everything :-)
Or you can write your text using some other format (8 bit Latin-1
codepage, or 16 bit Unicode, or 8 bit in whatever codepage you like
if you make a mapping file describing how to convert that to Unicode),
and then use the Allegro textconv program to turn this into UTF-8
(that's how I do it: I have my editor set up so I can enter strings
as 16 bit Unicode and then hit a keyboard shortcut to shell out to
textconv, which replaces them with a UTF-8 version of whatever I
typed).
Shawn Hargreaves.
- Raw text -