Sometime adapt to environment is needed, current we need windows user, isn't it? Maybe we should add automatic detecting for this BAD stuff, instead of new protocol. 2011/4/15 Måns Rullgård <[email protected]>
> Luca Barbato <[email protected]> writes: > > > On 04/13/2011 07:46 AM, Kirill Gavrilov wrote: > >> Hi, I'm newbie here. > >> > >> No Unicode API in FFmpeg make me very sad (this is important only for > >> Windows applications). > >> I partially investigate the current i/o and found that creating Unicode > >> versions for major functions cause to create the tons of another stuff. > >> But I found another 'stupid' way - I define new fileU protocol which > assume > >> the input path is in utf-8, automatically converts it to the utf16 > string > >> and use Unicode function to open the file. > >> > >> Tell me if there is a better way to provide Unicode support or give me > your > >> suggestions how I should modify the patch. > >> Thanks. > > > > The idea isn't bad, I'd like to have the opinion of window users. > > I think it is a stupid idea, just like Windows in the first place. If > an OS refuses to support unicode filenames in a sane way, its users will > simply have to accept not having that feature. End of story. > > -- > Måns Rullgård > [email protected] > _______________________________________________ > libav-devel mailing list > [email protected] > https://lists.libav.org/mailman/listinfo/libav-devel > -- wucan
_______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
