> -----Original Message----- > From: Robert P. J. Day [mailto:[EMAIL PROTECTED] > > On Mon, 20 Oct 2003, J.Pietschmann wrote: > > > > I can't confirm it, but surely there is *no* fix. > > i'm not sure what you mean by "surely". recall that this is the > same problem i mentioned a while back -- in a variable list, i asked <snip/> > > when we had this earlier discussion, i verified that the FO file > did not contain anything that would suggest this kind of break, > so it was pretty clearly FOP that was doing something weird. >
if i'm not mistaken, the reply was <q> according to the code, this shouldn't happen </q> and that the stated problem would be looked at in more detail, if there was the time for it... > so what do you mean by saying that there is surely no fix? > i guess this means that this is not the case. perhaps it got a bit out of focus because no one bothered to enter a bug for it? Greetz, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
