| Prev | Next |
Custom Language Settings
If you export RTF-format documents from Enterprise Architect in languages other than English, you can customize the codepage, default language ID and character set that Enterprise Architect uses when generating RTF. This makes it much easier to generate documentation appropriate to your country or locale.
You can also set up a list of word substitutions. For instance, where Enterprise Architect would include the word 'Figure', you can specify another word to replace it that is either in your language or more meaningful to your readers.
Set up Substitutions
Step |
Action |
See also |
|---|---|---|
|
1 |
Open the 'Rich Text Format Report' dialog. |
The Legacy RTF Report Generator |
|
2 |
In the 'Language' panel (bottom left of dialog) click on the . The 'Customize RTF Language' dialog displays. |
|
|
3 |
Double-click on an item to set or clear its Substitute word. |
|
|
4 |
When you have finished, click on the . |
Set Up Language, Codepage and Character Set
Step |
Action |
See also |
|---|---|---|
|
1 |
From the drop-down lists in the 'Language', 'Codepage' and 'Charset' fields, select the language, codepage and character set that most closely match your location. |
|
|
2 |
If required, modify the Substitute Tags by double-clicking on each and manually setting the value (for advanced use only). |
|
|
3 |
To clear the substitution list, double-click on each item in turn and delete the substitute value. |
|
|
4 |
When you have completed the settings, click on the to save them. Now when you generate RTF documents, the substitute tags are used in the output. |
Notes
- If you want to generate reports in a language that requires Unicode support, please note that Enterprise Architect .eap files default to using JET 3.5 as the database engine, which does not support Unicode character sets (see the Startup topic); to provide Unicode support in your project, either upsize to a DBMS repository, or set JET 4.0 as the database engine and download a copy of the Jet 4.0 EABase model from the Sparx Systems website, then do an EAP to EAP transfer of your model into the Jet 4.0 file
- You can transport these language and tag definitions between models, using the 'Configure > Model > Transfer > Export Reference Data' and 'Import Reference Data' ribbon options