RE: QuarkXPress: intermittant xtags export problems
RE: QuarkXPress: intermittant xtags export problems
- Subject: RE: QuarkXPress: intermittant xtags export problems
- From: mick wenlock <email@hidden>
- Date: Thu, 6 Sep 2001 09:03:55 -0600
Michael Turner <email@hidden> wrote on Thu, 06 Sep 2001
on the subject: QuarkXPress: intermittant xtags export problems
>
Hello everyone,
>
>
I have some text which intermittently 'disappears' when exported with xtags
>
filter, but appears fine when exported via ASCII filter. (By 'disappears' I
>
mean the text is replaced with the xtags entity for null, which is
>
incorrect: <\#000>) The text was placed into the story by a plugin
>
(PowerMath). Why does this text not export as expected? Is there some
>
command akin to 'update' which I need to make the text recognized? The same
>
text will cut & paste correctly. Sample text below. It is the equations
that
>
are mangled by the xtags: " [&*cf*{7}{15}&] " becomes "
>
<b-0.099><\!s><\#000><\#000><\#000><\#000><\#000><\#000><\#000><\#000><\#00
0
>
><\#000><\#000><\#000><\#000><\#000><\#000><$b-0.099><\f><\f><\f><\f><x@ANS
B><b-
>
0.099> ". However... not every time I run the export, only 1 out of 10 or
>
less. Even within the same xtags export, some equations are exported fine
>
while others are broken.
>
Any help would be appreciated. My only workaround is to export all the
>
broken equations via ASCII filter. Since I have many thousands of them, I
>
really prefer to keep them in the regular flow of my text processing.
>
Breaking them out then matching them back again is painful. Thanks!
>
/Michael
>
These pages are some 'answers to questions', question number is followed by
>
equation which is the answer.
Dear Michael,
I have seen something similar to this before, we isolated it down to what
appeared to be damaged documents. One fix that worked and which you may want
to give a try was to save the text out as Word 6 or 8 and then reimport with
style sheets. When we did that we were then able to save the updated text as
XPress tags with no problem. Not the most elegant of solutions I admit. It
did appear in this other case that there was something in the original text
that had been imported into the QXP document that was causing the whole
thing to act weirdly.
I hope that helps.
Best Regards,
Mick Wenlock
Quark AppleScript Support