![]() |
Hi Vyacheslav, thanks for your work on this. I haven't tried it yet, so maybe you've already considered this, but if any change is going to be made to the coversheet template in the source, my opinion would be to change it so that *both* 'commentsX' *and* 'CommentX' are accepted as valid. This way we can prevent breaking anyone's coversheet template who may be using either one. I doubt that there's many that use CommentX since it was undocumented and since it took reviewing the postscript code of the template to understand it - it probably won't be an issue if we "change back", but I'd like to prevent any issues if possible. Is this possible? Lee. At 12:44 PM 1/3/01 +0300, Vyacheslav Frolov wrote: >Hi Lee, > >May be it's not very useful (I know you've done new manpage), but I've done new BreakIntoCommentX. >The following BreakIntoCommentX compatible with old manpage. >It creates dictionary as discrabed in the manpage and > - breaks comments on linefeed (\n) > - breaks long words (substrings without space or linefeed) > >It seems that the faxcover's option for changing "35 characters" will be helpful too (/MaxLine 35 >def). > >Regards, >Vyacheslav. ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null