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 C150342540 for ; Sat, 23 Apr 2022 21:28:25 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 5DF1C68B3BB; Sun, 24 Apr 2022 00:28:23 +0300 (EEST) Received: from msg-1.mailo.com (msg-1.mailo.com [213.182.54.11]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id CDE5A68B223 for ; Sun, 24 Apr 2022 00:28:16 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mailo.com; s=mailo; t=1650749296; bh=XpjLeoyg2uJv7ZF6yo5YuYZoZ9yUoGTaqHRZtiU3yT4=; h=X-EA-Auth:From:To:Date:Subject:MIME-Version:X-Mailer:Message-ID: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=bXWgJ3KXpG/gyuGcJ+Ci/tU/gjZKW7C8VKJEcH+8i+WWZ0ys/sDdLSSPcz3bx79NB Zj6MSC+5PVyszAFPj89K296XnQsLTT9aN+E016331s8jjBWhwfoxzzdziwt8gv5Y1/ GFjRBfBfJVBuzzx6FT+clC8KmdTcA9SvBGus2Amw= Received: by www-7.mailo.com with http webmail; Sat, 23 Apr 2022 23:28:16 +0200 (CEST) X-EA-Auth: H/qazvJ3hmhSloykVdrs2wnuMWc0w0pLLOvGUdQKpJr7GUrPfJciuuX4UQe9lI4ze7CQLboGy2tBP/AOlCoWGQ/W9IWTphDm From: nil-admirari@mailo.com To: ffmpeg-devel@ffmpeg.org Date: Sat, 23 Apr 2022 23:28:16 +0200 (CEST) X-Priority: 3 MIME-Version: 1.0 X-Mailer: COMS/EA21.01/r20220415 Message-ID: In-Reply-To: <9f1ef01d-bde5-897-23aa-8f60db78566d@martin.st> Subject: Re: [FFmpeg-devel] [PATCH v9 6/6] fftools: Use UTF-8 on Windows 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: > This needs a similar commit message as what I suggested for the previous > commit, explaining what it does, when, why, and clarifying that this is a > noop for older versions. Done: https://ffmpeg.org/pipermail/ffmpeg-devel/2022-April/295572.html. > In particular, it'd be interesting to know why we actually need this; we > normally should be doing all the conversions between wchar_t and utf8 > everywhere anyway, so the exact codepage used shouldn't really matter > much? I presume the main noticable benefit is that it improves the path > name compatibility with avisynth which is stuck on using CP_ACP pathnames? Yes, it is primarily due to AviSynth. From https://github.com/staxrip/staxrip/wiki/AviSynth-Unicode-support-on-Windows-10-1903: > All AviSynth apps used by StaxRip have a UTF-8 manifest to enable full Unicode support for AviSynth on Windows 10 1903 or higher: > ... > ffmpeg.exe (Patman Mod) > ... > On Windows 10 1903 or higher all these apps expect AviSynth scripts to be UTF-8 encoded, ANSI encoded scripts don't work. _______________________________________________ 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".