Re: white-space-treatment property
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) The default value of whitespace treatment + linefeed treatment (which just converts the linefeed to a single space) should result in: "Here is sentence one. Here is sentence two.", It will do so anyway, reagardless of the white-space-treatment, because by default whitespace is collapsed. J.Pietschmann
Re: white-space-collapse property in PageNumber/PageNumberCitation
Victor Mote wrote: Actually, I have a strong interest in TTS. Check out http://sourceforge.net/projects/freetts/ Don't be carried away in the initial enthusiasm, it still sucks. But if your company has resources to spare to work on it, by all means try to do this! J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: white-space-collapse property in PageNumber/PageNumberCitation
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 at an original document (we convert old documents to text). Maybe someday ... after fonts ... after layout ... after layout strategy ... after API ... Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: white-space-collapse property in PageNumber/PageNumberCitation
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" <[EMAIL PROTECTED]> wrote: > 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 > > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, email: > [EMAIL PROTECTED] > __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: white-space-collapse property in PageNumber/PageNumberCitation
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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: white-space-collapse property in PageNumber/PageNumberCitation
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, scroll down to applicable properties). Am I missing something here--why do we have W-S-C defined for these two? Copy+paste, I think, and a lot of inertia. You've got hyphenation props on Character as well as aural props and other stuff all over the place. Apropos aural properties: anyone with enough time at hand to make a voice renderer based on FreeTTS? :-) J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: white-space & line-ending changes
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 subscribed to fop-cvs with my spam-filtered address and have no
problems.
But your commit messages nevertheless are sent only from [EMAIL PROTECTED]
My conclusion was based on a quick analysis of $CVSROOT/CVSROOT/loginfo file
at cvs.apache.org. This one usually defines an action being performed on each
commit into a cvs repository. Our one runs $CVSROOT/CVSROOT/log_accum.pl
script, which in turn (I should admit I'm not perl expert) actually
consolidates message and sends it to the mail list through sendmail program
from $ENV{'USER'}@apache.org address.
And if commit messages are always sent from $ENV{'USER'}@apache.org address,
this one should be subscribed to the list.
May be there is another door though.
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
RE: white-space & line-ending changes
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 > $ cvs commit > No parameters necessary. If the command asks you for a module to commit, > or for logging in again, you made something wrong. > BTW I'm subscribed to fop-cvs with my spam-filtered address and have no > problems. The commit was working, and I could even see that it was trying to create a mail message -- it just wasn't getting mailed. I followed Oleg's suggestion of switching my subscription to fop-cvs to my apache.org mailing address & that seems to have fixed the problem. I am not sure how to reconcile that with your experience -- maybe it just has to be touched & maybe there is more than one way to do that. I guess I don't care enough to find out. Thank you both for your help. BTW, it is good to have you back. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: white-space & line-ending changes
Oleg Tkachenko wrote: 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 coming from CVS related to these changes -- perhaps it is smart enough to know that these are innocuous, or perhaps there is something wrong with my mail account. 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 :). 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 $ cvs commit No parameters necessary. If the command asks you for a module to commit, or for logging in again, you made something wrong. BTW I'm subscribed to fop-cvs with my spam-filtered address and have no problems. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: white-space & line-ending changes
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 coming from CVS related to these changes -- perhaps it is smart enough to know that these are innocuous, or perhaps there is something wrong with my mail account. 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 :). -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: white-space
Title: RE: white-space u can put ( & # 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 that? ... > , >
Re: white-space
> I need white space between fields, how do I do that? ... > , >
RE: white-space
You can use the concat function, just to put a space after a value. Just like this: -Oorspronkelijk bericht- Van: Gus Delgado [mailto:[EMAIL PROTECTED]] Verzonden: donderdag 31 januari 2002 15:11 Aan: [EMAIL PROTECTED] Onderwerp: white-space > I need white space between fields, how do I do that? > > text-indent="10pt"> > , > > > > So that the address will look like this > > Austin, TX 78758 > > instead of, > Austin,TX78758 > > Thanks in advance for your help! > > > -Gus > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
