Re: Line breaks around dashes

2002-08-21 Thread J.Pietschmann

Jessica Perry Hekman wrote:
 Attached. It looks like every page-sequence starts over from zero -- 
 except the very first one, which starts from one.

This should be fixed now.

J.Pietschmann


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: Line breaks around dashes

2002-08-21 Thread Jessica Perry Hekman

On Thu, 22 Aug 2002, J.Pietschmann wrote:

 This should be fixed now.

It is. Thanks very much!

j

---
  Users complain that they receive too much spam, while spammers protest
messages are legal. -InfoWorld
  You do not have to do everything disagreeable that you have a right to
do. -Judith Martin (Miss Manners)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: Line breaks around dashes

2002-08-20 Thread J.Pietschmann

Karen Lease wrote:
 That's a good question. As far as I've seen there's nothing official in 
 the specification, so it's up to each implementation to handle this. I 
 believe it falls in the category of things which could be defined by the 
   user agent idea in FOP and then used by the line-breaking algorithm. 
 In the redesign branch of FOP, the line-breaking code assumes it has a 
 list of legal line-break characters; clearly this needs to depend on the 
 script, which isn't yet the case.

There seems to be a general consensus that a FO processor
has to be an Unicode compliant application, even though the
spec appears to carefully avoid to make this explicit. This
would mean implementing the Unicode TR14 line breaking
algorithm which is basically script independent (it
inherently handles *all* scripts), apart from cases which
are explicitely left to a higher application layer (which
I'd recommend to read as: let the user insert soft hyphens
and zero width spaces if he wants to have breaks).

TR14 needs a table for certain character properties be present,
which can be derived from the official database. We probably
need such a table for other purposes too, for example writing
direction and word separation. I fear an implementation which
is not too heavyweight could be tricky, however, there is a
report from the Unicode consortium which covers exactly this
topic, I just hadn't had time to read it yet.

J.Pietschmann


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: Line breaks around dashes

2002-08-20 Thread Jessica Perry Hekman

On Mon, 19 Aug 2002, J.Pietschmann wrote:

 HEAD doesn't work, check out fop-0_20_2-maintain.

Done.

Is fo:page-number/ broken on that branch? It was working fine in 0.20.4. 
However, in the version I checked out from cvs, calling it in some 
page-sequences returns the number 0, and then when eventually it does 
start working, it starts counting from 1, even though there were about 8 
rendered pages before that one.

j

---
  Users complain that they receive too much spam, while spammers protest
messages are legal. -InfoWorld
  You do not have to do everything disagreeable that you have a right to
do. -Judith Martin (Miss Manners)



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: Line breaks around dashes

2002-08-20 Thread J.Pietschmann

Jessica Perry Hekman wrote:
 Is fo:page-number/ broken on that branch? It was working fine in 0.20.4. 
 However, in the version I checked out from cvs, calling it in some 
 page-sequences returns the number 0, and then when eventually it does 
 start working, it starts counting from 1, even though there were about 8 
 rendered pages before that one.

I fiddled a bit with page number initialisation. Could
you post a small example which demonstrates the effect
you noticed? Use fo:block break-after=page/ to generate
pages to keep it short.

J.Pietschmann



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: Line breaks around dashes

2002-08-20 Thread Jessica Perry Hekman

On Tue, 20 Aug 2002, J.Pietschmann wrote:

 I fiddled a bit with page number initialisation. Could
 you post a small example which demonstrates the effect
 you noticed? Use fo:block break-after=page/ to generate
 pages to keep it short.

Attached. It looks like every page-sequence starts over from zero -- 
except the very first one, which starts from one. (You would have figured 
that out right away, but I had to say something more than just 
attached.)

j

---
  Users complain that they receive too much spam, while spammers protest
messages are legal. -InfoWorld
  You do not have to do everything disagreeable that you have a right to
do. -Judith Martin (Miss Manners)


?xml version=1.0 encoding=UTF-8?
fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;
  fo:layout-master-set
fo:page-sequence-master master-name=contents
  fo:single-page-master-reference master-reference=first-page/
  fo:repeatable-page-master-reference master-reference=simple/
/fo:page-sequence-master
fo:simple-page-master margin-right=.3in margin-left=.3in margin-bottom=.3in 
margin-top=.3in page-width=3.5in page-height=5.8in master-name=first-page
  fo:region-body margin-top=.2in/
  fo:region-before extent=0in/
/fo:simple-page-master
fo:simple-page-master margin-right=.3in margin-left=.3in margin-bottom=.3in 
margin-top=.3in page-width=3.5in page-height=5.8in master-name=simple
  fo:region-body margin-top=.2in/
  fo:region-before extent=.2in/
/fo:simple-page-master
fo:simple-page-master margin-right=.5in margin-left=.5in margin-bottom=1in 
margin-top=1in page-width=3.5in page-height=5.8in master-name=front
  fo:region-body margin-top=1in/
/fo:simple-page-master
fo:simple-page-master margin-right=.3in margin-left=.3in margin-bottom=.3in 
margin-top=.3in page-width=3.5in page-height=5.8in master-name=copyright
  fo:region-body margin-bottom=.2in/
  fo:region-after extent=.2in/
