DO NOT REPLY [Bug 11614] - DocBook programlistings are garbled in PDF, etc

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11614

DocBook programlistings are garbled in PDF, etc





--- Additional Comments From [EMAIL PROTECTED]  2002-10-06 10:57 ---
For me, I upgraded todocbook-xsl-1.55 and it now works for me.

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

DO NOT REPLY [Bug 11529] - , DocBook 1.53 and FOP don't want to play nice.

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11529

, DocBook 1.53 and FOP don't want to play nice.

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WORKSFORME



--- Additional Comments From [EMAIL PROTECTED]  2002-10-06 10:58 ---
Works now with Docbook 1.55 stylesheets

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

DO NOT REPLY [Bug 13345] New: - table-cell border information seems to be ignored?

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13345

table-cell border information seems to be ignored?

   Summary: table-cell border information seems to be ignored?
   Product: Fop
   Version: 0.20.4
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: pdf renderer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


In code like:





There is not border rendered for the table cell using .20.4.

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

cvs commit: xml-fop/src/org/apache/fop/fo/pagination PageMasterAlternatives.java PageCondition.java

[pbwest]

pbwest  2002/10/06 06:56:15

  Added:   src/org/apache/fop/fo/pagination Tag: FOP_0-20-0_Alt-Design
PageMasterAlternatives.java PageCondition.java
  Log:
  Classes for constructing page master alternatives.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.2.1   +64 -0 
xml-fop/src/org/apache/fop/fo/pagination/Attic/PageMasterAlternatives.java
  
  
  
  
  1.1.2.1   +49 -0 
xml-fop/src/org/apache/fop/fo/pagination/Attic/PageCondition.java
  
  
  
  

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

cvs commit: xml-fop/src/org/apache/fop/fo/pagination FoSinglePageMasterReference.java FoSimplePageMaster.java

[pbwest]

pbwest  2002/10/06 07:01:19

  Modified:src/org/apache/fop/fo/pagination Tag: FOP_0-20-0_Alt-Design
FoSinglePageMasterReference.java
FoSimplePageMaster.java
  Log:
  Get master-name directly from propertySet[].
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.2.2   +6 -8  
xml-fop/src/org/apache/fop/fo/pagination/Attic/FoSinglePageMasterReference.java
  
  Index: FoSinglePageMasterReference.java
  ===
  RCS file: 
/home/cvs/xml-fop/src/org/apache/fop/fo/pagination/Attic/FoSinglePageMasterReference.java,v
  retrieving revision 1.1.2.1
  retrieving revision 1.1.2.2
  diff -u -r1.1.2.1 -r1.1.2.2
  --- FoSinglePageMasterReference.java  7 May 2002 05:50:04 -   1.1.2.1
  +++ FoSinglePageMasterReference.java  6 Oct 2002 14:01:19 -   1.1.2.2
  @@ -16,20 +16,18 @@
   import org.apache.fop.xml.XMLEvent;
   import org.apache.fop.apps.FOPException;
   import org.apache.fop.fo.expr.PropertyException;
  -import org.apache.fop.datastructs.SyncedCircularBuffer;
  +import org.apache.fop.datastructs.SyncedXmlEventsBuffer;
   
  -public class FoSinglePageMasterReference implements SubSequenceSpecifier {
  -
  -private FOAttributes attributes
  -private masterReference;
  +public class FoSinglePageMasterReference extends FONode {
   
   public FoSinglePageMasterReference
   (SyncedCircularBuffer xmlevents, XMLEvent event) throws FOPException {
  -
  + super(foTree, FObjectNames.SINGLE_PAGE_MASTER_REFERENCE, parent,
  + event, FOPropertySets.SEQ_MASTER_SET);
   }
   
   public getMasterReference() {
  -return masterReference;
  +return getPropertyValue(PropNames.MASTER_REFERENCE);
   }
   
   }// FoSinglePageMasterReference
  
  
  
  1.1.2.6   +5 -15 
xml-fop/src/org/apache/fop/fo/pagination/Attic/FoSimplePageMaster.java
  
  Index: FoSimplePageMaster.java
  ===
  RCS file: 
/home/cvs/xml-fop/src/org/apache/fop/fo/pagination/Attic/FoSimplePageMaster.java,v
  retrieving revision 1.1.2.5
  retrieving revision 1.1.2.6
  diff -u -r1.1.2.5 -r1.1.2.6
  --- FoSimplePageMaster.java   2 Oct 2002 15:19:59 -   1.1.2.5
  +++ FoSimplePageMaster.java   6 Oct 2002 14:01:19 -   1.1.2.6
  @@ -31,8 +31,6 @@
   private static final String tag = "$Name$";
   private static final String revision = "$Revision$";
   
  -private String masterName;
  -
   /**
* @param foTree the FO tree being built
* @param parent the parent FONode of this node
  @@ -40,18 +38,10 @@
* this node
*/
   public FoSimplePageMaster(FOTree foTree, FONode parent, XMLEvent event)
  -throws Tree.TreeException, FOPException, PropertyException
  +throws Tree.TreeException, FOPException
   {
   super(foTree, FObjectNames.SIMPLE_PAGE_MASTER, parent, event,
 FOPropertySets.LAYOUT_SET);
  -System.out.println("FOAttributes: " + event);
  -// Check that the property has been set
  -PropertyValue name = propertySet[PropNames.MASTER_NAME];
  -if (name == null)
  -throw new PropertyException("master-name property not set");
  -if (name.getType() != PropertyValue.NCNAME)
  -throw new PropertyException("master-name property not an NCName.");
  -masterName = ((NCName)name).getNCName();
   // Process regions here
   XMLEvent ev = xmlevents.getEndElement(event);
   }
  @@ -59,7 +49,7 @@
   /**
* @return a String with the "master-name" attribute value.
*/
  -public String getMasterName() {
  -return masterName;
  +public String getMasterName() throws PropertyException {
  +return ((NCName)propertySet[PropNames.MASTER_NAME]).getNCName();
   }
   }
  
  
  

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

cvs commit: xml-fop/src/org/apache/fop/fo/pagination FoPageSequenceMaster.java

[pbwest]

pbwest  2002/10/06 07:15:11

  Modified:src/org/apache/fop/fo/pagination Tag: FOP_0-20-0_Alt-Design
FoPageSequenceMaster.java
  Log:
  Remove all SubSequenceSpecifier code.
  Removed no-event constructor.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.2.5   +14 -93
xml-fop/src/org/apache/fop/fo/pagination/Attic/FoPageSequenceMaster.java
  
  Index: FoPageSequenceMaster.java
  ===
  RCS file: 
/home/cvs/xml-fop/src/org/apache/fop/fo/pagination/Attic/FoPageSequenceMaster.java,v
  retrieving revision 1.1.2.4
  retrieving revision 1.1.2.5
  diff -u -r1.1.2.4 -r1.1.2.5
  --- FoPageSequenceMaster.java 2 Oct 2002 15:19:59 -   1.1.2.4
  +++ FoPageSequenceMaster.java 6 Oct 2002 14:15:11 -   1.1.2.5
  @@ -20,11 +20,14 @@
   import org.apache.fop.apps.FOPException;
   import org.apache.fop.fo.expr.PropertyException;
   import org.apache.fop.fo.Properties;
  +import org.apache.fop.fo.PropNames;
   import org.apache.fop.fo.FOPropertySets;
   import org.apache.fop.fo.FObjectNames;
   import org.apache.fop.fo.FOTree;
   import org.apache.fop.fo.FONode;
   import org.apache.fop.datastructs.Tree;
  +import org.apache.fop.datatypes.PropertyValue;
  +import org.apache.fop.datatypes.NCName;
   
   /**
* Implements the fo:page-sequence-master flow object.  These Fos are
  @@ -42,30 +45,19 @@
   
   private ArrayList subSequenceList = new ArrayList(1);
   
  -public FoPageSequenceMaster
  -(FOTree foTree, FONode parent, String masterName)
  -throws Tree.TreeException, FOPException, PropertyException
  -{
  -super(foTree, FObjectNames.PAGE_SEQUENCE_MASTER, parent, null,
  -  FOPropertySets.LAYOUT_SET);
  -this.masterName = masterName;
  -}
  -
   public FoPageSequenceMaster(FOTree foTree, FONode parent, XMLEvent event)
   throws Tree.TreeException, FOPException, PropertyException
   {
   super(foTree, FObjectNames.PAGE_SEQUENCE_MASTER, parent, event,
  -  FOPropertySets.LAYOUT_SET);
  -if (event == null) {
  -System.out.println("Null event; throwing FOPException");
  -throw new FOPException
  -("Null event passed to FoPageSequenceMaster constructor");
  -}
  -try {
  -masterName = foAttributes.getFoAttrValue("master-name");
  -} catch (PropertyException e) {
  -throw new FOPException(e.getMessage());
  -}
  +  FOPropertySets.SEQ_MASTER_SET);
  +// Check that the property has been set
  +PropertyValue name = propertySet[PropNames.MASTER_NAME];
  +if (name == null)
  +throw new PropertyException("master-name property not set");
  +if (name.getType() != PropertyValue.NCNAME)
  +throw new PropertyException
  +("master-name property not an NCName.");
  +masterName = ((NCName)name).getNCName();
   // Process sequence members here
   LinkedList list = new LinkedList();
   list.add((Object)(new XMLEvent.UriLocalName
  @@ -108,75 +100,4 @@
   return masterName;
   }
   
  -/**
  - * SubSequenceSpecifer objects contain the information about an
  - * individual sub-sequence.  They do not extend FONode
  - * because they are maintained only in the subSequenceList of an
  - * FoPageSequenceMaster object.
  - * When created from fo:single-page-master-reference,
  - * fo:repeatable-page-master-reference or
  - * fo:repeatable-page-master-alternatives and
  - * fo:conditional-page-master-references, the attributes on those
  - * nodes are merged into the attributes of the parent
  - * FoPageSequenceMaster object, so that they will be available
  - * to any children of this node, both
  - * during the parsing of the fo input and during the page construction
  - * process.
  - * Note that there is some ambiguity about the place of properties
  - * defined on the members of the layout-master-set subtree.  Do
  - * these properties participate in the properties environment of
  - * elements in page-sequence subtrees?
  - */
  -public class SubSequenceSpecifier {
  -public static final int UNBOUNDED = -1;
  -private int minRepeats = 1;
  -private int maxRepeats = UNBOUNDED;
  -private ArrayList conditionals = new ArrayList(1);
  -
  -public SubSequenceSpecifier() {
  -// Insert the SSS into the parent FoPageSequenceMaster's
  -// list
  -FoPageSequenceMaster.this.subSequenceList.add(this);
  -}
  -
  -public SubSequenceSpecifier(int maxRepeats) {
  -this();
  -minRepeats = 0;
  -this.maxRe

cvs commit: xml-fop/src/org/apache/fop/fo/pagination FoLayoutMasterSet.java

[pbwest]

pbwest  2002/10/06 07:18:05

  Modified:src/org/apache/fop/fo/pagination Tag: FOP_0-20-0_Alt-Design
FoLayoutMasterSet.java
  Log:
  Removed SubSequenceSpecifier references.
  Simplified exception catching and handling.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.2.5   +9 -31 
xml-fop/src/org/apache/fop/fo/pagination/Attic/FoLayoutMasterSet.java
  
  Index: FoLayoutMasterSet.java
  ===
  RCS file: 
/home/cvs/xml-fop/src/org/apache/fop/fo/pagination/Attic/FoLayoutMasterSet.java,v
  retrieving revision 1.1.2.4
  retrieving revision 1.1.2.5
  diff -u -r1.1.2.4 -r1.1.2.5
  --- FoLayoutMasterSet.java2 Oct 2002 15:19:59 -   1.1.2.4
  +++ FoLayoutMasterSet.java6 Oct 2002 14:18:05 -   1.1.2.5
  @@ -15,9 +15,6 @@
   import org.apache.fop.xml.SyncedXmlEventsBuffer;
   import org.apache.fop.datastructs.Tree;
   import org.apache.fop.fo.pagination.FoPageSequenceMaster;
  -import org.apache.fop.fo.pagination.FoPageSequenceMaster.SubSequenceSpecifier;
  -import org.apache.fop.fo.pagination
  -.FoPageSequenceMaster.SubSequenceSpecifier.ConditionalPageMasterReference;
   
   /*
* $Id$
  @@ -66,8 +63,7 @@
   }
   
   /**
  - * Set up all the page masters.  !!!Note that the masters are not entered
  - * in the FO tree.!!!
  + * Set up all the page masters.
* fo:layout-master-set contents are
* (simple-page-master|page-sequence-master)+
*/
  @@ -88,12 +84,7 @@
   localName = ev.getLocalName();
   if (localName.equals("simple-page-master")) {
   System.out.println("Found simple-page-master");
  -try {
  -simple = new FoSimplePageMaster(foTree, this, ev);
  -} catch (Tree.TreeException e) {
  -throw new FOPException
  -("TreeException: " + e.getMessage());
  -}
  +simple = new FoSimplePageMaster(foTree, this, ev);
   simpleName = simple.getMasterName();
   if (pageMasters == null)
   pageMasters = new HashMap();
  @@ -112,22 +103,6 @@
   ("simple-page-master master-name clash in "
+ "simplePageMasters: " + simpleName);
   simplePageMasters.put(simpleName, simple);
  -FoPageSequenceMaster seqMaster;
  -try {
  -// Construct a new PageSequenceMaster
  -seqMaster = new FoPageSequenceMaster
  -(foTree, this, simpleName);
  -} catch(Tree.TreeException e) {
  -throw new FOPException
  -("TreeException: " + e.getMessage());
  -}
  -// Construct a SubSequence
  -SubSequenceSpecifier subSeq =
  -seqMaster.new SubSequenceSpecifier();
  -// Construct a default ConditionalPageMasterReference
  -ConditionalPageMasterReference cond = subSeq.new
  -ConditionalPageMasterReference(simpleName);
  -pageMasters.put(simpleName, seqMaster);
   } else if (localName.equals("page-sequence-master")) {
   System.out.println("Found page-sequence-master");
   try {
  @@ -153,7 +128,10 @@
   // Masters exhausted
   }
   catch (PropertyException e) {
  -throw new FOPException("PropertyException: " + e.getMessage());
  +throw new FOPException(e);
  +}
  +catch (Tree.TreeException e) {
  +throw new FOPException(e);
   }
   }
   
  
  
  

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

cvs commit: xml-fop/src/org/apache/fop/fo FoRoot.java

[pbwest]

pbwest  2002/10/06 07:28:02

  Modified:src/org/apache/fop/fo Tag: FOP_0-20-0_Alt-Design FoRoot.java
  Log:
  Changed exception handler.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.2.7   +5 -5  xml-fop/src/org/apache/fop/fo/Attic/FoRoot.java
  
  Index: FoRoot.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/Attic/FoRoot.java,v
  retrieving revision 1.1.2.6
  retrieving revision 1.1.2.7
  diff -u -r1.1.2.6 -r1.1.2.7
  --- FoRoot.java   2 Oct 2002 15:14:21 -   1.1.2.6
  +++ FoRoot.java   6 Oct 2002 14:28:02 -   1.1.2.7
  @@ -58,7 +58,7 @@
   /**
* Process the FO tree, starting with this fo:root element.
* N.B. the FO tree is a collection of trees.
  - * Trees only occur with fo:flow and fo:static-content.  These will
  + * Layout trees only occur with fo:flow and fo:static-content.  These will
* be built at the appropriate places as part of the FO tree processing.
* Terminates at the completion of FO tree processing.
* 
  @@ -87,7 +87,7 @@
   ev = xmlevents.expectStartElement
   (XMLNamespaces.XSLNSpaceIndex, "layout-master-set");
   } catch (NoSuchElementException e) {
  -throw new FOPException(e.getMessage());
  +throw new FOPException(e);
   }
   // Process the layout-master-set
   try {
  
  
  

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

RE:

[Arved Sandstrom]

> -Original Message-
> From: Peter B. West [mailto:[EMAIL PROTECTED]]
> Sent: September 30, 2002 11:24 PM
> To: [EMAIL PROTECTED]
> Subject: Re: 
>
> Arved Sandstrom wrote:
> >>-Original Message-
> >>From: Tony Graham [mailto:[EMAIL PROTECTED]]
>
> >>Peter B. West wrote at 30 Sep 2002 13:28:18 +1000:
> >> > Tony Graham wrote:
> >> > > [EMAIL PROTECTED] wrote at 27 Sep 2002 16:44:32 -0300:
> >>...
> >> > >  > That means  "-", "#12235" , etc are characters, while
> >>"'1'" is not.
> >> > >
> >> > > ⿋ is a character reference.  '#12235' is how you
> talk about a
> >> > > character's code point, although the hexadecimal representation is
> >> > > usually preferable.
> >> > >
> >> > > In XSL terms, "'1'" is a one-character string literal, but
> while you
> >> > > could claim that it is one character, there's no XSL
> >>conversion from a
> >> > > string to a character, so 
> >>should fail.
> >> >
> >> > Tony,
> >> >
> >> > I don't think this gets us out of difficulty.  A casual inspection
> >>
> >>Forgive me, but I wasn't trying to get anybody out of any difficulty,
> >>I was just trying to keep the terminology accurate.
> >>
> >>...
> >> > So how do I represent a character?
> >> >
> >> > To me, the cleanest, least ambiguous way is to represent a
> 
> >> > attribute assignment value with "''" - a string literal of
> >> > length 1.
> >>
> >>Except that you know that that's not specified among the allowed
> >>conversions.
> >>
> >>The interesting thing is that 'character' doesn't appear in the
> >>productions in Section 5.9, Expressions, of the XSL Recommendation.
> >>Now there's a question for [EMAIL PROTECTED]!
> >>
> >>I think that you represent a character as a single character, e.g.,
> >>character="c", or as a numeric character reference, e.g.,
> >>character="
".
> >
> >
> > I agree with this last, after having digested everything.
> >
> > Point is well taken that we have some points to nitpick with
> xsl-editors,
> > mostly about disambiguating some of the language.
>
> Arved,
>
> Help me here. I must be missing something.  What is it that you agree
> with?  That the spec, as worded, leaves us with
>   character="c"
> or
>   character="c"
> which amounts to the same thing?

Yes, this is what I agree with.

> If so, fair enough.  Do you also agree that "c" is an NCName?  And that
>   character="-"
> is a parsing error?

Well, the production for NCName doesn't live in isolation, with reference to
http://www.w3.org/TR/REC-xml-names/#ns-decl. Yes, "c" fits the production,
but it's really an NCName when you have also declared the namespace.

Why is character="-" a parsing error? The XML Recommendation has at least
one example of an attribute value that contains a hyphen.

Maybe _I_ am missing something here. ;-)

> As far as I can see, the only immediate ways forward are to descend into
> the mire of context dependent parsing (which the editors have recently
> formally decided that we must do in respect of "format") or apply our
> own disambiguating condition.  How are you intending to implement
> ?

By storing it as a Unicode value according to the XML Rec production

Char::=#x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] |
[#x1-#x10]

It will depend on the implementation library. ICU for example has UChar and
UChar32 types.

Regards,
Arved


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

Re:

[J.Pietschmann]

Arved Sandstrom wrote:
> Why is character="-" a parsing error? The XML Recommendation has at least
> one example of an attribute value that contains a hyphen.

This comes from assuming that every unqoted sequence of characters which
is not a number, mesutrement or a color has to be interpreted as NCName,
as the grammar suggests, and IIRC a NCName must not start with a hyphen.
This means
  hyphenation-char="-"
can't parse as number, can't parse as string, can't parse as color, can't
parse as NCName  -> parsing error.
Interestingly
  hyphenation-char="-1"
would parse, but certainly can't be converted to a char
Some other niceties:
  hyphenation-char="1*4"
would this make the hyphenation charater be "4"?
Can
  hyphenation-char="1 div 4"
be converted to ¼?  I know this becomes silly.

>>How are you intending to implement
>>?
> 
> By storing it as a Unicode value according to the XML Rec production

Functions complicate matters, and something like
   hyphenation-char="from-table-column('hyphenation-char')"
might even make some sense.

J.Pietschmann


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

Re:

[J.Pietschmann]

Peter B. West wrote:
>> Just for curiosity: what should happen if the following snippet
>> is used:
>>  
>>
> 
> 
> This looks OK.

I see potential for an Obfuscated FO Code Contest :-)

J.Pietschmann


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

RE:

[Arved Sandstrom]

> -Original Message-
> From: J.Pietschmann [mailto:[EMAIL PROTECTED]]
> Sent: October 6, 2002 12:00 PM
> To: [EMAIL PROTECTED]
> Subject: Re: 
>
>
> Arved Sandstrom wrote:
> > Why is character="-" a parsing error? The XML Recommendation
> has at least
> > one example of an attribute value that contains a hyphen.
>
> This comes from assuming that every unqoted sequence of characters which
> is not a number, mesutrement or a color has to be interpreted as NCName,
> as the grammar suggests, and IIRC a NCName must not start with a hyphen.
> This means
>   hyphenation-char="-"
> can't parse as number, can't parse as string, can't parse as color, can't
> parse as NCName  -> parsing error.

Hi Joerg

Can you cite the specific productions that lead to this conclusion? I am not
saying that you are wrong but I can't find it.

I must be tired. ;-) I just looked at the XML 1.1 production for AttValue
which is

AttValue::='"' ([^<&"] | Reference)* '"'
   |  "'" ([^<&'] | Reference)* "'"

and I see a prohibition here on using a literal '<' or '&' in the attribute
value, anywhere. But I see nothing about '-'.

If the grammar of the recommendations leads to the conclusion that

character="-"

is not OK, then this just simply offends my common sense.

Arved


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

Re: fonts

[J.Pietschmann]

Victor Mote wrote:
> I am thinking through ways to eliminate as much user involvement in using
> non-base-14 fonts as possible. Is there a performance benefit to parsing the
> XML metric files instead of extracting the information directly from the
> font file itself at runtime?

Well, as far as I understand TTF and PFB files have a directory
and lots of pointers to other parts of the file. The metric
extractor loads the whole file into memory, for convenience.
This can be a significant memory load, and all the glyph
geometry definitions take up space unnecessarily.
This could probably be avoided using the RandomAccessFile class,
but I expect performance going down the toilet in this case.
Another point, important IMO, is that the metrics file can be
edited after extraction. Some fonts contain awful data.

I agree that user fonts should be made more usable, for example
by integrating a one step font metrics generation and installation
into the main command line application. Another possibility would
be a metrics file repository, combined with a tool which searches
the repository and the locally installed fonts and then installs
the font in the FOP config.

J.Pietschmann


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

Re:

[J.Pietschmann]

Arved Sandstrom wrote:
> Can you cite the specific productions that lead to this conclusion? I am not
> saying that you are wrong but I can't find it.
> 
> I must be tired. ;-) I just looked at the XML 1.1 production for AttValue
> which is

Don't look at XML AttValue, look at the XSLFO property expression language.
Somehow it is implicit that all attributes in a XSLFO document are parsed
as expressions which are defined in 5.9 "Expressions". Refer specifically
to 5.9.3 "Basics". A single hyphen is not a valid expression according to
the XSLFO expression grammar.
Maybe some fallbacks are implicit somewhere, I don't know.

J.Pietschmann


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

RE:

[Arved Sandstrom]

> -Original Message-
> From: J.Pietschmann [mailto:[EMAIL PROTECTED]]
> Sent: October 6, 2002 12:39 PM
> To: [EMAIL PROTECTED]
> Subject: Re: 
>
> Arved Sandstrom wrote:
> > Can you cite the specific productions that lead to this
> conclusion? I am not
> > saying that you are wrong but I can't find it.
> >
> > I must be tired. ;-) I just looked at the XML 1.1 production
> for AttValue
> > which is
>
> Don't look at XML AttValue, look at the XSLFO property expression
> language.
> Somehow it is implicit that all attributes in a XSLFO document are parsed
> as expressions which are defined in 5.9 "Expressions". Refer specifically
> to 5.9.3 "Basics". A single hyphen is not a valid expression according to
> the XSLFO expression grammar.
> Maybe some fallbacks are implicit somewhere, I don't know.

An Expr can be a Literal, the production for which is

'"' [^"]* '"'
| "'" [^']* "'"

If I look at the first alternative,

'"' [^"]* '"'

it seems to me that I have pretty considerable leeway, and "-" isn't ruled
out at all.

Arved


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

Re:

[J.Pietschmann]

Arved Sandstrom wrote:
> An Expr can be a Literal, the production for which is
> 
> '"' [^"]* '"'
> | "'" [^']* "'"
> 
> If I look at the first alternative,
> 
> '"' [^"]* '"'
> 
> it seems to me that I have pretty considerable leeway, and "-" isn't ruled
> out at all.

Erm, the expression is supposed to be inside the XML attribute quotes,
for example hyphenation-char="'-'" would be ok (literal, second
production), but hyphenation-char="-" does not match the literal
production, nor any other (except "operator"). Unless I missed
something, of course.

J.Pietschmann


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

RE:

[Arved Sandstrom]

> -Original Message-
> From: J.Pietschmann [mailto:[EMAIL PROTECTED]]
> Sent: October 6, 2002 1:29 PM
> To: [EMAIL PROTECTED]
> Subject: Re: 
> 
> 
> Arved Sandstrom wrote:
> > An Expr can be a Literal, the production for which is
> > 
> > '"' [^"]* '"'
> > | "'" [^']* "'"
> > 
> > If I look at the first alternative,
> > 
> > '"' [^"]* '"'
> > 
> > it seems to me that I have pretty considerable leeway, and "-" 
> isn't ruled
> > out at all.
> 
> Erm, the expression is supposed to be inside the XML attribute quotes,
> for example hyphenation-char="'-'" would be ok (literal, second
> production), but hyphenation-char="-" does not match the literal
> production, nor any other (except "operator"). Unless I missed
> something, of course.

And unless _I_ am missing something, "-" precisely matches that production.

You are looking at

"'" [^']* "'"

but I am looking at

'"' [^"]* '"'

According to the latter I can absolutely do "-".

Arved


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

DO NOT REPLY [Bug 13347] New: - fo:table with inline-progression-dimension in %

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13347

fo:table with inline-progression-dimension in %

   Summary: fo:table with inline-progression-dimension in %
   Product: Fop
   Version: 0.20.4
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: Normal
  Priority: Other
 Component: general
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


According to specification: http://www.w3.org/TR/xsl/slice6.html#fo_table
it should be possible to enter a procentage as inline-progression-dimension:


...

in the spec. it says under a Note:
---
The use of the "proportional-column-width()" function is only permitted when 
the fixed table layout is used.

If the use of proportional column widths are desired on a table of an unknown 
explicit width, the inline-progression-dimension cannot be specified to 
be "auto". Instead, the width must be specified as a percentage. For example, 
setting table-layout="fixed" and inline-progression-dimension="100%" would 
allow proportional column widths while simultaneously creating a table as wide 
as possible in the current context.

---
however when using FOP with a % it gives an ERROR:

[INFO] FOP 0.20.4rc
[INFO] building formatting object tree
[ERROR] Error in inline-progression-dimension property value '100%': 
org.apache.fop.fo.expr.PropertyException: No conversion defined
[INFO] [1]
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[INFO] Parsing of document complete, stopping renderer

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

Re:

[J.Pietschmann]

Arved Sandstrom wrote:
> And unless _I_ am missing something, "-" precisely matches that production.
> 
> You are looking at
> 
> "'" [^']* "'"
> 
> but I am looking at
> 
> '"' [^"]* '"'
> 
> According to the latter I can absolutely do "-".

Well, in
   hyphenation-char="-"
the hyphen is the expression, not "the hyphen surrounded by double
quotes". As I said, unless I'm something missing, the FO property
expression is the value of the XML attribute, which in turn is the
hyphen, because the double quotes are part of the XML syntax and
are stripped by the XML parser. The XSLFO property expression parser
gets the hyphen, without any quotes, double, or single. And without
the quotes, it does not match either of the two productions for literal.
This is the problem here.

Perhaps I should have written that
   hyphenation-char="'-'"
and
   hyphenation-char='"-"'
as well as
 hyphenation-char='"-"'
are legal, while neiter
 hyphenation-char='-'
nor
 hyphenation-char="-"
are ok.

J.Pietschmann


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

RE:

[Arved Sandstrom]

> -Original Message-
> From: J.Pietschmann [mailto:[EMAIL PROTECTED]]
> Sent: October 6, 2002 2:15 PM
> To: [EMAIL PROTECTED]
> Subject: Re: 
>
>
> Arved Sandstrom wrote:
> > And unless _I_ am missing something, "-" precisely matches that
> production.
> >
> > You are looking at
> >
> > "'" [^']* "'"
> >
> > but I am looking at
> >
> > '"' [^"]* '"'
> >
> > According to the latter I can absolutely do "-".
>
> Well, in
>hyphenation-char="-"
> the hyphen is the expression, not "the hyphen surrounded by double
> quotes". As I said, unless I'm something missing, the FO property
> expression is the value of the XML attribute, which in turn is the
> hyphen, because the double quotes are part of the XML syntax and
> are stripped by the XML parser. The XSLFO property expression parser
> gets the hyphen, without any quotes, double, or single. And without
> the quotes, it does not match either of the two productions for literal.
> This is the problem here.
>
> Perhaps I should have written that
>hyphenation-char="'-'"
> and
>hyphenation-char='"-"'
> as well as
>  hyphenation-char='"-"'
> are legal, while neiter
>  hyphenation-char='-'
> nor
>  hyphenation-char="-"
> are ok.

Yes, I see your point.

I think they screwed up the grammar. As I stated before, I find it ludicrous
that character="-" would not be OK.

Arved


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

Re: fonts

[Jeremias Maerki]

Hi Victor

On 05.10.2002 22:51:28 Victor Mote wrote:
> Jeremias & other FOP Developers:
> 
> In addition to OpenType support, the other goal that I had for font work is
> to support arbitrary fonts. My initial thoughts in this area revolved around
> using the Java 2D capabilities. I understood that the GraphicsEnvironment
> can only see what the O/S shows it, but it did not immediately dawn on me
> that the more popular O/Ss for running FOP are probably Linux & Unix may not
> have a concept of font registration like Windows & Mac do. (If there is a
> way to register fonts in the character environments of these platforms in
> such a manner that java can see them, please let me know -- I have looked
> for this, but have not found it.)

Don't ask me for details (because I wasn't directly involved) but we had
to register new fonts with Linux so they got available in Batik for SVG.
So there seems to be some kind of font registry in Linux. Don't know
about the other unixes but I guess they will be the same.

> Question: Is it therefore fair to conclude that the reason for using the
> generated XML metric files is to provide a platform-neutral way of getting
> such information, especially for non-graphical environments? The following
> discussion assumes that the answer to this question is "yes".

Not really. I think it's more of a historical thing. In the beginning
there was a class for each of the base 14 fonts (still in use today).
These classes are generated from XML files in the codegen directory.
Then, when I started to get involved, I finished work by others so we
could programmatically register Java classes generated from XML font
metric files (almost the same as today) in FOP. Tore Engvig then took
over, implemented TrueType support and provided a way for FOP to load
the XML font metric files directly. That's how things are today.

> I am thinking through ways to eliminate as much user involvement in using
> non-base-14 fonts as possible. Is there a performance benefit to parsing the
> XML metric files instead of extracting the information directly from the
> font file itself at runtime? If so, then perhaps I should just leave this
> alone. If not, then I see some options for possible improvement, listed from
> least radical to most.

I don't know what would be faster. We'd have to do some performance
measurings. As Joerg said, there's a benefit of being able to edit the
XML font metrics. You may have read the recent problem Paul Thibodeaux
reported with a PS Type 1 font. I've had this kind of problems before.
The reason for that is that currently, only the PFM file of a font is
used to generate the XML font metrics file. The PFM lacks certain values
that subsequently have to be guessed. These guesses tend to be wrong
relatively often. To fix this FOP would have to learn the ability to
also parse the AFM and maybe values from the PFB. I think the TrueType
support may have similar problem but far less often. I'm not sure
because I don't work with TrueType fonts.

> 1. Replace current font-by-font configuration item with a path to the font
> file itself. When the font is used in a session, parse the metric
> information in real time from the font file.
>
> 2. Add a configuration item that contains a PATH-like list of directories in
> which font files are located. When a font is requested in a session, search
> the path for the font file, parse it, and use it. (There would seem to be a
> performance penalty for this, so it should be optional).
> 
> 3. [This one is only half-baked]. Extend or otherwise hack the
> GraphicsEnvironment and/or java.awt.font classes to "see" non-registered
> fonts as if they were registered. In other words, to parse the fonts from
> the font files (found in the configuration file or PATH) and create
> java.awt.font objects for them that can be used. I do not know whether this
> is feasible, but if it were, it seems like we might gain a bunch of benefits
> from using the Java 2D classes that use these classes. If this is an
> impossible or otherwise bad idea, perhaps it will trigger a good one in
> someone else.

Yes please!!! But don't forget to provide backwards compatibility
(loading a font from a XML font metric file). Depending on what's faster
it may be beneficial to generate an XML font metric file into some
configurable directory acting as some kind of persistant font cache, the
first time the font is loaded. Adobe Acrobat Reader does something
similar, too.

For Type 1 font support that would mean that we have to write a AFM
and/or PFB parser (already on my todo list, but I'm lacking time ATM) so
we get better reliability for these fonts.

> I am betting that some of you have thought about these issues for a while,
> so I ask the questions hoping that you can save me many hours of tedious
> unfruitful work.

Today, making fonts available is the responsibility of the renderer. I'm
not sure if this is good. I'd prefer a central font manager which can
provide fonts from var

Re:

[J.Pietschmann]

Arved Sandstrom wrote:
> I think they screwed up the grammar.
Me too. However, I think it would be really hard to press
something which is "intuitive", consistent as well as easy to
parse into a single grammar for all XSLFO porperties. It seems
they fell for the same as the C preprocessor guys did, which
is intuitive and easy to implement for the most part, but had
this abominable 0xe-12 problem as well as the rather unintuitive
"argument prescanning" hidden in its dark corners.

> As I stated before, I find it ludicrous
> that character="-" would not be OK.
That's ok, but it would require some extensions to the whole
property handling.


J.Pietschmann



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

Re: fonts

[J.Pietschmann]

Jeremias Maerki wrote:
> Don't ask me for details (because I wasn't directly involved) but we had
> to register new fonts with Linux so they got available in Batik for SVG.
> So there seems to be some kind of font registry in Linux.

That's probably the X Windows font registry which is used by the
AWT, whose fonts are in turn used by Batik.

J.Pietschmann


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

Font Width

[Balajee Chandrasekaran]

Hi All,
I want to change the font width of  my report. Basically I want to accomodate more 
charaters perline of the report. So I beleive I have to reduce the font width of the 
characters so as to squeeze in more characters.

I'm usinf FOP 0.20.4. I tried using "fot-stretch" property. 
But FOP gave me

[ERROR] property - "font-stretch" is not implemented yet.

I saw the xslfoRef.pdf that came with FOP 0.20.4 download, It did mention 
"font-stretch" property usage.

My FO content is something like this

  
Extensible Markup Language (XML) 1.0
  

Is there any errorin my usage of the property??

How else can i acheive my objective?

Thanks in advance for the help

regards
Balajee Chandrasekaran


MASTEK
Investing in relationships
In the US, we're called MAJESCO

~~
Opinions expressed in this e-mail are those of the individual and not that of Mastek 
Limited, unless specifically indicated to that effect. Mastek Limited does not accept 
any responsibility or liability for it. This e-mail and attachments (if any) 
transmitted with it are confidential and/or privileged and solely for the use of the 
intended person or entity to which it is addressed. Any review, re-transmission, 
dissemination or other use of or taking of any action in reliance upon this 
information by persons or entities other than the intended recipient is prohibited. 
This e-mail and its attachments have been scanned for the presence of computer 
viruses. It is the responsibility of the recipient to run the virus check on e-mails 
and attachments before opening them. If you have received this e-mail in error, kindly 
delete this e-mail from all computers.
~~


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