I've always thought the requirement to enable the "hardcoded string literal"
inspection to i18nize strings via QuickFix is quite hard to find for an average
Now, since the "I18nize JSP Text" appeared in the refactoring menu, this is not
only non-obvious but also additionally confusing because one part of the I18N
functionality is available via the refactoring menu while another one is not. I
even dare to say that the less common functionality for JSP is easier and more
obvious to find than the one for plain Java.
I think this needs some thought how to make this more consistent, convenient to
use and easier to find for a new user. Unfortunately, I don't have a good
solution other than simply adding an "I18N" submenu to the refactoring menu and
putting both the i18nize actions for JSP and Java in it.
Talking about the refactoring menu, this has been getting fairly long these days
(especially with Refactor-J), so it might be worth to consider putting some less
frequently used actions into an "Advanced" (or similar) submenu.
Anyway, just some food for thought.