/fo:simple-page-master
  /fo:layout-master-set
  fo:page-sequence master-reference=front
fo:flow flow-name=xsl-region-body
  fo:blockThis is the first page, generated number: 
  fo:page-number/
/fo:block
  /fo:flow
/fo:page-sequence
fo:page-sequence master-reference=front
  fo:flow flow-name=xsl-region-body
fo:blockThis is the second page, generated number: 
fo:page-number/
  /fo:block
/fo:flow
/fo:page-sequence
fo:page-sequence master-reference=front
  fo:flow flow-name=xsl-region-body
fo:blockThis is the third page, generated number: 
fo:page-number/
  /fo:block
/fo:flow
/fo:page-sequence
fo:page-sequence format=1 master-reference=contents
  fo:static-content flow-name=xsl-region-before
fo:block text-align=center font-family=Times font-size=8ptStatic content
  /fo:block
/fo:static-content
fo:flow language=en flow-name=xsl-region-body
fo:block padding=14pt text-align=center font-family=Helvetica font-size=8pt
/fo:block

fo:block
  Page four, generated: fo:page-number /
  fo:block break-after=page/
  Page five, generated: fo:page-number /
  fo:block break-after=page/
  Page six, generated: fo:page-number /
/fo:block

/fo:flow

/fo:page-sequence

/fo:root


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]


Re: Line breaks around dashes

2002-08-20 Thread Peter B. West

J.Pietschmann wrote:

 TR14 needs a table for certain character properties be present,
 which can be derived from the official database. We probably
 need such a table for other purposes too, for example writing
 direction and word separation. I fear an implementation which
 is not too heavyweight could be tricky, however, there is a
 report from the Unicode consortium which covers exactly this
 topic, I just hadn't had time to read it yet.

Some form of character properties database is essential.  Not only line 
breaking but also bidi processing depend upon it.  In general, the only 
knowledge we can assume about the characteristics of the text we are 
processing is what is contained in the database.

Peter
-- 
Peter B. West  [EMAIL PROTECTED]  http://www.powerup.com.au/~pbwest/
Lord, to whom shall we go?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: Line breaks around dashes

2002-08-19 Thread Jessica Perry Hekman

On Mon, 19 Aug 2002, J.Pietschmann wrote:

 Unfortunately, FOP does not implement TR14, it treats nearly
 all characters except Unicode spaces as not allowing a break.
 You can insert a zero width space before and after the mdash
 in order to get the desired behaviour (as also defined by TR14).

That's a fine answer.

 Another caveat: FOP 0.20.4 has a bug in the white space width
 calculation, you'll have to get the 0.20.5cvs code from the
 repository directly or fall back to 0.20.3.

Hm. I don't mind falling back to 0.20.3 in theory. I just tried running 
the version I checked out of cvs, and found a bunch of problems:

* some stuff I'd asked to have centered is left-justified (perhaps all 
  centering is broken; I didn't check)
* some spacing between lines is way too big (padding? margins? I didn't 
  check closer)
* a graphic I include is rendered way too large
* most relevantly, the zero-width spaces are rendered as hash signs

I assume these are just problems which are going to be worked out before 
the next release, and that I should just fall back to 0.20.3; but if I did 
something wrong (like check out HEAD when I should have checked out a 
branch), please let me know.

j

---
  Users complain that they receive too much spam, while spammers protest
messages are legal. -InfoWorld
  You do not have to do everything disagreeable that you have a right to
do. -Judith Martin (Miss Manners)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: Line breaks around dashes

2002-08-19 Thread J.Pietschmann

Jessica Perry Hekman wrote:
 I assume these are just problems which are going to be worked out before 
 the next release, and that I should just fall back to 0.20.3; but if I did 
 something wrong (like check out HEAD when I should have checked out a 
 branch), please let me know.

HEAD doesn't work, check out fop-0_20_2-maintain.

J.Pietschmann


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: Line breaks around dashes

2002-08-19 Thread Karen Lease

Hi Jessica,

That's a good question. As far as I've seen there's nothing official in 
the specification, so it's up to each implementation to handle this. I 
believe it falls in the category of things which could be defined by the 
   user agent idea in FOP and then used by the line-breaking 
algorithm. In the redesign branch of FOP, the line-breaking code assumes 
it has a list of legal line-break characters; clearly this needs to 
depend on the script, which isn't yet the case.

Regards,
Karen

Jessica Perry Hekman wrote:

 Is there any way to ask FOP to allow line breaks before and after
 particular characters -- in my case, mdashes? Apologies if this should
 actually be specified in the FO; I've been trying to find a place in the
 FO spec which says how to specify legal breaking characters, and I've
 failed so far. It does seem to imply that a formatter should have access
 to rules for legal breaking characters per script.
 
 j
 
 ---
   Users complain that they receive too much spam, while spammers protest
 messages are legal. -InfoWorld
   You do not have to do everything disagreeable that you have a right to
 do. -Judith Martin (Miss Manners)
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]
 
 
 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]