{"author":"Jay Satiro","author_email":"raysatiro@yahoo.com","author_time":1714722050,"commit_time":1734842859,"committer":"Jay Satiro","committer_email":"raysatiro@yahoo.com","hash":"18650ea01166c0cbc332f574c533f1337642a7cf","message":"curl_multibyte: support Windows paths longer than MAX_PATH\n\n- Add a helper function for the Windows file wrapper functions that will\n  normalize a long path (or a filename in a long path) and add the\n  prefix `\\\\?\\` so that Windows will access the file.\n\nPrior to this change if a filename (when normalized internally by\nWindows to its full path) or a path was longer than MAX_PATH (260) then\nWindows would not open the path, unless it was already normalized by the\nuser and had the `\\\\?\\` prefix prepended.\n\nThe `\\\\?\\` prefix could not be passed to file:// so for example\nsomething like file://c:/foo/bar/filename255chars could not be opened\nprior to this change.\n\nThere's some code in tool_doswin that will need to be modified as well\nto further remove MAX_PATH (aka PATH_MAX) limitation.\n\nRef: https://github.com/curl/curl/issues/8361\nRef: https://github.com/curl/curl/pull/13512\nRef: https://learn.microsoft.com/en-us/dotnet/standard/io/file-path-formats\nRef: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation\n\nCloses https://github.com/curl/curl/pull/13522\n","parents":["7cf47a7740f666ae3c06361781a341a7da403041"],"tree_hash":"6cd3b35e96fe4994daa31a054e71c7e37dc6c551"}