[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Testing LUA: verify the correctness of a UTF16 LUA port
- From: Joshua Jensen <jjensen@...>
- Date: Wed, 14 Oct 2009 21:03:35 -0600
----- Original Message -----
From: David Given
Date: 10/14/2009 8:31 PM
It does the equivalent of wcscmp(), only it doesn't rely on the C
runtime to achieve this. That's because on some non-Visual C++
compilers, sizeof(wchar_t) != 2. sizeof(lua_WChar) is always 2.
Joshua Jensen wrote:
LuaPlus achieves this via a C-like string representation:
HelloWorld = L"Hello world!"
What does LuaPlus do for things like string comparison and surrogates?
My understanding is that UCS-2 doesn't support surrogates. I don't
think Microsoft's C runtime wide character library supports them
either. I could be wrong.
I would consider ditching the LuaPlus wide character support if there
was a small library that supported UTF-8 and allowed easy embedding of
UTF-8 string types in Lua source files.
Do any of them use UTF-8?
I work in mobile games; our company makes a portable native gaming
solution that allows you to install C-based games on any device,
regardless of architecture. The API's based on OpenKODE, which uses
UTF-8 in the few places where it uses strings. As I tend to do the
bottom-end porting to weird and freaky embedded operating systems,
I've got tiresomely familiar with having to translate UTF-8 to
whatever encoding the host OS uses. There are a surprising number that
use some form of half-assed UCS-2, and I've never figured out why ---
it just makes life complex. I suspect that it's simple tradition. Most
of them come from Asia, and Asia seems to have a culture of using
UCS-2 or UTF-16...
Have you looked at slnunicode? That seems to be the smallest one I can
find, but documentation is scarce, so I don't know if it achieves all of