[#SVC-4059] Identify LSL external communications functions not supporting UTF-8

2. Second Life Service - SVC

Identify LSL external communications functions not supporting UTF-8

Created: 31/Mar/09 01:55 PM Updated: 31/Aug/09 12:10 PM

Return to search

Component/s:

LSL HTTP, Scripts, XML-RPC

Affects Version/s:

1.25 Server, 1.26 Server

Fix Version/s:

None

Issue Links:

Relates

This issue Relates to:

SVC-391 llEmail and llHTTPRequest do not handle non-ASCII characters

SVC-1144 replies to offline emails can't contain unicode

SVC-3717 Email from out of SL does not arrive with specific encoding.

MISC-398 Meta-Issue: Meta-Issue Organization

Linden Lab Internal Branch:

DEV-29873

Description

« Hide

We need tests and reports on how well all of the sundry communications channels available from LSL do in handling non-ASCII characters. SVC-391 identifies llEmail and llHttpRequest as two channels that have problems. Can people please report success or failures on other channels of communication, including email, Im-to-email, XMLRPC, Http-In (on the Http-In sandboxes), and other things that I'm not thinking of right now? The goal is to identify all of these channels so we can get non-ASCII characters in LSL communications working once and for all....

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Nock Forager added a comment - 01/Apr/09 12:57 AM

Add related issue SVC-1144.
Detailed test done by Alissa may help?

[ Permlink | « Hide ]

Fake Fitzgerald added a comment - 02/Apr/09 02:20 AM

Link to an issue SVC-3717 I've posted.

[ Permlink | « Hide ]

Strife Onizuka added a comment - 02/Apr/09 05:44 AM

You don't need to post when your linking an issue, it shows up in the "Change History" and "All" views

[ Permlink | « Hide ]

Aargle Zymurgy added a comment - 30/Aug/09 05:14 PM

This was directed to my attention tonight after a frustrating time trying to get non-english data from database. My test, so far, is small so I can validate the techniques. Elements:

1) SQL Server database with ntext fields containing non-english text.
2) ASP page that gets a record from the database.
3) short LSL script to request the data.

Important notes: first,SQL Server stores data as UCS-2 (ick). However, with the addition of codepage information, you can have SQL Server cough up UTF-8 (<% Session.Codepage=65001 %>). This works.

So, in my database is "貢獻 L$@0 到彩池" which is served up via the ASP page to a web-browser as plain text (no added HTML). The following is shown in the browser: "è²¢ç» L$@0 åˆ°å½©æ± ã€‚" However, if I tell the browser that it's UTF-8, it's interpreted and looks fine. That said, according to the wiki, the BODY coming in from an llHTTPRequest, by default, is supposed to be treated as UTF-8. However, no matter how I've been able to prod the system, I just get the undecoded UTF-8 ( "è²¢ç» L$@0 åˆ°å½©æ± ã€‚" ).

Basically, I'd say this was broke, but I really can't believe I'm the first to find this.

[ Permlink | « Hide ]

CG Linden added a comment - 31/Aug/09 11:41 AM

You need to set charset=utf-8 in the HTTP header, as described in http://www.w3.org/International/O-HTTP-charset

[ Permlink | « Hide ]

Aargle Zymurgy added a comment - 31/Aug/09 12:10 PM

Confirmed. Using ASP, this change made all the difference:

response.ContentType="text/plain;charset=utf-8"

I've learned a lot about this whole process. I hope to put some info in the wiki about it.