255 byte path limit on Windows is a thing of the past since 2016, please respect that for flac/metaflac

Hi,

would it be possible that flac and metaflac can respect that the 255byte limit on Windows 10+ is a thing of the past as said since 2016.
It is more than annoying that in my batch processes both command line programs tell me that no files with the given name exist

 ERROR: reading metadata, status = "FLAC__METADATA_CHAIN_STATUS_ERROR_OPENING_FILE"

The FLAC file could not be opened.  Most likely the file does not exist
or is not readable.

The files are perfectly OK and usable, can be tested with any other program (e.g. ffprobe) or loaded (foobar etc,), I have to program workarounds to make testing/executing flac/metaflac possible.
It is no offense of course, but I think after 10 years this should be doable.

Please write me a short reply if you intend to fix that, or not.

Many thanks!

Start by reproducing the reported failure with flac and metaflac on Windows using paths longer than 255 bytes, then trace how each command-line program opens the file. Done means both programs can access valid long-path files and preserve the existing metadata operations and error handling.