On 26.11.2003 21:32:30 J.Pietschmann wrote:
Victor Mote wrote:
Yes, this can get ugly. If anybody knows of a way to find the physical font
file from an awt Font object, please speak up.
Currently (as of 1.4.1 you can create a awt.Font from an InputStream, but
you cant get back whatever
Jeremias Maerki wrote:
Anyway, it's the opposite of what Victor wanted.
Yeah.
I think you meant return Font.createFont(Font.TRUETYPE_FONT, new
FileInputStream...
OOps, yes.
This means users can use AWT fonts for creating PDF, but they can't
embed them. This may cause the resulting PDF to fail,
Peter B. West wrote:
Although not mandated in XSL-FO, CSS2 offers a number of methods of font
matching, only some of which preserve metrics. The FO User Agent is
free to make implementation-specific decisions about this, I assume. My
main interest here is in whether we want to try to separate
On 27.11.2003 17:30:18 J.Pietschmann wrote:
Jeremias Maerki wrote:
snip/
This means users can use AWT fonts for creating PDF, but they can't
embed them. This may cause the resulting PDF to fail, but so what.
-- Support questions
It depends. If users are still required to declare
J.Pietschmann wrote:
Peter B. West wrote:
Although not mandated in XSL-FO, CSS2 offers a number of methods of
font matching, only some of which preserve metrics. The FO User Agent
is free to make implementation-specific decisions about this, I
assume. My main interest here is in whether we
Jeremias Maerki wrote:
And there's still the question if we can produce font metric
information
for the target formats (there's PCL and PostScript and..., too) that
result in the desired output.
The idea was to query the renderer for fonts, or get a renderer
specific font
Peter B. West wrote:
BTW fonts aren't the only considerations, others are color and the
discretization of coordinates (e.g. bitmap vs. vector format).
All of which leads me to the question of what, exactly, we are trying to
isolate and amalgamate in the font system. We can't get away from
Jeremias Maerki wrote:
Font configuration should/will become easier. For TrueType and Type1
fonts this should just be a matter of specifying a list of directories
in which to look for fonts. A cache is needed to speed up the inventory on
startup.
Hmhm. Not bad.
My idea is still different: Having
Simon Pepping wrote:
I have taken a look at the way this question is dealt with in LaTeX
(TeX does not have the notion of font families, LaTeX does). Here the
question what to use for small caps font is deferred to the font
setup. The font definition tables must define a small caps font. If
they
Peter B. West wrote:
I'm fuzzy with this stuff, but isn't renderer-context a new notion?
What you are calling renderer-context was previously only associated
with the renderer as such, wasn't it? I'm assuming that the
renderer-context is something that amalgamates font metrics. Renderers
Peter B. West wrote:
What's the intention for the FOP font system? Is FOP going to define a
set of fonts and font metrics in its User Agent font database (as per
CSS2)? Will this be defined with reference to the supported renderers
(statically), the supported renderers and the fonts
Victor Mote wrote:
Yes, this can get ugly. If anybody knows of a way to find the physical font
file from an awt Font object, please speak up.
Currently (as of 1.4.1 you can create a awt.Font from an InputStream, but
you cant get back whatever physical representation the font has from
the awt.Font
Peter B. West wrote:
If a user renders a given .fo file on two different systems, using the
same renderer (say, PDF), and specifies a font family (say, Baskerville)
that does not exist on the first system, but does on the second, what
result should be expected?
If the user specified a fallback,
On Wed, Nov 26, 2003 at 08:21:33PM +1000, Peter B. West wrote:
Simon Pepping wrote:
I have taken a look at the way this question is dealt with in LaTeX
(TeX does not have the notion of font families, LaTeX does). Here the
question what to use for small caps font is deferred to the font
setup.
J.Pietschmann wrote:
Peter B. West wrote:
If a user renders a given .fo file on two different systems, using the
same renderer (say, PDF), and specifies a font family (say,
Baskerville) that does not exist on the first system, but does on the
second, what result should be expected?
If the
J.Pietschmann wrote:
Chris Bowditch wrote:
but my motivation is just to get something rather than nothing.
You are bored? Oh!
Thanks for the suggestions. I think you misunderstood though, I'm far
from bored, my employers keep me busy. Just trying to help get layout
unbroken.
Some tasks:
-
Victor Mote wrote:
I am confused by the distinction that you make between fop.PDFFont and
fop.Type1Font. In my mind, there is no such concept as a fop.PDFFont, unless
it is a renderer-specific class for getting a Type1Font (for example) into
the PDF output. But I think that should be a method in
J.Pietschmann wrote:
Victor Mote wrote:
No. Courier-Bold-Italic would be the Typeface, Courier would be the
TypefaceFamily. So my Font object that gets used by FOP would be
Courier-Bold-Italic at 12 points. It has a parent Typeface,
which represents
the Courier-Bold font file and its
Victor Mote wrote:
Same general concept, except I think there is a separate class for font
metrics in that system. If I can ever find a way to get to the physical file
(or some representation of it) through java.awt.Font (for embedding), we
would use it along with our other font scheme.
I believe
Simon Pepping wrote:
These days everybody uses scalable fonts, but in principle it is
possible that Courier-Bold-Italic at 10 points is a different font
than Courier-Bold-Italic at 20 points, with a different metric file
and different glyphs. The canonical example being of course TeX, with
(disclaimer: Due to lack of time and a hardware failure, I haven't read
everything, yet)
I don't think we can rely on java.awt.Font. A FOP-defined Font
interfaces is necessary to really make sure FOP gets what it need. What
we came up with on the Wiki pretty much shows my ideas for the font
J.Pietschmann wrote:
I believe we should just define a fop.Font interface which is
the same as awt.Font, then provide implementations fop.AWTFont,
fop.PDFFont (well all the variations), fop.Type1Font etc. A
configurable selector (an Avalon selector) could selcet them.
This way people could
From: J.Pietschmann [EMAIL PROTECTED]
I have done some investigation into emulating the Font-variant stuff in a
similar way to the maintenance branch.
Victor Mote wrote:
Typeface roughly corresponds to what is contained in a ttf of pfa font
file.
Hm hm. A TTF is typically Courier-bold-italic
Victor Mote wrote:
Victor Mote wrote:
Typeface roughly corresponds to what is contained in a ttf of
pfa font file.
Hm hm. A TTF is typically Courier-bold-italic or so. Did you mean this
or rather typeface==font-family?
No. Courier-Bold-Italic would be the Typeface, Courier would
Victor Mote wrote:
No. Courier-Bold-Italic would be the Typeface, Courier would be the
TypefaceFamily. So my Font object that gets used by FOP would be
Courier-Bold-Italic at 12 points. It has a parent Typeface, which represents
the Courier-Bold font file and its contents. This typeface has a
Chris Bowditch wrote:
but my motivation is just to get
something rather than nothing.
You are bored? Oh!
Some tasks:
- Implement text-align-last
- Implement text-align=justify
- Fix table headers.
- Fix content rectangle computation for background filling
- Fix bottom borders (and perhaps other
I have taken a look at the way this question is dealt with in LaTeX
(TeX does not have the notion of font families, LaTeX does). Here the
question what to use for small caps font is deferred to the font
setup. The font definition tables must define a small caps font. If
they do not do so, a
J.Pietschmann wrote:
(Still not making sense? If you need any more intermediate steps in
understanding how getters and setters actually make things
work, we're just
a message away ;) )
Dunno. Let me elaborate.
We have
FO - FOP layout - FOP renderer - output
Font variant SmallCaps
Victor Mote wrote:
Typeface roughly corresponds to what is contained in a ttf of pfa font file.
Hm hm. A TTF is typically Courier-bold-italic or so. Did you mean this
or rather typeface==font-family?
I don't understand what you are saying here. If emulation is used, it should
probably at least be
29 matches
Mail list logo
