robertschulze

Results 22 comments of robertschulze
trafficstars

> @robertschulze > > I reconsidered based on your comment. > > I agree with the approach of using only the `win32` backend, which can still function even if `UIAutomationCore.dll`...

[GUI.onedrive-gui.log](https://github.com/bpozdena/OneDriveGUI/files/13690188/GUI.onedrive-gui.log) [GUI.robert.onedrive.log](https://github.com/bpozdena/OneDriveGUI/files/13690189/GUI.robert.onedrive.log) [CONSOLE.robert.onedrive.log](https://github.com/bpozdena/OneDriveGUI/files/13690209/CONSOLE.robert.onedrive.log) Hi, this is the output to the console and log file(s) when running in GUI or on CONSOLE. You can see that it just stops. I don't...

We have the same issue in 1.21.10. It appears an upgrade will not solve it, is it correct?

> What sorts of setups are other people using? Is Gitea running behind a reverse proxy? Are you requiring HTTP authentication? I'm starting to wonder if there's some specific configuration...

Very strange, I don't think I did anything special to create these. Maybe the HTML entities are an artifact of me "mounting" other OneDrives within my main OneDrive?

You are probably right: even if I create a folder "BücherTest" within my main OneDrive (not a linked one) in the main root dir the special letter is HTML encoded...

For reference I also tested on a corporate SharePoint and also here folders with special characters are HTML encoded: ![image](https://github.com/abraunegg/onedrive/assets/13728481/2ca0b56a-cc3f-4552-8891-b452b7375386) For pure English locale this is not the case? Or...

In the Elements view in the browser it is indeed correctly encoded also for my OneDrives: ![image](https://github.com/abraunegg/onedrive/assets/13728481/5c1978d7-bd0e-4bff-bf46-a794b2524a90) So I guess here the browser has already applied some logic to convert...

@abraunegg I did a number of tests. Disabling all plugins in Chrome did not help, changing my country to Australia also did not help (language was already English (United States))....