C++ Message Resource Wizard Page
- Resource File Type: The generated resource file(s)
where externalized objects are inserted will be of this type.
- Resource File Frequency: Project means there
will be only one file, while Source File means each individual
source file where strings are externalized will receive its own
corresponding resource file.
- Retrieval Method: The method signature your program
uses to retrieve resources from a resource file. In the case of message catalog files,
the retrieval method is set to catgets([catd],[set],[key],"[originalString]")
and cannot be modified.
- String Key Format: This field displays the current
format for the resource keys that Globalyzer creates during string
externalization. Click the Edit Format button to change the
format, allowing you to completely customize your resource keys.
- String Key Next ID: Initially set to 1, this field is
incremented each time you externalize a string, and is used as the ID
part of the String Key Format. In this way, Globalyzer
maintains uniqueness across all resource keys.
- Set: An integer value, that can be used to group your messages.
- nl_catd Variable Name:
This field refers to a variable that must be available in order
to retrieve strings from message catalog files. If the .msg file type is selected
in this dialog, Globalyzer will replace all embedded strings with a call to
catgets , a
standard UNIX call to retrieve strings from message catalogs. One required argument to
catgets is the
nl_catd variable, which is a pointer to the compiled message catalog and is generated via a
call to catopen. Hence, somewhere early in the program, your code needs to call
catopen , which
returns the nl_catd variable. That variable needs to be made accessible as a global variable
and you also need to inform Globalyzer of that variable name so Globalyzer can pass it into all of the
calls to catgets
that it generates when it externalizes strings from your code.
- Share Strings: Allow the sharing of keys for
identical strings.
- Externalized String Comment: This will be used if you
choose to add a comment after externalizing a string. Select Window=>Preferences=>Globalyzer
and check Automatically Insert Externalized String Comment.
- Resource File Path: This is where your resource file
is stored. Add a name if you don't already have a file. In the case
where Resource File Frequency is set to Source File,
Globalyzer will create multiple resource files, with names that
correspond to the source filenames. For example, for a file named SwingTest.java,
Globalyzer will create a resource file name SwingTest.properties
to hold its externalized strings.
- Header File Path: Specify the directory for the
header resource file that Globalyzer creates during string
externalization.
- Resource File Encoding: Set the file encoding of the
resource file. Globalyzer will assume all your resource files
of this type are the same encoding, although it will ensure that if a resource file has
BOM bytes (bytes at the beginning of the file that indicate encoding), it will access the
file properly, regardless the Project's Resource File Encoding setting. To see the
encoding of an individual file, right-click on the file in the Project Explorer view
and select Properties.
|