I am proposing that the overview uses the word "Remove" on the overview page rather than "Delete" for two reasons:
a.) It will be consistent with the edit page
b.) It is a clearer definition of the action to be performed.

CommentFileSizeAuthor
wysiwyg-reword.patch899 byteserik.ahlswede

Comments

twod’s picture

a) I'll accept that, being consistent is good, the same term should be used in both places.

b) Not being a native English speaker, I'm not sure about this. I looked up a few definitions and it seems the consensus is that "delete" includes "remove", but "remove" does not include "delete" and the latter implies getting rid of something more permanently rather than "moving it out of the way".

Some argue that "remove" implies something which is not reversable since the rm command in many shells will remove files permanently. Though I believe that to be a misunderstanding since rm doesn't actually remove a file, but a link to it - if you still have another link to the file you can reverse that process (think unlink() in PHP and it'll be more on the spot).

I'm at work now so I can only skim through these text (and I have yet to find an "official" definition) but for now I think we should go with "Delete" in both places rather than "Remove", but I'm very interested in why you say the latter is more precise. I've always thought of removing an editor profile as something permanent that can not be undone, and getting rid of a profile doesn't "move" it anywhere. It also implies which SQL command will be executed when the action is confirmed.
If was possible to restore a profile from a dormant or inactive state, I think I would have chosen "Disable" and "Enable" instead.

References:
http://www.english-test.net/forum/ftopic17820.html
http://www.ixda.org/node/15267
http://www.google.com/search?q=define:delete
http://www.google.com/search?q=define:remove

sun’s picture

Status: Needs review » Needs work

While very minor, we can do this, because it's in line with the general direction that we are going to allow to attach multiple profiles to a text format -- thus, "remove" is going to remove a profile in terms of "unassigning from a format", whereas we'll introduce a new "delete" operation to kill a editor configuration entirely.

+++ wysiwyg.admin.inc	(working copy)
@@ -418,7 +418,7 @@
-    '#description' => t('To assign a different editor to a text format, click "delete" to remove the existing first.'),
+    '#description' => t('To assign a different editor to a text format, click "remove" to remove the existing first.'),

"remove to remove" sounds odd though ;)

Let's just remove the part:

'click "remove" to'

Powered by Dreditor.

sun’s picture

Status: Needs work » Closed (duplicate)

I just reviewed the actual administrative UI manually once more and I don't think this makes sense on its own.

Right now, "delete" means "delete"; i.e., the configuration is entirely nuked.

Therefore, marking as duplicate of #748980: Allow multiple editor profiles for the same format