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

Björn Kautler edited comment on FOP-2522 at 1/17/24 3:54 PM:
-------------------------------------------------------------

Look at the screenshots I had in my last comment.

In the upper example in each screenshot it is only not shown on line-end - and 
that is correct - as the {{hyphenation-character}} is set to empty value.

To reduce your confusion and uncertainty, I added the lower example, where you 
see that where it should be shown it still shown even with my patch.

That is on line-end where the word was split due to SHY.


was (Author: vampire):
Look at the screenshots I had in my last comment.

In the upper example in each screenshot it is only not shown on line-end 
correctly as the {{hyphenation-character}} is set to empty value.

To reduce your confusion and uncertainty, I added the lower example, where you 
see that where it should be shown it still shown even with my patch.

That is on line-end where the word was split due to SHY.

> [PATCH] Soft hyphens in front of some characters are transformed to 
> hyphen-minus
> --------------------------------------------------------------------------------
>
>                 Key: FOP-2522
>                 URL: https://issues.apache.org/jira/browse/FOP-2522
>             Project: FOP
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Björn Kautler
>            Priority: Major
>         Attachments: image-2024-01-17-14-48-50-945.png, 
> image-2024-01-17-14-49-08-309.png, issue-2522.fo, issue-2522.patch
>
>
> If you have a verbatim block like {{<programlisting>}} in DocBook, the 
> DocBook XSL stylesheets insert many soft hypens 
> (http://decodeunicode.org/u+00AD) into the content to show where the 
> FO-processor may insert linebreaks. By default after spaces and non-breakable 
> spaces, but configurable also after arbitrary other characters.
> Unfortunately it seems FOP does not handle the soft hyphens correctly, 
> depending on the character that follows it. Soft Hyphens in front of some 
> characters are transformed to hyphen-minus, no matter what 
> hyphenation-characters is configured and even if the occurence is within a 
> line and not at line break.
> I've observed this behaviour with soft hyphens in front of apostrophe 
> (http://decodeunicode.org/u+0027), quotation mark 
> (http://decodeunicode.org/u+0022), hyphen-minus 
> (http://decodeunicode.org/u+002D) and full stop 
> (http://decodeunicode.org/u+002E)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to