I suggest you back up and consider the more general problem - separating the interface to your program from the core logic. If you do a good job of that you may not have to resort to a message catalog right away (although that might still be a good idea, depending on how you rate the chances of an i18n project in your future).

In the web world the most common way to separate interface from logic is via a model-view-controller architecture (MVC). You didn't give us enough information to guess whether that would be directly applicable to your app, but anything you can do to make your code interface-agnostic will help you when it comes time to make cosmetic changes, i18n changes included.

-sam

In reply to Re: Are Message Catalogs Worth It? by samtregar
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.