[Fwd: Re: cvs commit: xml-fop/src/java/org/apache/fop/apps CommandLineOptions.java Fop.java]

[Peter B. West]

Resending, as I had been un-subscribed due to mail bounces.

Glen et al,

I have been severely distracted over the past couple of weeks, and I
seem to have lost a good deal of mail in the process.  Can you give me a
reference to the patch.  Sorry I didn't get around to replying to a
question of yours about the effects on alt-design integration of a patch
you wanted to apply.
Peter

[EMAIL PROTECTED] wrote:
gmazza  2004/04/08 20:05:40

  Modified:src/java/org/apache/fop/apps CommandLineOptions.java
Fop.java
  Log:
  3/4ths of Simon's patch committed at the moment, with minor changes
  made.
  
  Revision  ChangesPath
  1.17  +19 -37xml-fop/src/java/org/apache/fop/apps/CommandLineOptions.java
  
--
Peter B. West http://www.powerup.com.au/~pbwest/resume.html

Fontconfig

[Peter B. West]

Jeremias et al,

In connection with our recent discussions concerning font handling, I
looked at the contentious fontconfig system driven by Keith Packard.
The user documentation at
http://pdx.freedesktop.org/~fontconfig/fontconfig-user.html includes:
quote
Font Properties
While font patterns may contain essentially any properties, there are
some well known properties with associated types. Fontconfig uses some
of these properties for font matching and font completion. Others are
provided as a convenience for the applications rendering mechanism.
  PropertyTypeDescription
  --
  family  String  Font family name
  style   String  Font style. Overrides weight and slant
  slant   Int Italic, oblique or roman
  weight  Int Light, medium, demibold, bold or black
  sizeDouble  Point size
  aspect  Double  Stretches glyphs horizontally before hinting
  pixelsize   Double  Pixel size
  spacing Int Proportional, monospace or charcell
  foundry String  Font foundry name
  antialias   BoolWhether glyphs can be antialiased
  hinting BoolWhether the rasterizer should use hinting
  verticallayout  BoolUse vertical layout
  autohintBoolUse autohinter instead of normal hinter
  globaladvance   BoolUse font global advance data
  fileString  The filename holding the font
  index   Int The index of the font within the file
  ftface  FT_Face Use the specified FreeType face object
  rasterizer  String  Which rasterizer is in use
  outline BoolWhether the glyphs are outlines
  scalableBoolWhether glyphs can be scaled
  scale   Double  Scale factor for point-pixel conversions
  dpi Double  Target dots per inch
  rgbaInt unknown, rgb, bgr, vrgb, vbgr,
  none - subpixel geometry
  minspaceBoolEliminate leading from line spacing
  charset CharSet Unicode chars encoded by the font
  langString  List of RFC-3066-style languages this
  font supports
/quote
I have also, as I noted previously, looked briefly at the way fonts are
defined in Java.  Would I be correct in surmising that the current
manner of defining fonts is derived from Adobe's methods for PDF and PS?
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?
Peter
--
Peter B. West http://www.powerup.com.au/~pbwest/resume.html

The new logging framework and Java 1.4 logging

[Peter B. West]

Glen,

I see that you have the move to commons-logging.  I was encouraged by
this because of the support for 1.4 logging, which I have started to use
in alt-design.  When I looked at modifying the existing alt-design code
to use common-logging, however, I could find no way to set the logging
level on an existing logger, as there is, e.g., in SimpleLog.  I can
specify a default level in commons-logging.properties (I assume - I
haven't tried it), but if I want to dynamically change the level in
response to the options with the existing implementation, I'm stumped.
Does anyone know how to do this?

Peter
--
Peter B. West http://www.powerup.com.au/~pbwest/resume.html