Re: Strange SA/NV behavior--BK is culprit

[Carl Distefano cld@xxxxxxxx]

Reply to note from Carl Distefano  Sun, 18 Oct 2009
02:06:37 -0400

> Here's a fix:

And here's a slight revision to the fix. The original fix used
Ascii-14 as a parsing character that would be unlikely to appear in
any d:\path\filename. But it occurred to me that there is a set of
characters that cannot possibly appear in any filename (because
they're illegal), and that any of these would be a better choice for
this purpose than Ascii-14 (which is legal). So I've changed the two
instances of Ascii-14 to Ascii-63 ("?").

XPLeNCODE v2.0
b-gin [UNTITLED]
{<}IF{<}VA$MO{>}>0{>}{<}SX01,{<}VA$FP{>}{>}[BX_]exist {<}PV01
{>}[Q2_]{<}IF@NOT({<}ER{>}){>}{<}SX02,{<}IS01{>}{>}{<}IF{<}VA
$EX{>}>""{>}{<}SX03,{<}IS01{>}+"?"{>}{<}SX02,"."+{<}VA$EX{>}+
"?"{>}{<}XS03,02,02,04,04{>}{<}EI{>}[BX_]copy/nv {<}PV01{>} {
<}PV02{>}.BAK[Q2_]{<}EI{>}{<}EI{>}[GT_]{<}SV01,{>}{<}GT01{>}[
BX_]sa[Q2_]{<}IF@NOT({<}ER{>}){>}{<}PRFile saved{>}{<}EI{>}{<
}EX{>}[cr|lf][cr|lf]
-nd
XPLeNCODE

--
Carl Distefano
cld@xxxxxxxx