Wp2Html News on 13th Mar 1998 Here are the release note for Version 2.6c. As always all versions I am able to build myself, that is DOS, Aix, Solaris are made available at the same time. Sources are also available for the other platforms. This message goes to all users who are registered for the DOS program. Unix users will receive an additional short message giving them the location of the new program binaries for their platform. NOTE! If you are a REGISTERED Unix user and DO NOT receive the Unix news item (shortly after this message), please Email me to tell me so I can be sure I have missed no one. Wp2Html version 2.6c ===================== This is only a minor version release, not a full major change. It implements a number of extra features requested by users. I am still working on the Windows version, but have decided to implement extra user convenience features rather than just put out a windows "wrapper", as this appeared to be the major need of those users I spoke to. Version 2.6c Release Notes, March 98 ================================== Corrections and Bugs -------------------- Some (corrupt) WP files try and use a font which has not been defined. This can cause a core dump on some systems (notably Solaris). Fixed. Comments (that is WP comments) defined INSIDE Footnotes, can give problems This can manifest as some footnotes appearing blank. Fixed. Hypertext Index all wrong! Do not know why this has not been reported, but recent versions had an incorrect ndx2html program. Would result in failed Index file. Have a look at the manual converted to HTML where the hypertext index is referenced at the top. Now Fixed. Also some OSes had a problem with freeing some memory during creation of the Index file name. Fixed. DOS version only. Some %X<> and %=<> tags do not work. This was a problem with a pointer which was defined without the _far modifier. This affects the DOS version only, but would cause some tag lookups to fail. Now Fixed. If you use the DOS version and also make use of either %X<> or %=<> you should upgrade. New Features ============ GraphicsNames to set part format for graphics --------------------------------------------- When graphics images are extracted from the WP file and written to file they previously used a defined format, with the file type acting as an image number. For instance a WP file test.wp would result in files called test.f0 and test.f1 etc for the WPG image, and if you were running on UNIX and used the WPG2GIF convertor, the resulting GIF file were called test.g0 and test.g1. Some Web servers were confused by the fact that the GIF iamges were called .g0 rather than .gif. Also, the name length restrictions which required the use of the suffix as a part number do not apply on UNIX, where most graphic image manipulation occurs, or on 95 or NT. Therefore, I have changed the DEFAULT image file format, so that files are created with the form test_1.wpg and test_1.gif etc. This will work better on most systems. However, if you wish or need to change this a new tag called GraphicsNames allows this. Thia tag is defined in the new .cfg file but commented out as below. # Define GraphicNames to change the format for Graphics Images # The name is made up from the Root file name and image number, # via this C format #!GraphicsNames="%s_%d" You can use this to make the image names whatever you like. Note that the files will have the .wpg and .gif added to this name. I also find that when using thumbnail images which expand when clicked it works better to make the full size image appear in a separate window. See the example in the wp2html.cfg file for details. (Note the wpg2gif program can be used to create the small thumbnails while it is converting the WPG image to GIF if the -t option is used.) Uppercase style names --------------------- Some users who wish to define special handling of WP styles have a problem with the CASE of the style names. Specifically, if one WP doc has a style called Head1 and another has head1 or HEAD1, they are considered different. If you wish to prevent this, I have defined a new tag UpperStyle. You use this by inserting UpperStyle="yes" in your .cfy file. Then you define all of your style names in UPPERCASE. ie you may have HEAD1On="..." HEAD1OnEnd="..." etc Then any style found in the WP doc will be made uppercase before triggering on the defined style name. Note that only the style name is upper case, the ending, On, OnEnd etc remain case sensitive. Paragraph Numbering ------------------- Previous releases generated paragraph numbers in the default "legal" style. That is 1.1 1.1.2 etc Regardless of whether the WP doc has defined a different style. Now paragraph number will respect the WP doc setting, so you will see numbers like IV.A.1.a.ii if appropriate. Multicolumn format ------------------ Previously, I used the tag to handle multicolumn layout. This caused a few problems even using Netscape, especially as there was no way to cause a column break, that is Netscape decided how to "balance" the columns on screen, and this was often quite different to both the original document and the meaning. was also a Netscape extension, and is not respected by Internet Explorer 3 and many others. Therefore I have dropped this method of defining columns and now use tables with no borders. The results work in all browsers and look better. This required a change to the way the Column tag was handled, and a change to the wp2html.cfg file. Therefore from this release you will need to either use the supplied wp2html.cfg file, or modify your own to change the definition. Two exiting tags are affected and one new one added. # Column is passed the percentage width of the column Column="\n
\n" column="\n
\n" # New tag to define column break EoC="\n\n" Andrew ----------- ----------------------------------------------------------------------- Andrew Scriven andrew@brackenb.demon.co.uk "Brackenbeds", Lockeridge, Wiltshire, SN8 4ED, UK Phone (44) 1793 896206, Fax (44) 1793 896251 -----------------------------------------------------------------------