[#VWR-2292] Wrong and missing Japanese translation on Preferences dialog box

1. Second Life Viewer - VWR

Wrong and missing Japanese translation on Preferences dialog box

Created: 31/Aug/07 11:16 PM Updated: 16/Apr/08 08:46 AM

Return to search

Component/s:

Internationalization, User Interface

Affects Version/s:

1.18.3 Release Candidate, 1.18.1.2, 1.18.2.0

Fix Version/s:

None

File Attachments:

None

Image Attachments:

1. AdvGraphics.png (158 kB)	2. AudioVideo.png (159 kB)	3. Communication.png (175 kB)
4. Graphics.png (128 kB)	5. GraphicsDetails.png (144 kB)	6. Network.png (126 kB)
7. Popups.png (161 kB)	8. Web.png (131 kB)

Environment:

« Hide

Windows XP SP2 (Japanese version)
Viewer RC 1.18.3.2

Issue Links:

Relates

This issue Relates to:

~~VWR-4125~~ Duplicate names in XUI files make some translated UI texts to show inappropriately

This issue is related to by:

VWR-6607 Japanese UI translation is out of date.

Source Version:	1.18.3.2
Linden Lab Issue ID:	SL-53923

Description

« Hide

When running the viewer in Japanese UI, the Preferences.. dialog box is shown in Japanese. Unfortunately, some text are wrong or some other are not translated.

See attached PNG files for details and suggested corrections. Japanese-only comments are suggested translation, and the English sentences are explanations of problems.

This issue has been there since 1.18.1.2.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Alissa Sabre added a comment - 05/Sep/07 06:58 AM

Updated the affected version per Bridie Linden's request.

[ Permlink | « Hide ]

Jaime Linden added a comment - 17/Sep/07 09:28 AM

We are working on this now. Some of the issues may take longer to fix.

[ Permlink | « Hide ]

Alissa Sabre added a comment - 10/Feb/08 09:33 PM

Some of the wrong/missing translation in this issue is caused by the bug described in ~~VWR-4125~~. Some others are simple translation error.

[ Permlink | « Hide ]

Alissa Sabre added a comment - 16/Apr/08 08:46 AM

Because the Preferences window has greately changed both in 1.19.1 and 1.20.0, this issue filing became almost meaningless... I'm closing this issue as "Won't Finish".