Converting copied Library ID from Unicode to ASCII

%3CLINGO-SUB%20id%3D%22lingo-sub-1379710%22%20slang%3D%22en-US%22%3EConverting%20copied%20Library%20ID%20from%20Unicode%20to%20ASCII%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1379710%22%20slang%3D%22en-US%22%3E%3CP%3ELast%20August%2C%20the%20OneDrive%20Group%20Policy%20documentation%20has%20been%20updated%20to%20include%20a%20Unicode%20to%20ASCII%20conversion%20to%20manage%20synced%20library%20(see%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SharePoint%2Fcommit%2Ff0e63a2a667a41e514f24b1bfd76f5654c22cca8%23diff-b2e9feac11fcf00c73901527a94c69e8%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ecommit%3C%2FA%3E).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESeveral%20users%2C%20including%20myself%2C%20reported%20that%20it%20adding%20synced%20libraries%20works%20well%20even%20without%20replacing%20Unicode%20with%20ASCII%20(see%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SharePoint%2Fissues%2F323%23issuecomment-555513345%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SharePoint%2Fissues%2F323%23issuecomment-589993484%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%20and%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SharePoint%2Fissues%2F1941%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENevertheless%2C%20the%20need%20to%20manually%20replace%20Unicode%20with%20ASCII%20would%20make%20the%20procedure%20a%20little%20bit%20cumbersome%2C%20no%20longer%20that%20straightforward.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anyone%20have%20some%20clarifications%20on%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1379710%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EGroup%20Policies%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EGroup%20Policy%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOneDrive%20for%20Business%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Contributor

Last August, the OneDrive Group Policy documentation has been updated to include a Unicode to ASCII conversion to manage synced library (see commit).

 

Several users, including myself, reported that it adding synced libraries works well even without replacing Unicode with ASCII (see here, here and here).

 

Nevertheless, the need to manually replace Unicode with ASCII would make the procedure a little bit cumbersome, no longer that straightforward.

 

Does anyone have some clarifications on this?

0 Replies