<div>Dear Reinhard,</div>
<div> </div>
<div>Thank you for that backgrounder.</div>
<div> </div>
<div>The hard work is being done by others, Jonathan, Stefan, Alain and others I can not identify yet.</div>
<div> </div>
<div>I am in the priviledged position of doing something very simple here, applying a small piece of simplistic knowledge -- while myself riding on the shoulders of giants!</div>
<div> </div>
<div>Something very very simple, that produces a successful result ONLY because of the HARD work of the others!</div>
<div> </div>
<div>Paul<br><br></div>
<div class="gmail_quote">2009/9/20 Reinhard Kotucha <span dir="ltr"><<a href="mailto:reinhard.kotucha@web.de">reinhard.kotucha@web.de</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im">On 19 September 2009 Paul A Norman wrote:<br><br> > Dear Stefan,<br> ><br> > Thank you for that, it sparked something in my memory, and yes<br> > texdoc works under MiTeX on Windows as well.<br>
<br></div>texdoc only depends on LuaTeX's Lua engine and should work on all<br>systems which provide LuaTeX.<br>
<div class="im"><br> > My security fears are irrelevent I think unless "texdoc" is removed<br> > from the os.execute command string.<br><br></div>That's true.<br>
<div class="im"><br> > I don't think package names are allowed to have spaces in them, is that<br> > right does any one know?<br><br></div>This is a good question. There are no packages with spaces in their<br>
name on CTAN yet and I assume that there will be none in the near<br>future. However, it's poor software design if spaces in file names<br>are not supported. Even more important are spaces in directory names<br>because they can't always be avoided.<br>
<div class="im"><br> > Using texdoc may work on all/most distributions perhaps?<br><br></div>Hopefully! It's written in texlua for this reason.<br><br>Paul, thank you very much for your work. We (Jonathan, Manuel, and<br>
me) briefly discussed this feature at the TUG conference in Cork<br>already, but TeXworks lacked a scripting engine at this time. It's<br>very nice to see that a texdoc interface became re ality. I'm deeply<br>grateful because this is a great feature and not only newcomers<br>
benefit from it.<br><br>Another thing we discussed was to make Robin's FAQ accessible directly<br>from TeXworks. Jonathan prefers the HTML version of the FAQ because<br>QT supports HTML already and for a few other reasons. I don't know<br>
how much effort is necessary in order to make the QT HMTL interface<br>accessible to Lua. I also fear that it's necessary to "steal" some<br>code from LuaTeX. What I have in mind is the kpathsea interface.<br>
<br>Stefan, you are my hero anyway. A scripting language allows people to<br>contribute easily without worrying about system quirks. Paul already<br>proved that this statement is correct. No need to compile TeXworks<br>
again in order to add a new feature. I'm very glad that you provided<br>a scripting engine. Thank you very much!<br><br>Regards,<br> Reinhard<br><font color="#888888"><br>--<br>----------------------------------------------------------------------------<br>
Reinhard Kotucha Phone: +49-511-3373112<br>Marschnerstr. 25<br>D-30167 Hannover mailto:<a href="mailto:reinhard.kotucha@web.de">reinhard.kotucha@web.de</a><br>
----------------------------------------------------------------------------<br>Microsoft isn't the answer. Microsoft is the question, and the answer is NO.<br>----------------------------------------------------------------------------<br>
</font></blockquote></div><br>