Re: [Vote] New committer: Jeremias Maerki
+1 of course. On 2002.04.13 20:03 Christian Geisert wrote: Hi all, I would like to propose Jeremias Maerki as a new committert for Fop. Jeremias has already contibuted the PS Renderer and quite a few bugfixes/patches, helped to improve the documentation and is very helpful on the mailing lists. Here is my vote: +1 Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Bug handling
On 2002.04.13 05:33 J.Pietschmann wrote: I'm focusing on the development to fix those bugs, it would be good if someone could put a bit of effort into the bug handling process. I read this as It's ok? That depends on what it is. I don't find it a very effective form of communication under the circumstances and I did say a bit. We could change most of the bugs to won't fix or postpone with the assumption that the current cvs does fix these problems but there won't be a release for a while. So what is the bug list for? To tell users what bugs there are in releases, to tell developers what problems need fixing in development? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Nested Tables column-widths
Hi, Which converter prog did you used? I am programming html2fo and it converts colspanned cells into the corresponing widths within fo:table-column. You could get it from: http://sourceforge.net/projects/html2fo the currently available version is 0.4.1 but I will try to release a new version this week. Via CVS is a more recent version available. Regards Enrico Hi, I have been trying to convert html code to xsl:fo with a converter program. In html there are statements like - tr td width=20% colspan=3 class=qdtnl height=18Customer/td td width=30% colspan=3 class=qdtnd height=18: [~Customer~]/td td width=25% class=qdtnl height=18xyz/td td width=25% class=qdtndlc height=18: [~abc~] /td /tr I know I need to explicitely specify column widths in fo , like- fo:table fo:table-column column-width=2in/ fo:table-column column-width=3in/ before the fo:table-body. I have some thoughts like.. first- to see how many ' td .. /td statements exist between its 'tr /tr' in the html source code and then in fo code to create as many lines of 'fo:table-column column-width=(20/100 * 8)in/' before the 'fo:table-body'. ( Here- 20% in html code is being converted to inches in fo.) next- to change 'colspan=2' etc. in the html source code to ' number-columns-spanned=2 ' with in a fo:table-cell Is this a good approach? or if anybody has better sugestions please let me know.. Further I don't have any idea to handle attributes like class in the td .. of source code for conversion into fo code. If you dealt this issue already pl. let me know thanks Durga - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Bug handling
Keiron Liddle wrote: We could change most of the bugs to won't fix or postpone with the assumption that the current cvs does fix these problems but there won't be a release for a while. So what is the bug list for? To tell users what bugs there are in releases, to tell developers what problems need fixing in development? From my user's perspective, the most important thing is that I can check the buglist whenever I have a problem. If the problem is known and unfixed, I usually can't wait for the fix anyway and have to do a hotfix or woraround myself.But at least I know it's a bug and can stop searching for a mistake I may have made. Even if no active committer ever looked into the buglist, it'd still be a valuable resource for users. I suppose the biggest problem with the current FOP buglist is that most users are unaware that the current 0.20.3 is a maintenance branch only. This information is not very prominent in the documentation which leads users to expect more from the FOP committers than they realistically can. My two cents. Arnd Beissner -- Cappelino Informationstechnologie GmbH Arnd Beißner Bahnhofstr. 3, 71063 Sindelfingen, Germany Email: [EMAIL PROTECTED] Phone: +49-7031-463458 Mobile: +49-173-3016917 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/hyph tr.xml
keiron 02/04/15 05:14:16
Added: hyph tr.xml
Log:
turkish hyphenation file
Submitted by: Togan Muftuoglu [EMAIL PROTECTED]
Revision ChangesPath
1.1 xml-fop/hyph/tr.xml
Index: tr.xml
===
?xml version=1.0 encoding=iso-8859-9?
!DOCTYPE hyphenation-info SYSTEM ../hyph/hyphenation.dtd
!-- Constructed by Togan Muftuoglu from trhyphen.tex file
[EMAIL PROTECTED] 26 March 2002
% A mechanically generated Turkish Hyphenation table for TeX,
% using the University of Washington diacritical coding
% developed by P. A. MacKay for the Ottoman Texts Project.
% Slightly modified by H. Turgut Uyar.
%
% The following commands ensure correct \catcodes, \lccodes and
% \uccodes if your TeX implementations uses these character codes.
%
%\catcode`\^^c7=11 \lccode`\^^c7=`\^^e7 \uccode`\^^c7=`\^^c7 % \c{C}
%\catcode`\^^e7=11 \lccode`\^^e7=`\^^e7 \uccode`\^^e7=`\^^c7 % \c{c}
%\catcode`\^^d6=11 \lccode`\^^d6=`\^^f6 \uccode`\^^d6=`\^^d6 % \{O}
%\catcode`\^^f6=11 \lccode`\^^f6=`\^^f6 \uccode`\^^f6=`\^^d6 % \{o}
%\catcode`\^^dc=11 \lccode`\^^dc=`\^^fc \uccode`\^^dc=`\^^dc % \{U}
%\catcode`\^^fc=11 \lccode`\^^fc=`\^^fc \uccode`\^^fc=`\^^dc % \{u}
%
%\catcode`\^^87=11 \lccode`\^^87=`\^^a7 \uccode`\^^87=`\^^87 % \u{G}
%\catcode`\^^a7=11 \lccode`\^^a7=`\^^a7 \uccode`\^^a7=`\^^87 % \u{g}
%\catcode`\^^9d=11 \lccode`\^^9d=`\^^Y \uccode`\^^9d=`\^^9d % \.{I}
%\catcode`\^^Y=11 \lccode`\^^Y=`\^^Y \uccode`\^^Y=`\^^9d % \i{}
%\catcode`\^^83=11 \lccode`\^^83=`\^^b3 \uccode`\^^83=`\^^83 % \c{S}
%\catcode`\^^b3=11 \lccode`\^^b3=`\^^b3 \uccode`\^^b3=`\^^83 % \c{s}
%
--
hyphenation-info
hyphen-char value=-/
hyphen-min before=3 after=2/
classes
!-- @!$%^*()_-+=~`{[}]:;'|,.?/0123456789 --
aA
bB
cC
çÇ !-- ccedilla --
dD
eE
fF
gG
ðÐ !-- gbreve --
hH
ýI !-- idotless I --
iÝ !--i Iabovedot --
jJ
kK
lL
mM
nN
oO
öÖ !--odiaeresis --
pP
!-- qQ --
rR
sS
þÞ !--scedilla--
tT
uU
üÜ !--Udiaeresis--
vV
!--wW--
!--xX--
yY
zZ
!--äÄ--
!--öÖ--
/classes
patterns
2a1
2e1
2^^Y1
2i1
2o1
2ö1
2u1
2ü1
1b1
1c1
1ç1
1d1
1f1
1g1
1^^a71
1h1
1j1
1k1
1l1
1m1
1n1
1p1
1r1
1s1
1^^b31
1t1
1v1
1y1
1z1
2e2cek.
2bb
2bc
2bç
2bd
2bf
2bg
2b^^a7
2bh
2bj
2bk
2bl
2bm
2bn
2bp
2br
2bs
2b^^b3
2bt
2bv
2by
2bz
2cb
2cc
2cç
2cd
2cf
2cg
2c^^a7
2ch
2cj
2ck
2cl
2cm
2cn
2cp
2cr
2cs
2c^^b3
2ct
2cv
2cy
2cz
2çb
2çc
2çç
2çd
2çf
2çg
2ç^^a7
2çh
2çj
2çk
2çl
2çm
2çn
2çp
2çr
2çs
2ç^^b3
2çt
2çv
2çy
2çz
2db
2dc
2dç
2dd
2df
2dg
2d^^a7
2dh
2dj
2dk
2dl
2dm
2dn
2dp
2dr
2ds
2d^^b3
2dt
2dv
2dy
2dz
2fb
2fc
2fç
2fd
2ff
2fg
2f^^a7
2fh
2fj
2fk
2fl
2fm
2fn
2fp
2fr
2fs
2f^^b3
2ft
2fv
2fy
2fz
2gb
2gc
2gç
2gd
2gf
2gg
2g^^a7
2gh
2gj
2gk
2gl
2gm
2gn
2gp
2gr
2gs
2g^^b3
2gt
2gv
2gy
2gz
2^^a7b
2^^a7c
2^^a7ç
2^^a7d
2^^a7f
2^^a7g
2^^a7^^a7
2^^a7h
2^^a7j
2^^a7k
2^^a7l
2^^a7m
2^^a7n
2^^a7p
2^^a7r
2^^a7s
2^^a7^^b3
2^^a7t
2^^a7v
2^^a7y
2^^a7z
2hb
2hc
2hç
2hd
2hf
2hg
2h^^a7
2hh
2hj
2hk
2hl
2hm
2hn
2hp
2hr
2hs
2h^^b3
2ht
2hv
2hy
2hz
2jb
2jc
2jç
2jd
2jf
2jg
2j^^a7
2jh
2jj
2jk
2jl
2jm
2jn
2jp
2jr
2js
2j^^b3
2jt
2jv
2jy
2jz
2kb
2kc
2kç
2kd
2kf
2kg
2k^^a7
2kh
2kj
2kk
2kl
2km
2kn
2kp
2kr
2ks
2k^^b3
2kt
2kv
2ky
2kz
2lb
2lc
2lç
2ld
2lf
2lg
2l^^a7
2lh
2lj
2lk
2ll
2lm
2ln
2lp
2lr
2ls
2l^^b3
2lt
2lv
2ly
2lz
2mb
2mc
2mç
2md
2mf
2mg
2m^^a7
2mh
2mj
2mk
2ml
2mm
2mn
2mp
2mr
2ms
2m^^b3
2mt
2mv
2my
2mz
2nb
2nc
2nç
2nd
2nf
2ng
2n^^a7
2nh
2nj
2nk
2nl
2nm
2nn
2np
2nr
2ns
2n^^b3
2nt
2nv
2ny
2nz
2pb
2pc
2pç
2pd
2pf
2pg
2p^^a7
2ph
2pj
2pk
2pl
2pm
2pn
2pp
2pr
2ps
2p^^b3
2pt
2pv
2py
2pz
2rb
2rc
2rç
2rd
2rf
2rg
2r^^a7
2rh
2rj
2rk
2rl
2rm
2rn
2rp
2rr
2rs
2r^^b3
2rt
2rv
2ry
2rz
2sb
2sc
2sç
2sd
2sf
2sg
2s^^a7
2sh
2sj
2sk
2sl
2sm
2sn
2sp
2sr
2ss
2s^^b3
2st
2sv
2sy
2sz
2^^b3b
2^^b3c
2^^b3ç
2^^b3d
2^^b3f
2^^b3g
2^^b3^^a7
2^^b3h
2^^b3j
2^^b3k
2^^b3l
2^^b3m
2^^b3n
2^^b3p
2^^b3r
2^^b3s
2^^b3^^b3
2^^b3t
2^^b3v
2^^b3y
2^^b3z
2tb
2tc
2tç
2td
2tf
2tg
2t^^a7
2th
2tj
2tk
2tl
2tm
2tn
2tp
2tr
2ts
2t^^b3
2tt
2tv
2ty
2tz
2vb
2vc
2vç
2vd
2vf
2vg
2v^^a7
2vh
2vj
2vk
2vl
2vm
2vn
2vp
2vr
2vs
absolute positioning in an pdf
Hi, I am using FOP 0.20.3 and it works quite well for me. But there is some issue that I would like some advice: When FOP writes a line in PDF with spacing between characters for instance in a table with 2 or more cells per rows or words in general each word is positioned relative to the last one on the same line. What I would like to do is to make the start position of each word absolute. Is there any way to do this? Where would I have to start looking? Thanks in advance Enrico [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[GUMP] Build Failure - xml-fop
This email is autogenerated from the output from: http://jakarta.apache.org/builds/gump/2002-04-15/xml-fop.html Buildfile: build.xml init-avail: init-filters-xalan2: [copy] Copying 1 file to /home/rubys/jakarta/xml-fop/build/src/codegen init: [echo] --- Fop 1.0dev [1999-2002] prepare: [echo] Preparing the build directories [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/svg [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/conf [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/hyph [copy] Copying 3 files to /home/rubys/jakarta/xml-fop/build/classes/conf codegen: [echo] Resetting codegen directory [copy] Copying 30 files to /home/rubys/jakarta/xml-fop/build/src/codegen [echo] Generating the java files from xml resources [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/allprops.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/Constants.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/genconst.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/fo_ignore_this.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/properties.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/FOPropertyMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/propmap.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/foenums_ignore_this.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/enumgen.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/charlist.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/CodePointMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/code-point-mapping.xsl [style] Transforming into /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBold.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBold.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Courier.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Courier.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBoldOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBoldOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Helvetica.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Helvetica.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaBold.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaBold.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaBoldOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaBoldOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Symbol.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Symbol.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesBold.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesBold.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesBoldItalic.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesBoldItalic.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesItalic.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesItalic.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesRoman.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesRoman.java [style] Processing
Re: absolute positioning in an pdf
Enrico Horn wrote: When FOP writes a line in PDF with spacing between characters for instance in a table with 2 or more cells per rows or words in general each word is positioned relative to the last one on the same line. What I would like to do is to make the start position of each word absolute. Is there any way to do this? Where would I have to start looking? I'm not sure what you problem is, but you can specify absolute positions in XSLFO by specifying absolute-position=absolute and setting the left/top/right/bottom properties. Look into the spec: http://www.w3.org/TR/xsl/slice7.html#common-absolute-position-properties HTH J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Keeps and space specifiers
Soothed Foperators, I have been looking for a while, like everybody else, at keeps. I was looking for a way to unify the processing of keeps and breaks at the layout level. Breaks are easy enough; just create column-break and page-break pseudo-area and insert into the galley as a sibling of the affected object's area subtree. Once that's done, look-ahead and re-layout operate on the same stream of galley objects. However, keeps didn't fit. It occurred to me that, conceptually, the keeps can all be expressed as a new keep-together pseudo-area. The keep-together property itself is expressed during layout by wrapping all of the generated areas in a keep-together area. Keep-with-previous on formatting object A becomes a keep-together area spanning the first non-blank normal area leaf node, L, generated by A or its offspring, and the last non-blank normal area leaf node preceding L in the area tree. Likewise, keep-with-next on formatting object A becomes a keep-together area spanning the last non-blank normal area leaf node, L, generated by A or its offspring, and the first non-blank normal area leaf node following L in the area tree. The obvious problem with this arrangement is that the keep-together area violate the hierarachical arrangement of the layout tree. They form a concurrent structure focussed on the leaf nodes. This seems to be the essential problem of handling keep-with-(previous/next); that it cuts across the naturally tree-structured flow of processing. Such problems are endemic in page layout. In any case, it seems that the relationships between areas that are of interest in keep processing need some form of direct expression, parallel to the layout tree itself. I have yet to examine inline relationships or the problem of changes in block-progression-direction, but just looking at the simple block stacking cases, you get a diagram like the attached PNG. In order to track the relationships through the tree, I think you need four sets of links. The basic links are: Leading edge to leading edge of first normal child. Trailing edge to leading edge of next normal sibling. Trailing edge to trailing edge of parent Superimposed on the basic links are bridging links which span adjacent sets of links. These spanning links are the tree violators, and give direct access to the areas which are of interest in keep processing. They could be implemented as double-linked lists, either within the layout tree nodes or as separate structures. Gaps in the spanning links are joined by simply reproducing the single links, as in the diagram. The whole layout tree for a page is effectively threaded in order of interest, as far as keeps are concerned. The bonus of this structure is that it looks like a superset of the stacking constraints. It gives direct access to all sets of adjacent edges and sets of edges whose space specifiers need to be resolved. Fences can be easily enough detected during the process of space resolution. I will be looking at what happens with changes of block-progression-direction and the related structures for inline keeps. How does this gel with what other people are doing with keeps? Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7815] - Hotspot of an fo:basic-link in fo:table-cell is positioned in row above
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=7815. 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=7815 Hotspot of an fo:basic-link in fo:table-cell is positioned in row above --- Additional Comments From [EMAIL PROTECTED] 2002-04-16 05:35 --- I have a similar problem: two fo:basic-link's on a page which display fine, one mailto:; in a fo:table-cell and another http: in a fo:block. The hotspots are both 3.5cm in from the left margin of the page, and 5cm 2.5cm down respectively from the actual links. The page is landscape, and I am using fop 0.20.3. I can supply xsl if req'd. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
non rendered character in and before inline tags occurring at page-break
Hello, I've noticed that text() of tags that occur at page-break as well as the characters that preceed in the same word-unit (surrounded by whitespaces) are not rendered at all in PDF and AWT view. Look at the beginning of page 15 in the pdf file: 'tensible' for 'extensible' [Efo:inlinex/fo:inlinetensible]; notice that even though the first 'e' is not surrounded by any tag, it is not rendered either. One more thing: if I process a 'simple.xml' file with occurrences like [Erx/rtensible], the same happens, even if I dont write any template for the 'r' element. Thank you all for your answers. N. Mazziotta sample.zip Description: Zip compressed data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
