|
List Info
Thread: Re: Re: Weird little problem!
|
|
| Re: Re: Weird little problem! |
  United States |
2007-04-03 01:01:06 |
|
Thanks guys for the suggestions
David,
I did try Irfanview (wasn't aware of it) and had to download the full
list of plug-ins. It was calling for a DJVU plug-in for the PageStream
file, but when I tried it after installing the plug-in Irfanview still
balked at reading the PgS file!! I will use Irfanview for other
things, though. Thanks anyway.
Tim,
Saw the script file you referred to and saw the line where the editor
was and put in 'notepad.exe' in place of nedit (I think it was).
However when I went to try to run a script, that command in my menu is
faded out! Would this be due to the fact that I have the 'non-pro'
version or that I don't know what I'm doing (this last is the more
likely answer :->).
Anyway, I came up with a temporary solution and it involved cutting
and pasting the text into Notepad which apparently cleared whatever
the codes were and I was able to copy and paste this text back into
PageStream, then had to reformat the text as I had it before (bolds,
italics, underline and so on!).
So problem worked around for now, but still would like to know what
the problem is!
I'm still quite a newbie in using this version of PageStream even
though I had the original Atari ST version and I think I also received
one or two updates after that. Still lots to learn in desktop publishing!
Thanks again for the replies,
Frank Jordan
__._,_.___
.
__,_._,___
|
| Re: Re: Re: Weird little problem! |
  Netherlands |
2007-04-03 01:29:05 |
|
fjordanrr wrote:
> Thanks guys for the suggestions
>
>
>
...snip...
> Tim,
>
> Saw the script file you referred to and saw the line where the editor
> was and put in 'notepad.exe' in place of nedit (I think it was).
> However when I went to try to run a script, that command in my menu is
> faded out! Would this be due to the fact that I have the 'non-pro'
> version or that I don't know what I'm doing (this last is the more
> likely answer :->).
>
Do you have Python running? If not you can download this at:
http://www.python.org/.
If in Scripts/ Play external scripts... are no green snakes (Python),
you haven't installed Python.
Another way to look at the text is to export the text as ASCII with
textcodes from PageStream. This gives the same result as send text to
the editor, only if you change things in that ASCII text, you have to
import the ASCII text into PGS again.
...snip...
> Thanks again for the replies,
>
> Frank Jordan
>
>
The change to notepad.exe is good!
Theo
__._,_.___
.
__,_._,___
|
| Re: Re: Re: Weird little problem! |
  United States |
2007-04-03 06:49:18 |
|
On Tuesday 03 April 2007 01:29, Theo Zweers wrote:
> fjordanrr wrote:
> > Thanks guys for the suggestions
>
> ...snip...
>
> > Tim,
> >
> > Saw the script file you referred to and saw the line where the editor
> > was and put in 'notepad.exe' in place of nedit (I think it was).
> > However when I went to try to run a script, that command in my menu is
> > faded out! Would this be due to the fact that I have the 'non-pro'
> > version or that I don't know what I'm doing (this last is the more
> > likely answer :->).
>
> Do you have Python running? If not you can download this at:
> http://www.python.org/.
> If in Scripts/ Play external scripts... are no green snakes (Python),
> you haven't installed Python.
And as one final thought about Python, due to the way Python libraries are
loaded by an application they have to be called by version number. This means
PgS must be recompiled for each new version of Python. If you *do* have
Python installed and the menu item is still greyed out it means you have a
version that is not supported by PgS.
This is unfortunate and, because it can change with each release of PgS and
Python is not easy to compile a list for. But if you have the latest and
greatest Python and it doesn't work step back a version and try again until
it does.
Tim Doty
__._,_.___
.
__,_._,___
|
| Re: Re: Re: Weird little problem! |
  United States |
2007-04-03 09:07:05 |
|
fjordanrr wrote:
>
>
> Thanks guys for the suggestions
>
> David,
>
> I did try Irfanview (wasn't aware of it) and had to download the full
> list of plug-ins. It was calling for a DJVU plug-in for the PageStream
> file, but when I tried it after installing the plug-in Irfanview still
> balked at reading the PgS file!! I will use Irfanview for other
> things, though. Thanks anyway.
Sorry, Open Irfanview. In The File menu, select Open As > Hex file...
Then select your PgS file and it will display as a hex file, where you
can see each element (in hex numbers).
--
DAVID L. STEVENS -- TEAM AMIGA --Chapter Chat Publisher
Windows XP user (:^(> on Acer Aspire 9810 2.16 GHz Notebook
2 GB RAM; 2 120-GB Hard Drives; CanoScan LIDE 20
Canon i860 & Brother HL-5050 PageStream v5.0.2.10Pro
<http://davestevens.home.insightbb.com>
Without a rich heart, wealth is an ugly beggar.
Ralph Waldo Emerson
__._,_.___
.
__,_._,___
|
| Re: Re: Re: Weird little problem! |
  United States |
2007-04-03 11:08:08 |
Frank:
> ...So problem worked around for now, but still would
like to know what
> the problem is!
>
Haven't imported text directly from Word in a while. I've
always found
it a bit frustrating if only because so many useless
paragraph formats
are imported at the same time. But I think some of the
problem may be in
Word. I've seen the original problem you described exhibited
within Word
itself, particularly where lists, indents, or tables are
involved.
Without being able to see where the text codes are being
placed (as you
can do with PageStream and an outside text editor or with
the edit
window in WordPerfect), the workaround has usually been to
keep deleting
and restoring blocks of text until I hit the place where the
errant text
code was. As others have suggested, the workaround within
PageStream,
until you get the Python script running, is to manually go
through the
steps the script does—exporting as ASCII text with codes and
so on.
That's the only way I can see to actually track down where
the problem
lies and answer your question definitively.
With Word, it sometimes helps to back up and alter text on
both sides of
the problem area. Text codes are usually between words, so
pick the last
and first few words on either side of the problem, then
where the
problem begins retype those words running them together as
one word.
Finally, delete the old version and insert spaces and
returns within the
monster word. Sometimes that works. It may work in
PageStream as well.
Also in PageStream, your imported Word text will have a
paragraph format
attached. Sometimes changing an expanded selection to an
irrelevant, but
different format, then changing back to the correct one(s)
will do the
trick. Or you can try editing the paragraph format in some
arbitrary
way. When the problem goes away, change it back.
I've found you can run into problems with text codes in any
application
if you use that application heavily enough. Sooner or later
you do
something or other that the application was never exercised
with during
testing and a code gets marooned in an odd place. It usually
seems to
involve paired codes. The software should delete or relocate
both and
somehow only one of the pair gets moved or deleted. I would
expect this
to happen occasionally when using cut and paste between
applications.
That increases the chances that only one member of a pair
gets picked
up. So I try to select more than I expect to use in the
receiving
application and then trim it back after the import.
HB
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http
://groups.yahoo.com/group/PageStreamSupport/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/PageStreamSupport/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:PageStreamSupport-digest@yahoogroups.com
mailto:PageStreamSupport-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
PageStreamSupport-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.c
om/info/terms/
|
|
| Re: Re: Re: Weird little problem! |
  United States |
2007-04-03 11:25:05 |
|
Frank:
An amendment to my last response is in order. In the last step of the
"monster word" method, you need to delete a little of the monster word
along with the old stuff. So if the "word" ends "eproblem", delete the
"m" along with the old text and then restore it when you break up the
word. Hopefully, that way you squash any text code that migrated between
the words. Maybe that explanation doesn't make sense, but my experience
is that it can make the difference between success and failure.
HB
__._,_.___
.
__,_._,___
|
| Re: Weird little problem! |
  Canada |
2007-04-05 04:31:52 |
|
Greetings "fjordanrr" < fjordanrr%40bellsouth.net">fjordanrr bellsouth.net>
On 03/04/2007 at 06:01 you wrote concerning
[PageStreamSupport] Re: Re: Weird little problem!
Hello Frank,
I'm not using a Windows version here, but there is a small
possibility that you can solve your problem with less
drastic methods than looking at Pagestream's 'hidden' text
codes, etc. Of course, as others have noted, the real
problem may be with the Word guy, but ..... ???
<<snip>>
f> Anyway, I came up with a temporary solution and it
f> involved cutting and pasting the text into Notepad which
f> apparently cleared whatever the codes were and I was able
f> to copy and paste this text back into PageStream, then
f> had to reformat the text as I had it before (bolds,
f> italics, underline and so on!).
f> So problem worked around for now, but still would like to
f> know what the problem is!
f> I'm still quite a newbie in using this version of
f> PageStream even though I had the original Atari ST
f> version and I think I also received one or two updates
f> after that. Still lots to learn in desktop publishing!
I'll assume that the Windows version displays an Edit
palette.
Put the cursor within the block of text wherein the problem
lies.
In the Edit palette click on the button '¶' which will
reveal which "Paragraph style" is in effect. I'm assuming
also that you are using some 'personalized' style beyond
the PageStream given <No Style>. Suppose the style in
question is 'Body1'. In the Edit palette check that the
parameters for 'Body1' are what you expect; i.e., examine
the settings (shown graphically) for
first line indent
left indent
right indent
space above
space below
If they are not what you expect them to be, then the Edit
palette will probably tell you that 'Body1+' is in effect.
In such case, highlight the entire paragraph and then
change the parameters in the Edit palette to what you want
them to be. Then click the "apply these settings" button
which is the leftmost one in the Edit palette. In your
case, it might be the setting for "first line indent" that
is off.
In your case, it does not seem necessary to clik the 'C'
button and check which font, size, etc., is being used for
that style, but such a check will do no harm.
Even if the above works, it is clumsy since you have to
change the parameters for each offending paragraph.
Here is another possibility, but, it does not always work.
Suppose you have another style, say 'Body2'. Highlight the
offending paragraph. Apply 'Body2' and
immediately thereafter apply 'Body1'. You may get lucky and
the paragraph will be displayed in the 'Body1' format. But
don't be surprised if the offending format re-appears and
the Edit palette declares that 'Body1+' is applied.
I don't import Word docs here, but upon doing so, if
PageStream has created a bunch of new 'styles' from the
Word document -- I haven't the slightest as to whether or
not it does this -- then I suspect it would be best to get
rid of those and apply your own styles.
Hope I have not misled you because I refer to an Amiga
version.
Cheers Don (Green Dragon)
--
__._,_.___
.
__,_._,___
|
[1-7]
|
|