[FFmpeg-devel] [PATCH] doc: remove anchor garbage in filters.texi

Lou Logan lou at lrcd.com
Wed Oct 19 02:09:16 CEST 2011


On Wed, 19 Oct 2011 00:13:12 +0200, Stefano Sabatini wrote:

> On date Tuesday 2011-10-18 20:45:06 +0200, Michael Niedermayer
> encoded:
> > On Tue, Oct 18, 2011 at 07:45:37PM +0200, Stefano Sabatini wrote:
> > > On date Tuesday 2011-10-18 19:03:36 +0200, Michael Niedermayer
> > > encoded:
> > > > On Tue, Oct 18, 2011 at 06:17:15PM +0200, Stefano Sabatini
> > > > wrote:
> > > > > On date Tuesday 2011-10-18 00:26:12 +0200, Jean First encoded:
> > > > > > 
> > > > > > On Tue Oct 18 2011 00:12:38 GMT+0200 (CEST), Michael
> > > > > > Niedermayer wrote:
> > > > > > >On Mon, Oct 17, 2011 at 10:16:40PM +0200, Jean First wrote:
> > > > > > >>---
> > > > > > >>  doc/filters.texi |    4 ----
> > > > > > >>  1 files changed, 0 insertions(+), 4 deletions(-)
> > > > > > >LGTM, stefano ?
> > > > > > 
> > > > > > Sorry, I missed something. Please ignore this patch.
> > > > > 
> > > > > @anchor commands are not correctly rendered by texi2html 1.56k
> > > > > (installed on the server), it works fine with texi2html 1.86
> > > > > installed on my machine though, I don't know how hard would
> > > > > be to update the version installed on the server.
> > > > > 
> > > > > Another nice feature of the newer texi2html is that it
> > > > > supports symbolic section names (e.g. ffmpeg.html#image2 over
> > > > > ffmpeg.html#SECN).
> > > > 
> > > > IIRC the later texi2html had some issues with how parts of
> > > > their output looked
> > > 
> > > If you show me an example I'll report it upstream.
> > 
> > It seems it has been fixed
> > ive updated texi2html a little, i hope its new enough
> 
> Yes it looks very nice, problem fixed :)!
> 
> While we are at it, right now first Google entry for "ffmpeg
> documentation" points to http://ffmpeg.org/ffmpeg-doc.html, which is
> badly outdated, and it happens that sometimes users report
> problems/issues depending on this outdated documentation.
> 
> Best would be to remove that page from the server, and/or create a
> redirect from ff*-doc.html -> ff*.html.

A simple redirect added to .htaccess, .htconf, or equivalent would be
and easy and effective method, although I'm unfamiliar with the server:

Redirect 301 /ffmpeg-doc.html http://ffmpeg.org/ffmpeg-doc.html


More information about the ffmpeg-devel mailing list