From: Anne <ann...@gm...> - 2010-06-10 14:00:16
|
On Thu, Jun 10, 2010 at 14:39, Sebastian Rahtz < seb...@ou...> wrote: > > On 10 Jun 2010, at 12:07, Joe Wicentowski wrote: > > > > > Taking this a step further, what pieces would you need in place in > > order to produce something like the TEI Guidelines in eXist? I recall > > you saying that you preferred using xelatex for its native UTF-8 > > handling and easy access to Truetype fonts. > > > Until/unless the XeTeX or luatex folk make an embeddable TeX system, > it's a system call away. Writing the XSL to turn XML into rich LaTeX > like that used for the Guidelines is easy (ish), because LaTeX has a lot > of high-level features and packages coming for free. What stopped me doing > the work in FO is that I'd have to reimplement in XSL all the things > already > done in LaTeX macros and life is too short. Laziness…. > > On a second thought, after looking at XSL-FO a bit more, I have to agree with you Sebastian. I definitely would prefer the higher level of LaTeX, and not deal with pixels, indentation and such. (besides that, I have my XSLT to turn XML into LaTeX already lying around) So, Wolfgang, you mentioned before that we could write a simple servlet 'does the job' and could be added to the processing pipeline in controller.xql How would you go about doing that? Could you give me a pointer where to start? Best, Anne > Personally, If I could target XEP I might revisit FO, but thats unfair > on people who don't want to buy a licence. If one stays with FOP, > there are too many red bits on > http://xmlgraphics.apache.org/fop/compliance.html > no floating figures? forget it…. > > > -- > Sebastian Rahtz > (acting) Information and Support Group Manager > Oxford University Computing Services > 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431 > > Sólo le pido a Dios > que el futuro no me sea indiferente > > |