DO NOT REPLY [Bug 35948] - pre-patch for FOrayFont adaptation to Fop

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35948>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35948


vincent.hennebert@enseeiht.fr changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #17207|0                           |1
        is obsolete|                            |




------- Additional Comments From vincent.hennebert@enseeiht.fr  2006-09-26 13:56 -------
Created an attachment (id=18917)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18917&action=view)
Updated patch for the current trunks of Fop and FOrayFont

This is an early patch updating the old one to the trunks of both Fop and
FOray.
This patch is completely broken! It is mainly provided so that Bertrand can
start his work on the OpenType support, basing it on FOrayFont instead of the
soon-to-be-removed current font library.

Only the PDFRenderer is running (note that I didn't say working :-\ ). All of
the other renderers, along with the SVG transcoders currently have compilation
errors. So the ant build script cannot be used to create the binary, the
compilation directory of Eclipse should rather be used instead.

Currently there is a bug where digits are displayed instead of normal text with

all fonts but truetype ones. I'm sure this is not a big bug but I haven't found

it yet. I'll look at it ASAP.

There are a few necessary steps to run the application:
* A font-configuration file must be provided; currently its path is hardcoded
  in org.apache.fop.fo.FOEventHandler.java, line 163 (FOrayFontServer.setup(URL

  to the config file))
* A sample font-config file is provided with this patch; there are 3 paths to
  change to adapt it to another system:
  * the path to the dtd which is to be found in the aXSL codebase;
  * the xml:base attribute of the root element for access to custom fonts;
  * the base14-root key which should point to the directory of the FOray
    installation containing the metrics for the base14 fonts.
  Note that the ending slashes are important!

The font families which may be used are the generic families (serif,
sans-serif,
monospace), or the names of the fonts configured in the aXSL font-config file.
For example, in the provided sample file, there is a font-family entry for the
Bitstream Charter font. Only the upright normal-weight variant has been
configured, which may be accessed in an fo file like the following:
  <fo:block font-family="BitstreamCharter" font-style="normal"
font-weight="normal">
    Some text displayed with the Bitstream Charter Roman font...
  </fo:block>
So the value of the "font-family" attribute in the fo file should match the
value
of the "name" attribute of the font-family element in the config file.

The jar file contains additional files: two new source files, the jars for aXSL

and FOrayFont (which contain a not yet reported bug fix, so don't use other
binaries!), and a sample font-config file.

Well, I think those informations should be enough to get started...


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.