I've only used Printomatic Lite (most recently 1.6.5) so I have no info
on adding pages, but would inserting
reset doc
right after
if not objectP(doc) then exit
to reset the instance of the document help? I seem to recall it solved
some of my general woes with Printomatic Lite. Gr
On Saturday, March 15, 2003, at 07:08 PM, Howdy-Tzi wrote:
On Saturday, Mar 15, 2003, at 17:41 America/Chicago, Thomas Drapela
wrote:
Hello all,
I'm having a vexing problem creating a miaw at runtime on Windows.
The script I'm using runs fine in the _authoring_ environment on
Hello all,
I'm having a vexing problem creating a miaw at runtime on Windows. The
script I'm using runs fine in the _authoring_ environment on both Mac
(Dir8, MacOS 9.2 in OSX shell) and Win (Dir8, Win2000P), and fine in a
_projector_ on Mac, but not on Win. The offending line of code is:
th
> The only multibyte (not double-byte) character sets are Chinese, Korean,
> and Japanese. Unicode is double-byte, but Director doesn't support it.
Regardless, Director's double-byte interpreter accommodated Chinese
characters being read in from an ini file. That's the extent of my
experience wit
>>
>> Sample languages using double-byte characters: Arabic, Chinese, German,
>> Japanese, Korean, Portuguese, Russian
>
> This is from some MACR technote but I doubt it is correct when German is
> listed next to Chinese: German umlauts work pretty well in single-byte
> Characters and Swedish,
It's been a while, but try adding this to your startMovie script:
the romanLingo = FALSE
"the romanLingo" determines whether Director is using a single-byte (TRUE)
or double-byte (FALSE) interpreter. Normally, "the romanLingo" is set when
Director is first started and is determined by the local
