Skip to content

F
ffmpeg.wasm-core
Commit 28b4c06b authored by Anton Khirnov's avatar Anton Khirnov
Browse files
Options

lavf doxy: expand/reword metadata API doxy.

parent eca06cbe
Hide whitespace changes
Inline Side-by-side
Showing with 8 additions and 2 deletions
libavformat/avformat.h
View file @ 28b4c06b
...@@ -94,9 +94,15 @@ struct AVFormatContext; ...@@ -94,9 +94,15 @@ struct AVFormatContext;
* @{ * @{
* @ingroup libavf * @ingroup libavf
* The metadata API allows libavformat to export metadata tags to a client * The metadata API allows libavformat to export metadata tags to a client
* application using a sequence of key/value pairs. Like all strings in Libav, * application when demuxing. Conversely it allows a client application to
* metadata must be stored as UTF-8 encoded Unicode. Note that metadata * set metadata when muxing.
*
* Metadata is exported or set as pairs of key/value strings in the 'metadata'
* fields of the AVFormatContext, AVStream, AVChapter and AVProgram structs
* using the @ref lavu_dict "AVDictionary" API. Like all strings in Libav,
* metadata is assumed to be UTF-8 encoded Unicode. Note that metadata
* exported by demuxers isn't checked to be valid UTF-8 in most cases. * exported by demuxers isn't checked to be valid UTF-8 in most cases.
*
* Important concepts to keep in mind: * Important concepts to keep in mind:
* - Keys are unique; there can never be 2 tags with the same key. This is * - Keys are unique; there can never be 2 tags with the same key. This is
* also meant semantically, i.e., a demuxer should not knowingly produce * also meant semantically, i.e., a demuxer should not knowingly produce
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment