sorry Soft Hyphenation is nto an option, because the âwordsâ are no longer searchable by the adobe reader.
So the adhoc rules will be the right choise, so I will try to insert a kind of adhoc breaking before the exception will be thrown.
Do you know a possiblity to find the best position in the words to break?
I started to modify the LineLayoutManager class but Iâm not sure, there is maybe a better way to do this task.
Von: Glenn Adams [mailto:glenn@xxxxxxxxxx]
Gesendet: Montag, 4. MÃrz 2013 17:35
Betreff: Re: AW: Hyphenation
I think it better to require the author to insert SOFT HYPHEN (­) rather than encode more adhoc rules into the existing code.
On Thu, Feb 28, 2013 at 9:28 AM, <markus.sticker.epos@xxxxxx> wrote:
Iâve got some more cases with the hyphenation issue.
So, is it possible to extent the hyphenation patch with things like
â0xFFFFFFFFâ and identifierers with numbers used like
characters (R2D2_C3PO or TAB2D_3_260) . I also get problems with
things like abc_dfe_RTF_XYZ() or GET_MILEAGE_FROM_NAB() . The
brackets at the end seems to produce some nonhypenated strings.
So maybe it is possible to have something like a emergency hyphenating, so
it beaks if the lineOverflows event will be thrown.
Von: Sticker Markus EXT FRD EPOS
Gesendet: Dienstag, 22. Januar 2013 17:49
Betreff: AW: AW: Hyphenation
I did some tests with different sources. The â_â is working very well. But Iâve got an issue for a words like this: âparameter.for.fopâ or âHyperlink#Markâ.
So is it possible to extend these pattern? Maybe I can do it by my own because not everbody needs technical documentation hyphenation pattern.
Patches remain separate from any build until they are reviewed, accepted and pushed by a committer. You can tell when this has happened as an svn commit message will be added to the bug and the jira issue will be set to resolved status. Up until that point, the only way to test what's in the patch will be to download the patch file yourself and merge it manually or use a tool e.g. in Linux / Mac OS you can use "patch -p0 < patch.diff".
Thanks for you very quick answer.
Iâve seen you have fixed it (expermential or unreviewed).
So the patch is provided in the nightly build?
Because I will have a try on this bugfix.
Best Regards from germany
Not sure about the first one, but there was a patch I submitted a couple of weeks ago regarding FOP not breaking words with an underline. This can be seen here:
The patch is still waiting to be reviewed, so it might be worth looking out for the fix whenever someone gets around to looking at it.
I wonder about the hyphenation in fop or offo, because
if I try to hyphenate
computermonitor = com-puter-mon-it-or
computer_monitor = computer_monitor
So I tried to extend the rules but I didnât get a better result.
I tried to add more patterns in the user pattern file like â_0 ââ
Maybe somebody has a idea to fix this.