József Németh wrote:
snip/
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,
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.
It seems most of the
Anderas, Chris,
Well Gentlemen, why should I say? Maybe this.
What I have said was not unfair not even impolite, maybe a little coarse and
certainly true. The fact is that I had been acting on the false assumption
that the goal of the FOP project was to develop a product. Now from what you
say
Jeff,
I've just took leave of FOP for good (see somewhere up in the thread), but
what you say preserves a quick answer.
There is no mistake, I am on the proper list: regarding FOP I wanted to be a
user. Besides you have probably saw up in this thread what led to this
exchange. There is,
On Feb 21, 2007, at 14:37, Jeff Vannest wrote:
Hi Jeff,
I promised myself to ignore whatever spawned from the remainders of
this thread, but decided to peek anyway, and I'm glad to have
stumbled on this one:
snip /
... we're not nice people; or rather, it's irrelevant whether we are.
-Message d'origine-
De : Daniel Noll [mailto:[EMAIL PROTECTED]
Envoyé : mardi 20 février 2007 01:23
József Németh wrote:
Excuse the buttler butting in but what the spec says is:
Font family
names containing whitespace should be quoted. If quoting is
omitted,
any
On Feb 20, 2007, at 12:01, József Németh wrote:
No, they didn't!
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
Yes, we did! :)
It was fixed in FOP /Trunk/ (= fix will be in the next release)
Excellent! This means that my Altova StyleVision should work either way with
the new rev.
Is there a way to know when the next rev will be released?
Jeff
On Feb 20, 2007, at 19:49, Jeff Vannest wrote:
Yes, we did! :)
It was fixed in FOP /Trunk/ (= fix will be in the next release)
Excellent! This means that my Altova StyleVision should work either
way with
the new rev.
Indeed.
Is there a way to know when the next rev will be released?
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
On Feb 20, 2007, at 22:16, József Németh wrote:
Hey Joe,
Let me start off by saying that I was very tempted to let your
posting pass and not give you any more attention, but I just couldn't
help myself, so here we go...
I don't doubt that you, the FOP developers, are a group of good
But at the same time, the spec does say it SHOULD be quoted, so you
should quote it.
Excuse the buttler butting in but what the spec says is: Font family names
containing whitespace should be quoted. If quoting is omitted, any
whitespace characters before and after the font name are ignored
József Németh wrote:
Excuse the buttler butting in but what the spec says is: Font family names
containing whitespace should be quoted. If quoting is omitted, any
whitespace characters before and after the font name are ignored and any
sequence of whitespace characters inside the font name is
13 matches
Mail list logo
