You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "Glenn Adams (JIRA)" <ji...@apache.org> on 2016/09/27 15:41:21 UTC

[jira] [Commented] (FOP-2649) Implement an extensible way to select fonts

    [ https://issues.apache.org/jira/browse/FOP-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526502#comment-15526502 ] 

Glenn Adams commented on FOP-2649:
----------------------------------

Generally speaking, we aren't at liberty to change the syntax, including permitted attribute values, from what is specified in the XSL-FO RECs. If the development of XSL-FO itself were ongoing, then one could lobby for new values to be added over time in the standards process. But we don't have that luxury without causing deviations from the published standard.

So, the way this has to be handled is to define new namespace qualified attributes (or elements) in order to extend the language. For what you are suggesting, we would need to:

* define a new FOP specific attribute in the http://xmlgraphics.apache.org/fop/extensions namespace
* define the value of this new attribute to include namespace qualified names
* publish a registry where new qualified names of custom font selection strategies could be defined
* define a mechanism that maps from such custom font selection strategies (denoted as qualified names) to a Java class; this would undoubtedly entail new configuration file vocabulary


> Implement an extensible way to select fonts 
> --------------------------------------------
>
>                 Key: FOP-2649
>                 URL: https://issues.apache.org/jira/browse/FOP-2649
>             Project: FOP
>          Issue Type: Improvement
>          Components: font/unqualified
>            Reporter: Simone Rondelli
>            Priority: Minor
>
> Currently font selection is done through some static methods in the {{FontSelector}} class. There is no way to change font selection strategy even though there is a a fop attribute called {{font-selection-strategy}}.
> The outcome of this issue will be to have a way to define custom FontSelectionStartegy according to the value of the {{font-selection-strategy}} attribute.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)