Closed (fixed)
Project:
Drupal core
Version:
8.2.x-dev
Component:
language system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
25 Jan 2016 at 13:20 UTC
Updated:
28 Jun 2016 at 13:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
gábor hojtsyComment #3
gábor hojtsyComment #4
swentel commentedComment #5
catchCommitted/pushed to 8.1.x and cherry-picked to 8.0.x. Thanks!
Comment #9
gábor hojtsySuperb, thanks!
Comment #10
ifrikI know this issue is already fixed, but let me post an idea here before opening another issue to potentially undo this...
How about not having "English" and "Simple English" - but "English" and "Developers' English"? Then we can make labels and help texts that are generally easy to understand (with hopefully no need to dumb it down any further) - but additionally "translate" them in a much more technically - and technically correct - wording, where we could talk for example about entities types, entity bundles and entities, and where we could add the drush command to do the same task as the GUI of that page.
Comment #11
ifrikNot sure why the version got changed.
Comment #12
gábor hojtsy@ifrik: well, Drupal uses 'English' by default for the text that is in source codes. That is the source for every other translation. Dramatic changes in that are not allowed due to backwards compatibility. So the change you are proposing I am not sure is possible in Drupal 8. Unless you want a more "technically correct" English "translation" and keep English as-is. Either way, localize.drupal.org has Simplified English, so that is why this landed in core, to match the languages there. If we are to remove it from core, then there is no point in having it on localize.drupal.org either. The driver behind Simple English on localize.drupal.org was to have a space to experiment with more dramatic string changes while otherwise keeping backwards compatibility for source strings.