mirror of https://git.tukaani.org/xz.git
Windows: Update manifest comments about long UTF-8 filenames
This commit is contained in:
parent
0dfc67d37e
commit
b01b095802
|
@ -89,11 +89,18 @@ when writing to console with printf(). With UCRT it works.
|
||||||
Long path names
|
Long path names
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
The manifest enables support for path names longer than 259
|
The manifest enables support for path names longer than 260 wide
|
||||||
characters if the feature has been enabled in the Windows registry.
|
characters (UTF-16 code units) if the feature has been enabled in
|
||||||
Omit the longPathAware element from the manifest if the application
|
the Windows registry. Omit the longPathAware element from the manifest
|
||||||
isn't compatible with it. For example, uses of MAX_PATH might be
|
if the application isn't compatible with it. For example, some uses
|
||||||
a sign of incompatibility.
|
of MAX_PATH might be a sign of incompatibility.
|
||||||
|
|
||||||
|
Note that UTF-8 encoded filenames can exceed MAX_PATH (260) bytes when
|
||||||
|
the UTF-16 form is still within MAX_PATH wide characters. In this
|
||||||
|
situation the application doesn't need to be long path aware: functions
|
||||||
|
like _open() work with UTF-8 names that exceed MAX_PATH bytes if the
|
||||||
|
wide character form stays within MAX_PATH wide characters. (MAX_PATH
|
||||||
|
includes the terminating null character.)
|
||||||
|
|
||||||
Documentation of the registry setting:
|
Documentation of the registry setting:
|
||||||
https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later
|
https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later
|
||||||
|
@ -130,9 +137,9 @@ trustInfo
|
||||||
longPathAware
|
longPathAware
|
||||||
|
|
||||||
Declare the application as long path aware. This way many file
|
Declare the application as long path aware. This way many file
|
||||||
system operations aren't limited by MAX_PATH (260 characters
|
system operations aren't limited to MAX_PATH (260) wide characters
|
||||||
including the terminating null character) if the feature has
|
(including the terminating null character). The feature has to be
|
||||||
also been enabled in the Windows registry.
|
enabled in the Windows registry too.
|
||||||
|
|
||||||
activeCodePage
|
activeCodePage
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue