T.R | Title | User | Personal Name | Date | Lines |
---|
2937.2 | your options are: | AIMTEC::WICKS_A | U.S.A 2 England 0 - I was there! | Thu Jul 01 1993 18:10 | 9 |
| Louis,
remember this is an unofficial support channel. since this appears to
be a WPS-PLUS related question you could ask in their notes file. For
an official answer you submit SPRs.
Regards,
Andrew.D.Wicks
|
2937.3 | hmmm | SOS6::PROT | | Thu Jul 01 1993 18:45 | 8 |
|
Yes I know that it isn't an official support channel nevertheless
someone (especially in eng) could know a special attribute or
undocumented feature which could help me.
Maybe my question wasn't right clear.
Louis
|
2937.4 | A restriction | IOSG::NEWLAND | Richard Newland, IOSG, REO2-G/L2 | Mon Jul 05 1993 23:25 | 23 |
| I've looked at the TEXT_FILE code and this is a limitation. The SET
TEXT_ATTRIBUTES sets each character attribute from the info-symbol value,
and there is not an attribute letter for the combination of attributes you
want (Bold and Superscript).
It is probably not practicable to create more 'attribute letters' for all
possible combinations of attributes. Therefore removing this limitation
would require some way of calling SET TEXT_ATTRIBUTES multiple times to set
multiple attributes. For example, add a /MORE qualifier which would add
the specified attributes to the current attributes.
Supporting all possible combinations of attributes with a RETURN
TEXT_ATTRIBUTES is harder. One idea I have is to allow TEXT_ATTRIBUTE to
accept an optional qualifer (e.g. /BOLD, /UNDERLINE, /SUPERSCRIPT) so that
it returns only the attribute information requested. Only one qualifier
would be allowed with each call.
Any alternative ideas on how to extend SET and RETURN TEXT_ATTRIBUTES are
most welcome.
Richard
|
2937.5 | ENHANCE TEXT_FILE functions! | SUOSWS::HAMANN | | Tue Jul 06 1993 12:03 | 31 |
| Hi Richard,
I had some similar problems using the TEXT_FILE functions.
My problem was to convert an OfficeVision document to WPS+, and
I could have done better if the TEXT_FILE functions had been
less restrictive.
So I would back some sort of enhancment.
I would not suggest to change the current
TEXT_FILE RETURN TEXT_ATTRIBUTES id returnsymbol -functions
but to provide an additional enhanced function, something like
TEXT_FILE RETURN ALL_TEXT_ATTRIBUTES id symbol1 symbol2
and bitencode the attributes in the symbols. To avoid control
characters you might want to use only 6 bits/characters.
The attribute 'special' should be expanded a bit more.
Similary a
TEXT_FILE SET ALL_TEXT_ATTRIBUTES id symbol1 symbol2
function could be provided.
I hope some enhancement will be made available
Klaus Hamann
|
2937.6 | opinion. | PRSSOS::PROT | | Thu Jul 15 1993 13:11 | 6 |
| I agree with the last suggestion , a bit mask for all the current
attributes could be powerfull to modify and set.
But the .4 suggestion /MORE could also be easy to use.
Louis
|