bug-gnats
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gnatsweb/306: Gnatsweb fails to handle pipe symbols in query results


From: Michael Richardson
Subject: Re: gnatsweb/306: Gnatsweb fails to handle pipe symbols in query results
Date: Sun, 02 Dec 2001 20:34:01 -0500

>>>>> "Yngve" == Yngve Svendsen <yngve.svendsen@clustra.com> writes:
    Yngve> At 16:46 02.12.2001 -0500, Michael Richardson wrote:

    >> >>>>> "yngve" == yngve svendsen <yngve.svendsen@clustra.com> writes:
    yngve> See if GNATS qfmt accepts non-printable characters, if so use
    yngve> one. If not, use a more exotic field separator than '|'.
    >> 
    >> This is really not a useful way to do fix this.
    >> All interfaces to gnatsd will have this problem.
    >> Rather, we need a way in Gnats to have it escape the field seperators.

    Yngve> Since basically any character(s) can be specified in the qfmt 
string, I am 
    Yngve> not certain that that is really necessary. I solved this problem

  It is.

  Octal 037 is not illegal in email. Consider that some MS-looser will likely 
send email with character 237 in it (upper bit set) that will get its upper
bit set.

  Instead of providing a format string with %s and the field seperator, why
not specify the field seperator to gnatsd in the query definition, and then
the list of fields to return. Gnatsd can then escape any occurances of the
field seperator.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]