Hey Rob, It's generally best practice to ask fop-specific questions the fop-users mailing list, that way you'll get much better support by the community at large rather than a single person.
As to your question, honestly I've barely worked on AFP or FOP for that matter in a while and wouldn't be confident answering your question. Maybe one of the other guys can help? Apologies for not being particularly useful, Mehdi On 4 April 2014 16:04, Ron Snyder <rsnyd...@humana.com> wrote: > Hello Medhi, > > > > I wanted to reach out to you and see if you can provide me with technical > notes on how Apache FOP determines mapping of Windows TTF characters to AFP > output. > > > > I have been researching and reading various articles on the latest mapping > (no longer using EBCDIC but UTF16) > > > > My ultimate goal is to get ‘hollow bullet’ character in Calibri TTF font > to output to PDF and AFP using the same encoding. I am somewhat familiar > with how to write the parameters to define AFP fonts in FOP.XCONF. > > > > Can you validate my assumptions of how FOP determines characters from > window TTF fonts to FOP AFP rendered output? > > > > (based on section of code from FOP.XCONF below) > > <font> > > <afp-font name="Bullet" type="raster" > codepage="T100ANSI" encoding="Cp500"> > > <afp-raster-font size="8" > characterset="C0CA08NP"/> > > <afp-raster-font size="10" > characterset="C0CA10NP"/> > > <afp-raster-font size="12" > characterset="C0CA12NP"/> > > <afp-raster-font size="13" > characterset="C0CA13NP"/> > > <afp-raster-font size="14" > characterset="C0CA14NP"/> > > </afp-font> > > <font-triplet name="FS Humana" > style="normal" weight="normal"/> > > <font-triplet name="any" style="normal" weight="normal"/> > > </font> > > <font> > > <afp-font name="Hollow" type="raster" > codepage="T100ANSI" encoding="Cp1252"> > > <afp-raster-font size="8" > characterset="C0CA08BP"/> > > <afp-raster-font size="10" > characterset="C0CA10BP"/> > > <afp-raster-font size="12" > characterset="C0CA12BP"/> > > <afp-raster-font size="13" > characterset="C0CA13BP"/> > > <afp-raster-font size="14" > characterset="C0CA14BP"/> > > </afp-font> > > <font-triplet name="FS Humana" > style="normal" weight="normal"/> > > <font-triplet name="any" style="normal" weight="normal"/> > > </font> > > > > 1. By using the mapping for the “Bullet” and encoding=”cp500”, the > mappings are based on EBCDIC (because cp500 is based on EBCDIC) and use the > CODE points within the cp500 to map to matching Code Points with the > T100ANSI, determining the equivalent hexadecimal point of the character > (and T100ANSI is EBCDIC based) ○ (U25CB) ● (U2022) · (U00B7) (based on > cp500 U2022 and U00B7 are included in the AFP character set and based on > T100ANSI only U00B7 is available to be output to AFP. > > 2. Where are the cp500 and cp1252 files located in FOP? > > 3. Can ‘custom’ encoding files be used? (where should these be > located?) > > 4. By using the mapping for the “Bullet” and encoding=”cp1252”, the > mappings are based on ASCII (because cp1252 is based on ASCII keyboard > mappings) and use the CODE points within the cp500 to map to matching Code > Points with the T100ANSI, determining the equivalent hexadecimal point of > the character (and T100ANSI is EBCDIC based) ○ (U25CB) ● (U2022) · (U00B7) > (based on cp1252 U2022 and U00B7 are included in the AFP character set and > based on T100ANSI only U00B7 is available to be output to AFP. (where does > ASCII to EBCDIC conversion take place?) > note that all characters ○ (U25CB) ● (U2022) · (U00B7) output correctly to > PDF, but only U00B7 outputs to AFP > > > > If you are not the correct person to obtain this information can you > provide me with the contact information of the person I should be reaching > out to? > > > > Thanks, > > Ron > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. >
