Re: Font variant SmallCaps

anything about this. It should all be configured in the font system. That is how the user imposes his choice of fonts. With kind regards, Simon Pepping On Thu, Nov 20, 2003 at 09:22:41PM +0100, J.Pietschmann wrote: Victor Mote wrote: Typeface roughly corresponds to what is contained in a ttf

FOP documentation

should not believe what these notes say. If you do, and you act accordingly, you do so at your own risk. The notes can be found at: http://www.leverkruid.nl/FOP/index.html Regards, Simon Pepping -- Simon Pepping email: [EMAIL PROTECTED] home page: http://www.leverkruid.nl

Re: Font variant SmallCaps

On Wed, Nov 26, 2003 at 08:21:33PM +1000, Peter B. West wrote: Simon Pepping wrote: I have taken a look at the way this question is dealt with in LaTeX (TeX does not have the notion of font families, LaTeX does). Here the question what to use for small caps font is deferred to the font setup

Re: Suppression of leading space

to the characteristics of the 20pt font and bgcolor red, and one after foo according to the characteristics of the 10pt font and bgcolor blue. I see no space in the bar inline. Regards, Simon Pepping -- Simon Pepping email: [EMAIL PROTECTED] home page: http://www.leverkruid.nl

Re: Suppression of leading space

-site=15ptbar/fo:inline/fo:block I think this should generate two spaces between foo and bar. [Andreas L. Delmelle] One in 10pt, the other 15pt, or 2 spaces of 20pt? [Simon Pepping] I would think one space before foo according to the characteristics of the 20pt font and bgcolor red, I

Re: Suppression of leading space

-site=15ptbar/fo:inline/fo:block I think this should generate two spaces between foo and bar. [Andreas L. Delmelle] One in 10pt, the other 15pt, or 2 spaces of 20pt? [Simon Pepping] I would think one space before foo according to the characteristics of the 20pt font and bgcolor red, I

Error in junit tests (was: [Bug 25828] - [PATCH] fop.sh/bat should use java.endorsed.dirs)

which is incorrect with regard to namespaces. at org.apache.xerces.dom.CoreDocumentImpl.checkDOMNSErr(Unknown Source) at org.apache.xerces.dom.AttrNSImpl.setName(Unknown Source) at org.apache.xerces.dom.AttrNSImpl.init(Unknown Source) Regards, Simon -- Simon Pepping email

Attribute processing order (was: Re: [Bug 25803] - [PATCH] PropertyList: Fixes to convertAttributeToProperty and findBaseProperty)

