Talk:LSL Portal Translation Project

Chinese Language Variant Names

Aren't usual codes for Chinese zh-CN (traditional) and zh-TW (simplified)? -- Catherine Pfeffer

• Wikipedia has moved to using zh-hans and zh-hant. I don't know why but I think it may has something to do with zh-sg (which uses simplified) and zh-hk (traditional) isn't really needed as seperate variants most of the time. --Geneko Nemeth 20:35, 16 December 2007 (PST)

Templates

Many of the LSL templates and subtemplates should be translated. The function template will require some finesse. If there are any questions about the templates just leave a message on my userpage. The javascript used to change the article name case can't be used to strip the language code fyi. -- Strife Onizuka 12:02, 11 December 2007 (PST)

Highly Specific Language

One problem we have to try and avoid is the loss of specific language when translating the articles. Some of the language used to describe how things work has been chosen for very specific reasons. They have very tight and specific means and implications. I'm worried that in the process of translation some of this will be lost.

It would be beneficial if the translators could validate against SL what they are translating. It would ensure the translation is accurate and that the English documentation is accurate too.

In essence I'm worried that the translators won't have enough understanding of the content to ensure the correct nuances are kept. Considering the edits that take place on articles this fear is well founded.
--Strife Onizuka 09:41, 15 December 2007 (PST)

Common Proper Terms in Translation

Hey, I think it would be nice if there's a fixed translation for proper terms in Second Life like "Avatar" or "Parcel". --Geneko Nemeth 20:35, 16 December 2007 (PST)

It's not helping that the translation in the official viewer is... well, it makes the translation of Zero Wing look good by comparison. --Geneko Nemeth 21:05, 16 December 2007 (PST)

Example localization

does anyone have suggestions for localizing examples when the writer (like me) only has fluency in one of the languages a page is available in? I notice many of the /ja page examples are in english, which seems kind of silly, although I'm not sure if it's any better to only have an example in one language, but not another. My personal temptation is to example the known page, and leave a discussion note that the other pages need to be updated with localized versions.... or should I just copy the untranslated version across the available language pages as seems to have been done with many of the japanese examples? -- Void Singer 13:44, 19 February 2008 (PST)

If you talking about only comments in scripts, it could be better translate. (But if so, You can't just copy & paste it to LSL editor. because the editor built in some client version can't handle UTF-8 correctly.) And if you want to localize these scripts in such as messaging part level, I think it's not a good idea to do. To do it, we need to re-check them all again and could be en-bugging in the process of localization. -- Nock Forager 02:21, 20 February 2008 (PST)

mostly concerned with updates where the user (me in this case) isn't fluent in other languages the page is available in, examples are one case, but also did some rework/input to the rotation page, that is also available in french and japanese. in the case of examples being added what does everyone think? should we propogate the addition accross all pages, and let those familiar with the language translate it, or do something similar with translation software? should we only add to the language we're fluent in? I honestly don't know, but I'm gunshy about using translation software as it may add more confusion than help. I'm personally leaning towards propogating the addition without translation, but was hoping for others thoughts. in the case of reworking sections I'm leaning towards only adding it to the page I'm fluent in, but then how do I let someone fluent in other languages know there's a change/correction that should be translated? should we just leave a note on the discussion page for the non-fluent languages? very confusing to me -- Void Singer 16:39, 7 March 2008 (PST)

Re: Do not translate...

The page starts with

Do NOT translate this page. This would result in out-of-sync versions of the master list

This is not neccessarily the case. I would suggest to translate all the introductional part (not the list of course) and mark it with <noinclude>...</noinclude>. Then you could include the list in the translations (like it is done at SL Volunteer Linguist Center/German and SL Volunteer Linguist Center/German/de with the contributions). Or exclude the list at all like it is done in the translations of the Mentor Linguist Scribe Translation Project.
--Zai Lynch^{(talk|contribs)} 07:53, 3 June 2008 (PDT)

I have removed the "coordination list" which no one was using. so basically it becomes okay to translate this page. But what is the point of translating it? People wanting to help must be able to read and understand English anyway. Catherine Pfeffer 11:55, 23 March 2009 (UTC)

Rouge Translations

After I spend some time translating the LSL Portal Guideline page to dutch I realized there might have been some procedures I completely ignored. So here's my apology beforehand and also a request to fellow dutchmen to go over my dutch interpretation of the english version. Trying to find my translation, I realize there are some Templates that need adjusting to make available my translation at [[1]], this is something I cannot do. --Vernes 13:55, 19 December 2008 (UTC)

I can't answer on the quality of the translation, since I can't read Dutch, but replying to the template issue:

Pages in the Wiki are cached to reduce the load on the server. They also cache the underlaying templates and therefor it might need some time for the Dutch translation to show up on the language bar on top of the article. This can be bypassed by browsing to the English article and clicking "edit" and then "save", without changing anything. The Wiki is then forced to purge the cache and it will show the link to your translation. Such a procedure isn't showing in (and therefor not spamming) the history of the article (nor the Special:RecentChanges).

In case you'd like to do more LSL Portal related articles, I'd recommend to join the LSL portal translation group (just ask one of the owners), the Mentor Linguists group, or just keep writing on discussion pages when you're stuck so others can help you out =)

Thx for translating!!

Greetz, Lynch ^{(talk|contribs)} 00:50, 20 December 2008 (UTC)

Is the "coordination list" needed ?

As far as I know, most of the LSL_Portal_Translation_Project page is unmaintained, useless and outdated. I'll remove it. If anyone feels this is wrong, please revert. Catherine Pfeffer 11:18, 23 March 2009 (UTC)