Rt3, losing fixed-font formatting in ticket display

Tickets with content that depends on fixed-width displays get munged in
rt3’s ticket history. Tabs and the like get lost.

I changed webrt.css to include Courier:

SPAN.message {
font-size: 100%;
font-family: Courier, Verdana, Arial, Helvetica, sans-serif;
}

but I’m left with a Courier font with proportional spacing. What’s the
right way to do this?

matthew zeier | “Nothing in life is to be feared.
InteleNet Communications, Inc. | It is only to be understood.”
(949) 784-7904 | - Marie Curie

Tickets with content that depends on fixed-width displays get munged in
rt3’s ticket history. Tabs and the like get lost.

I changed webrt.css to include Courier:

SPAN.message {
font-size: 100%;
font-family: Courier, Verdana, Arial, Helvetica, sans-serif;
}

but I’m left with a Courier font with proportional spacing. What’s the
right way to do this?

sans-serif is proportional, try something like “font-family: Courier,
monospace;”.

cheers
Aurel

SPAN.message {
font-size: 100%;
font-family: Courier, Verdana, Arial, Helvetica, sans-serif;
}

but I’m left with a Courier font with proportional spacing. What’s the
right way to do this?

sans-serif is proportional, try something like “font-family: Courier,
monospace;”.

Thanks, tried that, however, I still lose the fixed spacing.

SPAN.message {
font-size: 100%;
font-family: “Courier New”, Courier, monospace;
}

However, the ticket content shows with proportional spacing (still). If I
reply/comment to a ticket item, the quoted text shows the monospaced content
(it’s an ASCII network diagram).

The only way to properly view this is to reply to a ticket which is a less
than ideal way to read these things.

What other nugget am I missing?

However, the ticket content shows with proportional spacing (still). If I
reply/comment to a ticket item, the quoted text shows the monospaced content
(it’s an ASCII network diagram).

The “download” link should display it correctly as well.

The only way to properly view this is to reply to a ticket which is a less
than ideal way to read these things.

What other nugget am I missing?

HTML clobbers whitespace unless text is enclosed in a “

” block.


rt-users mailing list
rt-users@lists.bestpractical.com
The rt-users Archives

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.

Jesse Vincent wrote:

However, the ticket content shows with proportional spacing (still). If I
reply/comment to a ticket item, the quoted text shows the monospaced content
(it’s an ASCII network diagram).

The “download” link should display it correctly as well.

The only way to properly view this is to reply to a ticket which is a less
than ideal way to read these things.

What other nugget am I missing?

HTML clobbers whitespace unless text is enclosed in a “

” block.

I’ve been trying this but it’s not clear how you use a

 tag here.
I’ve got the output of a web form being directed to RT via email and I’d
like to retain the spacing in the ASCII text e.g.

Site Details

Contact person on site: Wylee Coyote
Telephone No: 4564564564
Email: wc@acme.org
Building Name: sdff
Floor No: hkjjh
Street No & name: hjk
City: Smallville

vs

Site Details

Contact person on site: Wylee Coyote
Telephone No: 4564564564
Email: wc@acme.org
Building Name: sdff
Floor No: hkjjh
Street No & name: hjk
City: Smallville

I’ve tried the suggested changed to fixed font and that works fine but
the white space gets squeezed.

The only way to properly view this is to reply to a ticket which is a
less

than ideal way to read these things.

What other nugget am I missing?

HTML clobbers whitespace unless text is enclosed in a “

” block.

I’ve been trying this but it’s not clear how you use a

 tag here.
I’ve got the output of a web form being directed to RT via email and I’d
like to retain the spacing in the ASCII text e.g.

I gave up this since the download link does what I want.

Look at Ticket/Elements/ShowTransactions and search for ShowMessageStanza.
Wrap that in

 tags if you want.

% } else {

<& ShowMessageStanza, Depth => 0, Message => $quoted, Transaction =>
$Transaction &>

% }

That’s essentially want I did for ShowMessageHeaders since

 was
insanely wrapping and worked just fine for me.