[FFmpeg-devel] [PATCH] doc: add ffmpeg-bitstream-filters.texi file

Stefano Sabatini stefasab at gmail.com
Tue Nov 27 23:34:53 CET 2012


On date Tuesday 2012-11-27 20:56:59 +0100, Nicolas George encoded:
> Le septidi 7 frimaire, an CCXXI, Stefano Sabatini a écrit :
> > Currently bitstream filters depend on libavcodec, so putting them
> > together with media-level filters may be confusing
> 
> I do not think that users should be required to know this kind of internal
> (and historic) details.

But still bitstream filters API and functionality is embedded in
libavcodec, so users *should* be aware of that in case they need them

Also people looking for bitstream filters are ubergeek users anyway,
and are able to figure it out themselves, while "normal" users finding
bitstream filters in the "media" filters manual will easily get
confused.

> 
> >						     (and I want to
> > disable manual pages for which the corresponding library is disabled).
> 
> This is an interesting argument, but I wonder about it. Doing it would be
> rather logical, but it is not enough: the documentation will still contain
> filters / codecs / etc. that are individually disabled (because they depend
> on an external library, for example).
> 
> Do you know whether the texinfo tools would allow some kind of "#ifdef
> CONFIG_SOMETHING" pre-processing?

There is @ifset, but I'm not sure it is properly suppported in
texi2pod.pl. I'll test it soon as I want to understand if it is
possible to still compile Huge Wall of Text manuals, for users
preferring that.
-- 
FFmpeg = Fabulous and Fancy Multimedia Portable Erroneous Gadget


More information about the ffmpeg-devel mailing list