#8 Unicode Strings

[Eric Seidel]

OpenAG currently does not handle the conversion
between the server encoding (WindowsLatin1)
and the native client encoding... whatever that may
be... platform dependant.

A great way to do that would be to abstract the
string interface via a AGString structure. This has
been partially implemented already, however the
source is not currently online. Implementing this
abstraction layer is WAY up there on my list of
things to do.

The goal would be to read the strings in from the
server or in from the local hard disk, or from
hardcoded sources... either way, an AGString
object would be constructed and then whenever a
string of a certain type was needed... say to go to
the server, to go to the display, or to go to the file
system, one could be automatically constructed
(on a platform specifc basis) from within the
AGString abstraction layer.

Anyone interested in helping me implement this
functionallity, or who has suggestions for
compariable pre-existing functionality which I could
tap into... PLEASE CONTACT ME.

[Eric Seidel]

Logged In: YES
user_id=151346

The goal here has been changed.

AGString has been removed from the goal regarding
this bug, and instead functions string_localToServer
and string_serverToLocal are being used to translate
the one piece of data which we care about (Filename).

What is remaining on this bug is a POSIX
implementation of these two functions, which should
go into default.cpp. the MacOS X implementation is in
darwin.mm

[Eric Seidel]

Logged In: YES
user_id=151346

Regarding implementing FileName/FolderName conversion from
WindowsLatin1 (ANSI codepage 1252) to your local file system format...
this document (Thanks to justin fletcher) might help that.

Remember, the two functions in platform/ as seen in default.cpp need to
be implented for your file system.

ftp://ftp.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/
CP1252.TXT