Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] faxcover commentsX
Lee Howard wrote:
> At 06:54 PM 12/25/00 +0300, Vyacheslav Frolov wrote:
> >
> >
> >Lee Howard wrote:
> >
> >> Can anyone confirm that the faxcover 'commentsX' symbols/parameters
> >> function properly? Or rather, can anyone confirm that they *don't*
> >> function properly? I'm having extreme trouble implementing the usage of
> >> 'commentsX'...
> >
> >faxcover splits text at '\n' chars into CommentX, where X is
> [1-9\:\;\<\=\>\?\@A-D].
>
> (I'm asking this for a matter of documentation correction if correct...) Do
> you mean to say that the following paragraph from the faxcover manpage:
>
> If the comments string is longer than 35 characters, it is
> broken, on word boundaries, into multiple POSTSCRIPT
> strings commentsX where X is the line number; e.g. com
> ments2 for the second line of comments. By default fax
> cover will generate 20 commentsX strings, emitting null
> string values for empty lines. This number can be changed
> with the -m option; see below.
>
> is incorrect in that first, the variable name is "CommentX" rather than
> "commentsX" (capitalized and missing the s), and that the comments string
> is *not* broken on word boundaries as explained, but rather as you have
> described?
Yes, it is. And "X is the line number" is incorrect too.
I can fix that but it seems that that logic is not very useful because it can be used
with fixed fonts only and there is BreakIntoLines that is better.
Vyacheslav..
____________________ HylaFAX(tm) Users Mailing List _______________________
To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null