There are various instance in which while entity labels are either not translateable or not configurable. Tracking them here:
* admin/structure/short-news-type -> Wrong bundle label
* admin/structure/short-news-type -> Unconfigured table header description
* Local actions -> Untranslatable
* admin/structure/short-news-type -> Wrong page title / translation (double translation?)
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | d8_while.form_.patch | 10.37 KB | fago |
| #8 | config_page_translation-28585265-8.patch | 16.39 KB | archnode |
| #6 | fix_label_translations-2858265-6.patch | 1.3 KB | archnode |
| #5 | fix_label_translations-2858265-5.patch | 158 bytes | archnode |
| #2 | fix-labels-2858265-2.patch | 1.18 KB | archnode |
Comments
Comment #2
archnode commentedFixed most of the labels, translation needs further tests.
Comment #4
fagothx, the patch looks good - I've committed and pushed this one already. Leaving the issue open for the rest.
Comment #5
archnode commentedAnd another one with missing local actions translations.
Comment #6
archnode commentedWoops, the last patch was a bit insubstantial. Correct one added here.
Comment #7
fagohm, I think we are doing this wrong. The entity-name should be in config, thus it should be translated via the config system. Once that's done, there should not be a need for the t() call.
Comment #8
archnode commentedOk, I created following patch that removes all calls to "t" in this context and adds configuration translation as well as a configuration page. This patch also incorporates #2859637: Make content listing page more useful as the patch there also added some calls.
What I'm not sure about is the call to config translation in the alter hooks: This only gets called on cache clear, we would need to define a label callback, but I'm not sure on how to do this in this context. Any ideas?
Comment #9
fago>What I'm not sure about is the call to config translation in the alter hooks
I think this is fine. After while setting context changes, the entity type caches need to be cleared. Until there is no UI for that it's fine if one has to run a manual cache rebuild afterwards imo.
Comments need work.
Nope, that cache dependency has to stay.
whitespace
Would make sense to stay with consistent naming: Settings -> SettingsForm
as above, settings?
Comment #10
fagowrong issue
Comment #11
fagowrong issue
Comment #12
fagoComment #13
fagook, I addressed the remaining issues and fixed the titles in the breadcrumbs of the collection routes.
Comment #14
fagoComment #16
fagoAnd committed.