(INFO
". The data can be in one or more files, or coming from stdin. "
"This provides an easy way of specifying the information about some "
"data as to wrap it in a NRRD file, either to pass on for further "
"unu processing, or to save to disk. Note that with \"-h\", this creates "
"a detached nrrd header file, without ever reading or writing data files. "
"\n \n "
"When using multiple datafiles, the data from each is simply "
"concatenated in memory (as opposed to interleaving along a faster axis). "
"Keep in mind that all the options below refer to the finished data segment "
"resulting from joining all the data pieces together, "
"except for \"-ls\", \"-bs\", and \"-e\", which apply (uniformly) to the "
"individual data files. Use the \"-fd\" option when the things being joined "
"together are not slices of the final result, but slabs or scanlines. "
"It may be easier to put multiple filenames in a response file; "
"there can be one or more filenames per line of the response file. "
"You can also use a sprintf-style format to identify a numbered "
"range of files, so for example \"-i I.%03d 1 90 1\" "
"refers to I.001, I.002, ... I.090, using the inclusive range from the first "
"to the second integer (following the sprintf-style format), in steps of "
"the third. Can optionally give a fourth integer to serve same role as "
"\"-fd\"."
"\n \n "
"NOTE: for the \"-l\" (labels), \"-u\" (units), and \"-spu\" (space units) "
"options below, you can use a single unquoted period (.) to signify "
"an empty string. This creates a convenient way to convey something that "
"the shell doesn't make it easy to convey. Shell expansion weirdness "
"also requires the use of quotes around the arguments to \"-orig\" (space "
"origin), \"-dirs\" (space directions), and \"-mf\" (measurement frame).")