https://bugs.documentfoundation.org/show_bug.cgi?id=173260
Bug ID: 173260
Summary: Windows: Documents with path lengths exceeding 260
characters revert to 8.3 short DOS names (~1.ODT) when
opened or saved
Product: LibreOffice
Version: 26.2.5.2 release
Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: LibreOffice
Assignee: [email protected]
Reporter: [email protected]
When a document's full absolute pathname exceeds 260 characters on Windows
10/11, LibreOffice converts the long physical path into its legacy 8.3 short
path alias (e.g.,
"C:\Users\Pierre\Books\ODT\WILLIA~1.SHA\(4&5)C~1\GE93C3~1.ODT").
ThisComponent.getURL() and window titles report the 8.3 short name rather than
the full canonical filename. File Explorer launches pass short paths to
soffice.exe.
REQUESTED FIX: Ensure that LibreOffice's Windows application manifest declares
<longPathAware>true</longPathAware> and ensure that standard file I/O calls in
sal/osl/win32 prepend \\?\ for paths exceeding MAX_PATH.
FURTHER COMMENT: C'mon, guys. Windows NT 3.1 and NTFS began supporting long
paths in 1993, 33 years ago. Windows 10 1607 stopped enforcing 260-character
MAX_PATH limits in common Win32 file and directory functions in 2016, 10 years
ago. 64-bit apps and long pathnames are now the norm. What on EARTH is this
archaic limit doing in 64-bit LibreOffice 26.2.5.2? This needs to be fixed. In
Bug 151117 in 2022, Mike Kaganski reported this as a regression from
LibreOffice 7.3 to LibreOffice 7.4, but here it is again. It's time to squash
the bug for good. I mean seriously: the last time I ran into problems with
overly long pathnames was over ten years ago and it involved 32-bit apps.
--
You are receiving this mail because:
You are the assignee for the bug.
