Do you still use *MSGF exclusively?

I know that folks have put message files in data files by key, that is
nice for certain cases.
If you use *MSGF do you sit and type them 1 by 1, or do you use a
"power tool"  for heads down entry of the 500 messages in front of
you?
(Yes, please email me a copy or point me there if I am the only that
missed that thread)
And, what about native enhancements to *MSGF?
Is *MSGF now considered "for legacy compatability only" I am leaning
toward no as a guess, and if it is legacy, what is the best way to
organize messages on the iSeries here forward? I stress - natively.

Is this a dumb question?
I ask becuase the message file seems so limiting and without
enhancements (that are obvious to me) for more than a few releases.

I just think it is a project or /quality hit to try to have an
application tell the user EXACTLY what they did wrong, then have to
formulate that specific message, unique as it may be, in a *MSGF that
conforms easily to a multilingual environment. My only point is *MSGF
file is much more generic in structure than explaining the
complexities of today's applications.

Also, if there is a magic tool for this that helps project
organization, I missed it and a link would be appreciated.
-
Mark Villa
Summerville, SC