You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to revisit the discussion in #151, as there may be a much simpler solution for handling paths with illegal characters in WSL. Since WSL 17101 (see also microsoft/WSL#1514), paths containing illegal characters are re-encoded using private Unicode characters (for example, the colon : becomes 0xf03a). This behavior also applies to WinBtrfs, so a possible solution could be to add support for reversing this mapping, which would enable handling these paths correctly.
I would like to revisit the discussion in #151, as there may be a much simpler solution for handling paths with illegal characters in WSL. Since WSL 17101 (see also microsoft/WSL#1514), paths containing illegal characters are re-encoded using private Unicode characters (for example, the colon : becomes 0xf03a). This behavior also applies to WinBtrfs, so a possible solution could be to add support for reversing this mapping, which would enable handling these paths correctly.
This approach has already been implemented in other projects, such as Cygwin, which handles similar issues with special symbols. You can find the relevant Cygwin commit source code here: Cygwin commit. Additionally, the latest implementation of this solution in Cygwin can be found in the file strfuncs.cc.
https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars
cygwin/cygwin@9fa1c64
https://github.com/cygwin/cygwin/blob/main/winsup/cygwin/strfuncs.cc
I propose that this solution be considered for inclusion in WinBtrfs, as it would simplify the handling of paths with special reserved symbols.
The text was updated successfully, but these errors were encountered: