>Yes, we did! :)
>It was fixed in FOP /Trunk/ (= fix will be in the next release)
>0.93 won't be patched, that much is true...

>If you really, really need this feature, then you're welcome to  
>checkout the source w/ Subversion and build-it-yourself.


>Later,

>Andreas

Andreas,

I don't doubt that you, the FOP developers, are a group of good software
professionals and a bunch of nice peaple. But the way you handle FOP as a
product development project and relate to the user's of FOP is downright
amateurish. And for me irritating, too.

Let me take your answer:

I wonder, how should I have known about the fix. I specifically looked a the
answers to my error report before I sent my reply and had not found any
indication of it there.

As a user I am equiped with the necessary environment to keep the softwares
I am routinely using current. In this case using toroiseSVN I have checked
out the complete FOP trunk just to find that, just as you suggest, if I want
to use it I should build it myself. I didn't. (To state it slightly I wasn't
in the right mood.) [In fact I had already installed a different workaround
before I submitted the bug report.]

On the FOP Download page I found this:

"Fixme (jeremias)
Reenable the link to the SVN snapshots once they are available."

Now, what the heck it's supposed to mean?!. Can you tell me a valid reason
why there are no daily (or at least weekly) snapshot builds of the trunk
available at least on the main FOP server? 

Anyway, why should I be at the bleeding edge with FOP Trunk if I only need a
small, safe and fully tested fix in the 0.93 branch that I can easily update
if there is a new build available.

And finally knowing the history of FOP your mentioning of a new release is
not too promising either.

Please, do no take all this as an offence I have not meant it to be.

Joe


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-- 
View this message in context: 
http://www.nabble.com/font-family%3D%22Arial-Unicode-MS%22-in-rtf-doesn%27t-work-tf3177039.html#a9070526
Sent from the FOP - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to