Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
language.module
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Dec 2012 at 23:10 UTC
Updated:
29 Jul 2014 at 21:39 UTC
Jump to comment: Most recent, Most recent file


Comments
Comment #1
fenda commentedTaking on this task. Should be a quick one but it's my first core patch so who knows?
Comment #2
fenda commentedPatch attached for adding extra help text to cover this issue.
Generally the help test on the language list page could be improved. It doesn't really say anywhere what the admin is actually looking at which might be useful for first time users. But that's another issue?
Comment #3
yesct commentedThe: when specifying a content's language, sounded strange to me. How about:
The order of languages in the table below affects the order languages appear in the language selection form element, for example, when editing or creating content.
Comment #4
DeNelo commentedThe second comma (after "for example") makes the sentence ambigous. When I first read it, I understood the "example" to pertain to "the language selection form element", not to "editing or creating content".
Should be like this imho (also threw in an "in which" after the second "order"):
"The order of languages in the table below affects the order in which languages appear in the language selection form element, for example when editing or creating content."
Comment #5
tammo commentedIn another issue I wrote a proposal for a new text for this page. Please review
http://drupal.org/node/1998516#comment-7433280
Comment #6
pixeliteI think the text in #3 is a bit verbose. We should also mention this ordering effects the order of languages in the language switcher. Attaching a patch with this change:
Comment #7
DeNelo commentedThree things to #6:
Typo: "detection menthod" -> "detection method"
Also, "The selection of what" -> "The selection of which"
Finally, "will effect" -> "will affect"
Comment #8
attiks commentedtaging
Comment #9
KCarlile commentedAfter reading through the issue, I think #7 misunderstood that the patch in #6 had already addressed those issues. Also, I think the patch in #6 didn't completely address the spirit of the issue, so I've added the following text to the end of the string: " The ordering in this table does not impact fallback behavior."
Also, I did test the patch in #6 and it worked.
Comment #10
lydie commentedHere is the revised version for #9 which seems just perfect.
I just changed the typo "effect" for "affect".
Comment #11
KCarlile commentedShoot, I missed that one. Thank you! :)
Comment #12
KCarlile commented#9: language-list-order-help-1870746-9.patch queued for re-testing.
Comment #13
KCarlile commented#9: language-list-order-help-1870746-9.patch queued for re-testing.
Comment #14
DeNelo commented#9 OK, I didn't get that. I guess when you say "Attaching a patch with this change:" and then list code, I thought that that was the change... :)
Should have looked at the actual patch.
Comment #15
yoroy commentedSo this is a case of adding text to explain an inconsistent UX. Any change we can remove the cause for the inconsistency instead of stop gap explanations?
Comment #16
parthipanramesh commentedSeems to look fine. Thank you!
Comment #17
ianthomas_ukI don't think this new text is an improvement, because:
- It no longer suggests langauge-selection features will be shown/hidden depending on the number of languages enabled.
- 'language switcher' and 'language selector widget' sound overly technical. I'd prefer something like 'list of available languages'
- It loses any explaination of how fallback DOES happen.
The issue summary could also use an update before being set to RTBC.
--------
@yoroy the order the languages are shown to a user (e.g. alphabetically or by region) is a different problem to how to choose a users default language (e.g. by domain name example.us vs example.co.uk; by ip address; by browser settings).
--------
This help text in D8 HEAD was changed in #1803638: Improve default language change process (ui and help text) which was committed between patches #2 and #6. I think the new text solves the problem described and therefore suggest this is closed as a duplicate.
Comment #18
fenda commentedComment #19
schnitzel commentedI don't think that this issue is solved with #1803638: Improve default language change process (ui and help text)
It currently says:
So it's not yet clear what reordering does.
Comment #20
edmoran commentedComment #21
balagan commentedPatch #10 also drops the last part of the message of patch 9 about the fallback behavior. I have readded that, and made changes according to ianthomas_uk's comment in comment #17
Comment #22
balagan commentedComment #24
balagan commentedComment #25
balagan commentedThis should be fine now, the text actually says:
Reordering the languages below will affect the order in which the enabled languages appear in the language switcher and, when editing content, in the list of available languages. The ordering in this table does not impact fallback behavior. The selection of the language to display the page elements is made depending on the detection method settings in the <a href="@detection">Detection and Selection</a> tab.'Comment #26
balagan commentedComment #27
robertdbailey commentedPatch #25 still seemed a bit wordy, and I got confused about "fallback behavior", since the next sentence did not seem related (even though it was). So, I've shortened it, and hopefully it still gives the right meaning and link.
Comment #28
balagan commented..."does not impact fallback behavior in language fallback behavior."...
This sounds awkward.
How about ..."does not impact the fallback behavior set on the @link tab. ?
Comment #29
balagan commentedComment #30
balagan commentedAccidentally assigned to myself, unassigning now...
Comment #31
robertdbailey commented@balagan pointed out some better wording. Resubmitting patch.
Comment #32
robertdbailey commentedComment #33
yesct commentedTo get rid of the idea of "enabled" languages (which is not exposed in this table anymore),
and make this shorter...
Instead of
How about:
?
------
I think it would help to have a screenshot (with only one language, and with multiple languages) of the page/tab/table we are trying to describe.
Please upload screenshots in a comment and embed them in the issue summary.
(instructions to do that: https://drupal.org/contributor-tasks/add-screenshots)
tagging.
Comment #34
balagan commentedFor my part I think 'enabled languages' gives a hint for the user how languages can be added to the list. I vote for accepting the patch in#31
Comment #35
stijndmd commentedI'd like to help, but I don't see the use for screenshots of descriptions. Maybe I am missing something here.
The patch in #31 works and the description seems very clear to me.
Comment #36
sweetchuckBoth 2 screenshots were taken without the patch. One with only the English language, the other with 3 languages.
Comment #37
sweetchuckUpdate the issue summary and embed the screenshots from comment #36
Comment #38
balagan commentedI am adding an image with the last patch applied.
Comment #39
robertdbailey commentedmodified the patch to go with the wording by @YesCT in #33, if this is preferable to the committers.
Comment #40
balagan commentedPatch in comment 6 took out a lot of information, 9 put back the "fallback" expression, that does not appear on the related pages.
The text after the current patch says:
"Reordering the languages below will affect the order in which the added languages appear in the language switcher and, when editing content, in the list of selectable languages. The ordering in this table does not impact Detection and selection."
In this way we avoided the improper 'enabled' and the 'fallback' expressions, we keep the information, and the text gets shorter too, but the link to set the detection and selection remains.
Patch in comment 39 seems to be different from previous last patch only with the omission of the first "the".
I don't think that is a necessary change.
Comment #41
balagan commentedSorry, I started writing the patch, and I thought I will quickly send it in, but we got a prolonged discussion, and by the time I have sent in patch #39, I have overwritten yours.
Comment #42
sweetchuckI think the suggested help text in patch #40 is clear and consistent. Short enough but contains every necessary information.
Comment #43
yoroy commentedCurrent proposal:
Maybe this communicates the same necessary info but shorter and simpler:
Comment #44
balagan commentedIt just loses the information we tried to preserve, namely, that languages can be added.
Comment #45
balagan commentedChanged tha second part according to the above suggestion, but have put back the word "added" in front of languages.
Comment #46
yoroy commentedThank you.
Comment #48
vastav commented45: language-list-order-help-1870746-45.patch queued for re-testing.
Comment #49
yesct commentedcleaned up the issue summary.
I agree using "fallback" in the help text is not desirable, thanks for taking that out.
I agree using "added" now is better, we do not "enable" languages. we add them.
also read the patch. I dont see any errors. the information is accurate.
I wonder if it would be more helpful instead of
"in the language switcher"
to say
"in the language switcher block"
If I recall correctly the language switcher block is not on by default. So if someone reads this, and we say block, they have a hint of where to go to turn on the language switcher.
Comment #50
balagan commentedI have added the word "block" to the sentence, and changed the second word "change" to "set":
Text in earlier patch (45):
Reorder the added languages to change their order in the language switcher and, when editing content, in the list of selectable languages. This ordering does not impact detection and selection.Text in new patch (50):
Reorder the added languages to set their order in the language switcher block and, when editing content, in the list of selectable languages. This ordering does not impact detection and selection.Comment #52
yesct commented50: language-list-order-help-1870746-50.patch queued for re-testing.
[edit:]
fail was:
Drupal\config\Tests\ConfigImportAllTest->testInstallUninstall() failing
looked at the test results, in the error log and found:
Fatal error: Maximum execution time of 240 seconds exceeded in /var/lib/drupaltestbot/sites/default/files/checkout/core/vendor/symfony/yaml/Symfony/Component/Yaml/Parser.php on line 542
FATAL Drupal\config\Tests\ConfigImportAllTest: test runner returned a non-zero error code (255).
Comment #53
yesct commented#2233929: drupal_set_time_limit should not be able to change the time limit if it's already unlimited for the unrelated fail.
Comment #54
robertdbailey commentedAttached are screenshots with the patch applied. The wording seems simple enough and correct.
Comment #55
alexpottCommitted bfa4a9f and pushed to 8.x. Thanks!