Wes Plate wrote:
On 9/10/04 12:24 AM, "Robert L Mathews" wrote:
Sorry for the delay in submitting it; perhaps it's trivial enough (and
fixes a large enough bug) that it can make it into OTRS 1.3.
Please! :-)
I just looked into CVS and it seems like the fix didn't make it into
1.3.1. Any predic
Robert L Mathews wrote:
Is there any reason against wrap=soft in the input field? As I see it,
this would fix the problem.
Hmmm. I was the one who suggested the new line wrap algorithm (it was
discussed on dev list), but I think I must not have made that part clear:
the algorithm can only work w
r of the input field doesn't mean that
it's content is wrapped at this width, it just specifies the display
width. I'm not sure if any other browsers do the same.
Frederik
Martin Edenhofer wrote:
On Tue, Aug 31, 2004 at 02:59:02PM +0200, Frederik Seiffert wrote:
Yes, that was me. Unfort
Yes, that was me. Unfortunately, while the incoming message looks just
fine, the reply sent with OTRS still looks awful. Have a look at the
first and third external agent email.
Is there any reason against wrap=soft in the input field? As I see it,
this would fix the problem.
Thanks,
Frederik
Hi!
We're using OTRS 1.2 and noticed that the emails always look pretty ugly
as the lines are not correctly wrapped. For example, the following
should be one single paragraph. However, the email would look something
like this:
Text text text text text text. Text text text text text text text te
Hi Martin,
Martin Edenhofer wrote:
Hi Frederik,
On Tue, Jul 27, 2004 at 01:31:28AM +0200, Frederik Seiffert wrote:
We're currently using the DateChecksum module to generate ticket
numbers, but I always felt that the numbers are way too long. As I don't
see any reason for the date or th
've attached my module in case anyone finds it interesting. Feel free
to use it.
Thanks,
Frederik
# --
# Ticket/Number/RandomHex.pm - a ticket number random hex generator
# Copyright (C) 2004 Frederik Seiffert <[EMAIL PROTECTED]>
# --
# $Id: $
# --
# This software comes with ABSOLUTELY NO
