Publishing Reports to the Web - Downloads - Oracle

B.1.44 REPORTS_NLS_XML_CHARSETS
Environment Variables
Description This environment variable provides an override option to enable you to
define the character set encoding used when saving a report in XML format. This is
only required where the required character set mapping for Reports NLS_LANG to
XML IANA character sets do not produce the required results.
To enable your XML parser to understand the characters within the XML files, Oracle
Reports does the following:
1. Adds an encoding attribute to the XML declaration based on the value in NLS_
CHARACTERSET, the character set part of the NLS_LANG variable.
2. Translates the value set as the NLS_LANG character set (e.g., JA16SJIS) to what is
expected in the XML specification (e.g., Shift_JIS).
You can override this mapping by adding entries to the REPORTS_NLS_XML_
CHARSET.
Valid Values Set of mapping pairs separated by semicolons. The first value is the
encoding that is being produced and the second mapped value is the value that should
be used for these cases.
=[;=][;=]...
Default Not defined.
Usage notes This environment variable should not be required and is currently only
used as a workaround to Bug 2224413:
NLS:NEED STABLE MAPPING FROM ORACLE'S NLS_CHARACTER_SET TO IANA
ENCODING
Example
WISO-8859-8=ISO-8859-8-1;CSEUCKR=EUC-KR;WINDOWS-949=EUC-KR;EUC-CN=GBK;WINDOWS-936=GBK
B.1.45 REPORTS_NO_DUMMY_PRINTER
Description This environment variable specifies whether the system’s surface and
fonts should be used instead of the printer’s.
Valid Values TRUE|not set
Default TRUE
Usage Notes
■ REPORTS_NO_DUMMY_PRINTER is set by default and is required to be set at all
times. If it is not set (as a result of being user-modified), and there is no valid
printer, error REP-1800 error is raised. Alternatively, you could use TK_PRINT_
STATUS when you have no valid printer. A valid printer response is required by
Oracle Reports to generate output, even if you are generating to a file. Beginning
with Oracle Reports 10g (9.0.4), if the uiprint.txt file does not contain a valid
entry (i.e., no valid printer is defined), but REPORTS_NO_DUMMY_PRINTER is set,
Oracle Reports uses screenprinter.ppd specified in uiscreenprint.txt.
You should unset this environment variable only if you do not want the
screenprinter.ppd driver to be used by Oracle Reports when there is no valid
printer.
Reports-Related Environment Variables B-17