AW: hyphenation again
Hi! J.Pietschmann Robert P. J. Day - thanks for your answers! I can test the thing on the eving, but i'm sure, that they will work. My first problem with the path was solved for itself after rebuilding FOP with only packages, that i use. And the both others (# as hyphanation sign and warnings about not foundig de) are in fact DocBook, specially Stylesheet related difficulties. Here are the links which describe, how to solve it. Perhaps somebody has the same troubles: http://lists.oasis-open.org/archives/docbook-apps/200305/msg00211.html http://lists.oasis-open.org/archives/docbook-apps/200305/msg00233.html http://www.sagehill.net/xml/docbookxsl/CustomMethods.html#CustomGentext CU Anton - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
hyphenation again
Hi! I get the TeX hyphenation file and the XML version too, i set the path in the userconf.xml, but i read on the command line again and again, that they are not found. The path to the hyph files is correct, couse i'm able to embed the ttf fonts. Any suggestions? entry keyhyphenation-dir/key value/fop/build/classes/hyph/value /entry this can i see when i generate the fo-file with saxon: Making portrait pages on A4 paper (210mmx297mm) No de localization of hyphenation-character exists; using en. No de localization of hyphenation-push-character-count exists; using en. No de localization of hyphenation-remain-character-count exists; using en. No de localization of hyphenation-character exists; using en. No de localization of hyphenation-push-character-count exists; using en. No de localization of hyphenation-remain-character-count exists; using en. No de localization of hyphenation-character exists; using en. No de localization of hyphenation-push-character-count exists; using en. No de localization of hyphenation-remain-character-count exists; using en. No de localization of hyphenation-character exists; using en. No de localization of hyphenation-push-character-count exists; using en. No de localization of hyphenation-remain-character-count exists; using en. And these errors came from FOP: [ERROR] Couldn't find hyphenation pattern de [ERROR] Error building hyphenation tree for language de java.io.StreamCorruptedException: invalid stream header at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:737) at java.io.ObjectInputStream.init(ObjectInputStream.java:253) at org.apache.fop.layout.hyphenation.Hyphenator.getFopHyphenationTree(Hyphenator.j ava:164) at org.apache.fop.layout.hyphenation.Hyphenator.getHyphenationTree(Hyphenator.java :91) at org.apache.fop.layout.hyphenation.Hyphenator.hyphenate(Hyphenator.java:251) at org.apache.fop.layout.LineArea.doHyphenation(LineArea.java:1206) at org.apache.fop.layout.LineArea.addText(LineArea.java:856) at org.apache.fop.fo.FOText.addRealText(FOText.java:294) at org.apache.fop.fo.FOText.addText(FOText.java:252) at org.apache.fop.fo.FOText.layout(FOText.java:161) at org.apache.fop.fo.flow.Block.layout(Block.java:257) at org.apache.fop.fo.flow.Block.layout(Block.java:257) at org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154) at org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:110) at org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:400) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:338) at org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:262) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:221) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher .dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Sour ce) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.fop.apps.Driver.render(Driver.java:498) at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:106) at org.apache.fop.apps.Fop.main(Fop.java:62) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: AW: AW: Number alignment in TOC
Hi!
Sorry, it cuts off just before it gets interesting.
Sorry. ;-)
You can start with a copy of your real file and successively cut stuff.
It's a little bit confusing, but i'm find to my surprise, that the problem with
the sect2 apperas only than when i generated the abstract part of bookinfo. I
commented parts out and firstly it looks like the problem come from a table in
an abstract section. When i comment this table out the whole output of TOC is
OK. But after i tried to create a small file with only two sect1 and two sect2
in each of sect1 and with the table in bookinfo i get an ouput where only one
number of sect2 don't fit, like a russian roulette.
I attach here as you wish the whole fo file where the correct output can be
reached after commentig out the table with the address. I see, thtat if i use
instead of the table something other, there will be no more problem with the
toc numbers, but perhaps can somebody explain why i get this behavior.
Here just my xml and xsl code for the table
XML-Code:
informaltable frame=none
tgroup cols=1 colsep=0 rowsep=0
colspec colname=c1 /
tbody
rowentryYou can contact VarySys Technologies GmbH
amp; Co.KG at:/entry/row
rowentrynbsp;/entry/row
rowentryVarySys Technologies GmbH amp;
Co.KG/entry/row
rowentryMouml;nchhaldenstraszlig;e
28/entry/row
rowentryD ndash; 70191 Stuttgart/entry/row
rowentrynbsp;/entry/row
rowentryTel.: (07 11) 2 50 11 98/entry/row
rowentryFax: (07 11) 2 50 11 97/entry/row
rowentryEmail: ulink url=mailto:[EMAIL
PROTECTED][EMAIL PROTECTED]/ulink/entry/row
rowentry
Internet:
ulink
url=http://www.varysys.com;http://www.varysys.com/ulink
/entry
/row
/tbody
/tgroup
/informaltable
XSL-Code:
xsl:template match=[EMAIL PROTECTED]'none']
fo:table table-layout=fixed
width={$default.table.width}
padding-top={$body.font.master}pt
keep-together=always
keep-with-next=always
xsl:apply-templates /
/fo:table
/xsl:template
CU
Anton
attachment: PacketAlarm.zip
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
AW: automatic Page breaks on longer sections?
Hi! The XSL-FO solution to your problem is put keep-with-next=always on your heading blocks to ensure the text block always follows it or both are moved to the next page together. Unfortunately, keep-* properties are not implemented on fo:block in FOP yet. yes, i read this. Is there a time line, where is listed, when this function probably will be added? One work around, is to put all your block into a fo:table, since keep-* properties have been implemented on fo:table-row This don't really help on big documents. I thought, that this problem should have evrybody, and there may exists some others possibilities, like the use of vertical-align instead of baseline-shift. CU Anton - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: AW: Number alignment in TOC
Hi! The output of the TOC-Numbers looks now much better, but it is not perfect. The Numbers of sect2 fit not exact with the oders. Is this problem known and would be corrected in the next version? Could you supply a slightly more explicit problem description, preferably augmented by a small, self-contained FO document demonstrating it? Not everyone around has a clone of your DocBook development environment installed. DocBook DTD 4.2 XSL-Stylesheet 1.60.1 from Norm Walsh FOP 0.25.5rc3 See the screenshot. Chapters and all the sections numbers are OK, only the sect2 Numbers do not fit. The FO-File is hard to read, cause of no indents in the TOC-generated parts, a part of fo file is attached to this mail too. CU Anton attachment: toc-0.20.5rc3.gifattachment: toc.zip - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: Number alignment in TOC
Hi! [INFO] 1.0dev I told you to be sure to get the code from the maintenance branch. The branch tag is fop-0_20_2-maintain. Unfortunatly you wrote firstly only mantain without branch number. So i thougt, that the main may be correct. How can i see, which version of FOP contain the branch? I mean, that branch fop-0_20_2-maintain contains fop version 0.20.5rc3, so the number of the branch do not fit the number of the fop-version and i don't find in the WebCVS http://cvs.apache.org/viewcvs.cgi/xml-fop/ overview out how to see the really FOP-Version inside this branch. The output of the TOC-Numbers looks now much better, but it is not perfect. The Numbers of sect2 fit not exact with the oders. Is this problem known and would be corrected in the next version? CU Anton - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Set Standard Font
Hi! You need the correct path to the fonts, font declaration in the userconfig.xml and if you use docbook following entry in your xsl-file: xsl:param name=body.font.familyArial/xsl:param or for the titles xsl:param name=title.font.familyVerdana/xsl:param CU Anton - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Set Standard Font
Hi! Content of userconfig.xml: font metrics-file=frt45light.xml kerning=yes embed-file=C:\WINNT\Fonts\Ftl_.ttf font-triplet name=Frutiger style=normal weight=normal/ /font yes. And now, i define the Parameter in the XSL File? yes, if you customize Norms Stylesheets you have to use the parameter body.font.family. or direct in fo: fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; font-family=Arial font-size=11pt text-align=left line-height=normal language=en CU Anton - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
