URenko

There are actually two problems. The first is the same as #7456 and #6098: `None` encoding does not disable encoding. It can be mitigated with the trick mentioned in #7456...

I have opened a pr that should resolve the original problem. But I realized the "bare minimum setup" actually reveals the third problem: The case when there is some special...

This is an expected behavior, except for your last paragraph. rclone assumes your file path in the local filesystem is already encoded in a way specified in `local-encoding`. `Pipe` (`|`...

> for the command line parameters and the remote each have their own defaults, yet can be both overwritten by `local-encoding` `local-encoding` only specifies the encoding for the local filesystem....

> Specifically, it causes statements like `rclone copy .` to spontaneously miss if `.` expands to a path with a Full Width replacement character. This is actually a bug, I...

> > The behavior of `None` was not changed to keep backward compatibility. > > I think I'd prefer `None` to do what people expect and not do any encoding....

@ncw any progress or further concern? :-)

fixed #7824 > Specifically, it causes statements like rclone copy . to spontaneously miss if . expands to a path with a Full Width replacement character.

其实是有意不主动支持，以免失效 这一issue就开着留予会看到的有缘人吧

stale