New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Separator Hell #85

Open

LeonaMorro opened this issue Jul 13, 2016 · 0 comments

Member

LeonaMorro commented Jul 13, 2016

There are so many different separators that I loose the overview.
Example:

I guess it would be a bad idea to use "^" in the string part of a SATMSG?
or maybe "§" or "^" or "," or "|" as a part of a seat name?
I realy don't now wich signs I must not use in a button name (NC name)
may I use all signs for the Object name of a prim?
we don't want to use the NC_CONTENT_SEPARATOR in an NC

Can we:

make a users guide which signs should be avoided?
define some design goals for the future?
consider using JSON (even if JSON parsing is incredible slow) for the string part of internal link messages?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment