Yes, http://xml.apache.org/xalan-j/commandline.html is somewhat out of date. We should fix that.
Meanwhile, it you run org.apache.xalan.xslt.Process with no argument it will list most of the supported options. I believe there are a few which got added recently and didn't get into this list (oops), and there may be a few which may not currently be functional in alll possible combinations (I don't think we actually honor -ENTITYRESOLVER in incremental-parsing mode when running with with Xerces-2, for example). Xalan-J's formatting for newline should normally be whatever your JVM thinks is the "native" representation of newline on your platform. In Windows, that should be CRLF; in a Unix-style enviroment that should just be LF. Since you said you're running under Solaris, that means a bare LF is to be expected... and is usually what you want, since that's what Unix defines as normal text file format. Note too that XML parsers normalize newlines, so whether the file contains CR, LF, or CRLF it shows up as LF when viewed through DOM, SAX, or XNI. I'm not sure offhand whether the same rule applies to HTML, but since HTML generally treats line break as just another kind of whitespace (except in <pre/> blocks) it may not make much difference there either. Of course if you're trying to use TEXT output to generate a specific file format that absolutely requires CRLF, that's a problem... until/unless we reintroduce a way to control this, your best bet may be to put Xalan's output through a postprocessor that converts the newlines appropriately. Most Unix systems have such a tool these days, to facilitate exchanging files with the Unwashed Masses using DOS and Windows.