. Therefore, before dealing with the compound attribute, the base attribute should be processed if that is specified as well. This would be different if the compound property would not be filled with default components, but with null components. Regards, Simon -- Simon Pepping email: [EMAIL PROTECTED

Re: Justification in HEAD

. These are my thoughts on the process. Regards, Simon -- Simon Pepping email: [EMAIL PROTECTED] home page: http://www.leverkruid.nl public key: http://www.leverkruid.nl/personal/sp.asc fingerprint: E3BF 7295 9AA8 8B8A C01A 219D FAAC 088C 6B28 F549

Compile error in HEAD

/xsl:text The old code applies a precise test for the inclusion of the import statement. My change includes the import statement in all property makers. Not sure what a more precise test would look like, and if there can be any. Regards, Simon -- Simon Pepping email: [EMAIL PROTECTED] home page

Re: Compile error in HEAD

and fo.properties.Constants.java/class as previously generated from codegen. The former of these causes ant not to rebuild the class fo.Constants from the corresponding new code in src, thus leaving out the new constants that were declared in the latter. Thanks, Simon -- Simon Pepping email: [EMAIL PROTECTED

Comments on the changes to the property subsystem

only once? Regards, Simon Pepping -- Simon Pepping email: spepping AT leverkruid.nl home page: http://www.leverkruid.nl

Re: Comments on the changes to the property subsystem

On Sun, Jan 25, 2004 at 11:38:14PM +0100, Finn Bock wrote: [Simon Pepping] I have just catched up with the massive changes to the property system. Allow me to share a few observations: Thanks for your comments. How do you otherwise think it compares to the previous generated property

Re: [PATCH] unnesting Property.Maker and rollling datatypes into thier properties.

with the others. 3. Should ToBeImplemented.java also be removed? A lot of good work. Regards, Simon Pepping -- Simon Pepping home page: http://www.leverkruid.nl

Re: Nasty layout bug: maint vs. HEAD

when all its forward references are resolved? At that point it is rendered, but the PDF renderer should insert it at the proper position. That does not seem to happen. Regards, Simon Pepping -- Simon Pepping home page: http://www.leverkruid.nl

Re: Percentages

Quite a piece of work. I will try to understand it. A small correction: On Sun, Feb 08, 2004 at 10:03:57PM +0100, Finn Bock wrote: margin-[top,bottom]: width of containing block, except for page context where it ^ height (I suppose). Regards, Simon -- Simon Pepping

Re: DO NOT REPLY [Bug 26778] - [PATCH] Support for percentages and table-units

. The point here is the implementation, which had a small glitch. The enclosing block is the page. It is not really the enclosing block of the simple-page-master, nor of the region-body, but of the areas they generate. Resolution is done w.r.t. the area tree. Regards, Simon -- Simon Pepping home page

Re: [PATCH] Support for percentages and table-units

On Sun, Feb 15, 2004 at 10:43:12PM +0100, Finn Bock wrote: [Simon Pepping] Finn, I think it would be a better design if, in order to resolve the percent-based properties, you would not climb the FO tree but the Area tree. That avoids feeding back results from the Area tree into the FO

Re: [PATCH] Support for percentages and table-units

On Mon, Feb 16, 2004 at 08:22:31PM +0100, Andreas L. Delmelle wrote: -Original Message- From: Finn Bock [mailto:[EMAIL PROTECTED] [Simon Pepping] snip / However, I am not happy with your solution. During the layout process, you feed the page dimensions back into the FO

Re: [PATCH] Support for percentages and table-units

On Sun, Feb 15, 2004 at 10:43:12PM +0100, Finn Bock wrote: [Simon Pepping] I initially had a separate PropertyContext object where the length was stored. The FO element then had a reference to the PropertyContext and there was a PropertyContext for every FO. But since there was a one

Re: [PATCH] Support for percentages and table-units

to the percent based length types listed in LengthBase. Regards, Simon Pepping -- Simon Pepping home page: http://www.leverkruid.nl

Re: DO NOT REPLY [Bug 26778] - [PATCH] Support for percentages and table-units

Length iTextIndent; remove the i from the name; it stands for int. Regards, Simon Pepping -- Simon Pepping home page: http://www.leverkruid.nl

Re: [PATCH] Support for percentages and table-units

, which switches between building the FO tree and building the area tree. It does not necessarily mean that information should flow in both directions. Regards, Simon Pepping -- Simon Pepping home page: http://www.leverkruid.nl

Re: [PATCH] Support for percentages and table-units

myself though: No change is required. If the layout dimension is not found on a certain FO, it is looked for at the parent. Regards, Simon Pepping -- Simon Pepping home page: http://www.leverkruid.nl

Re: cvs commit: xml-fop/src/hyph cs.xml da.xml de.xml de_DR.xml el.xml en_GB.xml en_US.xml fr.xml nl.xml no.xml sk.xml tr.xml

for the maintenance branch. What are those legal problems? The Dutch file nl.xml is based on the hyphenation patterns created by the Dutch TeX user group, and are freely distributed with TeX software. Why cannot FOP distribute them? Regards, Simon Pepping -- Simon Pepping home page: http

Re: Applying the new license

, Simon Pepping -- Simon Pepping home page: http://www.leverkruid.nl

Re: namespace-prefixes

parser. In XMLReaderFactory, it may produce an XMLReader which throws an exception when I want to set the validating feature on it. Regards, Simon Pepping -- Simon Pepping home page: http://www.leverkruid.nl

Re: Fonts and Document

font information into alt-design as compatibly as possible with HEAD. What do I need? I am completing my documentation on FOP code, see http://www.leverkruid.nl/FOP/index.html. I have a chapter on fonts. Maybe it helps you gain some quick insight. Regards, Simon Pepping -- Simon Pepping home

Re: Fonts and Document

On Mon, Mar 15, 2004 at 01:40:59PM -0800, Clay Leeds wrote: On Mar 15, 2004, at 1:15 PM, Simon Pepping wrote: Looks good, Simon... I don't suppose you could create a PDF version? (I know a great XML = PDF conversion tool. :-)) Seriously though, this looks like a great potential addition

Re: baseline-shift property

!? Ive problary been misunderstanding a great deal here - but I hope you can help me anyway ... Regards, Simon Pepping -- Simon Pepping home page: http://www.leverkruid.nl

Re: Fonts and Document

associated with the XML file. The docbook stylesheets are too large and complicated to be applied by a browser. You can only save the XML file and apply XSL stylesheets to obtain an xhtml or pdf file. Mozilla Firefox fails as well. Same reason. Regards, Simon Pepping -- Simon Pepping home page

New version of LaTeX Project Public License

/lppl/ (listed on http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAudits/March2003) Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: DO NOT REPLY [Bug 28130] - Errors in the calculation of adjustment factors

-- Simon Pepping home page: http://www.leverkruid.nl

Re: [VOTE] Simon Pepping for Committer

On Thu, Apr 01, 2004 at 04:38:11PM -0800, Glen Mazza wrote: Team, I'd like us to go ahead and make Simon Pepping our newest FOP team member. He has provided steady ML help and numerous patch contributions for the past few months, and with the many layout patches that have been coming

Re: DO NOT REPLY [Bug 27901] - [PATCH] TextCharIterator.remove() does not work properly

or RemoveC. RemoveB does handle trailing spaces except for the last one. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [Bug 27901] - [PATCH] TextCharIterator.remove() does not work properly

I should add that I have realized that the rules of whitespace handling in the FO spec are quite complicated, and that it is unwise to handle whitespace outside of the Block.handleWhiteSpace method. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [Bug 27901] - [PATCH] TextCharIterator.remove() does not work properly

that. I do not think that that logic should be duplicated or moved. There is an inefficiency here, but I do not have any good idea for optimization. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [Bug 27773] - [PATCH] Hyphenation

+ pushCharCount), null is returned, without checking the exception list and performing the algorithm. I'm going to attach the proposed patch and a test fo file which shows a few examples. Regards Luca -- Simon Pepping home page: http://www.leverkruid.nl

Re: Justification (was: [Bug 28130] - Errors in the calculation of adjustment factors)

it is. Regards J.Pietschmann -- Simon Pepping home page: http://www.leverkruid.nl

Re: User configuration for hyphenation

of the relevant interface. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [Patch Proposal] Integrate FOP with Cocoon/Excalibur Source Resolving

href, String base) ? Note that org.apache.xml.resolver.tools.CatalogResolver is an implementation of this interface using various sorts of catalogs. Simon -- Simon Pepping home page: http://www.leverkruid.nl

User configuration

Commons Configuration. They do not yet have a stable release. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

User configuration for hyphenation

this be the right object to hold a reference to the user configuration? Your advice would be appreciated. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [Bug 29025] New: - Document/LayoutStrategy consolidation

, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: ANN: FOray

I will keep adding my small contribution to the layout system of the development code. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Justification and line breaking

that this is a desirable thing to have. I thought that it would be several releases away before we could address this. But if you have a viable solution, by all means show it to us. Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Incremental vs rewrite

. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [Bug 29124] New: - New line breaking algorithm

method AbstractLayoutManager.reset(Position pos) could be used to reset the childLMs and the iterator over them. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Justification and line breaking

be developed without problems with other work. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Justification and line breaking

in your code. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Justification and line breaking

, Simon -- Simon Pepping home page: http://www.leverkruid.nl

InlineLMs

that Luca's patch causes a loop on this block. The null implementation of AbstractLayoutManager.getNextKnuthElement causes this. It should be modified to finish the LM: public KnuthElement getNextKnuthElement() { setFinished(true); return null; } Regards, Simon -- Simon Pepping home page: http

Re: CVS Karma for Simon and Clay...

On Tue, May 25, 2004 at 09:56:04PM +0200, Jeremias Maerki wrote: ...should be in place now, thanks to Ted Leung. It works OK. Thanks, Jeremias, for your attention. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: InlineLMs

On Tue, Jun 01, 2004 at 12:16:24PM +0100, Chris Bowditch wrote: Simon Pepping wrote: Note that Luca's patch causes a loop on this block. The null implementation of AbstractLayoutManager.getNextKnuthElement causes this. It should be modified to finish the LM: Great stuff. Do you think

Re: [Fwd: CVS and Subversion]

to bother with migrating it. I'm in agreement with you Glen. I'm not motivated to do the migratation and relearn tools, etc. Lets wait and see how many other projects migrate. Chris -- Simon Pepping home page: http://www.leverkruid.nl

Re: cvs commit: xml-fop/src/java/org/apache/fop/fo/pagination Declarations.java Root.java

and PropertyList.elementName are now always null, and PropertyList.getElement() now always returns null. Can you fix that? Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: cvs commit: xml-fop/src/...

-- Simon Pepping home page: http://www.leverkruid.nl

Re: Offline

post some photos to my web site when I get back. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html -- Simon Pepping home page: http://www.leverkruid.nl

Re: cvs commit: xml-fop/src/java/org/apache/fop/tools/anttasks Fop.java

. You can see my logging strategy in my recent patch. In that patch I have also started to use the trace level for very detailed logging. Let us discuss a common logging strategy. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [PROPOSAL] Finally creating the XML Graphics PMC....

on the project anyway. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Documentation finished

of Docbook 4.2 XML files. Could this be part of the wiki? Or could it be in CVS? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Documentation finished

that may benefit from customization. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Documentation finished

, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Java text geometry

one of you could drop them a line... ExTeX, isn't that the name devised for NTS, but never used? Who are using that now? Is there development in that area? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Documentation finished

committers. That is not a problem. I never publish anything without a copyright holder. If it goes to FOP CVS and other contributions are merged, then the copyright holder is just changed, like with source code. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Still need DOM Tree processing?

-generation task. I guess we should keep it in then. I support that decision. It is one more entry point for apps. Of course they can fire off their own SAX events, but if they have a DOM tree and FOP does it for them, that is nice. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [PROPOSAL] API Changes

the reasons one follows a standard API. Note that the Xalan and other people call the javax.xml.transform part TrAX. AFAIK, javax.xml.parsers is also in JAXP. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: adding fonts to fop applet

On Fri, Jul 09, 2004 at 03:05:11PM -0700, Glen Mazza wrote: Thanks, Simon. Its good that we have people of your skill on our team. Thanks for the compliment. Simon -- Simon Pepping home page: http://www.leverkruid.nl

Combined the AreaTree and FOTreeHandler (was: Re: cvs commit: etc.)

building. Now the area tree activates itself, based on an event in the FO tree. I believe this change violates the separation between the FO tree and the area tree. I think that separation is a good idea and should be maintained. Regards, Simon -- Simon Pepping home page: http

Re: Combined the AreaTree and FOTreeHandler (was: Re: cvs commit: etc.)

of an app from each other. And often it is worth the extra lines of code. Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: cvs commit: xml-fop/examples/embedding/java/embedding ExampleFO2PDF.java

it before returning to the Transformer version. This way, we have a working example should we ever need to document this style (perhaps on a web page, so users are at least aware of it) in the future. Glen -- Simon Pepping home page: http://www.leverkruid.nl

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

to first construct the user agent with all desired features and then create a driver with it. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: SAXParserFactory vs. TransformerFactory (was: Re: cvs commit: ....)

transformations may find a SAXParser example easier to apply. That was my own situation until this thread. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

fox validation

. Even if it is true, it creates compatibility problems. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Building site with forrest

, or am I doing something wrong? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: fox validation

to be written--many of them quite complex. Feel free to help out if you'd like! Glen --- J.Pietschmann [EMAIL PROTECTED] wrote: Simon Pepping wrote: The code in Root shows that fox:bookmarks is the only allowed fox child of fo:root. It is not clear that that is true. The web page

Committing documentation

I am preparing my documentation for check-in into the repository. What would be a suitable place. A directory in src/documentation/content/xdocs? Would that be in the way of the forrest build of the web site? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: (Copyright question) Re: Committing documentation

and externally, in object code and, if included in your Contributions, source code form) your Contributions. Except for the rights granted to the Foundation in this paragraph, You reserve all right, title and interest in and to your Contributions. Christian -- Simon

