<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"/>  <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Another interesting thing about the index problem for my document – if it is a problem.  It turns out that it works fine on Internet Explorer and in the PLT Scheme Help Desk.  Only Firefox has the problem – on both Windows and Linux.  Unfortunately, I use Firefox as my default browser.<o:p></o:p> <o:p> </o:p> I’m going to chalk this one up to a Firefox problem.  The behaviour is actually different between Linux and Windows.  On Windows, the links seem to work on the second and subsequent uses – the first click seems to just go to some random (though consistent) place.  On Linux, it seems to go some random (though consistent) place on the first click and to some other random (at least it’s at an anchor, just usually the wrong one) place on the second and subsequent clicks.<o:p></o:p> <o:p> </o:p> In any case, it doesn’t seem to be a problem with PLT Scheme or text2page – so case closed.<o:p></o:p> <o:p> </o:p> Doug<o:p></o:p> <o:p> </o:p> <div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: Williams, M. Douglas Sent: Thursday, March 09, 2006 7:47 AM To: Williams, M. Douglas; PLT Scheme Subject: RE: [plt-scheme] User Documentation in Help Desk<o:p></o:p> </div> <o:p> </o:p> I little progress here on some of this and a step backwards.<o:p></o:p> <o:p> </o:p> 1.  I found Matthew Flatt’s makehdindex.ss and gettitle.ss and got them to work.  The only problem was the need to flatten the <div> structure (before flattening the structure, but similar code), which was apparently added to tex2page since the makehdindex.ss code was written.  So, it works and generates an hdindex file for me.  Unfortunately, the references were wrong.  Upon further examination, it turns out that the makehdindex code was working fine.  It was the index that tex2page constructs that was (and is) wrong.<o:p></o:p> <o:p> </o:p> I haven’t done a thorough look into the problem, but the index generated by tex2page for my document has the correct entries, but the links are wrong.  I’m not sure if it’s something I have done wrong (either in my document structure or in installing tex2page) or if it’s a bug.  I suspect the former since I checked indices of other documents in the help desk generated with tex2page and they’re fine.  Has anyone else had a similar problem?<o:p></o:p> <o:p> </o:p> 2. I finally just installed VMware and am running Ubuntu to get the tools under Windows on my laptop (thanks Matt Judad for pointing out VMware Player).  With the new VMware Player and Ubuntu virtual machine – both are free downloads from VMware – I have the tools on my laptop.<o:p></o:p> <o:p> </o:p> 3.  Advice is still welcome.<o:p></o:p> <o:p> </o:p> Doug<o:p></o:p> <o:p> </o:p> <div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: plt-scheme-bounces@list.cs.brown.edu [mailto:plt-scheme-bounces@list.cs.brown.edu] On Behalf Of Williams, M. Douglas Sent: Monday, March 06, 2006 9:14 AM To: PLT Scheme Subject: [plt-scheme] User Documentation in Help Desk<o:p></o:p> </div> <o:p> </o:p> I am reformatting the science collection documentation to fit into the Help Desk documentation scheme and have a few questions.<o:p></o:p> <o:p> </o:p> 1. Are there any tools to help automate the development of the keywords and hdindex files?  For example, the document has an index and it would be nice to have that information used to generate the hdindex file.<o:p></o:p> <o:p> </o:p> 2. I finally gave up getting a working PLT Scheme, <st1:place w:st="on"><st1:State w:st="on">TeX</st1:State></st1:place>, tex2page, gs, netpbm, … combination working on my Windows box.  On my Linux box I had a working combination up and running in (literally) a few minutes.  Does anyone have the magic combination to getting it to work on Windows?  [My laptop is Windows only and I like working on such things when I travel.  Dual boot isn’t an option because of a corporate, Windows-only hard disk encryption system.]<o:p></o:p> <o:p> </o:p> 3. Are there any remaining ‘gotchas’ I just haven’t gotten to yet?  Or, any lessons learned that will help make the documentation work seamlessly with the help desk and generally be better for the end user?<o:p></o:p> <o:p> </o:p> Thanks in advance,<o:p></o:p> Doug<o:p></o:p> <o:p> </o:p> M. Douglas Williams, Ph.D.<o:p></o:p> Sr. Scientist<o:p></o:p> Science Applications International Corporation<o:p></o:p> <o:p> </o:p> </div> </div> </div> </body> </html>