tag:blogger.com,1999:blog-121698332011-04-21T21:45:23.853-07:00Hauihttp://www.blogger.com/profile/06224906889861921569noreply@blogger.comBlogger41100tag:blogger.com,1999:blog-12169833.post-1124444764345726502005-08-19T02:46:00.000-07:002005-08-19T02:59:23.196-07:00If you are still missing SVG import in your OpenOffice.org Draw, there is now a <a href="http://haumacher.de/svg-import/">good address, where to go</a>. Thanks Stefan for your <a href="http://blogs.sun.com/roller/page/stx12?entry=contribution_of_the_week_svg">kind mention in your blog</a>!<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/12169833-112444476434572650?l=haumacher.blogspot.com' alt='' /></div>Hauihttp://www.blogger.com/profile/06224906889861921569noreply@blogger.com0tag:blogger.com,1999:blog-12169833.post-1116421545299389782005-05-18T05:57:00.000-07:002005-08-19T02:54:25.706-07:00A checked exception in Java is an exception that must either be caught or declared to be thrown. As the name suggests, the compiler ensures that these requirements are fulfilled or otherwise reports a program error. <a href="http://svn.ipd.uka.de/trac/javaparty/wiki/hauma/blog/UndeclaredCheckedExceptions">As my page in the JavaParty wicki shows, this guarantee is void due to unsafe techniques used in recent JDKs</a>.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/12169833-111642154529938978?l=haumacher.blogspot.com' alt='' /></div>Hauihttp://www.blogger.com/profile/06224906889861921569noreply@blogger.com0tag:blogger.com,1999:blog-12169833.post-1114799659799539502005-04-29T11:34:00.000-07:002005-08-19T02:58:11.763-07:00There is a cool tool called <a href="http://www.ccs.neu.edu/home/dorai/tex2page/tex2page-doc.html">tex2page</a> which is able to create lovely looking HTML pages from a LaTeX document. After trying it out on one of my LaTeX documents, I thought of the following improvements.<br /><br /><dl><dt style="font-weight: bold;">Support for character encodings</dt><br /><dd>I've got documents encoded in ISO-8859-1 using the LaTeX package <tt>inputenc</tt>. Non-ASCII characters are rendered as <tt>?</tt> by tex2page.</dd><dt><br /></dt><br /><dt style="font-weight: bold;">Internationalization (I18N)</dt><br /><dd>Text fragments inserted by tex2page are all in English. Unfortunately, some of my documents are written in German. Therefore, it would be much fancier, if tex2page would use "Kapitel" headings instead of "Chapter". </dd><br /><br /><dt style="font-weight: bold;">Alternative texts for all internal links</dt><br /><dd>The capabilities of the electronic target media are not completely exploited by tex2page. I would love to see the caption of the target used as alternative text for all document-internal links. When pointing with the mouse on a link "see Figure 42", my browser would display the caption of the referenced figure in a tool-tip window after a while. The same should apply for links into the bibliography and footnotes. </dd><br /><br /><dt style="font-weight: bold;">Direct HTML-rendering of (simple) math</dt><br /><dd>All math is rendered as GIF images. Generating these images is a time-consuming process and the rendering in a browser is absolutely sub-optimal. Much better were the generation of native HTML code for at least simple formulas. When using Unicode characters, most of the LaTeX specials should be displayable directly without the need for generating images. </dd><br /><br /><dt style="font-weight: bold;">Rendering figures without tables</dt><br /><dd>There seems to be a problem when rendering figures that contain just one centered minipage. Such figures produce tables with two columns. Maybe, a more general approach for minipages using <tt>div</tt> elements would be better. </dd><br /><br /><dt style="font-weight: bold;">Plugins</dt><br /><dd>The tex2page approach is to parse and execute the TeX file through a custom TeX processor. Naturally, this processor does not understand all macros defined in all existing TeX packages. The native TeX implementation of these macros is not useful for generating HTML output. It would be great, if tex2page could be extended with plugins that provide (scheme) implementations for macros defined in LaTeX packages. </dd><br /><br /><dt style="font-weight: bold;">Usage of macros defined in additional packages during image generation</dt><br /><dd>If a math environment uses macros provided by additional packages (imported with <tt>\usepackage</tt>) tex2page reports an error when trying to generate an image for this environment. </dd><br /><br /><dt style="font-weight: bold;">XHTML support</dt><br /><dd>The output generated by tex2page seems to be not always well-formed HTML 4. Even greater were XHTML 1.0 as target language. </dd><br /><br /></dl><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/12169833-111479965979953950?l=haumacher.blogspot.com' alt='' /></div>Hauihttp://www.blogger.com/profile/06224906889861921569noreply@blogger.com0tag:blogger.com,1999:blog-12169833.post-1113477950953235432005-04-14T04:23:00.000-07:002005-04-14T04:26:04.730-07:00<span style="font-family:arial;">Hi all, I'm completely new to the blogosphere. So this is the first message I post just to test if all works fine.</span><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/12169833-111347795095323543?l=haumacher.blogspot.com' alt='' /></div>Hauihttp://www.blogger.com/profile/06224906889861921569noreply@blogger.com0