reload_config_texts(3alleg4) [debian man page]

reload_config_texts(3alleg4)					  Allegro manual				      reload_config_texts(3alleg4)

NAME

       reload_config_texts - Reloads translated strings returned by get_config_text(). Allegro game programming library.

SYNOPSIS

       #include <allegro.h>

       void reload_config_texts(const char *new_language);

DESCRIPTION

       Reloads	the  translated strings returned by get_config_text(). This is useful to switch to another language in your program at runtime. If
       you want to modify the `[system]' language configuration variable yourself, or you have switched configuration files, you will want to pass
       NULL  to  just  reload whatever language is currently selected. Or you can pass a string containing the two letter code of the language you
       desire to switch to, and the function will modify the language variable. After you call this function, the previously returned pointers	of
       get_config_text() will be invalid. Example:

	  ...
	  /* The user selects French from a language choice menu. */
	  reload_config_texts("FR");

SEE ALSO

       get_config_text(3alleg4), get_config_string(3alleg4)

Allegro 							   version 4.4.2				      reload_config_texts(3alleg4)

get_config_text(3alleg4)					  Allegro manual					  get_config_text(3alleg4)

NAME

       get_config_text - Returns a string translated to the current language. Allegro game programming library.

SYNOPSIS

       #include <allegro.h>

       const char *get_config_text(const char *msg);

DESCRIPTION

       This  function is primarily intended for use by internal library code, but it may perhaps be helpful to application programmers as well. It
       uses the `language.dat' or `XXtext.cfg' files (where XX is a language code) to look up a translated version of the parameter  in  the  cur-
       rently selected language.

       This  is basically the same thing as calling get_config_string() with `[language]' as the section, `msg' as the variable name, and `msg' as
       the default value, but it contains some special code to handle Unicode format conversions. The `msg' parameter is  always  given  in  ASCII
       format,	but  the  returned  string  will  be converted into the current text encoding, with memory being allocated as required, so you can
       assume that this pointer will persist without having to manually allocate storage space for each string.

       Note that if you are planning on distributing your game on the Unix platform there is a special issue with  how	to  deal  with	the  `lan-
       guage.dat' file. Read section "Files shared by Allegro" of the chapter "Unix specifics" to learn more about this.

RETURN VALUE

       Returns a suitable translation if one can be found or a copy of the parameter if nothing else is available.

SEE ALSO

       get_config_string(3alleg4), reload_config_texts(3alleg4)

Allegro 							   version 4.4.2					  get_config_text(3alleg4)