... no changes ... no changes ... no changes ... no changes ... no changes ... no changes ... no changes ... no changes ... no changes ... no changes ... no changes ... car insurance : [http://www.insurance-top.com auto insurance] - [HTTP://www.insurance-top.com auto insurance] : [Insurance car|http://www.insurance-top.com] - [Insurance car|HTTP://www.insurance-top.com] : http://www.insurance-top.com/auto/ : [[http://www.insurance-top.com insurance quote]] : [[http://www.insurance-top.com | home insurance]] : "cars insurance" http://www.insurance-top.com : [http://www.insurance-top.com|insurance auto] [[could someone write some words here about what message catalogs are, as well as some of the facilities that exist for creation and use of them?]] '''DGP''' -- This page is very confusing because it comingles descriptions of two completely different things: the msgcat package bundled with Tcl, and the message catalog facilities provided by the TclX package. Please create separate pages for each of those, and just links here. In fact, feel free to replace '''ALL''' the text below. What I [LV] was seeking when creating this page was a place holder to discuss the ''concept'' of message catalogs. I didn't know that there were different things using the same name. Someone who actually understands the concepts can feel free to create here a proper description. The following text is a quote from the Tclx man page. ---- Tcl programmers can use message catalogs to create applications that are language-independent. Through the use of message cata- logs, prompts, messages, menus and so forth can exist for any number of languages, and they can altered, and new languages added, without affecting any Tcl or C source code, greatly easing the maintenance difficulties incurred by supporting multiple languages. A default text message is passed to the command that fetches entries from message catalogs. This allows the Tcl programmer to create message catalogs containing messages in various languages, but still have a set of default messages available regardless of the presence of any message catalogs, and allow the programs to press on without difficulty when no catalogs are present. Thus, the normal approach to using message catalogs is to ignore errors on catopen, in which case catgets will return the default message that was specified in the call. The Tcl message catalog commands normally ignore most errors. If it is desirable to detect errors, a special option is provided. This is normally used only during debugging, to insure that message catalogs are being used. If your Unix implementation does not have XPG/3 message catalog support, stubs will be compiled in that will create a version of catgets that always returns the default string. This allows for easy porting of software to environments that don't have support for message catalogs. Message catalogs are global to the process, an application with multiple Tcl interpreters within the same process may pass and share message catalog handles. ---- It's not true that message catalogs are global, they are namespace-specific. -- [CLN] 2002-05-21 ---- [Tcl] has support for message catalogs via [msgcat]. [Tclx] has support for message catalogs via [catopen], [catgets], and [catclose]. ---- [Category Local]