Re: Committing documentation

directory to commit the files into? Or shall I create a directory in src/documentation/content/xdocs? Or in src/documentation/content/? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Building site with forrest

). More recently, I've had some success, but I'm currently working with the forrest-dev list to get them resolved--and we've made progress[1] [1a]. I appreciate that that is not an easy problem to solve. (More comments inline) On Jul 25, 2004, at 11:41 AM, Simon Pepping wrote: I have tried

Re: Committing documentation

On Wed, Jul 28, 2004 at 01:24:22PM -0700, Clay Leeds wrote: On Jul 28, 2004, at 11:51 AM, Simon Pepping wrote: On Sun, Jul 25, 2004 at 12:51:56PM -0700, Clay Leeds wrote: As I understand it, you're primarily doing documentation that is more developer and/or embedded oriented, which is one

Re: Switch from AddLMVisitor to FObj.addLayoutManager()

--- Chris Bowditch [EMAIL PROTECTED] wrote: I think Joerg was saying that the details of the code are irrelevant to the end user. I tend to agree with this point, and see no benefit in removing tbe AddLMVisitor stuff. So I have to vote -0 as well. Chris -- Simon Pepping home

Re: Switch from AddLMVisitor to FObj.addLayoutManager()

be made simpler to allow a decent Java programmer to add code to the layout system. It is an aspect I want to pay attention to, but I will take it slowly and cautiously. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [Bug 29124] - New line breaking algorithm

