Thank you from Blockly!
I see your point. I wasn't there for the block's creation, but my guess is that it was designed to be easy for the beginner to understand, even if that's confusing to the experienced programmer, as discussed here.
Ellen, I have finished. I am more or less confident but I would appreciate if you allow me me to take another look before publishing.
Misha
I'm afraid I'm partly at the mercy of my translatewiki contacts, who decide when to export translations. I can request another export but don't know for sure when it will happen. Is it okay if the current version goes live without any public announcements? That would give you a chance to look it over before many people saw it.
It went live without your newest changes being exported, I'm afraid. You can see the Russian code app here. I won't make a public announcement yet, because I know you want more changes.
Thanks again!
I see, it's published. Good. I'll take another look? and, probably, a bit more correction, though mainly it should be now more or less stable.
For successful translation it's important to have some model of the subject. I prepared some memo about translation of Core, my way. As you'll have a lot more translations, you maybe can extract some ideas for future translators from my notes.
Notes.
"Physical" appearance: program consists of blocks and inputs. Blocks can be joint together, forming structure of a program. Blocks may have "slots?". Some slots to be fulfilled with blocks, some of them - with inputs. Input is a sort of block which can't be used in place of normal block but may have own slots to include other inputs. Input slots may appear differently in blocks: see context menu Inline Inputs/External Inputs. (No sure what to say about segments) [following the logic above, I would name functions as 'block f' and 'input f'. It could be reasonable to have in context menu for set explicit 'create input', and for item "create block set" Logical appearance; Every input has a value. Variable is an input, which value may be changed during program execution. Condition is a value of logical input for if if-else, while. Item is a unit of data structure, like list. Commands (statements) - actions, represented by a set of blocks.
Style of wording. Block text: key word is imperative. Context menu - mostly imperatives. Toolip for block, description: answers on question what block does. Toolip for block, tip: advises user what to do
I just got the requested push of translations. I'll get that out ASAP.
Thanks for the suggested information for future translators. I'm curious whether you think that information is not present on Translating:Blockly or that I shouldn't expect translators to read the whole page.
Regarding my 'notes', I didn't mean anything particularly, it was sharing 'just in case'. If nothing there provokes you to change or add anything in the text for translator, it's OK.
In Russian Code I see now just mess, I don't know what that means.
What do you mean by just seeing mess?
I mean, I don't see blocks to choose on Russian Code page http://blockly-demo.appspot.com/static/apps/code/index.html?lang=ru. I tried from different computers with different browsers: result is still the same. At the same time English Code is OK, so problem looks specific to Russian page. I see, there was an important modification: localized versions got their own url, which is very good, but probably during that reconstruction something went wrong.
Yikes! I'll fix right away.
Post-mortem: This was caused by a "\n" in CONTROLS_IF_TOOLTIP3. I'll modify my scripts to detect this and will improve my testing.
I've sent my fix for review.
Thanks for telling me. I couldn't duplicate this behavior. Could you say more?
FYI, next to be translated is this page.
Do you have any public presence I can link to when announcing the Russian translation?
Turtle: click on Colour - whole menu is moving up click on Logic - again moving up, etc.
Public presence... not sure what you mean. Place of work, titles, organizations I represent, or what?