On Jun 24, 2005, at 7:33 AM, Vincent Hennebert wrote:
Hi all...
Sorry to insist, but what is your final decision? A quick summary of the thread gives:
- Jeremias +1
- Simon +1
- Glen +0
- Chris +1 (attached below)
The FOray+aXSL stuff would be used in the form of a jar file put in the lib direct
On Tue, Jun 14, 2005 at 10:33:10AM +0200, Jeremias Maerki wrote:
> > I welcome any additional thoughts/comments. Now starting to work...
>
> I wish you had asked before diving into this. Before FOray-Font can be
> integrated with FOP we need to have a vote on this among the committers
> and frankl
On 16.06.2005 01:53:39 Peter B. West wrote:
> Jeremias Maerki wrote:
> > Do you, by chance, intend to visit ApacheCon in Stuttgart in July?
> >
>
> It's relatively expensive, isn't it?
Yes, that's the catch. Being a speaker it almost costs me nothing. I
disagree with the way this is currently d
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 eve
Andreas L. Delmelle wrote:
Do you, by chance, intend to visit ApacheCon in Stuttgart in July?
(I take this 'you' to be plural)
Me personally, I did intend to visit when I first received word, but
unfortunately I wasn't able to get the necessary time off... A shame though,
so close. :-(
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. T
Thomas DeWeese wrote:
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";
> -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)
Me personally, I did intend to visit when I first received word, but
unfortunately I wasn't able to
Do you, by chance, intend to visit ApacheCon in Stuttgart in July?
If you come to Switzerland, tell me!
On 15.06.2005 18:52:22 Peter B. West wrote:
> Andreas L. Delmelle wrote:
> >>-Original Message-
> >>From: Peter B. West [mailto:[EMAIL PROTECTED]
> >>
> >
> >
> > Hi Peter,
> >
> >
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 to
> -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 to drop me a line. Maybe we
http://java.sun.com/j2se/1.5.0/docs/api/java/awt/Font.html#createFont(int,%20java.io.InputStream)
http://java.sun.com/j2se/1.5.0/docs/api/java/awt/Font.html#TYPE1_FONT
http://java.sun.com/j2se/1.5.0/docs/guide/2d/new_features.html#createFont
Reading what's there I don't have high hopes that you ca
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: url(batik
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 subsyst
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 lat
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.
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 m
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 due
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
> possibilit
On 14.06.2005 23:21:51 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 pro
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 direct logging for different threads into different
des
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 later will get people with
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.
J.Pietschmann
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
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 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
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
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 F
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 F
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 sh
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 sh
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 processing then I am where
I would lik
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 abo
Glen Mazza wrote:
> I think Victor said he didn't want to collaborate anymore:
>
> http://marc.theaimsgroup.com/?l=fop-dev&m=111263144615399&w=2
> http://marc.theaimsgroup.com/?l=fop-dev&m=111265443425492&w=2
Even those on this list who are not native English speakers will be able to
easily unde
Glen Mazza wrote:
> I think Victor said he didn't want to collaborate anymore:
>
> http://marc.theaimsgroup.com/?l=fop-dev&m=111263144615399&w=2
> http://marc.theaimsgroup.com/?l=fop-dev&m=111265443425492&w=2
Even those on this list who are not native English speakers will be able to
easily unde
Hello Jeremias,
I must convey that your answer was a relief for me ;-) I was starting to wonder
what I could have done wrong so that things turn out that way.
I keep your technical comments in mind for later, if I eventually may work on
this. Don't worry about the time I've already spent on:
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
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
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:
http://marc.theaimsg
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.
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.
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:
> No. Licensing is absolutely no problem in this case. FOray is
> distributed under the same license as FOP. What we can't
> simply do is take Victor's (source) code and put it in our
> code repository without Victor doing a grant to the ASF.
> That's a matter of ASF pol
Jeremias Maerki wrote:
> No. Licensing is absolutely no problem in this case. FOray is
> distributed under the same license as FOP. What we can't
> simply do is take Victor's (source) code and put it in our
> code repository without Victor doing a grant to the ASF.
> That's a matter of ASF pol
Vincent,
thank you very much for wanting to help. You've seen that you
inadvertently touched a sensitive subject. I'm really sad that these
things must happen. Let me just comment on your initial mail from a
purely technical perspective.
On 12.06.2005 17:20:07 Vincent Hennebert wrote:
> Hi Fop Te
I'm sorry, that I'm so late. I'm currently drowning in dozens of little
things I need to attend to.
On 13.06.2005 18:47:09 Victor Mote wrote:
> Vincent Hennebert wrote:
> > If you decide not to do it, well, no matter, I'll find
> > another thing to do ;-)
>
> Since I am in a later time zone than
No. Licensing is absolutely no problem in this case. FOray is
distributed under the same license as FOP. What we can't simply do is
take Victor's (source) code and put it in our code repository without
Victor doing a grant to the ASF. That's a matter of ASF policy. We can
add a JAR, however.
On 13
On Jun 13, 2005, at 5:10 AM, Vincent Hennebert wrote:
My goal is not to create any problem within the Team, or between it
and other people. Adapting FOrayFont to Fop is an issue that has
already been raised by a couple of persons here. I'm willing to do
this work because I feel capable of and
Vincent Hennebert wrote:
> When politics interferes in open-source development ;-) Hey,
> I don't think we are here to flame each other. I respect both
> Victor's and your opinions. I think you both contribute in a
> useful way. I agree with your willing to clean up the
> development code beca
Vincent Hennebert wrote:
> When politics interferes in open-source development ;-) Hey,
> I don't think we are here to flame each other. I respect both
> Victor's and your opinions. I think you both contribute in a
> useful way. I agree with your willing to clean up the
> development code beca
Glen Mazza a écrit :
Speaking for myself, I really don't want Victor's code in 1.0. I don't
like his personality, and have not been a fan of his architectural ideas
much either--especially his emphasis on placing the 0.20.5 layout code
into 1.0 via "multiple layout strategies".
I would not
Victor Mote wrote:
Vincent Hennebert wrote:
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:
First, thanks for your interest, and welcome to FOP. Even though I am no
Vincent Hennebert wrote:
> 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:
First, thanks for your interest, and welcome to FOP. Even though I am not an
active FOP dev
Vincent Hennebert wrote:
> 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:
First, thanks for your interest, and welcome to FOP. Even though I am not an
active FOP dev
Welcome back Vincent! No, we switched from Avalon Logging to Commons
Logging some time ago. The FOPAvalonization page is rather out-of-date.
Victor and I tend to have different architectural ideas. I have not
researched his font work but I believe other team members are more
knowledgable ab
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 APIs
56 matches
Mail list logo
