Not knowing too much about your specs, I'd lean towards "Yes, have a structured message system."

For one, it's really not that difficult before-the-fact. It can be much more expensive to implement if you change your mind and do it later. Also, it should be much easier to standardize and control the message delivery, (formatting, tense, tone-of-speech, etc.).

Finally, I think it would be easier to test. One of my pet peeves is when a project has the capability to issue messages that aren't to be found in the docs. If the messages are structured, you'll be able to more easily ensure that they're all documented correctly.

I just can't really see much downside to doing it 'right'. Who ever regretted that?

In reply to Re: Are Message Catalogs Worth It? by pboin
in thread Are Message Catalogs Worth It? by jffry

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.