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.e...@zf.com> wrote:

> Hi Robert,****
>
> ** **
>
> 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. ****
>
> ** **
>
> Original: ****
>
>  TAB_1892****
>
> ** **
>
> Result:****
>
>   TAB-****
>
> _1892****
>
> ** **
>
> ** **
>
> Best regards****
>
> ** **
>
> Markus****
>
> ** **
>
> ** **
>
> ** **
>
> *Von:* Sticker Markus EXT FRD EPOS
> *Gesendet:* Dienstag, 22. Januar 2013 17:49
> *An:* fop-users@xmlgraphics.apache.org
> *Betreff:* AW: AW: Hyphenation****
>
> ** **
>
> Hi,****
>
> ** **
>
> 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.***
> *
>
> ** **
>
> Best Regards****
>
> ** **
>
> Markus****
>
> ** **
>
> ** **
>
> ** **
>
> *Von:* Robert Meyer [mailto:rme...@hotmail.co.uk <rme...@hotmail.co.uk>]
> *Gesendet:* Dienstag, 22. Januar 2013 14:52
> *An:* fop-users@xmlgraphics.apache.org
> *Betreff:* RE: AW: Hyphenation****
>
> ** **
>
> Hi Markus,
>
> 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".
>
> Regards,
>
> Robert****
> ------------------------------
>
> Subject: AW: Hyphenation
> Date: Tue, 22 Jan 2013 09:07:05 +0100
> From: markus.sticker.e...@zf.com
> To: fop-users@xmlgraphics.apache.org****
>
> Hi Robert,****
>
>  ****
>
> 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****
>
>  ****
>
> Markus****
>
>  ****
>
> *Von:* Robert Meyer [mailto:rme...@hotmail.co.uk <rme...@hotmail.co.uk>]
> *Gesendet:* Montag, 21. Januar 2013 17:54
> *An:* fop-users@xmlgraphics.apache.org
> *Betreff:* RE: Hyphenation****
>
>  ****
>
> Hi,
>
> 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:
>
> https://issues.apache.org/jira/browse/FOP-2044
>
> 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.
>
> Regards,
>
> Robert Meyer****
> ------------------------------
>
> Subject: Hyphenation
> Date: Mon, 21 Jan 2013 17:25:42 +0100
> From: markus.sticker.e...@zf.com
> To: fop-users@xmlgraphics.apache.org****
>
> Hi there,****
>
>  ****
>
> I wonder about the hyphenation in fop or offo, because
> if I try to hyphenate ****
>
>  ****
>
> computermonitor  = com-puter-mon-it-or****
>
>  ****
>
> and ****
>
>  ****
>
> 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.****
>
>  ****
>
> Best Regards****
>
>  ****
>
> Markus****
>

Reply via email to