Re: Memory allocation - large table
Chieh Tong wrote: Hi, I'm currently printing a very large table with over 30,000 rows in it. I understand that memory allocation problems can be avoided by using multiple page-sequences. However, the data I'm prinitng is in a table and I can't seem to think of a way to break up the table into multiple page sequences. The table gets its data from a xsl:for-each loop. Any suggestions? You can use usual xslt technics of grouping data into reasonable sized chunks and then generate page-sequence from each chunk of data. Don't ask here how to group in xslt, it's offtopic here, ask on xsl-list instead, see http://www.mulberrytech.com/xsl/xsl-list/index.html. -- Oleg Tkachenko Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
OutOfMemoryError when running FOP in Websphere 4.0.4 but sucessful in Win 2000
Hi, I am currently writing a fop serlvet. The input is a xml xslt file and the output is a pdf file. During development, we write and test the program under Win 2000 and running in Websphere 4.0.4 environment. The font file is installed and the corresponding font xml file is generated as well. In Win 2000, the servlet can run and generate the pdf file successfully without error. However, when we port them (including userconfig, font ttf and xml) to the AIX environment (also running in Websphere 4.0.4 environment), it cannot run successfully, and throws the java.lang.OutOfMemoryError. The problem is all the userconfig.xml, font xml ttf files are the same. And all these files can be found by the servlet sucessfully. We have also try to increase the heap sizes to 256. However, still fails in AIX environment. The expected output pdf is only 2 page with a simple table. Is there any difference between AIX Win 2000 for running fop? Should the font xml file must be generated in Aix? Do you have any comment? Regards, Sherlane __ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: OutOfMemoryError when running FOP in Websphere 4.0.4 but sucessfulin Win 2000
Sherlane Lam wrote: However, when we port them (including userconfig, font ttf and xml) to the AIX environment (also running in Websphere 4.0.4 environment), it cannot run successfully, and throws the java.lang.OutOfMemoryError. I've run FOP in a WebSphere environment quite successfully, even with rather large output. OutOfMemory errors are also a problem but in our JVM (a 1.3.0 bugfix level) seems only to happen due to memory leaking in case exceptions are thrown across threads. Other JVM versions are reported to misoptimize code, getting calculations wrong and having more substantial memory leaks. Also, WebSphere 4 has some implementation quirks which make the problem worse. Is there any difference between AIX Win 2000 for running fop? No. Should the font xml file must be generated in Aix? No. Do you have any comment? I vaguley remember to have read some hints on the net about conserving memory with WS4. It included stripping the classpath and some configuration changes. Either search the net and ask on a WS related forum, or ask your friendly WS support at IBM (though they weren't of much help for us). It might already help to disable the JIT. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/pdf PDFNumber.java
jeremias2003/02/16 04:39:49
Modified:src/org/apache/fop/pdf Tag: fop-0_20_2-maintain
PDFNumber.java
Log:
Removed some unnecessary duplicate code.
Revision ChangesPath
No revision
No revision
1.5.2.1 +5 -33 xml-fop/src/org/apache/fop/pdf/PDFNumber.java
Index: PDFNumber.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/pdf/PDFNumber.java,v
retrieving revision 1.5
retrieving revision 1.5.2.1
diff -u -r1.5 -r1.5.2.1
--- PDFNumber.java30 Jul 2001 20:29:30 - 1.5
+++ PDFNumber.java16 Feb 2003 12:39:49 - 1.5.2.1
@@ -1,6 +1,6 @@
/*
* $Id$
- * Copyright (C) 2001 The Apache Software Foundation. All rights reserved.
+ * Copyright (C) 2001-2003 The Apache Software Foundation. All rights reserved.
* For details on use and redistribution please refer to the
* LICENSE file included with these sources.
*/
@@ -9,39 +9,11 @@
public class PDFNumber {
-private PDFNumber() {}
-
public static String doubleOut(Double doubleDown) {
-StringBuffer p = new StringBuffer();
-if (doubleDown.doubleValue() 0) {
-doubleDown = new Double(-doubleDown.doubleValue());
-p.append(-);
-}
-double trouble = doubleDown.doubleValue() % 1;
-if (trouble 0.950) {
-p.append(doubleDown.intValue() + 1);
-} else if (trouble 0.050) {
-p.append(doubleDown.intValue());
-} else {
-String doubleString = new String(doubleDown + );
-int decimal = doubleString.indexOf(.);
-if (decimal != -1) {
-p.append(doubleString.substring(0, decimal));
-
-if ((doubleString.length() - decimal) 6) {
-p.append(doubleString.substring(decimal, decimal + 6));
-} else {
-p.append(doubleString.substring(decimal));
-}
-} else {
-p.append(doubleString);
-}
-}
-return (p.toString());
+return doubleOut(doubleDown.doubleValue());
}
public static String doubleOut(double doubleDown) {
-
StringBuffer p = new StringBuffer();
if (doubleDown 0) {
doubleDown = -doubleDown;
@@ -54,7 +26,7 @@
} else if (trouble 0.050) {
p.append((int)doubleDown);
} else {
-String doubleString = new String(doubleDown + );
+String doubleString = Double.toString(doubleDown);
int decimal = doubleString.indexOf(.);
if (decimal != -1) {
p.append(doubleString.substring(0, decimal));
@@ -85,7 +57,7 @@
} else if (trouble (5.0 / (Math.pow(10.0, dec {
p.append((int)doubleDown);
} else {
-String doubleString = new String(doubleDown + );
+String doubleString = Double.toString(doubleDown);
int decimal = doubleString.indexOf(.);
if (decimal != -1) {
p.append(doubleString.substring(0, decimal));
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/svg PDFGraphics2D.java
jeremias2003/02/16 04:41:58
Modified:src/org/apache/fop/svg Tag: fop-0_20_2-maintain
PDFGraphics2D.java
Log:
Fixed some sources of wrong operand type error in Acrobat Reader.
They were caused by rounding bugs, mostly experienced with SVG files coming from
OpenOffice.
The PDF contained matrices like 0 0 0 0 0 0 cm when the values really shouldn't be
zero.
Revision ChangesPath
No revision
No revision
1.20.2.10 +20 -22xml-fop/src/org/apache/fop/svg/PDFGraphics2D.java
Index: PDFGraphics2D.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/svg/PDFGraphics2D.java,v
retrieving revision 1.20.2.9
retrieving revision 1.20.2.10
diff -u -r1.20.2.9 -r1.20.2.10
--- PDFGraphics2D.java8 Nov 2002 10:25:29 - 1.20.2.9
+++ PDFGraphics2D.java16 Feb 2003 12:41:57 - 1.20.2.10
@@ -548,12 +548,12 @@
AffineTransform trans = getTransform();
double[] tranvals = new double[6];
trans.getMatrix(tranvals);
-currentStream.write(PDFNumber.doubleOut(tranvals[0]) +
-+ PDFNumber.doubleOut(tranvals[1]) +
-+ PDFNumber.doubleOut(tranvals[2]) +
-+ PDFNumber.doubleOut(tranvals[3]) +
-+ PDFNumber.doubleOut(tranvals[4]) +
-+ PDFNumber.doubleOut(tranvals[5]) + cm\n);
+currentStream.write(PDFNumber.doubleOut(tranvals[0], 8) +
++ PDFNumber.doubleOut(tranvals[1], 8) +
++ PDFNumber.doubleOut(tranvals[2], 8) +
++ PDFNumber.doubleOut(tranvals[3], 8) +
++ PDFNumber.doubleOut(tranvals[4], 8) +
++ PDFNumber.doubleOut(tranvals[5], 8) + cm\n);
PathIterator iter = s.getPathIterator(new AffineTransform());
while (!iter.isDone()) {
@@ -938,12 +938,12 @@
double[] vals = new double[6];
trans.getMatrix(vals);
-currentStream.write(PDFNumber.doubleOut(vals[0]) +
-+ PDFNumber.doubleOut(vals[1]) +
-+ PDFNumber.doubleOut(vals[2]) +
-+ PDFNumber.doubleOut(vals[3]) +
-+ PDFNumber.doubleOut(vals[4]) +
-+ PDFNumber.doubleOut(vals[5]) + cm\n);
+currentStream.write(PDFNumber.doubleOut(vals[0], 8) +
++ PDFNumber.doubleOut(vals[1], 8) +
++ PDFNumber.doubleOut(vals[2], 8) +
++ PDFNumber.doubleOut(vals[3], 8) +
++ PDFNumber.doubleOut(vals[4], 8) +
++ PDFNumber.doubleOut(vals[5], 8) + cm\n);
currentStream.write(1 0 0 -1 0 0 Tm [ + startText);
int l = s.length();
@@ -1084,12 +1084,12 @@
}
-currentStream.write(PDFNumber.doubleOut(vals[0]) +
-+ PDFNumber.doubleOut(vals[1]) +
-+ PDFNumber.doubleOut(vals[2]) +
-+ PDFNumber.doubleOut(vals[3]) +
-+ PDFNumber.doubleOut(vals[4]) +
-+ PDFNumber.doubleOut(vals[5]) + Tm ( + ch
+currentStream.write(PDFNumber.doubleOut(vals[0], 8) +
++ PDFNumber.doubleOut(vals[1], 8) +
++ PDFNumber.doubleOut(vals[2], 8) +
++ PDFNumber.doubleOut(vals[3], 8) +
++ PDFNumber.doubleOut(vals[4], 8) +
++ PDFNumber.doubleOut(vals[5], 8) + Tm ( + ch
+ ) Tj\n);
}
@@ -1285,11 +1285,9 @@
}
// needed for compiling under jdk1.4
-@jdk14codestart@
public java.awt.image.VolatileImage createCompatibleVolatileImage(int
width, int height) {
return null;
}
-@jdk14codeend@
}
/**
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/render/pdf PDFRenderer.java
jeremias2003/02/16 04:42:11
Modified:src/org/apache/fop/render/pdf Tag: fop-0_20_2-maintain
PDFRenderer.java
Log:
Fixed some sources of wrong operand type error in Acrobat Reader.
They were caused by rounding bugs, mostly experienced with SVG files coming from
OpenOffice.
The PDF contained matrices like 0 0 0 0 0 0 cm when the values really shouldn't be
zero.
Revision ChangesPath
No revision
No revision
1.91.2.12 +7 -7 xml-fop/src/org/apache/fop/render/pdf/PDFRenderer.java
Index: PDFRenderer.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/render/pdf/PDFRenderer.java,v
retrieving revision 1.91.2.11
retrieving revision 1.91.2.12
diff -u -r1.91.2.11 -r1.91.2.12
--- PDFRenderer.java 7 Feb 2003 00:10:46 - 1.91.2.11
+++ PDFRenderer.java 16 Feb 2003 12:42:10 - 1.91.2.12
@@ -550,12 +550,12 @@
if (!at.isIdentity()) {
double[] vals = new double[6];
at.getMatrix(vals);
-currentStream.add(PDFNumber.doubleOut(vals[0]) +
-+ PDFNumber.doubleOut(vals[1]) +
-+ PDFNumber.doubleOut(vals[2]) +
-+ PDFNumber.doubleOut(vals[3]) +
-+ PDFNumber.doubleOut(vals[4]) +
-+ PDFNumber.doubleOut(vals[5]) + cm\n);
+currentStream.add(PDFNumber.doubleOut(vals[0], 8) +
++ PDFNumber.doubleOut(vals[1], 8) +
++ PDFNumber.doubleOut(vals[2], 8) +
++ PDFNumber.doubleOut(vals[3], 8) +
++ PDFNumber.doubleOut(vals[4], 8) +
++ PDFNumber.doubleOut(vals[5], 8) + cm\n);
}
PDFGraphics2D graphics = new PDFGraphics2D(true, fs, pdfDoc,
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop CHANGES
jeremias2003/02/16 04:42:33 Modified:.Tag: fop-0_20_2-maintain CHANGES Log: Update changes Revision ChangesPath No revision No revision 1.10.2.49 +3 -0 xml-fop/CHANGES Index: CHANGES === RCS file: /home/cvs/xml-fop/CHANGES,v retrieving revision 1.10.2.48 retrieving revision 1.10.2.49 diff -u -r1.10.2.48 -r1.10.2.49 --- CHANGES 14 Feb 2003 08:00:08 - 1.10.2.48 +++ CHANGES 16 Feb 2003 12:42:33 - 1.10.2.49 @@ -1,5 +1,8 @@ == Done since 0.20.4 release +- Fixed some sources of wrong operand type error in Acrobat Reader. They + were caused by rounding bugs, mostly experienced with SVG files coming from + OpenOffice. (Jeremias Maerki) - FOP Ant task: Fix for logging behaviour, fix for directory structure preservation for nested filesets and additional attribute logFiles. Submitted by: Stefan Wachter [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/svg PDFGraphics2D.java
pietsch 2003/02/16 16:09:44
Modified:src/org/apache/fop/apps Tag: fop-0_20_2-maintain
StreamRenderer.java
src/org/apache/fop/fo Tag: fop-0_20_2-maintain FONode.java
FObj.java
src/org/apache/fop/fo/flow Tag: fop-0_20_2-maintain
AbstractTableBody.java Block.java ListBlock.java
ListItem.java Marker.java RetrieveMarker.java
Table.java
src/org/apache/fop/layout Tag: fop-0_20_2-maintain Area.java
AreaTree.java Page.java
src/org/apache/fop/render/xml Tag: fop-0_20_2-maintain
XMLRenderer.java
src/org/apache/fop/svg Tag: fop-0_20_2-maintain
PDFGraphics2D.java
Log:
Revamped marker handling. Retrieving markers works now always for
all retrieve boundaries. Long markers should also work now.
First-including-carryover does not work yet. Last-ending-within-page
probably doesn't work yet either.
Submitted by: Based on patch submitted by Marc C. Allman
Revision ChangesPath
No revision
No revision
1.6.2.9 +63 -75xml-fop/src/org/apache/fop/apps/Attic/StreamRenderer.java
Index: StreamRenderer.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/apps/Attic/StreamRenderer.java,v
retrieving revision 1.6.2.8
retrieving revision 1.6.2.9
diff -u -r1.6.2.8 -r1.6.2.9
--- StreamRenderer.java 19 Nov 2002 01:03:57 - 1.6.2.8
+++ StreamRenderer.java 17 Feb 2003 00:09:42 - 1.6.2.9
@@ -13,13 +13,14 @@
import org.xml.sax.SAXException;
-import org.apache.fop.layout.FontInfo;
-import org.apache.fop.layout.Page;
-import org.apache.fop.render.Renderer;
-import org.apache.fop.layout.AreaTree;
import org.apache.fop.datatypes.IDReferences;
import org.apache.fop.extensions.ExtensionObj;
+import org.apache.fop.fo.flow.Marker;
import org.apache.fop.fo.pagination.PageSequence;
+import org.apache.fop.layout.AreaTree;
+import org.apache.fop.layout.FontInfo;
+import org.apache.fop.layout.Page;
+import org.apache.fop.render.Renderer;
import org.apache.avalon.framework.logger.Logger;
@@ -98,6 +99,13 @@
*/
private ArrayList extensions = new ArrayList();
+/**
+ * The list of markers.
+ */
+private ArrayList documentMarkers;
+private ArrayList currentPageSequenceMarkers;
+private PageSequence currentPageSequence;
+
private Logger log;
public StreamRenderer(OutputStream outputStream, Renderer renderer) {
@@ -126,7 +134,7 @@
pageCount = 0;
if (MEM_PROFILE_WITH_GC)
-System.gc(); // This takes time but gives better results
+System.gc(); // This takes time but gives better results
initialMemory = runtime.totalMemory() - runtime.freeMemory();
startTime = System.currentTimeMillis();
@@ -158,7 +166,7 @@
}
if (MEM_PROFILE_WITH_GC)
-System.gc(); // This takes time but gives better results
+System.gc(); // This takes time but gives better results
long memoryNow = runtime.totalMemory() - runtime.freeMemory();
long memoryUsed = (memoryNow - initialMemory) / 1024L;
@@ -217,33 +225,50 @@
public synchronized void queuePage(Page page)
throws FOPException, IOException {
+
+// process markers
+PageSequence pageSequence = page.getPageSequence();
+if (pageSequence != currentPageSequence) {
+currentPageSequence = pageSequence;
+currentPageSequenceMarkers = null;
+}
+ArrayList markers = page.getMarkers();
+if (markers != null) {
+if (documentMarkers == null) {
+documentMarkers = new ArrayList();
+}
+if (currentPageSequenceMarkers == null) {
+currentPageSequenceMarkers = new ArrayList();
+}
+for (int i=0;imarkers.size();i++) {
+Marker marker = (Marker)markers.get(i);
+marker.releaseRegistryArea();
+currentPageSequenceMarkers.add(marker);
+documentMarkers.add(marker);
+}
+}
+
/*
Try to optimise on the common case that there are
no pages pending and that all ID references are
valid on the current pages. This short-cuts the
pipeline and renders the area immediately.
*/
-if ((renderQueue.size() == 0) idReferences.isEveryIdValid())
+if ((renderQueue.size() == 0)
Markers in areas
Hi, does somebody need the markers attached to an area? I just canned them, as well as another array atteched to areas (lineage pairs). Markers were only used in the XML renderer. They ought to have uses to implement retrieve-positions first-include-carryover and last-ending-within-page, but they didn't get used for this. Objections? J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Changes to maintenance release to support fo:marker
Ok, I worked on the patch. Some notes: Mark C. Allman wrote: These files just have a mayContainMarker() method added: I don't understand the advantage of this. Checks for proper FO structure are flaky anyway. You also canned the check that a marker can be preceded by whitespace. This is actually important. 3. In the searchPage() method I relaxed the search on the current page for the desired marker. Please correct me if I'm wrong, but the spec appears to say the is-first and is-last positional attributes are preferences and not exclusionary. So for example if we can't find a marker that's first but we can find the marker somewhere else on the page then return what we can, not null/not found. I believe that's what the XSLFO spec intends but I could very well be wrong. I left this as is was, because this is what people currently use an nobody complained yet. I'll look at it again if I'm going to implement first-including-carryover and last-ending-within-page. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16999] - fo:retrieve-marker takes marker from wrong page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16999. 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=16999 fo:retrieve-marker takes marker from wrong page [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-02-17 00:29 --- This was caused by missing to unregister markers while undoing layout due to the keeps. Marker handling has been improved a bit as a side effect. Fixed now in CVS maintenance branch. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop CHANGES
pietsch 2003/02/16 16:31:58 Modified:.Tag: fop-0_20_2-maintain CHANGES Log: Added CHANGES entry for marker fix. Revision ChangesPath No revision No revision 1.10.2.50 +8 -1 xml-fop/CHANGES Index: CHANGES === RCS file: /home/cvs/xml-fop/CHANGES,v retrieving revision 1.10.2.49 retrieving revision 1.10.2.50 diff -u -r1.10.2.49 -r1.10.2.50 --- CHANGES 16 Feb 2003 12:42:33 - 1.10.2.49 +++ CHANGES 17 Feb 2003 00:31:58 - 1.10.2.50 @@ -1,5 +1,12 @@ == Done since 0.20.4 release +- Fixed marker handling thouroughly. All retrieving boundaries and + retrieve-position first-starting-within-page and last-starting-within-page + should work now, as well as multiline/multiblock marker contents. + Retrieve-position first-including-carryover and last-ending-within-page + do not yet work. Also fixed marker handling in case layout was undone + due to keeps (#16999). (J.Pietschmann, based on material submitted + by Marc C. Allman) - Fixed some sources of wrong operand type error in Acrobat Reader. They were caused by rounding bugs, mostly experienced with SVG files coming from OpenOffice. (Jeremias Maerki) @@ -18,7 +25,7 @@ - Added Turkish messages for AWT Viewer Submitted by: Togan Muftuoglu [EMAIL PROTECTED] - Fixed leader expansion and leader alignment to reference area to some - extent(#7490 and #15936). + extent(#7490 and #15936). (J.Pietschmann) - Temporary fix for wrong mapping of the hyphen character in the PostScript renderer. Needs to be done in a clean way later. Submitted by: Arnd Beissner [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/hyph pt.xml
pietsch 2003/02/16 16:47:42 Modified:src/hyph Tag: fop-0_20_2-maintain pt.xml Log: New portugese hyphenation. Submitted by: [EMAIL PROTECTED] Revision ChangesPath No revision No revision 1.1.2.2 +267 -226 xml-fop/src/hyph/pt.xml Index: pt.xml === RCS file: /home/cvs/xml-fop/src/hyph/pt.xml,v retrieving revision 1.1.2.1 retrieving revision 1.1.2.2 diff -u -r1.1.2.1 -r1.1.2.2 --- pt.xml15 Jan 2003 14:03:32 - 1.1.2.1 +++ pt.xml17 Feb 2003 00:47:42 - 1.1.2.2 @@ -1,226 +1,267 @@ -?xml version=1.0 encoding=iso-8859-1? -!DOCTYPE hyphenation-info SYSTEM hyphenation.dtd -!-- -Converted from pthyph.tex to XML by Paulo Soares ([EMAIL PROTECTED]). Added accented characters -support. Original comments follow. - -% Tabela TeX de separacao de silabas para portugues. -% The Portuguese TeX hyphenation table. -% (C) 1987 by Pedro J. de Rezende -% Release date: 02/13/87 -% -% Pedro de Rezende -% College of Computer Science -% Northeastern University -% 360 Huntington Ave -% Boston MA 02115 -% -% (617) 437-2078 -% CSnet: [EMAIL PROTECTED] -% -% Permission is hereby granted to copy and distribute this material provided -% that the copies are not made or distributed for commercial or lucrative -% purpose. -% -% FURTHERMORE, THE CONTENTS OF THIS TABLE ARE NOT TO BE CHANGED IN ANY WAY! -% - --- -hyphenation-info - -classes -aA -bB -cC -dD -eE -fF -gG -hH -iI -jJ -kK -lL -mM -nN -oO -pP -qQ -rR -sS -tT -uU -vV -wW -xX -yY -zZ -aá -aÁ -aà -aÀ -aâ -a -eé -eÉ -eê -eÊ -ií -iÍ -oó -oÓ -uú -uÚ -çÇ -ãà -õÕ -oô -oÔ -/classes - -exceptions -!-- % If needed, add other exceptions to this list -- -hard-ware -soft-ware -sub-lin-gual -ec-lipse -ec-lipses -ec-lipsar -ec-le-si-as-ti-co -ec-le-si-as-ti-cos -terp-si-core -/exceptions - -patterns -!-- % The Plain TeX hyphenation tables [NOT TO BE CHANGED IN ANY WAY!] -- -1ba -1be -1bi -1bo -1bu -1by -1b2l -1b2r -o2b3long -1ca -1ce -1ci -1co -1cu -1cy -1c2k -1ch -1c2l -1c2r -1da -1de -1di -1do -1du -1dy -1d2l -1d2r -e1e -1fa -1fe -1fi -1fo -1fu -1fy -1f2l -1f2r -1ga -1ge -1gi -1go -1gu -1gy -1g2l -1g2r -ba1hia -1j -1ka -1ke -1ki -1ko -1ku -1ky -1k2l -1k2r -1la -1le -1li -1lo -1lu -1ly -1lh -1ma -1me -1mi -1mo -1mu -1my -m2n -m1h -1na -1ne -1ni -1no -1nu -1ny -1nh -o1o -1pa -1pe -1pi -1po -1pu -1py -1ph -1p2l -1p2r -1p2neu -1p2sic -1qu -1ra -1re -1ri -1ro -1ru -1ry -1sa -1se -1si -1so -1su -1sy -1ta -1te -1ti -1to -1tu -1ty -1th -1t2l -1t2r -1va -1ve -1vi -1vo -1vu -1vy -1v2l -1v2r -w2 -1xa -1xe -1xi -1xo -1xu -1xy -1z -1ç -/patterns -/hyphenation-info - - +?xml version=1.0 encoding=iso-8859-1? +!DOCTYPE hyphenation-info SYSTEM hyphenation.dtd +!-- + Copirraite (C) 2001-2003 pela Apache Software Foundation. Todos os + direitos reservados. Para detalhes sobre o uso e redistribuição + refira-se ao arquivo LICENSE que acompanha estes fontes. + + Copyright (C) 2001-2003 The Apache Software Foundation. All rights + reserved. For details on use and redistribution please refer to the + LICENSE file included with these sources. + + Tabela de hifenação FOP para o português. / FOP hyphenation table for Portuguese + versão / version 1.0(2002-07-01) + + Escrito por / Written by: + Marcelo Jaccoud Amaral ([EMAIL PROTECTED]). + Com a colaboração de / With the help of: + Ingrid Alexandra Zech ([EMAIL PROTECTED]) + + A hifenização em português é simples e bem regular, pois se faz pela soletração e + não com base etimológica. So há problemas quando a ortoépia é dúbia. + Estas regras funcionam para o português brasileiro ou o lusitano, mas não + leva em conta as novas regras em pauta no iminente acordo ortográfico acertado + mas não efetivado de 1998. Revisemo-las então se necessário. + Note-se que nem todos os hífens possiveis são validados pelo algoritmo. Por + exemplo, i-ta-ú nunca será hifenado pois as regras de leiaute reprimem letras + órfãs seja antes ou após o ponto de separação. + + Hyphenation in Portuguese is simple and fairly regular, since it is based only in + spelling and not on etymological roots. The only problems arise from ambiguous + pronunciation. These rules are valid for both Portugal and Brazil ortographies, but + does not account for the forthcoming ortography reform and unification approved in +
cvs commit: xml-fop/src/hyph pt.xml
pietsch 2003/02/16 16:49:26 Modified:src/hyph pt.xml Log: New portugese hyphenation file. Submitted by: [EMAIL PROTECTED] Revision ChangesPath 1.3 +267 -226 xml-fop/src/hyph/pt.xml Index: pt.xml === RCS file: /home/cvs/xml-fop/src/hyph/pt.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- pt.xml15 Jan 2003 15:02:52 - 1.2 +++ pt.xml17 Feb 2003 00:49:26 - 1.3 @@ -1,226 +1,267 @@ -?xml version=1.0 encoding=iso-8859-1? -!DOCTYPE hyphenation-info SYSTEM hyphenation.dtd -!-- -Converted from pthyph.tex to XML by Paulo Soares ([EMAIL PROTECTED]). Added accented characters -support. Original comments follow. - -% Tabela TeX de separacao de silabas para portugues. -% The Portuguese TeX hyphenation table. -% (C) 1987 by Pedro J. de Rezende -% Release date: 02/13/87 -% -% Pedro de Rezende -% College of Computer Science -% Northeastern University -% 360 Huntington Ave -% Boston MA 02115 -% -% (617) 437-2078 -% CSnet: [EMAIL PROTECTED] -% -% Permission is hereby granted to copy and distribute this material provided -% that the copies are not made or distributed for commercial or lucrative -% purpose. -% -% FURTHERMORE, THE CONTENTS OF THIS TABLE ARE NOT TO BE CHANGED IN ANY WAY! -% - --- -hyphenation-info - -classes -aA -bB -cC -dD -eE -fF -gG -hH -iI -jJ -kK -lL -mM -nN -oO -pP -qQ -rR -sS -tT -uU -vV -wW -xX -yY -zZ -aá -aÁ -aà -aÀ -aâ -a -eé -eÉ -eê -eÊ -ií -iÍ -oó -oÓ -uú -uÚ -çÇ -ãà -õÕ -oô -oÔ -/classes - -exceptions -!-- % If needed, add other exceptions to this list -- -hard-ware -soft-ware -sub-lin-gual -ec-lipse -ec-lipses -ec-lipsar -ec-le-si-as-ti-co -ec-le-si-as-ti-cos -terp-si-core -/exceptions - -patterns -!-- % The Plain TeX hyphenation tables [NOT TO BE CHANGED IN ANY WAY!] -- -1ba -1be -1bi -1bo -1bu -1by -1b2l -1b2r -o2b3long -1ca -1ce -1ci -1co -1cu -1cy -1c2k -1ch -1c2l -1c2r -1da -1de -1di -1do -1du -1dy -1d2l -1d2r -e1e -1fa -1fe -1fi -1fo -1fu -1fy -1f2l -1f2r -1ga -1ge -1gi -1go -1gu -1gy -1g2l -1g2r -ba1hia -1j -1ka -1ke -1ki -1ko -1ku -1ky -1k2l -1k2r -1la -1le -1li -1lo -1lu -1ly -1lh -1ma -1me -1mi -1mo -1mu -1my -m2n -m1h -1na -1ne -1ni -1no -1nu -1ny -1nh -o1o -1pa -1pe -1pi -1po -1pu -1py -1ph -1p2l -1p2r -1p2neu -1p2sic -1qu -1ra -1re -1ri -1ro -1ru -1ry -1sa -1se -1si -1so -1su -1sy -1ta -1te -1ti -1to -1tu -1ty -1th -1t2l -1t2r -1va -1ve -1vi -1vo -1vu -1vy -1v2l -1v2r -w2 -1xa -1xe -1xi -1xo -1xu -1xy -1z -1ç -/patterns -/hyphenation-info - - +?xml version=1.0 encoding=iso-8859-1? +!DOCTYPE hyphenation-info SYSTEM hyphenation.dtd +!-- + Copirraite (C) 2001-2003 pela Apache Software Foundation. Todos os + direitos reservados. Para detalhes sobre o uso e redistribuição + refira-se ao arquivo LICENSE que acompanha estes fontes. + + Copyright (C) 2001-2003 The Apache Software Foundation. All rights + reserved. For details on use and redistribution please refer to the + LICENSE file included with these sources. + + Tabela de hifenação FOP para o português. / FOP hyphenation table for Portuguese + versão / version 1.0(2002-07-01) + + Escrito por / Written by: + Marcelo Jaccoud Amaral ([EMAIL PROTECTED]). + Com a colaboração de / With the help of: + Ingrid Alexandra Zech ([EMAIL PROTECTED]) + + A hifenização em português é simples e bem regular, pois se faz pela soletração e + não com base etimológica. So há problemas quando a ortoépia é dúbia. + Estas regras funcionam para o português brasileiro ou o lusitano, mas não + leva em conta as novas regras em pauta no iminente acordo ortográfico acertado + mas não efetivado de 1998. Revisemo-las então se necessário. + Note-se que nem todos os hífens possiveis são validados pelo algoritmo. Por + exemplo, i-ta-ú nunca será hifenado pois as regras de leiaute reprimem letras + órfãs seja antes ou após o ponto de separação. + + Hyphenation in Portuguese is simple and fairly regular, since it is based only in + spelling and not on etymological roots. The only problems arise from ambiguous + pronunciation. These rules are valid for both Portugal and Brazil ortographies, but + does not account for the forthcoming ortography reform and unification approved in + 1998. This file may require maintenance when the new ortography is estabilished. + Note that not every possible hyphen
Plan for HEAD
Hi all, and especially Keiron. What are currently the most pressing problems with HEAD, in order to make a dev-release? I looked around and found quite a few details, but I can't seem to get the big picture. I have somethig to do for the API spec but there wasn't much activity in this area either last week. Does somebody already have a TODO list with prioritized tasks, preferably broken down to activities taking days rather than months? J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Plan for HEAD
Hi all, and especially Keiron. What are currently the most pressing problems with HEAD, in order to make a dev-release? I looked around and found quite a few details, but I can't seem to get the big picture. I have somethig to do for the API spec but there wasn't much activity in this area either last week. Does somebody already have a TODO list with prioritized tasks, preferably broken down to activities taking days rather than months? This page sort of has things: http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectTasks Mostly we need to get the renderers back and fix/improve some layout things like forced page break, table cell spanning, couple of problems calculating current bpd. What standard are you looking for in a dev release. Do we include the new api in the release. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Plan for HEAD
On 17.02.2003 01:57:21 J.Pietschmann wrote: Hi all, and especially Keiron. What are currently the most pressing problems with HEAD, in order to make a dev-release? I looked around and found quite a few details, but I can't seem to get the big picture. I have somethig to do for the API spec but there wasn't much activity in this area either last week. You'll see more on the API from me in the next two days. Does somebody already have a TODO list with prioritized tasks, preferably broken down to activities taking days rather than months? Let's try to come up with priorities on the Wiki todo list. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
