At 10:00 PM 2/24/00 +1100, Terry Collins wrote:
>Does anyone have a url for Framemaker for Linux that can be
>downloaded?
>
>Twice I have received emails telling me about downloading it and both
>times the down load goes for hours with zilch downloaded.


Funny you should mention that...;-)

Just received this;

This email is being sent to registered users of FrameMaker on Linux. The
second beta release is now available through Adobe.com at:

     http://www.adobe.com/products/framemaker/fmlinux.html

Release notes are included below, and are also available from the above
page. You can install the beta 2 product over your existing installation,
though you should create a back-up beforehand in case anything goes wrong.
The Online Manuals, Help, and Dictionaries have not changed.

Thanks for your time in testing and using FrameMaker on Linux. We've
received excellent feedback about the environments and requirements
you have for FrameMaker, and have made changes for the most pressing
items in this release. As before, please continue sending comments to
our feedback address:

     mailto:[EMAIL PROTECTED]

If you no longer wish to participate in the FrameMaker Linux beta
program, please send email to [EMAIL PROTECTED] with the word REMOVE in
the subject line, and we'll remove you from future mailings. If you do
so, I'd appreciate it if you would add a line or two to the body of the
email describing why you wish to be removed.

Thanks again!

Lee Richardson
FrameMaker Development Manager
_________________________________________________

RELEASE NOTES FOR BETA 2

(1) FrameMaker and support binaries built appropriately for all
     glibc 2.0.7 distributions, including Red Hat 5.2, Debian 2.0
     and 2.1, and Corel Linux. All run-time linking errors should
     be resolved.

     Technical details: definitions for "__register_frame_info"
     and other related gcc internal symbols are now linked directly
     into the binaries.

(2) FrameMaker now successfully runs in demonstration mode if there is
     no portmap/rpcbind service running locally, rather than hanging or
     crashing.

     Note that in addition to licensing, some extended functionality
     depends directly on portmap service, including RPC API client
     support, fmbatch, and FrameServer.

     There may be a few remaining problems with the portmapper and
     licensing that will continue to cause problems for some users.
     These will be addressed in a later release.

(3) FrameMaker no longer crashes at startup when run on 16-bit color
     X servers. 16-bit servers are not fully supported, however. A
     warning message is printed at startup, and most imported bitmap
     graphics will not display, appearing as grey boxes instead. This
     includes graphics in online Help and documentation files, as well
     as elements of the Quick Access bars and other UI components.

(4) The Xlib interface libraries are now linked dynamically. This
     should provide greater compatibility with Linux X servers.

     In particular, the product will now convert fontsets at startup
     properly, rather than displaying error messages.

(5) FrameMaker printing now works properly in European locales where
     the numeric decimal point is a comma (','). Numbers were not being
     formatted correctly in FrameMaker's internal printer output language.

(6) A related problem involving corruption of FrameMath equations in
     FrameMaker files saved while running in certain locales has
     been fixed. Unfortunately, there is no way for users to retrieve
     data already lost in this fashion, unless the documents in question
     are in MIF format.

(7) Linux FrameMaker will now take advantage of Display PostScript when
     displayed to an X server with DPS extensions installed. In the
     first release, this would typically result in FrameMaker hanging.

     This Display PostScript support has only been tested against
     Adobe Display PostScript running in the CDE environment.

(8) The 'fmusersetup' script was modifying user PATH settings incorrectly
     in $HOME/.profile files when run. This has been fixed.

     In general, it is not necessary to run 'fmusersetup' or modify
     PATH settings in order to run FrameMaker. Simply running the
     "$FMHOME/bin/maker" startup script will initialize the product
     correctly, if the product has been installed correctly.

(9) Additional error reporting has been inserted for users having
     trouble getting the product licensed. Run "maker -nlverbose" for
     explanatory console output.


--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text

Reply via email to