"Sorry" in user-facing errors violates the User Interface Standards

"Sorry" is used elsewhere in user-facing error messages, so I changed the component to "base system".

Drupal 8 is the same thing, so I have moved this to the Drupal 8 queue according to the backport policy.

Please review my patch. Do we have to remove Sorry keyword from all files like Sorry, too many failed login attempts from your IP address.. etc.

attached the patch file

Please review updated patch

I found a few more and removed the text. I left unmodified a few more because I am not sure if I should change them or not.

Updated #13 patch with two more changes

Cool! At the time we avoided the "front-facing" parts but I am happy to fix this now.

There are two more in the quickedit module's JavaScript that should have this change. In those cases "Sorry!" should perhaps be "Error!".

Added the last two from quickedit module.

+++ b/core/modules/quickedit/js/models/EntityModel.js
@@ -410,7 +410,7 @@
-                Drupal.quickedit.util.networkErrorModal(Drupal.t('Sorry!'), message);
+                Drupal.quickedit.util.networkErrorModal(Drupal.t('Error!'), message);

+++ b/core/modules/quickedit/js/util.js
@@ -125,7 +125,7 @@
-          Drupal.quickedit.util.networkErrorModal(Drupal.t('Sorry!'), message);
+          Drupal.quickedit.util.networkErrorModal(Drupal.t('Error!'), message);

This should then become something like Network problem.

Ok, lets do that.

Changed according #19

#23 removes all user-facing "sorry"s. I read over the patch and found no problems with it. I manually tested the bad password error and it looks fine. Could someone else give the patch a thorough read and mark this RTBC?

As a Canadian, I am only committing this under extreme duress.

:P

Committed and pushed to 8.0.x. Sniff. ;)

Back to 7.x.

Hah! duress, fascinating :) Learning new words every day.

@Bojhan "Duress" is fun, but "sorry" is the hardest word.

Ported patch to Drupal 7.

I'm not sure how much of this we can backport given https://www.drupal.org/node/1527558 - at least we'd probably want to leave out end-user-facing strings and error messages.

...we'd probably want to leave out end-user-facing strings and error messages

That is pretty much all this issue is, so is this a "won't fix"?

Yup, pretty much.

Yeah, guess so. The IP address "has been banned" message isn't even translated so technically that could certainly be changed, but not sure anyone really cares much about that one.