.. is it worth the effort to have all messages in this command-line suite be separated out into a message catalog?

My experience in dealing with developers in India (i.e., with a very biased sample with respect to the entire population) is that English is a non-issue. I have no experience with working with developers in China (from, but not in).

Extracting messages into a catalog isn't too big a deal. It's one of those problems you just throw time at. Getting those messages translated (and the translations checked), can be a large, long, frustrating undertaking, even for large enterprises that do it on an ongoing basis. You either have to impose early "language change" freezes so that translations can all be done at once, or you stagger releases as translations become available. Neither is fun.

I'd run the question by your product manager. Not phrased as "should we do this?", which just invites a "Yes!", but phrased as "If we do this, it'll cost us X$ to do the message catalog, and Y$ (where Y might be "unknown, and we'll need outside help") to get the translations done. Where should that fit on the list of priorities?"

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