Just committed the initial support for the soft hyphen.
As we had two in favour of having the SHY always produce a break
opportunity and only one against that's the route I took.
I had no luck with giving the SHY a reduced penalty and have the Knuth
algorithm favour them before normal
Jeremias Maerki a écrit :
On 12.01.2007 09:25:59 Vincent Hennebert wrote:
Jeremias Maerki a écrit :
Good to see that happen! Here's my take:
On 11.01.2007 13:24:16 Manuel Mall wrote:
Hi,
when I implemented the UAX#14 line breaking I noticed that fop doesn't
currently support the Unicode
On Saturday 13 January 2007 19:57, Vincent Hennebert wrote:
Jeremias Maerki a écrit :
On 12.01.2007 09:25:59 Vincent Hennebert wrote:
Jeremias Maerki a écrit :
Good to see that happen! Here's my take:
On 11.01.2007 13:24:16 Manuel Mall wrote:
Hi,
snip/
Still don't agree. Overriding
On Jan 12, 2007, at 13:00, [EMAIL PROTECTED] wrote:
snip /
Just a quick comment on this, given the above stats you might
consider having a single Object field and switch the type of object
from the actual child (when there is a single child) to a List of
children when there are multiple
After having delved into the UAX#14 and SHY issues I am interested in
compiling a FOP UNICODE issues list. That is a list of things that
still require work to make FOP Unicode compliant. Obviously the best
place for such a list is the wiki. But before doing this I am
interested in some even
On Sat, Jan 13, 2007 at 08:27:20PM +0900, Manuel Mall wrote:
On Saturday 13 January 2007 19:57, Vincent Hennebert wrote:
Well, again, the description of the hyphenate property (§7.9.4)
sounds clear to me: when false, Hyphenation may not be used in the
line-breaking algorithm.
I still
On Jan 13, 2007, at 10:31, Manuel Mall wrote:
Hi Manuel,
Just committed the initial support for the soft hyphen.
Nice job, thanks!
As we had two in favour of having the SHY always produce a break
opportunity and only one against that's the route I took.
I had no luck with giving the SHY a
