| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
My customer says:
(Now, I am not saying I don't believe him, but does anyone have more
information!)....
He has various Printer Tables he used with ALL-IN-1 V2.4. Now he is
testing his applications with V3.0, and he says "They don't work".
To be more precise:
In V2.4 users put PRINTER TABLE LANDSCAPE or PRINTER TABLE 10_PITCH or
PRINTER TABLE 12_PITCH type of control block commands into their
WPS-PLUS documents. With V3.0 these are ignored.
"OK", says I, "Did you put modify the new tables with your required
changes?". The customer says "Yes", BUT the PRINTER TABLE WHATEVER bit
is still ignored.
If they use PRINTER FORMAT LANDSCAPE etc - no problems. But, PRINTER
TABLE LANDSCAPE gives problems.
Is this likely??
If so is there a workaround??
If there is, what happens when one node is at V3 (using the workaround,
or new training etc) while other nodes are still at V2.4 and sending
documents to the V3 system??
Sorry about the ill-defined problem statement - but this is a manager
telling me what his techy told him...
ALSO.... If the users now need to enter HORIZONTAL_PITCH 12 or whatever
to set the correct pitch (as per the manuals in ALL-IN-1 V3...) what
happens when these documents are sent to a V2.4 system?
Presumably that ignores the HORIZONTAL_PITCH<space> type of commands...
and so two control blocks are needed in the document :- one so it
prints correctly on V3, and another so it prints correctly if sent to a
V2.4 system.....
Cheers, Chris
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1419.1 | Ask in WPS-PLUS conference | IOSG::NEWLAND | Richard Newland, IOSG, REO1-D/4A | Tue Sep 15 1992 17:36 | 11 |
I suggest that you ask in the WPS-PLUS conference because you are describing changes in WPS-PLUS Printer Tables which are created for and used only by the WPS-PLUS Formatter. I have seen other reports of PRINTER TABLE control blocks not working or not being compatible from WPS-PLUS V3.1 (the version in ALL-IN-1 V2.4) to WPS-PLUS V4.1 (the version in ALL-IN-1 V3.0). Richard | |||||
| 1419.2 | Can you help with co-existance problem? | LARVAE::SHORE | The wonderful thing about tiggers... | Tue Sep 29 1992 16:19 | 23 |
I have now taken on the issue, detailed in .0, for resolution. I have been
discussing this in the WPS-PLUS conference and am now aware of a migration
aid which will convert a WPS-PLUS v3.1 document to v4.1 printer formats,
eliminating the initial problem. This is fine for upgrading a system.
However I am left with a problem which I think may exist on many ALL-IN-1
sites. When planning the ALL-IN-1 v3.0 upgrade the customer will be
migrating some sites before other. v3.0 and v2.4 will co-exist within the
customer site for a number of months.
As the WPS-PLUS priter format commands have changed I need to convert
documents as they go between v3.0 and v2.4 and vica verca. I was thinking
of having an option on the v3.0 EM menu which could be called if printing
a v2.4 document. This would call the WPS-PLUS migration aid. An
alternitive was to convert all mail attachments as they come into the v3.0
system. As for documents going from v3.0 to v2.4 well I'm not sure what to
do here, as I do not know of a convertion aid which goes the other way,
i.e. WPS-PLUS v4.1 to v3.1.
I'm not sure which is the best way to jump here. The customer is asking
for a "Digital recommendation" on how to live in this co-existing world.
Can anyone offer me any advice or ideas?
Yours greatfully, Angela
| |||||