[sldev] s/Second Life/Snowglobe/g

[Melinda Green]

Rob Lanphier wrote:
> Check out these messages notifications.xml:
>
> Viewer:
> notifications.xml:Cache will be cleared after you restart [SECOND_LIFE].
> notifications.xml:Cache will be moved after you restart [SECOND_LIFE].
> notifications.xml:Port settings take effect after you restart [SECOND_LIFE].
> notifications.xml:The new skin will appear after you restart [SECOND_LIFE].
> notifications.xml:[SECOND_LIFE] crashed while initializing graphics drivers.
> notifications.xml:You can still look at existing IM and chat by clicking
> 'View IM & Chat'. Otherwise, click 'Quit' to
> exit [SECOND_LIFE] immediately.
> notifications.xml:[SECOND_LIFE] installation is complete.
> notifications.xml:A new version of [SECOND_LIFE] is available.
> notifications.xml:An updated version of [SECOND_LIFE] is available.
> notifications.xml:A new version of [SECOND_LIFE] is available.
>
> Website:
> notifications.xml:You can propose to another Resident or dissolve an
> existing partnership through the [SECOND_LIFE] website.
> notifications.xml:Go to the [SECOND_LIFE] events web page?
> notifications.xml:Go to the [SECOND_LIFE] web page to see auction
> details or make a bid?
> notifications.xml:Visit the [SECOND_LIFE] Wiki and learn how to report
> bugs correctly.
> notifications.xml:Visit the [SECOND_LIFE] Wiki for details of how to
> report a security issue.
> notifications.xml:Visit the [SECOND_LIFE] QA Wiki.
> notifications.xml:Visit the [SECOND_LIFE] Public Issue Tracker, where
> you can report bugs and other issues.
> notifications.xml:Visit the [SECOND_LIFE] Wiki for info on how to use
> the Public Issue Tracker.
>
> The world:
> notifications.xml:You must agree to the Terms of Service to continue
> logging into [SECOND_LIFE].
> notifications.xml:You need an account to enter [SECOND_LIFE]. Would you
> like to create one now?
> notifications.xml:You have been logged out of [SECOND_LIFE]:
> notifications.xml:You can build new objects in some areas of [SECOND_LIFE].
>
> Ambiguous:
> notifications.xml:You can use [SECOND_LIFE] normally and other users
> will see you correctly.
> notifications.xml:If this is your first time using [SECOND_LIFE], you
> will need to create an account before you can log on.
> notifications.xml:Press the F1 key at any time for help or to learn more
> about [SECOND_LIFE].
> notifications.xml:You must download this update to use [SECOND_LIFE].
>
> Here's my thinking on how to tackle this.  Let's do the least disruptive
> thing for now, which is to replace the instances of [SECOND_LIFE] in the
> "Viewer" category with [VIEWERNAME], and then make
> [VIEWERNAME]="Snowglobe"  Since  we're not likely to change the "Second
> Life" string for those in this release, we can leave the others
> "SECOND_LIFE" for now.  There's a lot of bikeshed arguments about what
> to name the other categories, but it'll be more obvious not only what to
> name the new token but where it should be sourced from at the time that
> we're ready to change those to other values.
>
> Sound reasonable?

It's trickier than that. For one thing, for this to do what you want, we 
need to distinguish between "Second Life" the place, and "Second Life" 
the viewer. For example, we don't want to say "You need an account to 
enter Snowglobe". Users will still be logging into Second Life, they'll 
just be using Snowglobe to do that. Some of these problems might be 
fixed by simply removing a few of the items from your list.

The other thing I highly suggest is to try to stop using the term 
"viewer", or at least think of that term as part of the name of the 
other one. In this case that means using the tag CLIENT_NAME instead of 
VIEWER_NAME. This way the new *client* name is "Snowglobe" while the old 
client has the awful name "The Second Life Viewer".

Putting it all together and creating a worst case example, imagine a 
message that contains both the client and world concepts. Imagine that 
you want the English version to say
       "Snowglobe has lost contact with Second Life. Please check your 
Internet connection."
We'd then need an entry in notifications.txt that reads
       "[CLIENT_NAME] has lost contact with [SECOND_LIFE]. Please check 
your Internet connection."

It may be a straight forward task but it's not trivial. We can quibble 
over the client verses viewer thing but I think that all of the above 
needs to happen. The only question is whether you've missed the merge 
window in which to do it. ;-)

-Melinda