Not working when there are Umlauts in the Output

[SenorCerveza]

Hello

We are using a German environment to query the OneDrive Status. As soon the Field "Label" contains a string with an Umlaut (ä, ö, ü), the Output stops at this point resulting in an incomplete JSON response in STDOUT.

We tried to run the binary in the 25001 Codepage (UTF8) and also redirecting the output directly to a file with UTF8 and also changed the system wide Regional Settings to the new UTF8 (beta) feature on the Operating System.

None of these worked. Can this please be addressed? As I can see, the JSON serializer using UTF16 which should be fine but it seems somehow the API class can't handle non latin chars.

Kindly

[rodneyviana]

SenorCerveza (finally a worth alias :) ),

See the new version I just published and follow the Troubleshooting steps in README,md and report the results if you still have problems.

[SenorCerveza]

Hey and thanks for your reply :)

I'm a bit confused. So you suggest to use the switch to output it to a File directly instead (which is unicode)? In your README it says to use "ODSyncUtil.exe -s output.txt -d" but you can't use -d with another switch as you described a bit above and it also don't work.

So did you change anything related to get a native UTF8 Output which supports umlauts or do you need the debug version to troubleshoot?

As this is a productive environment we have little room to just "test" it. And we can't really force reproduce it.

Kindly

[rodneyviana]

Just try the changes and only if it fails, run with -d to troubleshoot

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: SenorCerveza @.> Sent: Friday, February 23, 2024 4:32:11 AM To: rodneyviana/ODSyncUtil @.> Cc: Comment @.>; Subscribed @.> Subject: Re: [rodneyviana/ODSyncUtil] Not working when there are Umlauts in the Output (Issue #10)

Hey and thanks for your reply :)

I'm a bit confues. So you suggest to use the switch to output it to a File directly instead (which is unicode)? In your README it says to use "ODSyncUtil.exe -s output.txt -d" but you can't use -d with another switch as you described a bit above and it also don't work.

So did you change anything related to get a native UTF8 Output which supports umlauts or do you need the debug version to troubleshoot?

As this is a productive environment we have little room to just "test" it. And we can't really force reproduce it.

Kindly

— Reply to this email directly, view it on GitHubhttps://github.com/rodneyviana/ODSyncUtil/issues/10#issuecomment-1961083493 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGT5MAUHJIDWGIDABECTFDDYVBV2ZBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLLDTOVRGUZLDORPXI6LQMWWES43TOVSUG33NNVSW45FGORXXA2LDOOJIFJDUPFYGLKTSMVYG643JORXXE6NFOZQWY5LFVE3TKMBQGM3TOMZUQKSHI6LQMWSWS43TOVS2K5TBNR2WLKRSGE2DQOBYG4YTIONHORZGSZ3HMVZKMY3SMVQXIZI. You are receiving this email because you commented on the thread.

Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[rodneyviana]

Also I made changes to allow -d to work with -s (version 1.0.4.5000)

[SenorCerveza]

Allright thanks! Looks promising so far. We implemented it as additional step but not relying on it on productive environment. So we see if it "would" fail.

Will report back.

And thanks :)

[SenorCerveza]

Hey

It seems it working now. We hadn't a single issue with using the file output and reading it back with Powershell. Thanks a lot :)

Kindly