Xref: utzoo comp.unix.programmer:1596 comp.lang.perl:4947 comp.std.internat:856 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!mcsun!hp4nl!sci.kun.nl!cs.kun.nl!hansm From: hansm@cs.kun.nl (Hans Mulder) Newsgroups: comp.unix.programmer,comp.lang.perl,comp.std.internat Subject: Re: Tools for manipulating message catalogs Message-ID: <2959@wn1.sci.kun.nl> Date: 16 Apr 91 09:40:11 GMT References: <1991Apr7.190119.24825@motcad.portal.com> <1991Apr15.170901.18836@dg-rtp.dg.com> Sender: root@sci.kun.nl Followup-To: comp.unix.programmer Distribution: comp Organization: University of Nijmegen, The Netherlands Lines: 26 In <1991Apr15.170901.18836@dg-rtp.dg.com> eliot@chutney.rtp.dg.com (Topher Eliot) writes: >Sure, in an ideal world I would like to have one huge build process that >starts with my source archives for everything, and burps out a tape at the >far end that I can ship to any customer, anywhere in the world, and have it >work correctly, no matter what earlier versions of software they have on their >machine. I have yet to see any company that actually implements such >a system, and I've worked at some of the largest computer manufacturers in >the world. The realities of getting things translated into other languages >are horrendous. You don't really expect a company to delay the release of their latest product until they are able to bundle with it free message catalogs in a dozen major languages, do you? In the real world the product is shipped as soon as the English version of the product is ready. Simultaneously the message catalog (but not the executable) is sent to the translator. Non-English versions of the product hit the market 6 months later than the English version, at the earliest. And they are sold as separate products. And combining the correct version of the executable with a translated message catalog is really trivial, compared to the problem of getting the catalog translated in the first place. -- Hans Mulder hansm@cs.kun.nl