Closed (duplicate)
Project:
Drupal core
Version:
8.0.x-dev
Component:
user interface text
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Sep 2015 at 15:17 UTC
Updated:
2 Oct 2015 at 14:58 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
snehi commentedPlease review the attached patch.
Comment #3
phantomvish commentedThe patch doesn't work. It seems to be for only 'classy' theme and the pager text doesn't get capitalised after installing patch.

Comment #4
cilefen commentedIs this a regression from Drupal 7?
If they are lower-cased on purpose it could be because the expectation is the theme layer will do it.
Comment #5
cilefen commentedComment #6
hass commented#2560049: Incorrect capitalisation of translatable strings
Comment #7
chrisfree commentedIt was my understanding that the values for pagers can be customized within views. This is why the template uses
{{ items.previous.text|default('‹ Previous'|t) }}instead of simply hard coding the values for first, last, etc.Since we're changing the defaults in the theme I thought we should also change the defaults installed with views setup with core. Maybe I'm missing something though!
Comment #8
hass commentedThis patch changes the same lines!? I guess since views is using default pager there is nothing more to do here.
Comment #9
chrisfree commentedThis patch does use the same lines as the other issue, so no reason to commit this one. However, regardless of what is in the template as a default, the values stored in the view itself will takeover. The default is lowercase. I'm wondering if we should change these as well (stored in installation yml files) so that the default set in the theme matches what comes with stock views. I suppose you could argue for either in this case.
Comment #10
hass commentedYes, that is a good point. Let's integrate these view settings in the other case patch, please.