that allows the final line of a paragraph to be shorter than the others'. Setting \parfillskip to 0 removes this ability. Usually \parfillskip has infinite stretchability. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [Bug 29124] - New line breaking algorithm

of difference due to recent cvs commits. Perhaps you cannot include new files, because as an anonymous CVS user you cannot add files (cvs add). Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [Bug 29124] - New line breaking algorithm

can have the default value auto. I think normal should be a keyword. Apparently, the actual value can only be calculated at layout time, when the font is known. Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Setting up the output format

mentioned this--and by virtue of working in Layout and FOTree, they would presumably come across this problem much more often. -- Simon Pepping home page: http://www.leverkruid.nl

Re: Setting up the output format

to write this down more in extenso? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [Bug 29124] - New line breaking algorithm

inconsistent code. When I apply it to the newer version, I get errors by the patch program. Can you try to generate a new patch? Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: validateChildNode prevents extensions.

, but at least *without* having to rewrite and replace core FO classes. My thoughts are along the same lines that Jörg has argued. I think we should do option 2. vCN() should be written such that it allows this. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [Bug 29124] - New line breaking algorithm

like in such a scenario with the current code? The current code breaks the paragraphs into lines. It makes short lines. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Handling of text-align=justify when nesting blocks

like you are right. This would apply to a displayed formula in a paragraph. Nobody would want a layout in which the last line before the display is justified, so there seems to be a problem here. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: [Bug29124] - New line breaking algorithm

