Re: Include paths for makeinfo

2011-12-21 Thread Dumas Patrice
On Wed, Dec 21, 2011 at 02:35:33PM -0800, Karl Berry wrote: > It looks at > ('eps', 'gif', 'jpg', 'jpeg', 'pdf', 'png', 'svg'); > > HTML output, there's no real use in linking to an eps or a pdf as an > image in html output, is there? Browsers will not render them as an > image within

Re: Include paths for makeinfo

2011-12-21 Thread Karl Berry
It looks at ('eps', 'gif', 'jpg', 'jpeg', 'pdf', 'png', 'svg'); HTML output, there's no real use in linking to an eps or a pdf as an image in html output, is there? Browsers will not render them as an image within the page (at least not that I've ever seen), which is what is desired.

Re: Include paths for makeinfo

2011-12-21 Thread Patrice Dumas
On Wed, Dec 21, 2011 at 11:15:38AM +, John Darrington wrote: > > Did you try running the test case I sent? It passed (testing in-source in tp/ using ./texi2any.pl). -- Pat

Re: Include paths for makeinfo

2011-12-21 Thread John Darrington
On Wed, Dec 21, 2011 at 11:57:37AM +0100, Patrice Dumas wrote: On Mon, Dec 19, 2011 at 03:43:40PM -0800, Karl Berry wrote: > > With this flag, it warns that picture.txt is missing, even though > it's not. In fact, it shouldn't be looking for that, but for > pi

Re: Include paths for makeinfo

2011-12-21 Thread Patrice Dumas
On Mon, Dec 19, 2011 at 03:43:40PM -0800, Karl Berry wrote: > > With this flag, it warns that picture.txt is missing, even though > it's not. In fact, it shouldn't be looking for that, but for > picture.{png,jpg}. > > Patrice, are you looking for the "html" image formats for docbook