Inline (pop up) translation is nice, but how do we find text in places like the title bar or buttons (otrans)? Do we still need search?

I've been looking at the translation interface a bit today and have some suggestions / comments:

One point of confusion is that the language selector at the bottom does not change the language you are translating. Does this make sense? I mean does it make sence to translate the site into French whilst viewing it in German? I guess maybe. So, if it does then we should make it clearer how you change the translation language otherwise its only natural to want to use the bottom language selector for that purpose (because it is on every page)

Translation Header

Thus, maybe we need a "header" for all translation pages that shows a drop down list of languages (instead of them being on the home translation page). The header would also contain the link to the FAQ and the translation Search box. Maybe this header should go *above* the whole site so its obvous you are outside the site?

Translate this page

• This does not seem to work with blocktrans.
• Doesn't work with What's Up (cuts off after ')
• Should be an On/Off feature. I.e. once you turn it on it should stay on until you turn it off. (so footer text should change to "translation links off" when we are in translation mode)

Search page

Should be part of the translation header so its always available if you are translating.

Workflow and FAQ

We need to be explicitly clear about the translation process. i.e.

• When will new translations go on line etc?
• What is the workflow?

We need to give clearer guidlines to template developers e.g. is the following ok?

{% blocktrans with focus_node.nod_name as nod_name %} Private messages sent to and from the {{nod_name}} {{W_NODE}}.{% endblocktrans %}

English Translation

I don't think it makes sense to allow an english translation at this stage. i.e. the strings in the templates should be the definitive English. It's going to be super confusing if I start to see strings in the site which are not in the templates. Or is this unreasonable?

*If* we have an English transaltion then maybe it should be a US en translation or an Indian en Translation! But plain English should not appear in the translation list. Or?

cheers,

Simon.



Update: Following this Evis, Deepak implemented "inline" translation (well pop up translation actually) and first looks, seem good.

Who Test
Where Test
When 21-06-2009

I am testing this evis with another node :)

Help text has been revised.