Everyone,
I've been doing some digging and how far back do we want to support for
the Windows batch files?
The reason I'm asking is I found some new items that will help the batch
files for the binary release. Particularly in finding the OPENNLP_HOME
directory.
There is an interesting series of options that allow the user to expand
some sets of the parameters.... and will help with specifying the
OPENNLP_HOME directory. It would also bring things more in line with
the LINUX implementation by specifying the directory for this.
The 1's in the below table are for the first parameter... %0 is the
first and I am going to use "%sp0.." as the path to the directory for
OPENNLP_HOME.
James
>From Microsoft's Site:
The following table lists the modifiers you can use in expansion.
Modifier Description
*%~1*
Expands %1 and removes any surrounding quotation marks ("").
*%~f1*
Expands %1 to a fully qualified path name.
*%~d1*
Expands %1 to a drive letter.
*%~p1*
Expands %1 to a path.
*%~n1*
Expands %1 to a file name.
*%~x1*
Expands %1 to a file extension.
*%~s1*
Expanded path contains short names only.
*%~a1*
Expands %1 to file attributes.
*%~t1*
Expands %1 to date and time of file.
*%~z1*
Expands %1 to size of file.
*%~$PATH:1*
Searches the directories listed in the PATH environment variable and
expands %1 to the fully qualified name of the first one found. If the
environment variable name is not defined or the file is not found, this
modifier expands to the empty string.
The following table lists possible combinations of modifiers and
qualifiers that you can use to get compound results.
Modifier Description
*%~dp1*
Expands %1 to a drive letter and path.
*%~nx1*
Expands %1 to a file name and extension.
*%~dp$PATH:1*
Searches the directories listed in the PATH environment variable for %1
and expands to the drive letter and path of the first one found.
*%~ftza1*
Expands %1 to a *dir*-like output line.
