[Etoys] Many missing translations in POs

[Bert Freudenberg]

> I don't think 'degree arc tan' is better than 'degreeArcTan'

Right - however, it indicates to the translator that it is okay to  
use separate words instead of camelCase. Not sure how we would  
communicate this otherwise, we have had camelCase translations  
before. And there is actually a method that translates between  
selectors and tile phrases for these more obscure cases.

> One possible solution other is to create translations even for  
> English.

I think this would be a good way to handle it, yes.

- Bert -

On Oct 29, 2007, at 3:32 , korakurider wrote:

> Hi, Bert.
> Actually I took care of keeping #camelCase for symbols.
>
> One of reasons is some wording seems not clear if it is
> shown as quasi-english with no-camel.
>
> for instance:
>
>     aPlayer setBorderStyle: #complexAltFramed
>
> I think some symbols are like a "magic word" and
> conversion is meaningless.
>
> Though I agree emptyScripts could be shown as 'empty
> scripts'.
>
> Other reason is about function names in function tile,
> that I hesitated to change wording.
> I don't think 'degree arc tan' is better than
> 'degreeArcTan'.
>
>
> One possible solution other is to create translations even
> for English.  I think this is better because wording is
> too fragile for also using as key of translation (msgid).
> If you guys speaking English adjust wording, it will break
> translations for other languages.
>
> /Korakurider
>
> --- Bert Freudenberg <bert at freudenbergs.de> wrote:
>
>> Thanks. Does this take care of changing #camelCase
>> to "separate words"?
>>
>> - Bert -
>>
>>
>> On Oct 28, 2007, at 19:49 , korakurider at yahoo.co.jp
>> wrote:
>>
>>> Hello.
>>> After switching translation dictionary from NLT to
>> extracted POs, a
>>> few
>>> words don't have translation because those haven't
>> been exported to
>>> POs.
>>> Here are proposed fix (attached).
>>>
>>>
>>> (1) viewer category.
>>>     for instance "collections" isn't translated.
>>>     TransCategory-KR will fix this.
>>>
>>> (2) symbols
>>>     For instances, these aren't translated.
>>>     - true/false on boolean readout
>>>     - emptyScript on ScriptNameTile of "Scripting"
>> category
>>>     - all of SymbolListTile
>>>
>>>     Unfortunately #translatedNoop isn't useful for
>> this because
>>> current
>>> exporter implementation omits arrayed symbols.
>>>
>>>     By transNoopAll-KR, all of string receiver of
>> #translatedNoopAll
>>>     including arrayed symbols will be exported.
>>>     (the patch has also test).
>>>
>>>     By transSymbols-KR symbols in Vocabulary will
>> be exported.
>>>
>>>
>>> We switched translation engine very silently in
>> development stream,
>>> So folks may haven't recognized these degrade.  I
>> think translation
>>> stuff needs more testing.
>>>
>>>
>> /Korakurider<TransCategory-KR.1.cs><transNoopAll-KR.
>>
>>> 2.cs><transSymbols-KR.
>>>
>> 1.cs>_______________________________________________
>>>