Le primidi 1er vendémiaire, an CCXXIV, James Darnley a écrit :
> At present it only converts global metadata as that is what I wanted to do.
> It
> should be possible to extend it so that the conversion can be different for
> different files or streams.
> ---
> doc/ffmpeg.texi | 6 +++
> ffmpeg.c | 15 ++++++
> ffmpeg.h | 1 +
> ffmpeg_opt.c | 149
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> 4 files changed, 169 insertions(+), 2 deletions(-)
>
> diff --git a/doc/ffmpeg.texi b/doc/ffmpeg.texi
> index f4ffc6c..d4c1c23 100644
> --- a/doc/ffmpeg.texi
> +++ b/doc/ffmpeg.texi
> @@ -855,6 +855,12 @@ such streams is attempted.
> Allow input streams with unknown type to be copied instead of failing if
> copying
> such streams is attempted.
>
> +@item -metadata_iconv_code_page_list @var{code_page_list}
> +Force the metadata from input files to be converted through the given
> codepages
> +using iconv. This allows the user to correct
> +@uref{https://en.wikipedia.org/wiki/Mojibake, mojibake} providing they know
> the
> +correct code pages to use.I will have some more technical comments later. For now, I would just remark that I believe "code page" is not the wording I would suggest: it refers to proprietary and obsolete implementations. IMHO, the best way to refer to this is "character encoding". Regards, -- Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
