User talk:Spiky

Welcome!

I should really get template-like-welcome message for translators... In the meantime: welcome!

I noticed your page Original page/lang-ja and it states that the 'source' is OLPC FAQ... not being able to read japanese (and a bit lazy to try {{Google Translate}} on it, I can't decide what is 'wrong' with it... except that there's no page named [[Original page]], so I pressume that the intended destination would've been instead [[OLPC FAQ/lang-ja]]... please let me know and I'll move it :)

BTW, I consider the FAQ to be a tricky thing to translate, as you probably don't really want to translate the questions but rather the summaries or 'base q&a' and let the japanese-speaking community generate their own questions...

Either way, welcome! If you have any doubts please check Translating/HowTo or drop me a line. Cheers --Xavi 01:59, 10 August 2007 (EDT)

Xavi Note: other people joined and you said not one thing. 

I find this very rude. And wonder why is this so? Oh I Heard you know them? Cool but it would look better if you treated them the same.TO Spiky welcome to OLPC. Bakersdz 8/24/07

PS: I noticed that you are using 'version = 0001' when it should be the number that appears in the 'original' page (ie: «HowTo [ID# 57522] +/-») as this will allow the synchronization using the 'changes' link (変更) that shows the modifications since the last version used as the source of the translation and the current source version (see Translating/HowTo#Notes for more information and {{Translation}}). Xavi 02:27, 10 August 2007 (EDT)

follow-up to User talk:Xavi#Thank you for your kind welcome message

Glad to help! :) Yes, translating a wiki is not the usual translation project I guess. If you have any suggestion on how to make it simpler, please let me know :)

BTW, I just moved the page, and tagged the original for deletion. If you have any questions, please do ask! Either wiki or IRC (usually in #olpc-content and some other olpc-channels). Cheers, Xavi 02:57, 10 August 2007 (EDT)

About synchronization between original page and translated page

Xavi,

Thank you so much again, and very sorry for may mistake about the use of "version" parameter. I now understand that. I'm going to fix them.

Spiky

Je... edit conflict, guess you're faster than me :)

I've already fixed them (used the latest # since I'm assuming you started from those) but please do check that I didn't miss any, thanks. Xavi 02:57, 10 August 2007 (EDT)

PS: you can use the Xavi 02:57, 10 August 2007 (EDT) to sign your posts ;)

/lang-ja pages

Hi! Making my comeback after too many days off the wiki... anyway, I noticed several /lang-ja pages (and corresponding new or edited /translations) only to discover that they are in english... something that I find confusing at best. I mean, what's the point of having lots of duplicate pages posing as translations? If there's a logic or reason, it escapes me...ᅜ Xavi 15:26, 17 August 2007 (EDT)

Hi, Xavi! Welcomeback. I'm grad to hear you. I guess your point is "why so many 'ongoing translation' pages indicated as Japanese page but still in English?", is that right? Ok, there's a simple reason. I would like to lower threshold for many ordinary Japanese people who would like to contribute in translation work but are not skilled so much to prepare Japanese template pages in wiki world. Talking about me, I think I'm getting used to prepare template pages for Japanese translation work from original English pages now a days, but still it was tricky and bothersome work. I guess It'll be some kind of barrier for ohter Japanese. My concern for now, is to bring as many Japanese as possible to help us out, so I just would like to remove any difficulties for them as much as I can, for their convenince to be able to start helping right away. If this situation will cause something bad for OLPC wiki community, then it is ok to remove or hide them those are not translated into Japanese yet at all. (Also the reason why I put Ongoing Translation tags in these pages are that we now uses "http://wiki.laptop.org/go/Category:Ongoing_Translation" page as "todo" list. I guess it is easier for other people to know which pages are prepared or under translation and which pages they can start to translate.) Spiky 21:08, 17 August 2007 (EDT)

Anyway, I've just posted one question on your pages about how to translate 'menu' items displayed on the lefthand side of the top pages. Currently all these menus are in English even if user changed page mode to Japanese, like page 'Home' or 'OLPC overview'. If they would like to move from Japanese 'OLPC overview' page to, for example, 'Educators' page, then they once move to English 'Educators' page and then switch it to Japanese page again. I will really appreciate if you give me some advise if you have a time. Thank you! Spiky 21:16, 17 August 2007 (EDT)

yatc

(Yet Another Translation Comment :)

That's a nice list you did for your translations, one that finally pushed me to review the {{Translation}} template... which I'm doing right now, and would like to discuss so that it accomodates better to our needs and uses.

For starters the {{Translation}} has 5 parameters, 3 of which are mandatory (lang, version & source); the other two are just visual and not really important. If the translations stick to the subpage scheme, the source parameter is the parent-page, which iirc, can be retrieved by a function. so we could change it from mandatory to optional. There have been several ocassions where the source parameter was wrong (usually copy-paste) and thus the language navigation bar was wrong too) so anything to avoid those dumb mistakes should be ok.

The other problem I see currently is the use of the {{Ongoing Translation}}. The problem with this is that we lose all info on which language we are talking about (ongoing lang-ja? lang-es?)

