Ping
Mail troubles. Just testing. Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Ping
Welcome back--You may wish to let Berin know about your email troubles--he tried multiple times to contact you: http://marc.theaimsgroup.com/?l=xml-apache-generalm=106172165515361w=2 Glen --- Peter B. West [EMAIL PROTECTED] wrote: Mail troubles. Just testing. Peter __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: encoding problem with Fo file
sri vela wrote: I have a fo file which has some special characters, which are not being parsing by FOp and throwing Invalid byte 1 of 1-byte UTF-8 sequence exception. Can any one tell me how to fix this problem.please have a look at the Fo file.It is throwing exception at single quote which is used in Trey's word There is no single quote. ?xml version=1.0 encoding=ISO-8859-1? ^^ fo:block ...Treys Best Well, MS Word is lying: the XML is probably encoded in Windows CP1252 (or so). The fancy apostrophe (IIRC #x90; or #x91;) is not a valid XML character in ISO-8859-1 encoding. Admittedly, the error message is a bit misleading (but good for a laugh). J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Place committers on inactive list?
-Original Message- From: Bertrand Delacretaz [mailto:[EMAIL PROTECTED] Sent: September 2, 2003 2:49 AM To: [EMAIL PROTECTED] Subject: Re: Place committers on inactive list? Le Mardi, 2 sep 2003, à 03:33 Europe/Zurich, Glen Mazza a écrit : ...Perhaps Karen, Arved and Bertrand should be added to the inactive list... No problem for me, I'd actually feel better being listed as inactive! That would be realistic. I have no intentions of permanently leaving the project, but I have been inactive for quite some time. I am just too busy in other pursuits at the moment. Arved - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: layout strategy packaging
Victor, I'm inclined to keep 0.20.x out of 1.0. There's too much a risk that merging the two apps into one is going to create a bunch of mush. I don't have any problem with maintaining both a development and a release version--that's just about how every other Apache team operates. Having studied both the PDF Renderer in the old and the new architecture, and the AWT Renderer in the old (so I could implement some of it in the new)--the layout is incompatible with the Area Tree and the Renderers. You'd have to bring those in as well. Also, it is clear that the inventors of the 1.0 layout system were quite knowlegable of the 0.20.x system--they improved on it--for the 10% of it I understand, it appears to be in every way a better architecture (indeed, I would call *it* the 'simple' package)--it just needs more work to be complete. IMO multiple layout strategies have a value in two cases: (1.) Where (a) layout strategies follow different philosophies, say one LS is for ultra-detailed graphics, while the other is fast document generation, and (b) these strategies are so significant that they can't be handled by compiler switches. or (2.) To allow/encourage committers like Peter, on their own, to come up and test alternative designs that may be better without needing to recode an entire app. 0.20.x isn't satisfying these cases--because 1.0 is designed to be better than it--(although, if/when Peter returns, Alt-Design might). Like you, I want to get more people--both developers and users--into 1.0. Perhaps another way of doing that would be for you to sink your teeth into the 1.0 renderers--PDF, and feel free to lend me a hand in AWT. PDF might be 70% of our audience. If we can get 1.0 PDF reasonably up to the level of 0.20.x--it's maybe halfway there already--we will then have a pretty good 1.0 user base. Also, the work that you do for the PDF renderer--bouncing back and forth between layout, the area tree, and its renderer--also helps me with AWT because much of it is the same code. Glen --- Victor Mote [EMAIL PROTECTED] wrote: Optimistically assuming for a moment that I can get the maintenance branch layout ported into the trunk world (I can almost __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs team.xml
gmazza 2003/09/03 22:15:07 Modified:src/documentation/content/xdocs team.xml Log: Moved three committers to inactive status. Revision ChangesPath 1.13 +5 -46 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- team.xml 29 Jul 2003 16:50:49 - 1.12 +++ team.xml 4 Sep 2003 05:15:07 - 1.13 @@ -11,9 +11,7 @@ section id=commit-active titleActive Committers/title ul -li id=bdlink href=mailto:[EMAIL PROTECTED]Bertrand Delacr#x00E9;taz/link (BD)/li li id=cglink href=mailto:[EMAIL PROTECTED]Christian Geisert/link (CG)/li -li id=kllink href=mailto:[EMAIL PROTECTED]Karen Lease/link (KL)/li li id=klllink href=mailto:[EMAIL PROTECTED]Keiron Liddle/link (KLL)/li li id=jmlink href=mailto:[EMAIL PROTECTED]Jeremias M#x00E4;rki/link (JM) is a software engineer from Lucerne, Switzerland. He is currently enjoying a longer period of @@ -24,7 +22,6 @@ with EDS in Arlington, Virginia, USA./li li id=wvmlink href=mailto:[EMAIL PROTECTED]Victor Mote/link (WVM) is the founder and manager of jump href=http://www.outfitr.com;Enterprise Outfitters/jump, a business software company, and of jump href=http://www.portagepub.com;Portage Publications/jump, a republisher of old documents. Both are located in Colorado Springs, Colorado, USA./li li id=jplink href=mailto:[EMAIL PROTECTED]J#x00F6;rg Pietschmann/link (JP)/li -li id=aslink href=mailto:[EMAIL PROTECTED]Arved Sandstrom/link (AS)/li li id=otlink href=mailto:[EMAIL PROTECTED]Oleg Tkachenko/link (OT)/li li id=pbwlink href=mailto:[EMAIL PROTECTED]Peter B. West/link (PBW)/li /ul @@ -40,23 +37,24 @@ recent XML/XSL-FO convert, he has been nit-picking FAQs amp; assorted web pages since his first webmaster position @brain.com in 1996. Most important creation? Jeremy Logan Leeds was born June 18, 2002./li -lilink href=mailto:[EMAIL PROTECTED]Anton Tagunov/link/li -lilink href=mailto:[EMAIL PROTECTED]Zhong (George) Yi/link/li /ul /section section id=founder titleFounder/title pFOP was originally created and donated to the Apache Software Foundation by link href=mailto:[EMAIL PROTECTED]James Tauber/link. Information about him can be found at jump href=http://www.jtauber.com;his website/jump./p /section -section id=commit-former - titleFormer Committers/title +section id=commit-inactive + titleInactive Committers/title ul li id=kclink href=mailto:[EMAIL PROTECTED]Kelly Campbell/link/li li id=sclink href=mailto:[EMAIL PROTECTED]Steven Coffman/link/li +li id=bdlink href=mailto:[EMAIL PROTECTED]Bertrand Delacr#x00E9;taz/link/li li id=telink href=mailto:[EMAIL PROTECTED]Tore Engvig/link/li li id=sglink href=mailto:[EMAIL PROTECTED]Stanislav Gorkhover/link/li li id=fjlink href=mailto:[EMAIL PROTECTED]Fotis Jannidis/link/li +li id=kllink href=mailto:[EMAIL PROTECTED]Karen Lease/link/li li id=jnlink href=mailto:[EMAIL PROTECTED]Jordan Naftolin/link/li +li id=aslink href=mailto:[EMAIL PROTECTED]Arved Sandstrom/link/li li id=eslink href=mailto:[EMAIL PROTECTED]Eric Schaeffer/link/li li id=awlink href=mailto:[EMAIL PROTECTED]Art Welch/link/li /ul @@ -66,15 +64,12 @@ table tr th/ - thBD /th thCG /th - thKL /th thKLL/th thJM /th thGM /th thWVM/th thJP /th - thAS /th thOT /th thPBW/th /tr @@ -82,19 +77,15 @@ tdPMC representation/td td/ td/ - td/ - td/ tdX/td td/ td/ td/ td/ - td/ tdX/td /tr tr tdRelease manager/td - td/ tdX/td td/ td/ @@ -103,34 +94,26 @@ td/ td/ td/ - td/ - td/ /tr tr tdXSL-FO tree/td td/ - td/ - td/ tdX/td td/ td/ td/ td/ td/ - td/ tdX/td /tr tr tdLayout/td td/ - td/ - tdX/td tdX/td td/
RE: Place committers on inactive list?
Understood--I moved you three to our inactive list on the team page--you're always committers, though, feel free to move yourselves back to active when you're ready to return. Thanks! Glen --- Arved Sandstrom [EMAIL PROTECTED] wrote: -Original Message- From: Bertrand Delacretaz ...Perhaps Karen, Arved and Bertrand should be added to the inactive list... No problem for me, I'd actually feel better being listed as inactive! That would be realistic. I have no intentions of permanently leaving the project, but I have been inactive for quite some time. I am just too busy in other pursuits at the moment. Arved __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
SVG Text layout/modification patch
Sorry for the length of this note. This note is to prepare people for an upcoming commit. I have modified the way the text bridge works to improve the performance of text. I can provide the patch for current CVS to anyone who is interested. I will hold off on committing this until I get some feed back from others but it's a fairly important improvement over the current architecture. Batik still passes all of it's regression tests. However FOP's PDF transcoder will have issues because it accesses the Attributed string properties in it's replacement TextBridge (see below). This brings me to my question. How would people feel about moving the PDFTranscoder and associated special purpose bridges to Batik? I think this would help a lot of the ongoing issues we have had keeping FOP/Batik in sync. The major interface between FOP/Batik should generally be at a higher level. The real problem is that there will be a circular dependency that needs breaking. Batik uses FOP's PDF Graphics for PDF output (and that uses at the very least FOP Font stuff), and FOP FO uses Batik to render SVG. I don't know how to resolve this right now but it seems like the right thing to do eventually. Anyway onto the gritty details: In the past the Batik Text Bridge would annotate the text element with individual properties for fill (FOREGROUND), stroke (STROKE_PAINT), stroke-width, underline/overline, etc (around 12 in total). This required relaying out the text when ever any of these properties changed because there was no way to propagate the changes through the complexities of BIDI etc. This patch replaces all those text attributes with one (PAINT_INFO) that references a TextPaintInfo object that contains all the various paint/stroke/underline etc values. The advantage of this approach is that Batik can now swap the paint/stroke objects that the TextPaintInfo object references to change these paint attributes. This allows us to update all these paint attributes without doing any text layout just a repaint. This also allows us to avoid the current double layout when we create text elements. We currently layout once to get geometry bounds then again so we can associate the various paints (which may depend on the text bounds, like gradients). The changes should be fairly minor in FOP (it actually generally cleans up the code a bit). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
