how to get chat text to appear in white instead of green?

text = llDumpList2String( llParseString2List( text, [" "], [] ), insert );

If you want to preserve adjacent spaces:

text = llDumpList2String( llParseStringKeepNulls( text, [" "], [] ), insert );

Doesn't work in Cool Viewer. In fact Cool Viewer also leaves a space and does not insert the *. Chatting "secondlife:///app/chat/0/Hello world" or "secondlife:///app/chat/0/Hello*world" results in a clickable link but nothing happens when it is clicked in history. Slurls and urls both work fine thou.

To make it even stranger, SL beta client also does not replace the url and the result is also ""secondlife:///app/chat/0/Hello world", it is a clickable link and it works just fine. It will chat "Jesse Barnett: Hello world" with "Hello world" in blue.

I can't imagine what Henry could have done so that it does not work. Guess I'll be sending a query to Boy Lane this afternoon.

EDIT: I guess it is even stranger that the link is valid and works correctly in SL beta viewer considering it is not a legal link with the space.

Chaz, drop this in a prim and then touch it. Then touch the resulting link in chat history.

default
{
    touch_start(integer total_number)
    {
        llOwnerSay("secondlife:///app/chat/0/Hello" + llUnescapeURL("%c2%ao") + "world");
    }
}

OK, so what the hell is ///app/chat? What is the purpose for its existence, what other apps are there, and where did you learn this?

I'm just glad that Day Oh uses that brilliant mind of his for good instead of evil

Too bad "/me" doesn't work with that app. Not surprising, though.

A slash is interpreted as a path separator, so it ends up being "me". Escaping it doesn't work because the app doesn't unescape before chatting (too bad).

For those who are curious, you can find the list of the "secondlife:///" URI parameters here:

I'm there there are more than that small list, or at least more extensions... I seem to remember search being one of them

it breaks down to
secondlife:/// <-- program that handles the request
app/ <-- tells the program what group of functions to pick from
<specific function thats being used + parameters>

so that
secondlife:///app/chat/0/Blah
ACTS LIKE a (nonexistent in lsl) function llAvatarSay( integer channel, string message) for any person clicking the link in the history

ETA:
ps what exactly is the %C2 doing?

i was wondering that too what each funtion was doing, i tried each one separately (%c2 and $ao), both just put a question mark instead of a space, but it put a space when i put it together

edit:

# /chat

* /<channel> any channel number greater then or equal to 0
o /<text>

interesting, so negative channels won't work, so i guess dialog is still the only way to get an avatar to speak on a negative channel

and this could be an alternative function for leaving messages without having to look for a a profile

/app/agent/<agent_id>/im to start IM session

It isn't actually putting a space in there, even if that is what you see. Evidently with some operating systems it is placing *. But I don't see that either, I also see "what looks" like a space. But if you copy the output link that works and paste it back into chat it is still a valid link and works. BUT if you type the exact same line into chat with a space, where it looks like there is a space, the link drops " hello".

Could a script "open" the URL to make the chat happen?

/me reminds oneself that one can try it in seconds instead of asking question, so / me will right now :}

Well heck if you can pull off that trick let me know. I will put up my own $L2000 bounty for that solution because the same could then be applied to a slurl tp:

secondlife:///app/teleport/Sesia/83.537470/20.360020/602.515600

oh my word, tried that SLURL and ended up in a boudoir :} (grin)

Yep, it's just below the torture chamber and above the stable

LOL!

well %A0 is the encoded form of the html entity   or the non-breaking space (which is why it's valid in a url, because it's ignored for breaking lines on spaces)

from the ascii character map %C2 is the encode for  (Capital "a" circumeflex accent) or the same as the html Â

I was just wondering if it was doing something special in this case

%20 (the encode for a space) won't work because the viewer breaks it along the space in the chat history window. although I haven't tried it as encoded, it might work. (in which case you could just replace spaces with it using the string to list to string method)

EDIT:
just tested it, doesn't work. and I realized what the %C2 is... it's the utf-8 control code. so that %C2%A0 = non-breaking space... duh, of course the url de/en-code functions would treat everything as utf-8

quick function to replace regular spaces with non-breaking ones

string fStrHardenSpaces( string vStrInput ){
    return llDumpList2String( llParseString2List( vStrInput. (list)" ", [] ), llUnescapeURL( "%C2%AO" ) );
}
//-- you can replace llUnescapeURL( "%C2%AO" ) with a hand typed
//-- quotation mark, alt+0160 (or alt+049824), quotation mark that'll look like " "

the forum apparently replaces nbsp with *

PS. the history window, chat display, and chat bubbles still correctly wrap with nbsp... good to know

but parsestring2list only works for up to 8 spacers right? which is why i didn't go that route


EDIT: oh ok, i read that wrong, i was thinking you could only seperate up to 9 words (a space between each 2) read it again and realized, it means you can specify up to 8 seperators and spacers. but i did just test another string, this time with some words with an apostrophe. it breaks the link there, any way around that?