On Tue, Nov 08, 2005 at 11:19:15AM +0800, Manuel Mall wrote:
On Tue, 8 Nov 2005 04:40 am, Simon Pepping wrote:
Step 2. Refinement: white-space-collapse
Issue 1. The spec intentionally addresses only XML white space,
because only such white
On Oct 31, 2005, at 22:18, Andreas L Delmelle wrote:
On Oct 27, 2005, at 06:29, Manuel Mall wrote:
Actually something like:
fo:block background-color=yellowword1fo:character
character=#10;/fo:character character=
/word2fo:character character= /word3fo:character
character=#10;//fo:block
On Nov 1, 2005, at 10:04, Manuel Mall wrote:
I am sure it is doable - but is it worth it at this stage? Possibly
after a better understanding of the white-space handling issues that
whole current system needs revision? One problem with the current char
iterator is that it iterates over inline
On Oct 27, 2005, at 06:29, Manuel Mall wrote:
Manuel,
Some more on this example:
Actually something like:
fo:block background-color=yellowword1fo:character
character=#10;/fo:character character=
/word2fo:character character= /word3fo:character
character=#10;//fo:block
currently causes an
If its any consolation in this discussion I wrote a little HTML test to
see how browsers deal with these white space (and some line height)
issues. To mimic the XSL-FO situation I used only div and span. You
can see the results here:
http://people.apache.org/~manuel/fop/test5.html
I viewed
Andreas,
excellent - I think there is now lots of convergence and common
understanding between your and my interpretations.
A bit more inline.
On Fri, 28 Oct 2005 04:58 am, Andreas L Delmelle wrote:
On Oct 25, 2005, at 10:57, Manuel Mall wrote:
When FOP is collapsing (b) or removing (c)
Manuel Mall wrote:
Side note: FOP doesn't quite do the same internally, i.e. a character
explicitly specified using fo:character.../ is handled separately from
'plain text'. If someone would write a style sheet which does a
transform of every character into a fo:character / object and would
On Fri, 28 Oct 2005 11:08 pm, Luca Furini wrote:
Manuel Mall wrote:
Side note: FOP doesn't quite do the same internally, i.e. a
character explicitly specified using fo:character.../ is handled
separately from 'plain text'. If someone would write a style sheet
which does a transform of
On Oct 28, 2005, at 12:28, Manuel Mall wrote:
On Fri, 28 Oct 2005 04:58 am, Andreas L Delmelle wrote:
(second example)
Same thinking here, b) seems to be the way to go.
We agree but did you notice the difference it would make in visual
appearance if the inline just happens to be at the
On Wed, 26 Oct 2005 06:22 am, Andreas L Delmelle wrote:
On Oct 25, 2005, at 10:57, Manuel Mall wrote:
/snip
No, it talks about 'character flow objects', which makes me wonder...
Are all characters to be considered 'character flow objects' or only
those that were specified using fo:character?
On Wed, 26 Oct 2005 06:22 am, Andreas L Delmelle wrote:
On Oct 25, 2005, at 10:57, Manuel Mall wrote:
snip/
The right order in which the related properties should be dealt with
seems to be:
1. white-space-treatment (property refinement)
2. linefeed-treatment (property refinement)
3.
Hi,
I haven't got any technical comments to the issues raised on the Wiki
page. Is this 'too hard' or 'too boring' or 'too messy' or what? The
problem is not going away. We currently don't do it right in some parts
(that is established) but I don't know overall what is right or wrong.
May be
Hi Manuel,
On Tue, Oct 25, 2005 at 04:57:41PM +0800, Manuel Mall wrote:
Hi,
I haven't got any technical comments to the issues raised on the Wiki
page. Is this 'too hard' or 'too boring' or 'too messy' or what? The
problem is not going away. We currently don't do it right in some parts
Andreas,
firstly a great thanks for looking at this.
I am not going to comment on your comments right now but there is
probably an important clarification required: All my interpretations of
the spec with respect to white space handling are based on the 1.1WD
not the 1.0 spec. The WG has
I was close to throwing temporarily the proverbial towel into the ring
with respect to whitespace handling. However an offline IM chat with
Jeremias and writing the response to Stephen's post encouraged me to
take a different approach.
Instead of trying to understand whitespace handling on the
Manuel Mall wrote:
Manuel,
I was close to throwing temporarily the proverbial towel into the ring
with respect to whitespace handling. However an offline IM chat with
Jeremias and writing the response to Stephen's post encouraged me to
take a different approach.
Instead of trying to
On 19.10.2005 03:45:33 Manuel Mall wrote:
On Wed, 19 Oct 2005 05:44 am, Jeremias Maerki wrote:
I've started to comment on the individual issues you listed and only
when I got to the examples I realized there must be something wrong.
You place the white-space-treatment after the
On Wed, 19 Oct 2005 03:33 pm, Jeremias Maerki wrote:
On 19.10.2005 03:45:33 Manuel Mall wrote:
On Wed, 19 Oct 2005 05:44 am, Jeremias Maerki wrote:
snip/
Still, I get the impression that *-treatment
are both handled before white-space-collapse.
Yes, linefeed-treatment is definitely a
On Thu, 20 Oct 2005 08:15 am, Stephen Denne wrote:
I have not read the spec regarding these attributes recently, but I
was wondering whether the treatment of whitespace in the fo file
defaults to the normal whitespace treatment in xml files if no
special white-space treatment attributes are
I have started a white space handling Wiki page
(http://wiki.apache.org/xmlgraphics-fop/LineLayout/WhitespaceHandling).
As with many other areas of the spec it seems to raise more questions than
providing answers. I really would appreciate any comments, different views,
clarifications
:09 Manuel Mall wrote:
I have started a white space handling Wiki page
(http://wiki.apache.org/xmlgraphics-fop/LineLayout/WhitespaceHandling).
As with many other areas of the spec it seems to raise more questions than
providing answers. I really would appreciate any comments, different views
On Wed, 19 Oct 2005 05:44 am, Jeremias Maerki wrote:
I've started to comment on the individual issues you listed and only
when I got to the examples I realized there must be something wrong.
You place the white-space-treatment after the white-space-collapse
but I think it is clear that the
22 matches
Mail list logo
