> On 27 Apr 2026, at 19:29, Nicolas George via ffmpeg-devel > <[email protected]> wrote: > > Hi. > > ... > > > The first question I want to ask is: Do we want it? +1 It will help to keep the documentation in sync with the code. > > > If the collective answer is no, then I can stop thinking about it and > move to something else. > > If the collective answer is yes, then we can discuss in more details. > But it also means we want everything that is necessary to implement it. > And since it produces text, that includes AVWriter. Also, it probably > includes reworking the way the documentation is stored in files in the > source code, maybe changing its format. > > Note: I am not interested in a less ambitious system. A version where we > just add a few text fields to components and let applications deal with > them, without transverse documentation like the syntax for timestamps, > is absolutely possible, but I would not be the one to work on it. > > I hope the answer is yes. > > Regards, > > -- > Nicolas George > _______________________________________________ > ffmpeg-devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
[FFmpeg-devel] Re: RFC: Embedded documentation
Ingo Oppermann via ffmpeg-devel Tue, 28 Apr 2026 03:45:06 -0700
- [FFmpeg-devel] RFC: Embedded documentation Nicolas George via ffmpeg-devel
- [FFmpeg-devel] Re: RFC: Embedded docu... Ingo Oppermann via ffmpeg-devel
- [FFmpeg-devel] Re: RFC: Embedded docu... Gyan Doshi via ffmpeg-devel
- [FFmpeg-devel] Re: RFC: Embedded ... Nicolas George via ffmpeg-devel
