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 A0401423DA for ; Sun, 15 May 2022 19:53:57 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 229E568B4CC; Sun, 15 May 2022 22:53:54 +0300 (EEST) Received: from msg-4.mailo.com (ip-15.mailobj.net [213.182.54.15]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 1433D68B1FD for ; Sun, 15 May 2022 22:53:46 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mailo.com; s=mailo; t=1652644425; bh=ZEAV7RBumQV3JRa7LXXibrcOJdg2bLiIOfSN6RxXoHE=; h=X-EA-Auth:From:To:Date:Subject:MIME-Version:X-Mailer:Message-ID: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=G4txKy4QBVzXwCG4ftE18uB4aAEit0G0u4hLMYx2NHYylzsE6wuZTi4HeztgP8kWm PpHAwS2B/3in7wXbcBAl1kNfErCVa3hG/wDv4knSQgjCfpqpANPIs6PrMhEcIw3sak hp97WWSpbLYNP/oR+XqTts7fqF/QPfI+lvb0llPc= Received: by www-7.mailo.com with http webmail; Sun, 15 May 2022 21:53:45 +0200 (CEST) X-EA-Auth: NrgwG+yt9YJHyPVL+Mkux1VccOWjcf+o9v5Zm7FOMGsaRzOXfvcfTJOEHMUYd5kAKTaDuutOjvx6ltGQUdpcKoD1y/mi3NfC From: nil-admirari@mailo.com To: ffmpeg-devel@ffmpeg.org Date: Sun, 15 May 2022 21:53:45 +0200 (CEST) X-Priority: 3 MIME-Version: 1.0 X-Mailer: COMS/EA21.01/r20220415 Message-ID: In-Reply-To: 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: > All these paths end up either in win32_open (in file_open.c) or in > one of the functions mapped inside os_support.h where they are now > (with my submitted patchset) handled by the get_extended_win32_path() > function, which handles all cases (e.g. forward slashes, relative paths, > prefixed, non-prefixed, UNC, drive letters, long, short, etc.) in > the same way as .NET does. You are saved by the fact that nobody tries to get a path name from a file descriptor or a FILE* (which is indeed difficult, but possible), and then appending additional path components to such obtained path name; thus turning a normalised path name into denormalised one. .NET by the way, is not fully \\?\-aware. Its Path.Combine https://github.com/dotnet/runtime/blob/main/src/libraries/System.Private.CoreLib/src/System/IO/Path.cs would blindly append "..\relative" to "\\?\C:\extended" turning it into invalid "\\?\C:\extended\..\relative" > I did that now, and you can see that it's as easy as I said. If it's so easy, then why I'm still finding problems: - absence of \\.\ handling: https://ffmpeg.org/pipermail/ffmpeg-devel/2022-May/296447.html - stat and is_dos_path: https://ffmpeg.org/pipermail/ffmpeg-devel/2022-May/296448.html - av_fopen_utf8 remnants: https://ffmpeg.org/pipermail/ffmpeg-devel/2022-May/296452.html _______________________________________________ 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".