Thread:User talk:MS/Thank you from Blockly!/reply (24)

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