[crossfire] msg/endmsg in maps/objects

[Kevin R. Bulgrien]

Mark Wedel wrote:

> Kevin R. Bulgrien wrote:
>> Mark Wedel wrote:
>>> Ideally, I think most of the newlines from the msg/endmsg structures
>>> should be
>>> removed - the client is plenty smart enough to do proper wrapping. 
>>> There are also a few messages which should have the '[fixed]' tag added,
>>> since they are maps or diagrams, and just don't look right when printed
>>> with the proportional font.

BTW, not sure what "proper wrapping" means.  In gcfclient, it mercilessly
chops the text to fit the window.  Word boundaries are not honored.

>> How about blank lines?  Is this discouraged in order to consume less
>> vertical space, or is it seen to be acceptable for improving readability
>> for longer multi-paragraph output?
> 
>   I'd say they should be there for readability.  Without a blank line, it
>   can be very difficult to really see where the paragraph breaks are.
> 
>   In addition, this really only comes up with NPC messages - generally,
>   I'd say those are a relatively small portion of the total text output
>   (things like attack messages being much more prevalant), and I can't
>   imagine a couple extra newlines being that big a deal.

It turns out, blank lines are stripped.  I don't know how to add blank
lines.  This is can be problematic when you use split windows because, for
example, if you walk down the main drag in scorn reading all the signs, all
the output is just strung in sequence with no separation between signs or
headings.  It is pretty hard to scroll back and see what happened, and,
it is hard for any given message to be well formatted so that paragraphs
are separated nicely.

Does anyone know how to output a blank line in message text?  I tried
\n, but it does not seem to work.

Kevin