Re: Configure fonts for FOP
Hi Fernando, I'll address each question individually: On 27 July 2011 23:29, Fernando Israel fernando.isr...@kognoz.com wrote: Hi All, I know this is a recurring issue but going through the documentation and forum listings I am still no clear but I hope I know what to ask. /snip The questions I have (and pardon my ignorance but fonts is not my subject) are: 1. What type of font files do I have to package ? TTF, TTC .. ?. If you're producing PDF you can use either TTF or TTC. 2. Once I create the jar file if I put it in the same directory as fop.jar I guess FOP will find it, right ?. http://xmlgraphics.apache.org/fop/1.0/fonts.html should help you configure the fonts appropriately. The font metrics files are deprecated, so no need for that, but you will have to configure the fop.xconf to let FOP know the directory of the font file. 3. If I go this route, do I have to tell FOP anything else (for instance in the configuration file) ? See the link above. 4. Does FOP always looks first in the classpath for fonts ? No, if FOP isn't explicitly given the font configuration, it looks in the System fonts, which are, as the name suggests, OS dependent. I don't think putting the font in the classpath makes the slightest bit of difference, FOP still won't have a font-name and so no way to link the font to a font-family in the FO. Hope that helps, there is also an example config file in fop directory/conf/fop.xconf, which should help you get started Mehdi - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Configure fonts for FOP
Hi Mehdi, Thank you very much for your response. It is helping me a lot. I've seen the document on fonts you suggest but your input helps me to interpret it better. So what you suggest is that I just stick all the necessary font files TTF or TTC in a directory and direct FOP to use these fonts via the configuration file using the directory element to specify that directory. Good !. Since I am only using the PDF renderer I will have an entry in the config file for it only. I will stick there the directory element with the name of the directory where I put all the necessary fonts. 1. What should I do with the auto-detect element ?. I would like to force FOP to use only the fonts in the specified directory so shall I remove the auto-detect ? 2. Using this approach will the fonts be embbeded automatically in the target (a PDF) ? 3. For testing purposes, can I take the TTF files from a Windows OS and stick them on directory on a Linux box where the server (with FOP) runs ?. Will that work ?. Thanks again for your help ! Regards, Fernando On Thu, Jul 28, 2011 at 3:45 AM, mehdi houshmand med1...@gmail.com wrote: Hi Fernando, I'll address each question individually: On 27 July 2011 23:29, Fernando Israel fernando.isr...@kognoz.com wrote: Hi All, I know this is a recurring issue but going through the documentation and forum listings I am still no clear but I hope I know what to ask. /snip The questions I have (and pardon my ignorance but fonts is not my subject) are: 1. What type of font files do I have to package ? TTF, TTC .. ?. If you're producing PDF you can use either TTF or TTC. 2. Once I create the jar file if I put it in the same directory as fop.jar I guess FOP will find it, right ?. http://xmlgraphics.apache.org/fop/1.0/fonts.html should help you configure the fonts appropriately. The font metrics files are deprecated, so no need for that, but you will have to configure the fop.xconf to let FOP know the directory of the font file. 3. If I go this route, do I have to tell FOP anything else (for instance in the configuration file) ? See the link above. 4. Does FOP always looks first in the classpath for fonts ? No, if FOP isn't explicitly given the font configuration, it looks in the System fonts, which are, as the name suggests, OS dependent. I don't think putting the font in the classpath makes the slightest bit of difference, FOP still won't have a font-name and so no way to link the font to a font-family in the FO. Hope that helps, there is also an example config file in fop directory/conf/fop.xconf, which should help you get started Mehdi - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: FOP-ComplexScript (connectivity, direction and fonts of Arabic)
Hello Qais, Thanks for taking some time to test out the complex script features being developed for FOP. To help address these issues, could you: (1) provide input FO test files showing the specific problems you have found? it is best if each test file contains the minimum needed to demonstrate the problem; (2) indicate which complex script build you are using? fyi, the latest work is available at http://github.com/skynavga/fop; Regarding connectivity, shape selection, kerning, point placement, etc., keep in mind that FOP doesn't do anything special other than implement the substitutions and positioning operations defined in the OpenType GSUB/GPOS tables. I'm not certain if the Arabeyes or other fonts you have tried support these tables. If they do, then there may be a bug in the new TTF/OTF parsing of this table data. In any case, if you provide some additional input as requested above, I'm sure we can resolve this matter soon. Also, if you haven't already seen it, please take a look at the documentation and active tickets found at http://skynav.trac.cvsdude.com/fop. Regards, Glenn Adams On Wed, Jul 27, 2011 at 1:57 PM, Qais m.q...@gmx.de wrote: Hi, Since a week I am working closely with FOP, Cocoon and Co, especially with the Complex Script (connectivity, direction and fonts of Arabic). Below is the result. Testing the Complex Script of FOP (27.07.2011) 1) Supported Fonts by the Complex Script: 1.1) Automatically registered: Arial Unicode MS, Lateef and Scheherazade in a fo:block: connectivity: ok, direction: ok. Arial Unicode MS, Lateef and Scheherazade in a fo:block-container, fo:table or fo:list-block: connectivity: none, direction: ok. 1.2) Using font metrics: Arial Unicode MS and Traditional Arabic in a fo:block, fo:block-container, fo:table or fo:list-block: connectivity: none, direction: ok. Simplified Arabic in a fo:block, fo:block-container, fo:table or fo:list-block: connectivity: none, direction: ok, glyphs: partially. Lateef and Scheherazade in a fo:block, fo:block-container, fo:table or fo:list-block: glyphs: none. 2) Base-14 Fonts: 2.1) Automatically registered: Arial, Times New Roman, Courier New and Tahoma in a fo:block: connectivity: ok, direction: ok. Arial, Times New Roman, Courier New and Tahoma in a fo:block-container, fo:table or fo:list-block: connectivity: none, direction: ok. 3) Arabeyes Fonts: www.arabeyes.org 3.1) Automatically registered: KacstArt, KacstBook, KacstDecorative, KacstDigital, KacstFarsi, KacstLetter, KacstNaskh, KacstOffice, KacstOne, KacstPoster, KacstScreen, KacstTitle, KacstTitleL and Thabit in a fo:block, fo:block-container, fo:table or fo:list-block: connectivity: none, direction: ok. 3.2) Using font metrics: KacstArt, KacstBook, KacstDecorative, KacstDigital, KacstFarsi, KacstLetter, KacstNaskh, KacstOffice, KacstOne, KacstPoster, KacstScreen, KacstTitle, KacstTitleL and Thabit in a fo:block, fo:block-container, fo:table or fo:list-block: connectivity: none, direction: ok. 4) Other Fonts: 4.1) Automatically registered: Advertising Light, Advertising Bold, Advertising Extra Bold and Bassam Ostorah in a fo:block, fo:block-container, fo:table or fo:list-block: glyphs: none. 4.2) Using font metrics: Advertising Light, Advertising Bold, Advertising Extra Bold and Bassam Ostorah in a fo:block, fo:block-container, fo:table or fo:list-block: connectivity: none, direction: ok. 5) Connectivity and Direction Problem: A small tool called Free Ressam can be used to pre adjust connectivity and direction of the text parts. This is of course not the accurate solution, especially dealing with long texts, but the tool might give an idea about the necesarry logic. Free Ressam was developed to adjust connectivity and direction of arabic text by using of some programs that don't properly support the display of arabic text, such as older versions of Photoshop. Maher - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
