Re: [etoys-dev] [Localization] Doubts about connectors.po

List overview All Threads
Download

newer

older

[ANN] Waveplace starting another...

Etoys: Etoys-kfr.74.mcz

Bert Freudenberg

4 Jun 2011 4 Jun '11

1:45 p.m.

These are event names, and they should be localized, and it is nicer to not use camelCase. (Actually I'd consider it a bug that in the English original they are not spelled as separate words)

- Bert -

On 04.06.2011, at 09:52, Alexandro Colorado wrote:

...

Actually this is not about the content, but rather seems to be set classes which means that shouldn't be localizaed.

2011/6/4 Miguel Bouzada mbouzada@gmail.com IMHO

2011/6/4 Alexandro Colorado jza@openoffice.org #: Connectors-Base,NCAAConnectorMorph_class>>initialize msgid "sourceConnected" msgstr "origen conectado"

#: Connectors-Base,NCAAConnectorMorph_class>>initialize msgid "sourceDisconnecting" msgstr "origen desconectado"

-- /\ Dia da liberdade dos documentos - Libera os teus documentos _/` http://documentfreedom.org/ - 30 de marzo de 2011

-- Alexandro Colorado OpenOffice.org Español http://es.openoffice.org

Attachments:

attachment.html (text/html — 2.4 KB)
PastedGraphic-2.png (image/png — 40.0 KB)

Show replies by date

Chris Leonard

5 Jun 5 Jun

6:42 p.m.

New subject: [Localization] Doubts about connectors.po

On Sat, Jun 4, 2011 at 7:45 AM, Bert Freudenberg bert@freudenbergs.dewrote:

...

These are event names, and they should be localized, and it is nicer to not use camelCase. (Actually I'd consider it a bug that in the English original they are not spelled as separate words)

Dear Etoys develoeprs,

I have discussed with Bert in the past that I think that eToys needs a substantive review of it's UI strings with an eye towards enhancing it's internationalization (i18n) and making it easier to localize.

My pet peeve is that there are many instances where the number of strings to localize could possibly be reduced by eliminating minor variations (camel case, spaces, punctuation) that are not truly meaningful, but there are far more substantial i18n issues that require attention. I feel that real progress in enhancing eToys i18n requires a comprehensive and systematic approach and is unlikely to simply emerge from the sum of fixed bugs in the tracker.

It is my opinion that the best way to approach this is to form a "tiger team" ( http://en.wikipedia.org/wiki/Tiger_team ) chartered and empowered to conduct a systematic string review and to introduce the necessary changes. It should consist of at least one core eToys developer (with the experience to determine which changes might have unexpected "knock-on" effects) and one or more localizer (to identify and advocate for potential string changes).

I understand that developer time is precious and that there are always bugs to fix and new features to code, but I would ask the eToys developers to think strategically about the potential impact of improving the quality of the UI experience (in over 100 languages) versus adding a new feature or hunting down a bug. It seems to me that i18n enhancement would be a high ROI (return on investment) activity and therefore a high priority, in spite of the fact that it is admittedly a somewhat mundane and fussy task.

I would be willing to commit my own time to taking part in such a string review, but I would want to know in advance that it would be fast-tracked for action (not just filed in the bug tracker) and it would be important to have input from an eToys developer (thus the suggested tiger team approach). Is there an eToys developer that feels as strongly about i18n as I do and that would be willing to work with me on this effort? Consider that the quality of your strings in other languages forms much of that user's impression of the quality and utility of your software.

A quick scan of the tracker shows a substantial number of tickets at least tangentially related to internationalization issues, adding to my impression that i18n has perhaps not received enough attention from the eToys developers. (see list below)

cjl

http://tracker.squeakland.org/browse/SQ-934

http://tracker.squeakland.org/browse/SQ-922 (fixed, but not rolled out in new PO?)

http://tracker.squeakland.org/browse/SQ-910

http://tracker.squeakland.org/browse/SQ-890

http://tracker.squeakland.org/browse/SQ-871

http://tracker.squeakland.org/browse/SQ-840

http://tracker.squeakland.org/browse/SQ-813

http://tracker.squeakland.org/browse/SQ-805

http://tracker.squeakland.org/browse/SQ-797

http://tracker.squeakland.org/browse/SQ-790

http://tracker.squeakland.org/browse/SQ-789