Problem/Motivation
If my default language is italian, and I create a view while in the italian language, and I want to add a header/footer, I have to write that in Italian, and then I will be able of translating it in other languages. But it is not clear in the input what language should I use. Maybe we should add a hint somewhere.
Proposed resolution
Show the language the user should be entering texts.
Remaining tasks
Discuss if this is desirable.
User interface changes
Show the language the user should be entering texts.
API changes
None.
Comment | File | Size | Author |
---|---|---|---|
ccc Contenuto Site-Install.png | 89.63 KB | penyaskito |
Comments
Comment #1
Gábor HojtsyI think this is a matter of experience. There are so many places you can/need to enter something. Eg. when creating a content type, a field, a taxonomy vocabulary, a term, a free tagging term on a node, etc. The idea is you get the idea from the UI. Here the UI is Italian, so you assume its Italian. If you configure your UI language to be different, or edit an Italian view on an English UI (all possible), the idea is you'll get the language by looking at the settings already there (eg. title of view, etc).
I know these are implicit queues, but not sure where to put explicit queues. I think putting them into labels of every field where you may enter text will be quickly overwhelming.
Comment #2
penyaskitoYou are right. Maybe we can take this into account when tours for views are created and specify it there.
Comment #3
Bojhan CreditAttribution: Bojhan as a volunteer commentedI am not really sure, because this can easily be several languages. Do we display all? I am not convinced.
Comment #16
penyaskito