[Matroska-devel] mmg.exe 2 Bugs Related to Charset

Moritz Bunkus moritz at bunkus.org
Wed Dec 29 09:51:49 CET 2004


> (1) MMG produces this:
> "mkvmerge" -o "C:\FILENAME.mkv" --command-line-charset UTF-8
> It won't work. Because MMG is trying to handle FILENAME as UTF-8, 
> we should declare --command-line-charset BEFORE -o
> That is,
> "mkvmerge" --command-line-charset UTF-8 -o "C:\FILENAME.mkv"


> (3) Solution...
> A. First, like older versions, MMG should customize/disable 
> "--command-line-charset"
> When uncheck --command-line-charset, it uses the default charset 
> defined by the user's locale.

That caused very uncool problems, too.

> B. More fundamentally, MMG can stop relying on stdin (dos-box),
> and aggressively tell Windows to give it everything in 
> Unicode from the begining, by calling
> LPWSTR GetCommandLineW( VOID )
> But this has downsides...again, Win98 users will get angry. So,

Neither mmg nor mkvmerge uses Unicode internally.

> C. Something like this might be the best:
> mkvmerge -j job.utf8

This is what mkvmerge does. The correct syntax is

mkvmerge @job.utf8

Maybe I should just disable the "copy to clipboard" function and only
keep the "create option file" option.


If Darl McBride was in charge, he'd probably make marriage
unconstitutional too, since clearly it de-emphasizes the commercial
nature of normal human interaction, and probably is a major impediment
to the commercial growth of prostitution. - Linus Torvalds

More information about the Matroska-devel mailing list