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 981E140306 for ; Fri, 18 Feb 2022 19:04:09 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 349DF68B0A8; Fri, 18 Feb 2022 21:04:07 +0200 (EET) Received: from msg-1.mailo.com (msg-1.mailo.com [213.182.54.11]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 65CE568AFC9 for ; Fri, 18 Feb 2022 21:04:00 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mailo.com; s=mailo; t=1645211039; bh=PUXu2lH3dUcGdPZaUHb117cRqJvLXWGMvDjx0PBeQM0=; h=X-EA-Auth:From:To:Date:Subject:MIME-Version:X-Mailer:Message-ID: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=G5vh66oAiTr7bPJwzlVmYhFaEe87YH5JvLqwMJIsGInyHx4bnNOZ2CFwlxgnF9x4D enziX6dm30Isd2ccqeUvNNH6UmYeaWAnT76qQV2XW1vC7LVTGLkhe5GCer3BiSMhZt sruP9aSlXcUiudgxKPPtIyNNjCThmOBFqWGUiWjk= Received: by www-7.mailo.com with http webmail; Fri, 18 Feb 2022 20:03:59 +0100 (CET) X-EA-Auth: qMduGgGbXbx+LThCrqvIoWXc1vBfmN02DhPvJmBCpLRis9SlDjWMPuoVtdt1GWhzO2nqKhbeKq+lOGrm3CW2u8Ie2e/eB6y6 From: nil-admirari@mailo.com To: ffmpeg-devel@ffmpeg.org Date: Fri, 18 Feb 2022 20:03:59 +0100 (CET) X-Priority: 3 MIME-Version: 1.0 X-Mailer: COMS/EA21.01/r20211110 Message-ID: In-Reply-To: <94ddaad-1c96-2eea-39ee-222c41f36b3@passwd.hu> Subject: Re: [FFmpeg-devel] [PATCH v3 5/5] fftools: Enable long path support on Windows (fixes #8885) 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: > Generally UTF-8 codepage should not be needed, because unicode windows functions should be used everywhere, right? No. FFmpeg does not seem to use WinAPI ANSI functions explicitly, but it still uses ordinary stdlib functions (fopen etc.) instead of their wide equivalents. See https://ffmpeg.org/pipermail/ffmpeg-devel/2022-February/293169.html. > And use simple fftools/fftools.manifest and fftools/manifest.rc as filenames, because later other things might be put there, not only utf8/longpath support. Done in https://ffmpeg.org/pipermail/ffmpeg-devel/2022-February/293204.html. > I'd perfer if you enable UTF8 codepage in a separate patch. Done in https://ffmpeg.org/pipermail/ffmpeg-devel/2022-February/293207.html. Actually, UTF-8 codepage was already absent in the fourth version of this patch: https://ffmpeg.org/pipermail/ffmpeg-devel/2022-February/293168.html. Microsoft documentation (https://docs.microsoft.com/en-us/windows/win32/sbscs/application-manifests) says that manifests can be added to DLLs too, and does not say whether longPathAware and activeCodePage apply to the process or to individual DLLs loaded into it. Thus I wasn't sure whether ANSI-encoded strings passed to external APIs will be decoded correctly. Unfortunately, if it were that longPathAware is per DLL, manifests would need to be added to avformat.dll etc., so I decided to test how things actually work. It turned out that longPathAware and activeCodePage are applied per process, which means that all externally loaded libraries will have CP_ACP set to CP_UTF8, which means that there should be no problem in using activeCodePage in FFmpeg. For some reason, fifth version of patches ended up being sent as separate messages. Only the second part (https://ffmpeg.org/pipermail/ffmpeg-devel/2022-February/293206.html) is a reply to the first (https://ffmpeg.org/pipermail/ffmpeg-devel/2022-February/293205.html). It's a strange email glitch. I swear I used git send-email to send these patches. _______________________________________________ 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".