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 0F2B3426E6 for ; Mon, 25 Apr 2022 20:51:42 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 068FB68B15A; Mon, 25 Apr 2022 23:51:40 +0300 (EEST) Received: from mail-vk1-f171.google.com (mail-vk1-f171.google.com [209.85.221.171]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 1F31068AEFA for ; Mon, 25 Apr 2022 23:51:33 +0300 (EEST) Received: by mail-vk1-f171.google.com with SMTP id c4so7775883vkq.9 for ; Mon, 25 Apr 2022 13:51:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=x4Hb9t9EPrZbszY0qSvBmRnHOKsIe0BSa+ChArTgM0E=; b=SsqikhgSkLzyYy5M2nFAPw11edOKEtM6drBidJzR30PXwjB7IszrCaCh2bt+HsDzGi CrtkkvJVwllDD78NA2LYuyM6UMqU9dA06tfp2xpxDYHeekJy6/hNi7nbJK4LI8ga9R+u 00iNtNUZAchOCVGmAUVz9OlXWbfe8+W8xxZiozgHE7YTfEdO8K668+1xmbvIiLhjpkVL /xCh57HgDKdXkhVXpdUQKcSzUHPrW6r9moo/d6zYcvuIR1TLahXf/h8CsWOa7al5wDZz OAaoZtfuyClUND73J+3ZtORzEU3+3puPbt8sm3+qgKZXsfHld33XVBw6a5IWkr9yfvFc wSCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=x4Hb9t9EPrZbszY0qSvBmRnHOKsIe0BSa+ChArTgM0E=; b=p1gAnac/ZG+oPWx619GlxGXLoyLQCURjOSgCTigBmVO1ihHPnDcXwG8wUVjbICLMtp 7ZYaYv0PMozwo9aSDvpAdkLirEJ4reDeZKhRrBgrljDEAdsYFf5UOL7EZDJ4qL4OwF2I jb3GUgZQnx+E7S3Dt4PBT0hWSlSdKNdHFsJEh6SblcqrLVRPfB5q1OYaUKT8/4fsSZT1 2y3eGQ03iIsKe3M3Vei384H+zYmj5zRVLkY8w7qkiLaNWufZsrnsoTHDfxqxFXyxGh0f zdWVhRvOMgOSwLeASWjt64TK1y3S8QfC/GopmAPEGcSD04YKLegPLiN/E4L6rV8vV2yU Wwyg== X-Gm-Message-State: AOAM532T+An4oYmDsxFTrpnLteNAzO8Pg2y/CubE59566ArseTZPv7y5 0waYALgU2uuO9QCDAmsIv8bYXA+Jmjg= X-Google-Smtp-Source: ABdhPJww4fc+Tl1xzBsrh2bzLV6CIDnmeMrmWBkX/4iLN90CckNakPBb5W4xXqrRlqQJ5dy6HAYTmw== X-Received: by 2002:a1f:38c2:0:b0:349:9667:9232 with SMTP id f185-20020a1f38c2000000b0034996679232mr5936043vka.16.1650919891386; Mon, 25 Apr 2022 13:51:31 -0700 (PDT) Received: from [192.168.1.5] (075-115-109-114.inf.spectrum.com. [75.115.109.114]) by smtp.gmail.com with ESMTPSA id n21-20020ab06035000000b003626f894df6sm39287ual.36.2022.04.25.13.51.30 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Apr 2022 13:51:31 -0700 (PDT) Message-ID: <933601d5-5347-111a-323f-279e20dfb3bb@gmail.com> Date: Mon, 25 Apr 2022 16:51:29 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Content-Language: en-US To: ffmpeg-devel@ffmpeg.org References: From: Stephen Hutchinson 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Thus far I've avoided jumping into this because I genuinely do not care about Windows' code page shenanigans or what-all, but because this seems to be zeroing in on one thing in particular... On 4/25/22 5:03 AM, nil-admirari@mailo.com wrote: > If you were to look at the code, you would've seen that charset conversion > was already there. AviSynth is not Unicode-aware, it expects ANSI strings. > Inline charset conversion was replaced by a library call, which, again, > was already there, only slightly extended. > > Which is necessary for compatibility with AviSynth, It has nothing to do with compatibility with AviSynth, because AviSynth just uses the code page the system is set on. What 'it's not Unicode-aware' means is that it doesn't jump into convoluted conversions to UTF-16, because that's what Windows meant by 'Unicode' for 20+ years, and nobody from either classic AviSynth or Plus wanted to do that, because it's an absolute mess and now that Plus is cross-platform, utterly pointless on every other OS, because they all use UTF-8 and have for at least 15 years, if not [much] longer. Some third-party applications that utilize AviSynth have decided they want to bend over backwards to make sure their users don't have to freak themselves out by telling Windows to use UTF-8 as the system code page, so they'll do an end-run around it and use these sorts of manifests to force the program's locale to UTF-8, AppLocale style. But that's not a compatibility issue with AviSynth. 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. Nothing special was required regarding locale support when Linux, macOS, BSD, and Haiku support landed. All of those use UTF-8 and AviSynth+ works with it transparently. And it works with UTF-8 on Windows transparently if you've gone into the Region Settings and actually enabled it. Even AviSynth 2.6 is cool with it, as this screenshot from *two years ago* illustrates: https://i.imgur.com/1p5osrE.jpg _______________________________________________ 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".