From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 8073442789 for ; Fri, 29 Apr 2022 19:25:34 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 035B568B2F6; Fri, 29 Apr 2022 22:25:31 +0300 (EEST) Received: from msg-6.mailo.com (ip-16.mailobj.net [213.182.54.16]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 96ED068A7FD for ; Fri, 29 Apr 2022 22:25:24 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mailo.com; s=mailo; t=1651260323; bh=UppoLPDWzyZ5ECdCKbDAkMxyzkM281rsHU2a4uoQzP0=; h=X-EA-Auth:From:To:Date:Subject:MIME-Version:X-Mailer:Message-ID: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=gABkdmHJrWVTrZ2fj17jnd+HniFPlQHm8pVMXDkzsPRzyG5y8+5itCI+H8kPN6PgK +sp/27DbipwGpHPo/rAr6PSgEE8borU8fW6Tcz0UKHNQOu4p18iEQGJ98YeujVRLCH 3vb5AMDqF07weQgyALfXmlAkob0OTRPWLIsWIR0w= Received: by www-7.mailo.com with http webmail; Fri, 29 Apr 2022 21:25:23 +0200 (CEST) X-EA-Auth: G3qg0rxPtT3qznVOaUqHvKg2yw6i559iE1RU4AHYOcV0n3FQQ2BZSJUzrHtaqTri1MqIINfBmucd0JFiqmIX7beXYxn2ELom From: nil-admirari@mailo.com To: ffmpeg-devel@ffmpeg.org Date: Fri, 29 Apr 2022 21:25:23 +0200 (CEST) X-Priority: 3 MIME-Version: 1.0 X-Mailer: COMS/EA21.01/r20220415 Message-ID: In-Reply-To: <933601d5-5347-111a-323f-279e20dfb3bb@gmail.com> Subject: Re: [FFmpeg-devel] [PATCH v11 1/6] libavutil/wchar_filename.h: Add whcartoutf8, wchartoansi and utf8toansi X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: > As soon as Microsoft actually makes UTF-8 > the default code page going forward, that issue will poof > out of existence, as if by magic. It already does if you > toggle it on in the system settings. True. System-wide UTF-8 can cause problems with legacy software, but starting with Windows 11 such software can specify a non-UTF8 activeCodePage for itself: https://docs.microsoft.com/en-us/windows/win32/sbscs/application-manifests#activeCodePage. "Set active code page to UTF-8 on Windows" is a separate patch, independent from all others: https://ffmpeg.org/pipermail/ffmpeg-devel/2022-April/295572.html. If it's deemed to be too problematic, the rest of the patchset can simply be merged without it. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".