Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Why there is no support for non-US strings in LSL?
Eadoin Welles
Registered User
Join date: 5 Jan 2007
Posts: 149
02-25-2007 11:25
When I write an LSL, I have problems with strings containing any character above 0x7F. Not only Unicode is not supported, but even characters as à, è, ì, ò and ù break the script. Can you please improve the editor to support Unicode or at least Latin-1 (ISO-8859-1)?
Strife Onizuka
Moonchild
Join date: 3 Mar 2004
Posts: 5,887
02-25-2007 13:50
It does technically support UTF-8, I reported a couple months ago problems in the UTF-8 support of the compiler which is unfortunately incomplete.
_____________________
Truth is a river that is always splitting up into arms that reunite. Islanded between the arms, the inhabitants argue for a lifetime as to which is the main river.
- Cyril Connolly

Without the political will to find common ground, the continual friction of tactic and counter tactic, only creates suspicion and hatred and vengeance, and perpetuates the cycle of violence.
- James Nachtwey
Eadoin Welles
Registered User
Join date: 5 Jan 2007
Posts: 149
02-25-2007 14:28
From: Strife Onizuka
It does technically support UTF-8, I reported a couple months ago problems in the UTF-8 support of the compiler which is unfortunately incomplete.


Well, it could be enough if it would support \uxxxx in strings, at least. That would avoid to change compiler.
Ernesto Leonard
Registered User
Join date: 23 Jan 2007
Posts: 1
04-12-2007 15:36
is there a solution for this, meanwhile?
thx
RJ Source
Green Sky Labs
Join date: 10 Jan 2007
Posts: 272
04-12-2007 15:41
From: Ernesto Leonard
is there a solution for this, meanwhile?
thx


Yes you can represent utf-8 as, for example, %C3%A7 for ç

Then before printing, use llUnescapeURL on that string.

Rj
DoteDote Edison
Thinks Too Much
Join date: 6 Jun 2004
Posts: 790
04-12-2007 17:13
From: Strife Onizuka
It does technically support UTF-8, I reported a couple months ago problems in the UTF-8 support of the compiler which is unfortunately incomplete.
I ran into this problem just last night, a script that needs to chat messages in both English and French. Since you indicate this is a compiler problem... what would happen (and would it be a workaround) if I accept the strings via chat command or notecard reading? This would bypass a compile bug I would think.
Simil Miles
Creator
Join date: 1 Mar 2007
Posts: 300
04-13-2007 05:05
Bug reported on JIRA : LSL scripts created on Mac with non-ASCII characters won't compile in Windows viewer

Another solution is to compile the script on the Mac OSX or Linux viewer.
If you don't have access to one, you can ask a Mac OSX or Linux user to compile it for you (ask in corresponding groups).

(I've noticed that scripts that failed to be compiled on the Windows viewer have a corrupted state On the Mac OS X viewer: Running will not stay checked and llSetScriptState will not find the script.)
_____________________
UnConWTech @ Flo (144, 84, 224) http://unconwtech.free.fr

SL books http://astore.amazon.com/secondlife-sl-20/

Need a beta tester for quality assurance ?
Need a translator for English, French, Spanish ?
Yumi Murakami
DoIt!AttachTheEarOfACat!
Join date: 27 Sep 2005
Posts: 6,860
04-13-2007 13:45
There is definately a work around for this - a friend gave me a script a few weeks back which applies Japanese float text to an object. I'll see if I can find it when I'm in-world..
Peekay Semyorka
Registered User
Join date: 18 Nov 2006
Posts: 337
04-13-2007 17:17
A workaround was already mentioned above. Related thread:

/54/c4/170745/1.html

-pk