| Some valid points Jane,
I'd simply like to know what is the position regarding the license
for LN03 fonts ?
Is it true that the site has one license which allows for the fonts
to be available from CURRNT, but not any other nodes ?
What is the position regarding getting more licenses, perhaps ?
Regards,
Rob
|
| > 1. The size of the print has changed (larger) this means that
> existing documents have to be re-worked to ensure sensible
> page breaks.
This is documented in the release notes. It only affects the
postscript output though to bring it into line with the LN03
fonts, personally I prefer the new fonts.
> 2. The tag combination of <FIGURE> and <LINE_ART> no longer works
> the <LINE_ART> tag has to have a minimum of the (KEEP) option,
> which used to be optional, and still is according to the
> documentation.
I've just compiled a document on CURRNT with this combination
I've not had any errors generated, must be your figures ;-)
> 4. The final extension for postscript output has been changed from
> .POST to .PS, which makes life confusing as the inclusion figure
> files have the extension of .PS
I've seen this documented somewhere, perhaps in the document
conference, surely its only an irritant at first and you'll
soon get used to it ;-)
P.S. V1.1 now supports /OUTPUT qualifier, you could always
use that to override e.g. /OUTPUT=JANE.POST
> Please can we have V1.0 back on CURRNT until we can have a version
> of document that causes fewer problems, either that or put the
> licence for the LN03 device conversion software onto the FUTURS
> cluster.
As I remember Document V1.1 contains many enhancements
and I've seen a statement somewhere from the DOCUMENT group
that says that some documents may need to be reworked or something.
In summary you've got to live with the product as it is and
its highly unlikely that the next release of DOCUMENT is going
undo all their efforts just to please you. I say we keep V1.1
CURRNT and also upgrade on FUTURS so that all documentation
produced is consistant on this site.
There is something to be said for having a second LN03 license
on FUTURS though.
Danish.
|
| >> 1. The size of the print has changed (larger) this means that
>> existing documents have to be re-worked to ensure sensible
>> page breaks.
> This is documented in the release notes. It only affects the
> postscript output though to bring it into line with the LN03
> fonts, personally I prefer the new fonts.
I'm sorry to dispute this statement but the font type when using the
combination of REPORT Doctype and LN03 output has got much bigger, it used
to be the same size as the old LPS40 font.
>> 2. The tag combination of <FIGURE> and <LINE_ART> no longer works
>> the <LINE_ART> tag has to have a minimum of the (KEEP) option,
>> which used to be optional, and still is according to the
>> documentation.
> I've just compiled a document on CURRNT with this combination
> I've not had any errors generated, must be your figures ;-)
Nope, it's :-
<FIGURE>
<FIGURE_ATTRIBUTES>(WIDE)
<LINE_ART>
lots of lovely text for several lines at least 80 characters wide...
<ENDLINE_ART>
<ENDFIGURE>
that doesn't work. There was no problem with V1.0
> P.S. V1.1 now supports /OUTPUT qualifier, you could always
> use that to override e.g. /OUTPUT=JANE.POST
Thanks for that tip.
> In summary you've got to live with the product as it is and
> its highly unlikely that the next release of DOCUMENT is going
> undo all their efforts just to please you. I say we keep V1.1
> CURRNT and also upgrade on FUTURS so that all documentation
> produced is consistant on this site.
I haven't stated that I want the efforts undone, I like the idea of most of
the enhancements, it's just that I wish that so much of my time wasn't spent
compensating for enhancements that don't work properly !
The POSTSCRIPT handling of <FIGURE> screens is definitely unacceptable so it
would be VERY unwise to loose all versions of V1.0 available to us.
Jane.
|