<br><br>---------- Forwarded message ----------<br><span class="gmail_quote">From: <b class="gmail_sendername">Yuri Robbers</b> <<a href="mailto:yuri.robbers@gmail.com">yuri.robbers@gmail.com</a>><br>Date: Aug 25, 2006 2:30 AM
<br>Subject: Re: [texhax] TeX v. Word, etc.<br>To: Juergen Fenn <<a href="mailto:juergen.fenn@gmx.de">juergen.fenn@gmx.de</a>><br><br></span><div><br>I have tried oolatex (with tetex under Gentoo linux - it compiled immediately, without a single error) extensively, and it's virtually useless. It converts to the old .sxw format rather than the more modern .odt format, which need not be a problem. What is a problem, however, is that it can deal with only the most basic LaTeX documents. As soon as something slightly more complicated than an itemized list is used, the resulting .sxw file will be corrupt and crash OOo as soon as one tries to open it. Pictures are hopeless, other fonts than computer modern (which gets translated into Times New Roman) don't work (apart from CM I've tried Lucida Bright, Pandora, Bookman and Times), and don't even consider using something as non-standard as the AMS document classes, redefining a counter (so that it goes a. b. c. rather than 1. 2. 3. for example) or changing the way section headings look. Mathematics are especially dramatic. Simple maths get butchered:
<br><br>\int_0^4 \frac{1}{2} x^2 dx<br><br>becomes<br><br>[half an integral sign] 01<br>---------------------------------<br>2 x dx<br><br>That's right: the {} get ignored, the integral sign gets butchered, the lower limit is wrong, the upper limit is missing, and the ^2 disappears without a trace.
<br><br>And anything more complicated than that just crashes OOo while the document opens. Actually, even some simple things crash OOo after oolatex is done: \pagebreak for example:<br><br>\documentclass{article}<br>\begin{document}
<br>Hello, world!<br><br>\pagebreak<br><br>Hello, world!<br>\end{document}<br><br>I considered renaming it \OOobreak after this...<br><br>So really... you might have better things to do with your time than trying to get the current version of oolatex to work on your system, unless you have the time to actually submit a decent bug-report or do some development work on it...
<br><br>It could be such a valuable tool, as could the reverse (oo2latex perhaps?), but it isn't even close to being usable yet, and I am not holding my breath...<br><br>Cheers,<br></div><div><span class="sg">Yuri/</span>
</div><div><span class="e" id="q_10d42bc3f4dcab52_2"><br><br><div><span class="gmail_quote">
On 8/24/06, <b class="gmail_sendername">Juergen Fenn</b> <<a href="mailto:juergen.fenn@gmx.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">juergen.fenn@gmx.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
"Yuri Robbers" <<a href="mailto:yuri.robbers@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">yuri.robbers@gmail.com</a>> writes:<br><br>> I feel the ODF format is a step in the right direction when it comes to
<br>> office documents. I don't think it's quite there yet, but it's probably the
<br>> best we can hope for. My main two objections are:<br>><br>> 1) Not all vendors support it (actually, apart from the commercial version<br>> of OpenOffice, none of the commercial office programs support it, to my
<br>> knowledge), and many explicitly intend to not use it (probably since format<br>> chances force people to update their software, which is a major source of<br>> income for vendors). What use is a standard, ISO-certified or not, when only
<br>> a small minority uses it, or even intends to use it?<br><br>AFAIK, ODT by now is a must in all public invitations to bid,<br>especially by the European Union. MS products mostly do not fit these<br>requirements because MS has always declined to support any standards.
<br>In these cases OOo indeed already was chosen by many public<br>administrations in Europe. The last case was the administration of the<br>Spanish region of Extremadura. Many German city administrations and<br>public bodies already have switched to OOo, some on Windows, some on
<br>Linux, some are in the midst of migrating. MS struggles hard not to<br>lose yet more market share. License fees for employees of companies<br>that decide to keep to MS Office are as low as never before (one<br>poster recently told us of 12 Euros per employee for a personal
<br>license of MS Office pro). So ISO certification for the ODT format was<br>an important step that has really hurt MS. And the turn towards<br>XML-based formats is a real turn-around for the MS-dominated<br>market. MS Office now has to support ODT, and remember that at least
<br>in Europe when it comes to office suites there is *nothing* left<br>besides MS Office and OOo (Word Perfect has disappeared from the<br>market years ago).<br><br>So with ODT step by step becoming the standard for data exchange, what
<br>really matters is how good LaTeX converters from and to ODT are. This<br>far there is only one I know of, viz. tex4ht that has a new command<br>named oolatex, but I have not yet been able to try it out because I<br>didn't manage to install the new version on my machine and it does not
<br>work in my MiKTeX 2.4.<br><br>Converters between LaTeX and office-suite formats unfortunately are<br>not as good as they should be. Eg, I just realised that latex2rtf does<br>not support the jurabib package, so when you write a paper in LaTeX
<br>for a German legal journal that encourages submissions in doc or rtf<br>format (they all do because DTP programs can import these formats good<br>enough) you cannot use BibTeX... don't know whether oolatex can cope<br>
with this properly...<br><br>Regards,<br>Jürgen.<br><br>_______________________________________________<br>TeX FAQ: <a href="http://www.tex.ac.uk/faq" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.tex.ac.uk/faq</a><br>Mailing list archives: <a href="http://tug.org/pipermail/texhax/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://tug.org/pipermail/texhax/</a><br>More links: <a href="http://tug.org/begin.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://tug.org/begin.html</a><br><br>Automated subscription management:
<a href="http://tug.org/mailman/listinfo/texhax" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://tug.org/mailman/listinfo/texhax
</a><br>Human mailing list managers: <a href="mailto:postmaster@tug.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">postmaster@tug.org</a><br></blockquote></div><br>
</span></div>