MICR font problem in 1.0

[Anil Pinto <ap...@lobotec.com>]

Hello,

We have been using FOP 1.0 for quite a while now and are very happy with 
it. Thanks to all the developers for their time, hard work and efforts.

Recently we had a need to incorporate MICR into one of the PDFs we were 
generating for our customer but are having issues getting it to work and 
would greatly appreciate some insights on what may be going wrong.

The font is not rendered with 1.0 but renders correctly in 0.95 
(although both version show the same warning as below)

Dec 2, 2011 1:54:10 PM org.apache.fop.fo.properties.CommonHyphenation 
getHyphChar
WARNING: Substituted specified hyphenation character (0x2d) with 0x20 
because the font doesn't have the specified hyphenation character: 
MICR,normal,400

I am attaching the sample, xml, xsl and PDFs for both versions. Note for 
obvious reasons I cannot include the MICR font (micr.ttf) as it was 
purchased by the customer. I can send it individually to the developer 
who can help resolve this problem in a separate email.

Appreciate any help to resolve this behavior.

Thanks,
Anil Pinto.

*Lobo Technologies, Inc.*
www.lobotec.com

Re: MICR font problem in 1.0

[Anil Pinto <ap...@lobotec.com>]

An update. The problem with the MICR font was resolved by creating the 
font-metrics XML. Somehow this same font worked with FOP 0.95 but 
stopped working the usual way with FOP 1.0. Maybe the FOP developers can 
throw some light there, something to do with changes within the font 
handling mechanism?

Thanks to Eric for responding to my email. Actually the hyphenation 
warning was not responsible for causing the MICR behavior, it was a 
different issue that did not interfere with the font issue.

Thanks,
Anil Pinto.

*Lobo Technologies, Inc.*
www.lobotec.com

On 12/6/2011 4:43 AM, Amick, Eric wrote:
>
> If you do something like
>
> <block hyphenation-character="X">
>
> <!---text here -->
>
> </block>
>
> then X will appear whenever a hyphen is required to break a word. The 
> property is inherited, so you could put it on the <root> element if 
> you need to specify a character for the entire document. I have no 
> idea if this restricted license on your font matters.
>
> Eric Amick   Systems Engineer II
>
> Legislative Computer Systems
>

RE: MICR font problem in 1.0

["Amick, Eric" <Er...@mail.house.gov>]

There is a hyphenation-character property; perhaps all you need to do is use it to specify the character to use?

Eric Amick   Systems Engineer II
Legislative Computer Systems

From: Anil Pinto [mailto:apinto@lobotec.com]
Sent: Friday, December 2, 2011 17:20
To: FOP Mailing List
Subject: MICR font problem in 1.0

Hello,

We have been using FOP 1.0 for quite a while now and are very happy with it. Thanks to all the developers for their time, hard work and efforts.

Recently we had a need to incorporate MICR into one of the PDFs we were generating for our customer but are having issues getting it to work and would greatly appreciate some insights on what may be going wrong.

The font is not rendered with 1.0 but renders correctly in 0.95 (although both version show the same warning as below)

Dec 2, 2011 1:54:10 PM org.apache.fop.fo.properties.CommonHyphenation getHyphChar
WARNING: Substituted specified hyphenation character (0x2d) with 0x20 because the font doesn't have the specified hyphenation character: MICR,normal,400

I am attaching the sample, xml, xsl and PDFs for both versions. Note for obvious reasons I cannot include the MICR font (micr.ttf) as it was purchased by the customer. I can send it individually to the developer who can help resolve this problem in a separate email.

Appreciate any help to resolve this behavior.

Thanks,
Anil Pinto.

Lobo Technologies, Inc.
www.lobotec.com<http://www.lobotec.com>