-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Auftrag
von J.Pietschmann
Gesendet: Monday, January 26, 2004 8:58 PM
An: [EMAIL PROTECTED]
Betreff: Re: RTF: white-space-treatment and linefeed-treatment
Peter Herweg wrote:
(2) I defer the processing of all
Peter Herweg wrote:
Maybe difficulties is the wrong word. Just a thing i have to care for. If i
do the processing of FOs in endBlock, i have to suppress the processing
within nested blocks. Or the nested blocks will be processed twice.
I think you can flush the queue each time a nested block
quite good.
Kind regards
Peter Herweg
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
J.Pietschmann
Sent: Tuesday, January 27, 2004 9:16 PM
To: [EMAIL PROTECTED]
Subject: Re: AW: RTF: white-space-treatment and linefeed-treatment
Peter Herweg wrote
Hello,
i am currently working on support for white-space-treatment and
linefeed-treatment for the RTF module. Of course i don't want to reinvent
the wheel, so i tried wanted Block.handleWhiteSpace method to do the job.
But when i read the text data which is passed to RtfHandler.characters
Peter Herweg wrote:
(2) I defer the processing of all inline-generating, text-containing FOs,
and process them in RtfHandler.endBlock.
I'd say start with this option, although I'm starting to believe we
could and should move whitespace processing to before the invocation
of the structure
Team,
I'm having some confusion with the
white-space-treatment property for a
block.(http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#white-space-treatment)
The default value is this property is
ignore-if-surrounding-linefeed, and here is its
definition in the spec: (sorry to torture you
Look here:
Specifies that any character flow object, except for
U+000A (linefeed) characters, whose character is
classified, before any linefeed-treatment handling is
considered, as white space in XML (or any sequence of
such character flow objects
Question: property white-space-collapse (Spec
7.15.12) is defined within both PageNumber.java and
PageNumberCitation.java as an integer, but according
to the spec this property is not defined for these two
FO's (example:
http://www.w3.org/TR/xsl/slice6.html#fo_page-number,
scroll down
Glen Mazza wrote:
Question: property white-space-collapse (Spec
7.15.12) is defined within both PageNumber.java and
PageNumberCitation.java as an integer, but according
to the spec this property is not defined for these two
FO's (example:
http://www.w3.org/TR/xsl/slice6.html#fo_page-number
J.Pietschmann wrote:
Copy+paste
Well, actually the FO classes were boostrapped by generating the Java
classes from an XML file derived from a draft of the spec itself.
Note: draft. Probably also some errors crept in during the process...
J.Pietschmann
I guess we have some cleanup to do--I'll take a look
at some of the FO's this weekend and report back to
the team on property-removals we may need. The
interesting FO's will be those which are actually
utilizing invalid properties in their processing
logic--hopefully there won't be many!
Glen
J.Pietschmann wrote:
Apropos aural properties: anyone with enough time at hand to
make a voice renderer based on FreeTTS? :-)
Actually, I have a strong interest in TTS. We are trying to work it into our
proofreading cycle, so the computer reads the text out loud to a proofreader
who is looking
J.Pietschmann wrote:
I had the same problem when I commited for the first time. As far as I
found out, you have to be subscribed to fop-cvs mail list using your
*apache email address* + first message may be postponed a little bit
by moderator (nobody knows who is it though :).
BTW I'm
J.Pietschmann wrote:
Well, the cvs commit command has to be invoked from within the checked out
tree. Otherwise no commit message is mailed at all.
For example
$pwd
$CWD is /usr/pietsch/gnu/fop
$cvs checkout xml-fop
$...
Change to xml-fop before committing at this place.
$ cd xml-fop
$
I have committed some changes to the trunk that clean up 1) tabs, 2) spaces
at end of lines, and 3) CR/LF line endings. These touched quite a few files,
mostly doc, but should have no effect other than to minimize future spurious
deltas. I do not see the auto mail messages coming from CVS related
Victor Mote wrote:
I have committed some changes to the trunk that clean up 1) tabs, 2) spaces
at end of lines, and 3) CR/LF line endings. These touched quite a few files,
mostly doc, but should have no effect other than to minimize future spurious
deltas. I do not see the auto mail messages
/show_bug.cgi?id=4171
white-space-collapse=false does not work
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
Title: RE: white-space
u can put #160; ( # 1 6 0 ;)
this will work.
rgds,
Rabi.
-Original Message-
From: Joerg Pietschmann [SMTP:[EMAIL PROTECTED]]
Sent: Friday, February 01, 2002 5:37 PM
To: FOP Dev
Subject: Re: white-space
I need white space between fields, how do I do
I need white space between fields, how do I do that?
fo:block font-size=10pt font-weight=bold font-family=sans-serif
text-indent=10pt
xsl:value-of select=city /, !--I NEED A WHITE SPACE HERE--
xsl:value-of select=state / !--I NEED WHITE SPACE
HERE-- xsl:value-of select
januari 2002 15:11
Aan: [EMAIL PROTECTED]
Onderwerp: white-space
I need white space between fields, how do I do that?
fo:block font-size=10pt font-weight=bold font-family=sans-serif
text-indent=10pt
xsl:value-of select=city /, !--I NEED A WHITE SPACE HERE--
xsl:value-of select=state
/show_bug.cgi?id=4171
white-space-collapse=false does not work
Summary: white-space-collapse=false does not work
Product: Fop
Version: all
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Blocker
Priority: Other
At 10:25 15-10-2001, [EMAIL PROTECTED] wrote:
When I create a FO document with fo:inline white-space-collapse=false
/fo:inline I see that in my final document I can get two spaces to separate
certain items. But when I change the document to a xsl stylesheet with FO I
stops working.
No - it's
22 matches
Mail list logo
