On 15.06.2005 21:32:21 Andreas L. Delmelle wrote:
-Original Message-
From: Jeremias Maerki [mailto:[EMAIL PROTECTED]
Hi Jeremias,
Do you, by chance, intend to visit ApacheCon in Stuttgart in July?
(I take this 'you' to be plural)
Sure, this is addressed to every FOP
Hi All,
Just to throw in my 2 cents. Batik Handles this through the
@font-face CSS property. This allows you to provide a mapping
from a CSS font-family (with weight etc) to a font file on disk/network
etc:
@font-face { font-family: CSS Batik SVGFont;
src:
Andreas L. Delmelle wrote:
-Original Message-
From: Peter B. West [mailto:[EMAIL PROTECTED]
Hi Peter,
..., and Jenni and I are moving to the UK for 12
months at the end of June, ...
Well, if you have plans to cross the channel and visit Belgium during those
12 months, be sure
Jeremias Maerki wrote:
Do you, by chance, intend to visit ApacheCon in Stuttgart in July?
It's relatively expensive, isn't it? I don't know what I will be doing
at any particular time. It depends on what work is available to me.
If you come to Switzerland, tell me!
I certainly will.
Victor,
I know you intended that. But use and further develop are two
different things. What I was getting at with the license grant thing is
the possibility to take your font code and put it FOP code repository
(or better XML Graphics Commons when it finally pops into existence,
still in the
Jeremias Maerki wrote:
Just to be clear, these are the possibilities:
1. FOP uses FOray-Font (JAR file in lib directory), no
license grant necessary, no FOray sources in an ASF repository.
This is my preference.
2. FOP forks FOray-Font, license grants are necessary due to
ASF policy.
I
Jeremias Maerki wrote:
Ideally, a font engine that is shared between two projects should be in
a more or less neutral place write-accessible by both parties but as
we've seen now there are personal dissonances.
I think Victor said he didn't want to collaborate anymore:
Jeremias Maerki wrote:
To state my opinion on this matter:
I would like to see Vincent integrating FOray-Font into FOP.
There has been some work on fonts compared to the FOP
maintenance branch but Victor has invested more time in
FOray-Font. Victor's font subsystem is now technically more
Jeremias Maerki wrote:
To state my opinion on this matter:
I would like to see Vincent integrating FOray-Font into FOP.
There has been some work on fonts compared to the FOP
maintenance branch but Victor has invested more time in
FOray-Font. Victor's font subsystem is now technically more
Glen Mazza wrote:
I think Victor said he didn't want to collaborate anymore:
http://marc.theaimsgroup.com/?l=fop-devm=111263144615399w=2
http://marc.theaimsgroup.com/?l=fop-devm=111265443425492w=2
Even those on this list who are not native English speakers will be able to
easily understand
Glen Mazza wrote:
I think Victor said he didn't want to collaborate anymore:
http://marc.theaimsgroup.com/?l=fop-devm=111263144615399w=2
http://marc.theaimsgroup.com/?l=fop-devm=111265443425492w=2
Even those on this list who are not native English speakers will be able to
easily understand
Thanks, Glen, for your statement earlier. And I apologize for jumping to
early conclusions about your expected behaviour. I've been burnt a few
times so I get jumpy.
Victor, your offer for write access on FOray for qualified developers is
greatly appreciated and does away with some of my fears
Jeremias Maerki wrote:
The logging problem is a minor one. There's a wrapper for JCL
that easily wraps an Avalon Logger [1]. But that's obviously
the exact opposite of what you need. On the other side,
creating an implementation of Avalon's Logger interface that
wraps a JCL logger should
Jeremias Maerki wrote:
Ok, but this assumes that you work in concert with AWT's font
subsystem.
If we talk about the font subsystem for PDF and PS we have
all liberties we want. If we can give the FO processor a
directory and it makes all the fonts in this directory
available for FO
On 14.06.2005 17:29:01 Victor Mote wrote:
Jeremias Maerki wrote:
The logging problem is a minor one. There's a wrapper for JCL
that easily wraps an Avalon Logger [1]. But that's obviously
the exact opposite of what you need. On the other side,
creating an implementation of Avalon's
On 14.06.2005 17:59:03 Victor Mote wrote:
Jeremias Maerki wrote:
Ok, but this assumes that you work in concert with AWT's font
subsystem.
If we talk about the font subsystem for PDF and PS we have
all liberties we want. If we can give the FO processor a
directory and it makes all
Jeremias Maerki wrote:
Most people will want to point the auto-registration to
C:\WINDOWS\FONTS.
Mine has 581 files in it, each of which would have to be opened and
partially parsed. I actually use no more than 10-15 for FO work. I
think this might actually open up a bunch of
On 14.06.2005 23:27:44 J.Pietschmann wrote:
Jeremias Maerki wrote:
Relying on static
variables in the case of logging is not necessarily bad.
*cough* This depends on whether a single logger for all threads
is not necessarily bad. I personally would probably prefer the
possibility to
Victor Mote wrote:
Jeremias Maerki wrote:
Just to be clear, these are the possibilities:
1. FOP uses FOray-Font (JAR file in lib directory), no
license grant necessary, no FOray sources in an ASF repository.
This is my preference.
2. FOP forks FOray-Font, license grants are necessary
Jeremias Maerki wrote:
On 14.06.2005 17:59:03 Victor Mote wrote:
That whole idea deserves more thought and experimentation,
and I haven't had time to work on the font system since October.
Victor, I have been experiencing similar frustrations, and Jenni and I
are moving to the UK for 12
J.Pietschmann wrote:
Jeremias Maerki wrote:
Ok, but this assumes that you work in concert with AWT's font subsystem.
Well, AWT doesn't provide a way to get the file for a font, but
we can at least get an AWT Font from a TTF file.
And a Type1 file (Java 5). Java just keeps getting better.
J.Pietschmann wrote:
Vincent Hennebert wrote:
I was starting to wonder what I could have done wrong so that things
turn out that way.
Just ignore the bickering for now. There seems to be a law that every
Open Source project (or any other reasonably open project for that
matter) sooner or
Let's not even start discussing the intellectual property implications that are
starting to surface...
From: Peter B. West [mailto:[EMAIL PROTECTED]
Sent: Tue 6/14/2005 9:22 PM
To: fop-dev@xmlgraphics.apache.org
Subject: Re: Foray's font subsystem for Fop
Hi Fop Team and Victor,
I'm considering to adapt Foray's font subsystem to Fop. I have already
experimented a bit and the thing seems to be rather feasible. So far I have
encountered two problems:
- logging mechanism: Foray uses the avalon framework while Fop uses commons
logging. The 2
24 matches
Mail list logo