From: Pete S. <pst...@gm...> - 2008-06-14 19:38:12
|
In a separate thread, Donald B. Moore wrote... DM>> I checked the tex2rtf help (in it's src-tree)... DM>> DM>> It doesn't actually conclude a position of being DM>> able to path specify the image_include_dir....which DM>> is in equivalence to this situation. In fact, this DM>> notion isn't discussed at all... DM>> DM>> ...what one can consider is _inferred_ by the tex2rtf DM>> help docs, is a situation example in usage where the DM>> words read "make sure the image file you wish to include, DM>> is in the same directory as the tex file being processed" DM>> ...or such'n'similar. This morsel of text, coupled with DM>> the observed behaviour, leads me to believe this is DM>> a limitation hardcoded into tex2rtf itself somewhere.... PS> I don't think this is a Tex2RTF issue, but a PS> browser/help displayer issue. I'll have to look PS> into it. Well Donald, I was wrong. This is a Tex2RTF issue. If you open jazz_topic14.html generated from the latest jazz.tex and Tex2RTF with Firefox, and look at the source for the page, you will notice the path portion of the image name is missing. I'll try to fix this in Tex2RTF. I'll report back to this thread if and when I do fix it. Pete |
From: Pete S. <pst...@gm...> - 2008-06-14 21:05:45
|
PS = Pete Stieber PS> In a separate thread, Donald B. Moore wrote... DM>>> I checked the tex2rtf help (in it's src-tree)... DM>>> DM>>> It doesn't actually conclude a position of being DM>>> able to path specify the image_include_dir....which DM>>> is in equivalence to this situation. In fact, this DM>>> notion isn't discussed at all... DM>>> DM>>> ...what one can consider is _inferred_ by the tex2rtf DM>>> help docs, is a situation example in usage where the DM>>> words read "make sure the image file you wish to include, DM>>> is in the same directory as the tex file being processed" DM>>> ...or such'n'similar. This morsel of text, coupled with DM>>> the observed behaviour, leads me to believe this is DM>>> a limitation hardcoded into tex2rtf itself somewhere.... PS>> I don't think this is a Tex2RTF issue, but a PS>> browser/help displayer issue. I'll have to look PS>> into it. PS> Well Donald, I was wrong. This is a Tex2RTF issue. PS> If you open jazz_topic14.html generated from the PS> latest jazz.tex and Tex2RTF with Firefox, and look PS> at the source for the page, you will notice the path PS> portion of the image name is missing. PS> PS> I'll try to fix this in Tex2RTF. I'll report back PS> to this thread if and when I do fix it. Donald, I believe I just committed a fix for this to the Tex2RTF sources. Testing welcome. Pete |
From: D.B. M. <db...@ho...> - 2008-06-15 00:25:07
|
Greets, > Date: Sat, 14 Jun 2008 14:05:48 -0700 > Subject: Re: [jazzplusplus-devel] Tex2RTF HTML generated image path > > PS = Pete Stieber > PS> In a separate thread, Donald B. Moore wrote... > > DM>>> I checked the tex2rtf help (in it's src-tree)... > DM>>> > DM>>> It doesn't actually conclude a position of being > DM>>> able to path specify the image_include_dir....which > DM>>> is in equivalence to this situation. In fact, this > DM>>> notion isn't discussed at all... > DM>>> > DM>>> ...what one can consider is _inferred_ by the tex2rtf > DM>>> help docs, is a situation example in usage where the > DM>>> words read "make sure the image file you wish to include, > DM>>> is in the same directory as the tex file being processed" > DM>>> ...or such'n'similar. This morsel of text, coupled with > DM>>> the observed behaviour, leads me to believe this is > DM>>> a limitation hardcoded into tex2rtf itself somewhere.... > > PS>> I don't think this is a Tex2RTF issue, but a > PS>> browser/help displayer issue. I'll have to look > PS>> into it. > > PS> Well Donald, I was wrong. This is a Tex2RTF issue. > PS> If you open jazz_topic14.html generated from the > PS> latest jazz.tex and Tex2RTF with Firefox, and look > PS> at the source for the page, you will notice the path > PS> portion of the image name is missing. > PS> > PS> I'll try to fix this in Tex2RTF. I'll report back > PS> to this thread if and when I do fix it. > > Donald, > > I believe I just committed a fix for this to the Tex2RTF sources. > > Testing welcome. > > Pete > Okidoki, thanks Pete, that seems to have fixed this issue ..... Note that the install path is still broken -- here it's installing the documentation in $PREFIX/bin/HelpFiles instead of something like $PREFIX/share/jazz++/HelpFiles ....but I know this isn't a problem as such, just an issue in makefile.am or so... Otherwise, great work Pete! As I get to them, other images that need renewing will be replaced and moved into the 'images' dir to keep everything spic&span ... but now, on with the show!! Regards, Donald B _________________________________________________________________ It's simple! Sell your car for just $30 at CarPoint.com.au http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%2Ecom%2Fcgi%2Dbin%2Fa%2Fci%5F450304%2Fet%5F2%2Fcg%5F801459%2Fpi%5F1004813%2Fai%5F859641&_t=762955845&_r=tig_OCT07&_m=EXT |
From: Pete S. <pst...@gm...> - 2008-06-15 16:29:56
|
DM = D.B. Moore DM> Note that the install path is still broken -- here DM> it's installing the documentation in DM> $PREFIX/bin/HelpFiles instead of something DM> like $PREFIX/share/jazz++/HelpFiles ....but I DM> know this isn't a problem as such, just an DM> issue in makefile.am or so... This is intentional. After a fresh install and Jazz++ is started for the first time, I know how to search for the help files if they are under the executable's directory. I haven't put effort into finding them if they are somewhere else. Pete |