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 or so. Did you mean this or rather typeface==font-family?

I just added the fontVariant property to the font class (the private member already existed - so it felt right)

I don't understand what you are saying here. If emulation is used, it should
probably at least be logged. Alternatively, a config option could control
whether this is allowed at all. But I don't follow at all what you are
suggesting with the renderer using the font to control the emulation. How
does layout get done at all then? And what is the advantage over simply
establishing the emulation in the FO Tree itself?

The layout gets the metric from a FOP font structure, and it doesn't have to know whether the font is a true small caps font or emulates it.

During rendering, of course, emulation has to take effect.

Well, on a secont thought there is not much difference from emulating
small caps before layout.

Of course it makes sense to log if small caps is emulated.

I am just aiming to implement small-caps emulation at this stage. I realise it is not the ideal solution, but my motivation is just to get something rather than nothing. The emulation is by no means "easy" I have the code from the maintenance branch, but it cannot simply be copied.

In order to emulate small-caps, the text area in question must be broken up whenever case changes. This involves changing TextLayoutManager.getNextBreakPoss code to detect this, thus creating break possibilities and changing "something else" possibly the TLM.addAreas to ensure areas are created for each BP whilst font-variant="small-caps"


Find a cheaper internet access deal - choose one to suit you.

Reply via email to