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.

Files: 
CommentFileSizeAuthor
ccc Contenuto Site-Install.png89.63 KBpenyaskito

Comments

Gábor Hojtsy’s picture

I 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.

penyaskito’s picture

You are right. Maybe we can take this into account when tours for views are created and specify it there.

Bojhan’s picture

Issue tags: -Needs usability review

I am not really sure, because this can easily be several languages. Do we display all? I am not convinced.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.