Glen,
I put in a vote for Simon. The language thing is confusing, I know.
There have been occasions on which the Austrian flag has been flown, or
the Austrian National Anthem been played, somewhat inappropriately. But
it's en_AU over here; AU because we got in first.
Peter
Glen Mazza
On 11.04.2004 01:55:48 Peter B. West wrote:
In connection with our recent discussions concerning font handling, I
looked at the contentious fontconfig system driven by Keith Packard.
snip what=very interesting resource/
I have also, as I noted previously, looked briefly at the way fonts are
On Mon, 2004-04-12 at 04:33, Peter B. West wrote:
Glen,
I put in a vote for Simon. The language thing is confusing, I know.
There have been occasions on which the Austrian flag has been flown, or
the Austrian National Anthem been played, somewhat inappropriately. But
it's en_AU over
Jeremias Maerki wrote:
If that is the case (a big if) might we not be better to move to a more
generic form, with translation into each particular form of font
specification?
I can't tell. I don't see much benefit because the current system
already provides most of what FOP needs. A total
John Austin wrote:
On Mon, 2004-04-12 at 04:33, Peter B. West wrote:
Glen,
I put in a vote for Simon. The language thing is confusing, I know.
There have been occasions on which the Austrian flag has been flown, or
the Austrian National Anthem been played, somewhat inappropriately. But
it's
on-the-fly font discovery: Specify a directory and FOP finds all the
compatible fonts in there without the need for manual font metrics
creation. So this is something else.
font aliases: Mapping Arial to Helvetica, for example. Mapping font
characteristics is somewhat hardcoded already into FOP,
On Apr 12, 2004, at 5:55 AM, Peter B. West wrote:
Jeremias Maerki wrote:
If that is the case (a big if) might we not be better to move to a
more
generic form, with translation into each particular form of font
specification?
I can't tell. I don't see much benefit because the current system
I applied Clay's breadcrumbs.js patch directly in the
cvs xml-site/targets/fop/skin directory (where our
production site reads from). This overwrites the
buggy breadcrumbs.js that forrestbot keeps putting
there everytime we do a website publish.
I also put in a request to have the default
On Apr 12, 2004, at 2:57 PM, Glen Mazza wrote:
I applied Clay's breadcrumbs.js patch directly in the
cvs xml-site/targets/fop/skin directory (where our
production site reads from). This overwrites the
buggy breadcrumbs.js that forrestbot keeps putting
there everytime we do a website publish.
I
