General
Command Line
Character Sets
command.xml.file:input.txt.US-ASCII.file:output.txt.US-ASCII. For strictly
compliant encoding, you can use one of the character sets supplied with Bacchus. These character
sets guarantee that no invalid character will be emitted, and include some transposition to
replace invalid characters with reasonable alternates.\n). For strictly compliant encoding, eliminate this value by
setting this value to an empty string.validate command line job in the built in context:org.springframework.batch.core.launch.support.CommandLineJobRunner command.xml validatenormalize command line job in the built in context:org.springframework.batch.core.launch.support.CommandLineJobRunner command.xml normalizeX-ACH character set?
X-ACH character set simply replaces invalid characters with a question mark
'?'. The Unicode substitute character \u00a1 is not used because it is not legal in ACH.X-ACH-X character set?
X-ACH-X character set attempts to transpose invalid characters to 1-byte
equivalents. The transpositions replace characters found within the
java.lang.Character.UnicodeBlock#LATIN_1_SUPPLEMENT and
java.lang.Character.UnicodeBlock#LATIN_EXTENDED_A ranges with reasonable equivalents within
the allowed range. In most cases, the replacement is simply the unaccented version of the same character.X-ACH-XL character set?
X-ACH-XL character set extends the X-ACH-X character
set with transliterations that cover ligatures found in the
java.lang.Character.UnicodeBlock#LATIN_1_SUPPLEMENT and
java.lang.Character.UnicodeBlock#LATIN_EXTENDED_A ranges. This character set is intended
for internal translations. The transliterations may result in more than one byte of output for a
single input character. In addition, the byte order marks FFFE and FFFF
are suppressed and result in no output. Because of these length-changing properties, this
character set should not be used directly on the output stream, where it could cause
unexpected extra or missing bytes in fixed width fields.