https://issues.apache.org/bugzilla/show_bug.cgi?id=50471
Dominik Stadler dominik.stad...@gmx.at changed:
What|Removed |Added
CC|
https://issues.apache.org/bugzilla/show_bug.cgi?id=50471
Glenn Adams gl...@skynav.com changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment
https://issues.apache.org/bugzilla/show_bug.cgi?id=50471
--- Comment #4 from Andreas L. Delmelle adelme...@apache.org 2011-01-07
07:31:03 EST ---
(In reply to comment #3)
At least there should be some configuration available to the end user to tell
FOP to use some default line break in such
https://issues.apache.org/bugzilla/show_bug.cgi?id=50471
Andreas L. Delmelle adelme...@apache.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.apache.org/bugzilla/show_bug.cgi?id=50471
--- Comment #2 from Chris Bowditch bowditch_ch...@hotmail.com 2011-01-06
06:48:25 EST ---
Indeed you raise a very good point Andreas. Even if you make the code change, I
would expect # to appear in the output, because no font is likely to
https://issues.apache.org/bugzilla/show_bug.cgi?id=50471
--- Comment #3 from tvsud...@rediffmail.com 2011-01-06 23:36:48 EST ---
Andreas,
Thanks a lot for your response.
Actually we came across some special characters which are not intended to be
present in our database. We can figure out the
https://issues.apache.org/bugzilla/show_bug.cgi?id=50471
--- Comment #1 from Andreas L. Delmelle adelme...@apache.org 2011-01-05
13:31:26 EST ---
Thanks for reporting, and apologies for the late reply...
At first glance, this seems like a minor oversight in the implementation of
Unicode
