From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v11 1/6] libavutil/wchar_filename.h: Add whcartoutf8, wchartoansi and utf8toansi
Date: Wed, 11 May 2022 20:50:53 +0000
Message-ID: <DM8P223MB03657EC98D163D856AE08933BAC89@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <ac5f9467-eb9a-46ec-93d5-f8e010457165@noa-archive.com>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Tobias Rapp
> Sent: Wednesday, May 11, 2022 3:33 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v11 1/6]
> libavutil/wchar_filename.h: Add whcartoutf8, wchartoansi and
> utf8toansi
>
> On 11/05/2022 09:57, Soft Works wrote:
> >
> > [...]
> >
> > I'm not sure how much you had followed, so please excuse in case you
> > had already read it: the manifest approach does not work on a
> default
> > Windows installation.
> > To activate long path support, the users needs to opt-in to a
> behavior
> > that is probably deactivated by default for some reason. Also it
> > requires administrative privileges to make this change.
> > For me - and probably for others as well - that approach is useless,
> > as it would be the same as if there would be no long path support.
> > (when you cannot rely on that feature being always working, you
> > cannot use it)
>
> For me an analogous case is the usage of the "--large-address-aware"
> linker flag. It enables FFmpeg to use more than 2GiB of memory on
> Win32.
> That feature is useless to users having <= 2GiB of total system memory
> available, and it makes no guarantee that an OOM error is avoided.
> Still
> it allows to exceed a limit for those that match the requirements --
> knowingly or by pure coincidence.
That's similar except for the fact that there wasn't an alternative
method that would always work.
I respect others opinions, but I don't agree to the "better than
nothing approach". I'm following this mailing list for a long time
and suggesting a full working solution over a half-baked or half-
working solution has always been a valid argument, so I don't see
why it shouldn't be in this case.
My interest is to have a good solution, not to block anything, so
I'll try to prepare a patch implementing path prefixing shortly.
Thanks,
softworkz
_______________________________________________
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".
next prev parent reply other threads:[~2022-05-11 20:51 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 12:08 nil-admirari
2022-04-24 22:04 ` Soft Works
2022-04-25 9:03 ` nil-admirari
2022-04-25 9:31 ` Soft Works
2022-04-25 9:51 ` nil-admirari
2022-04-25 11:12 ` Soft Works
2022-04-25 12:51 ` Hendrik Leppkes
2022-04-25 13:02 ` Martin Storsjö
2022-04-25 13:36 ` Soft Works
2022-04-29 19:08 ` nil-admirari
2022-04-25 13:17 ` Soft Works
2022-04-29 18:59 ` nil-admirari
2022-04-29 18:52 ` nil-admirari
2022-04-30 12:34 ` Soft Works
2022-05-05 20:20 ` nil-admirari
2022-05-05 22:38 ` Soft Works
2022-05-06 16:07 ` nil-admirari
2022-05-07 2:57 ` Soft Works
2022-05-07 17:33 ` nil-admirari
2022-05-07 17:59 ` Soft Works
2022-05-10 21:22 ` nil-admirari
2022-05-10 22:59 ` Soft Works
2022-05-10 23:32 ` Soft Works
2022-05-11 7:46 ` Tobias Rapp
2022-05-11 7:57 ` Soft Works
2022-05-11 8:08 ` Hendrik Leppkes
2022-05-11 9:03 ` nil-admirari
2022-05-11 13:32 ` Tobias Rapp
2022-05-11 20:50 ` Soft Works [this message]
2022-05-11 8:57 ` nil-admirari
2022-05-14 0:42 ` Soft Works
2022-05-15 19:53 ` nil-admirari
2022-05-15 20:34 ` Soft Works
2022-05-16 8:49 ` nil-admirari
2022-05-08 19:48 ` Martin Storsjö
2022-04-25 20:51 ` Stephen Hutchinson
2022-04-29 19:25 ` nil-admirari
-- strict thread matches above, loose matches on Subject: below --
2022-04-23 20:56 Nil Admirari
2022-04-24 3:39 ` Soft Works
2022-05-07 17:57 ` Soft Works
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM8P223MB03657EC98D163D856AE08933BAC89@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz@hotmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git