On Sun, 04 Jun 2000, you wrote:
>Uwe Bonnes wrote:
>[snip]
>> Just a remainder. \r\n vs pure \n might be another source of problems.
>
>I am not sure whether I should take up this issue on the scanner side
>because it is trivial to resolve by other means. Afterall, we are
>compiling on unix-type machines, which have '\n' as standard. The only
>valid reason would be to backport wrc to dos/win32 platforms, but I
>haven't done that since (approx) version 1.0.0 anymore. If there are any
>other compelling reasons to suppurt '\r\n', then I might reconsider.
Modifying my resource file to this:
STRINGTABLE
{
WCMD_CALL,
"CALL <batchfilename> is used within a batch file to execute commands\n \
from another batch file. When the batch file exits, control returns to\n \
the file which called it. The CALL command may supply parameters to the\n \
called procedure.\n \
\n \
Changes to default directory, environment variables etc made within a \n \
called procedure are inherited by the caller.\n"
}
produces the correct result in Wine but the Borland resource compiler
inserts two newlines.
I agree this is not a big issue. It will only affect someone porting an
application to WineLib which uses strings in this way, and there may not
be too many of those. I am happy to patch wcmd if you want to leave the
compiler as it is.
Dave Pickles