On Fri, Sep 03, 2004 at 10:23:27AM +0200, Luca Furini wrote: Simon Pepping wrote: You mention that you have not implemented the Knuth algorithm for ContentLM. Would it be difficult to do that? No, I have almost done. I think I will be able to attach a patch including this fix

Re: remove layout package?

hyphenation a top-level package (i.e., org.apache.fop.hyphenation). Comments? I have no problem with your proposal. Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: foray integration

efforts to realize a valuable open source formatting objects processor. As I said earlier, I wish to spend my time on the layout system in the trunk, which leaves me no time to port FORay's code back into FOP. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: BreakPoss class

that that is not explained; the text behaves as if that is the only version of FOP. I will change that some time. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

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

. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Project offo distributes hyphenation pattern files for FOP

dependent on one person. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Project offo distributes hyphenation pattern files for FOP

explained and this license statement accepted was lengthy. I took care to state each license carefully in the covering page http://sourceforge.net/offo/hyphenation.html. For a large part thanks to Jeremias earlier work. Simon -- Simon Pepping home page: http://www.leverkruid.nl

[VOTE] Luca Furini for Committer

=allwordssubstrkeywords=keywords_type=anywordsfield0-0-0=nooptype0-0-0=noopvalue0-0-0=cmdtype=doitorder=Reuse+same+sort+as+last+time -- Simon Pepping home page: http://www.leverkruid.nl

  1   2   >