So I've been thinking on tweaking the {{Translation}} template to drop the required source and add some status or level. The status I was thinking either your approach in the User:Spiky#To Do with a percent number, or something more textual:

{{ Translation | lang = ja | version = xxxxx | status = 50% }}
or
{{ Translation | lang = ja | version = xxxxx | status = ongoing, to review, wanted, to update, synced }}

The xx% approach is nice as it provides some quantification (but don't think that it would be necessary or usefull that level of detail). On the other hand, the discrete status may be annoying. One thing that xx% would be messy in solving is when a page has been translated, but after its source has been modified it'll need to be sync'ed.

BTW, the status would be used to classify the pages accordingly in for example a [[Category:Translation Ongoing lang-ja]] (avoiding you the hassle of manually building the list. Other categorizations should be possible. That way we split things more by language instead of having all languages mixed up.

So, if you have any ideas or suggestions, please drop me a note or contact me in IRC #olpc-content (usually as Xavi there too). Xavi 09:06, 23 August 2007 (EDT)

PS: I made a prototype in {{Sandbox}} on how the new {{Translation}} may end up doing... the resulting categories would need to be reviewed for consistency. Xavi 10:27, 23 August 2007 (EDT)

Hi, Xavi!

Thank you for your sincere comments and modification idea for the improvemnt of the template. I'm just back from my businesstrip and have just read your idea above right now. Would you give me a time to think for a while? regards Spiky 01:37, 25 August 2007 (EDT)

I've left my comments on above page. I'm grad if you take a look at them Spiky 20:13, 29 August 2007 (EDT)

yatc2

Two comments: one vis-a-vis translations linking and the other is an open question.

I've noticed that the preserving section anchors in the Translating/HowTo was lacking some steps and details, so instead of explaining them here, I expanded there on how the translated links should work. If you have any questions or commments, please let me know :)

Basically, translated pages should 'link' to [[Foo/lang-xx]] always, if the page doesn't exist, a dummy redirect (categorized as a missing or wanted translation) can be created. This enables adding a new translation and having all the 'backlinks' use it directly (instead of having to go back to each of the other translated pages previously linking to the 'original' instead of the 'translated' version). Xavi 09:56, 7 September 2007 (EDT) |I think I understand the fundamental rules to create the translation pages... But it seems I'm missing some points I should keep as a translator? Especially your explanation inside (), does that means I should keep original link (that is, foo (in English) instead of foo/lang-ja even if inside the translated page? Is that your points? I'm grad if you explain me with more words. There might be problems in my language skill and wiki rules.

I forgot the 'open question'... which basically was "how to deal with the wanted translations", but sort of answered it through the categorization of the redirects, although I'm not too sure about it. BTW, as a side effect, your (currently manual) to-do list would be maintained by the wiki—albeit without the %s :) Xavi 10:44, 7 September 2007 (EDT) |I'm happy if you saw my idea about how to deal with pages wainting for translation or on going tranlsation pages on your notes of your page though, but I fundamentaly agree with your idea to put some descrete status keywords as a parameter for "Translated text" tag. In addition, I also think it'll be nice to put numerical progress status (for example, in percentage, like in my page) just for the people who are really interested in the progress of OLPC acitivity day by day (it exist, ;-)). FYI, in my page, the percentage I put at the end of all pages which I've prepared the templates for Japanese translation means just the progress of simple and rough simple conversion rate ( from English to Japanese), and I always welcome anybody who modify or continue my translation work in the middle of my work. And, offcourse, after the conversion was completed ( that is, percentage is 100%), that means "Conversion was completed and waiting for modification or refinement from other excellent translators. Simple conversion progress is easy to represent its progress with numerical number, because it is very obvious how much the original was converted from English to , in this case, Japanese, but on the otherhand, it is slight difficult to show people "how fine the completed translation" wiht numerical numbers, so it is nice (as in your idea) to show descrete words. Some people says refinement work (of the translation) might last forever (because there might be some people who don't want others translations or something, or simply because of the difference of translation policy, or maybe simply because of their favors), so the final status of every translated pages maybe "waiting for refinment" (it's a joke, never mind.) Oh well, this is my opinion, but Japanese are one of the most "rashly" people, because almost all traffic signals for the pedestrian has the "meter" that shows "how many seconds they have to wait", in some cases it is a ditital bar meter and some in ditital numbers in seconds, and they know how many time they have to wait watching the bar length or number decreasing. It'll be strange for the people in other countries. Spiky 23:53, 17 September 2007 (EDT)

yatc3 - the HIG

Saw your edition of the /translations for OLPC Human Interface Guidelines/The Laptop Experience... and thought I should 'warn' you that the wiki-text in those pages is not very friendly :( I tried to set up some notes & guidelines on the translation of the HIG (which I haven't reviewed in some time)... if you have any questions or doubts, please let me know (either in my talk or better, on the page) so that we can make it better :) Xavi 02:48, 17 September 2007 (EDT)

PS: As a reference you may want to take a look at the OLPC Human Interface Guidelines/lang-es (the spanish version I did) that was the guinea pig used to tweak the templates and structure in order to enable translations... Xavi 02:52, 17 September 2007 (EDT)