anzio Printing overlays

[Brian K. White]

Walter Vaughan wrote:
> Dennis DIller wrote:
> 
>> Is anyone using anzio win 16 for printing overlays onto a filefro form
>> I need to know the script to send from the host to anzio. I have mutable
>> forms and would like to be able to choose these forms from the host.
>> I've tried This filepro doesn't like it
>>  
>> 'System noredraw    (echo -e 
>> "\034//?overlay<c:\eusa\eusahednc.tif>>://?view \035" )
> 
> You do know that you have a "the rest of this line is a comment" mark 
> before the system command.

Did anyone point out that it's
system expression
not
system (expression)
also there are quoting mistakes since he's trying to use an echo command 
  which needs it's arguments quoted, within a system command which 
itself need to be a quoted litteral or an expression that adds up to the 
  string he wants. Also there are windows path seperator escaping 
problems. Those back-slashes in the file name will take several trial & 
error runs to get right.

in other words:
system noredraw "echo -e 
\"\034//?overlay<c:/eusa/eusahednc.tif>>://?view \035\""

Here I have ONLY fixed the overall system command quoting and the 
beginning and ending of the echo command quoting, and I know that now 
the \034 and \035 will work, and I have taken a gamble that Anzio will 
accept forward-slashes as path seperators. But I have no idea about 
what's in between \034 and \035, so the command may or may not yet work.
If Anzio actually requires back-slashes in the file argument for that 
command, then you will likely need to use either 2 or 4 backslashes for 
each one that you want Anzio to "see".

So possibly:

system noredraw "echo -e 
\"\034//?overlay<c:\\eusa\\eusahednc.tif>>://?view \035\""

or

system noredraw "echo -e 
\"\034//?overlay<c:\\\\eusa\\\\eusahednc.tif>>://?view \035\""

But I would avoid that even if it works because you will just have never 
ending problems handling these strings. If you try to replace any part 
with a variable, or hand off the entire string to some other process, 
etc.. always going to be fighting with those backslashes to get them 
escaped past all the things that want to eat them (interpret them as 
commands or special syntax, which include the filepro system command, 
the shell inside the system command, the echo command inside the shell 
inside the system...) yet, arrive at the destination as the single 
backslashes the destination expects.
Far simpler just to see if forward-slash works instead and use that 
everywhere possible. And if it doesn't in this case, well, since those 
are Anzio internal commands reading the string, it means it's probably 
within Anzio's power to allow forward-slash, and since Bob is a nice guy 
and reads this list, you may be able to get forward-slashes to work by 
asking even if they don't already. I'm  only referring to the 
backslashed in the c:\path\to\file . Every other backslash up there is 
fine. We WANT those to be interpreted.

-- 
bkw