SIRMSG parameter: Difference between revisions
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
==Description== | ==Description== | ||
Controls the case (mixed vs. upper) of | Controls the case (mixed vs. upper) of <code>MSIR</code> messages. | ||
This numeric parameter must have a value of 0, 1, or 2. | This numeric parameter must have a value of 0, 1, or 2. | ||
| Line 28: | Line 28: | ||
<br /> | <br /> | ||
Unless a site is using DBCS, this default setting should be fine. | Unless a site is using DBCS, this default setting should be fine. | ||
<dt>1 | <dt>1 | ||
<dd>Forces translation of <code>MSIR</code> messages to upper case. | <dd>Forces translation of <code>MSIR</code> messages to upper case. | ||
<dt>2 | <dt>2 | ||
Revision as of 13:56, 15 June 2017
Upper casing of MSIR. messages
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- System manager resettable
- Related products
- All
- Introduced
- Before Sirius Mods 6.7
Description
Controls the case (mixed vs. upper) of MSIR messages.
This numeric parameter must have a value of 0, 1, or 2.
The values for SIRMSG are:
- 0
- Means that
MSIRmessages are left as mixed case unless DBCSENV is set to a non-zero value, in which case they are translated to upper case. This value means that mixed case messages are translated to upper case in any Online using DBCS characters where lower case characters might end up being displayed as katakana.
Unless a site is using DBCS, this default setting should be fine. - 1
- Forces translation of
MSIRmessages to upper case. - 2
- Always leaves
MSIRmessages in mixed case, even if DBCSENV is set to a non-zero value. This is useful at DBCS sites where it is known that lower case characters will be correctly displayed.