UI Linguistic-Truncation Smoke Test/Part 2

<< Back to UI Linguistic-Truncation Smoke Test
VERSION: Viewer 1.23 and above
= Additional Features =
* 10.1 God Tools
** 10.1.1 Setup step: Ctrl+Alt+D to open the Advanced menu. Click Advanced menu > View Admin Options.
** 10.1.2 Click Admin menu > God Tools... (floater_god_tools.xml)
* 10.2 Memory Leaking Simulation 
** 10.2.1 Setup step: you will need to exit the Viewer and run it in QA mode. 
*** To use the viewer in QA mode (Windows), right click the Second Life property icon and open Properties. In Target field, add --qa to the end of the existing line of data. Choose Apply, then OK. Now, run the viewer again.
*** To use the viewer in QA mode (Mac), go to Applications, then Cmd-click the Second Life icon and select "Show Package Contents". Open Contents > Open Resources > Open "Arguments.txt" and add --qa. Close the file and save it. Now, run the viewer again.
** 10.2.2 From the menus, choose Advanced > Rendering > Memory Leaking Simulation (floater_mem_leaking.xml)
= Notifications =
* 11.1 Alerts and Notifications (notifications.xml)
** NOTE: Generally, these are displayed in their own centered dialog window, so they are not subject to truncation problems most of the time. However, some legacy formatting by the viewer may cut off a final word/letter in rare cases.
** There are too many popup/error messages/warning dialog windows that can occur in Second Life to trigger them all in context. However, translators can utilize a debugging console to review the output of notifications as they might appear:
** 11.1.1 Use the Advanced menu > Consoles > Notification Console (floater_notification.xml, floater_notifications_console.xml, panel_notifications_channel.xml)
** 11.1.2 Once the console appears, you can choose any named Notification from the top dropdown menu, and click "Add" button to display it (ie, to add it to a faux queue of notifications). 
** 11.1.3 Select and "add" every item in the list, one at a time, and review the results for truncations or errors. Note that variables like [NAME] will appear as the variable name, since this is not a "live" action.
= Other strings =
* 11.2 Strings not used in windows (strings.xml)
**This file contains strings which don't belong in a floater, for example, the strings used in avatar chat bubbles, and strings that are returned from one component and may appear in many places. There is no direct way to trigger them all in context. However, translators can review the strings.xml file in a separate XML editor to review such messages that can appear. 
**11.2.1 <!-- Login --> Section
*** These strings are shown with the progress bar as you are logging into the Second Life viewer (and the world is loading, etc).
*** NOTE: Generally these are not subject to truncation problems, since they are short and use almost the entire window-width.
**11.2.2 <!-- Tooltip --> Section
*** These strings are shown in hover tip bubbles as you hover over objects inworld. To see this feature, you must enable View > Hover Tips > Show Tips on All Objects
*** NOTE: Generally these are not subject to truncation problems, since tooltips are drawn in a bubble that will resize to fit any string.
**11.2.3 <!-- animations --> Section
*** These strings are the descriptive names of the common gestures such as /clap. To see these strings, you must create or edit a Gesture from Edit > Gestures..., then click on New button. Add an Animation from the leftside Library to the rightside Steps and choose from the dropdown.
*** NOTE: Generally these are not subject to truncation problems, since the dropdown will resize to fit reasonable-sized strings.
**11.2.4 <!-- Chat --> Section
*** These strings are used as descripters in Local Chat.
*** NOTE: Generally these are not subject to truncation problems, since Local Chat allows unlimited lengths and wraps words.
* 11.3 Strings for teleport (teleport_strings.xml)
**This file contains strings which are used during a Teleport, whether successful or failed due to an error. There is no direct way to trigger them all in context. However, translators can review the teleport_strings.xml file in a separate XML editor to review such messages that can appear. 
*** NOTE: Generally these are displayed in their own window, and not subject to truncation problems.
* 11.4 Strings for instant message errors (floater_im.xml)
**This file contains strings which are used during a (Group) IM session, for status or due to an error. There is no direct way to trigger them all in context. However, translators can review the strings.xml file in a separate XML editor to review such messages that can appear. 
*** NOTE: Generally these are not subject to truncation problems, since Local Chat allows unlimited lengths and wraps words.
= Fonts =
* The file fonts.xml has no localizable strings and is NOT shown anywhere in the user interface. Rather, this file is to specify the font definitions (typeface, style, size) to use in the viewer.
** See this page for more information: Skinning How To/The XML files/fonts.xml