[
https://issues.apache.org/jira/browse/FOP-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904671#comment-13904671
]
Luis Bernardo commented on FOP-2044:
------------------------------------
The burden of forcing "uncommon" hyphenation should be on the user, not on FOP.
But FOP provides the means to do it through customized hyphenation patterns.
See https://xmlgraphics.apache.org/fop/trunk/hyphenation.html.
An example, for one of the cases used here:
PROFILING_PC_STATUS_NO_COUNTER_AVAILABLE_FOR_TYPE
>From svn://tug.org/texhypen get the file
>trunk/collaboration/repository/offo/en.xml (or the file for whatever language
>you are using). Place the file in the hyph directory of FOP, and edit it by
>adding these two lines inside the patterns element:
.counte5r
.t5ype
These mean that COUNTE-R and T-YPE are valid hyphenations, and even likely
(given the value of 5). Run ant jar-hyphenation. This updates the fop-hyph.jar
in the build directory. Then run FOP with the example uppercase-hyphen-2.fo
provided here. The result should be uppercase-hyphen-2-fixed.pdf.
> [PATCH] Hyphenation of Uppercase Words, Combined with Underlines
> ----------------------------------------------------------------
>
> Key: FOP-2044
> URL: https://issues.apache.org/jira/browse/FOP-2044
> Project: Fop
> Issue Type: Improvement
> Components: general
> Affects Versions: 1.0
> Environment: Operating System: All
> Platform: All
> Reporter: Thomas Schraitle
> Assignee: Robert Meyer
> Fix For: trunk
>
> Attachments: fop-trunk-jan02-2014-test-fop-2044.fo,
> fop-trunk-jan02-2014.log, fop-trunk-jan92-2914-test-fop-2044.pdf, output.pdf,
> patch.diff, patch2.diff, uppercase-hyphen.fo, uppercase-hyphen.pdf
>
>
> Consider the attached FO file which combines words of lowercase and uppercase
> letters.
> As it is expected, the word "expected" is hyphenated correctly (example 2).
> Also the uppercase "SUCCESS". Even combined with underlines before and after
> the word (see example 4 and 5).
> However, if there is another word (like OCF_SUCCESS) the word isn't
> hyphenated at all anymore. I don't know if this is an expected behaviour or
> an issue in the hyphenation patterns. Interestingly, XEP from RenderX
> hyphenates it as "OCF_SUC-CESS". As far as I know, they use also the TeX
> hyphenation patterns as FOP.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
