ptdrumm at terra.com.br
Sun Oct 7 22:42:47 EDT 2007
Ok. And I know about the openness idea of OLPC, XO (Etoys incuded).
Then, my question changes to: is it safe (systemwise) translating ALL
these composed things into separate words?
On Oct 7, 2007, at 5:39 PM, Bert Freudenberg wrote:
> Well, you are only partly wrong. Some of these are visible in the
> interface, like removeAllFromPatchDisplayList appears in the viewer
> of a Kedama world.
> That getTextColor shows seems to be a bug. It is not actually used
> directly, but appears as the "color" property in a viewer on a Text.
> makeNewDrawingIn is used in a ReferenceMorph.
> Not sure where mouseMove is used, that may or may not be a bug.
> And they still should be translated - even if they are purposely
> not shown, kids can unlock them. Etoys is an environment that goes
> beyond the tile scripting you see by default.
> - Bert -
> On Oct 7, 2007, at 21:55 , Paulo Drummond wrote:
>> Thanks, Bert.
>> Correct me if I'm wrong, but if they were created with a special
>> meaning they should remain as a single word. And this cohesiveness
>> may explain the camelCasing. On the other hand, as they are not
>> used (or purposely not shown) on the XO Etoys interface, so I
>> don't see why they should be translated at all.
>> On Oct 7, 2007, at 4:27 PM, Bert Freudenberg wrote:
>>> On Oct 7, 2007, at 20:45 , Paulo Drummond wrote:
>>>> Should the system scripts, messages and the likewise composed
>>>> wordings (e.g. removeAllFromPatchDisplayList, getTextColor,
>>>> makeNewDrawingIn, mouseMove etc) — be literally translated?
>>>> Suggestions welcomed.
>>> IMHO, they should not have those camelCase names in the first
>>> place ... this is even wrong for English.
>>> I think for now they should be translated to regular phrases with
>>> spaces. Or is there any good reason for those strange spellings?
>>> Not sure when we will get around to fixing them ...
>>> - Bert -
More information about the Etoys