mirror of
https://github.com/abraunegg/onedrive
synced 2024-05-04 15:03:24 +02:00
Update usage.md
* Improve restriction language for clarity
This commit is contained in:
parent
c592ba5a25
commit
8f407375b8
|
@ -93,11 +93,12 @@ To ensure seamless synchronisation with Microsoft OneDrive, it's critical to adh
|
|||
#### Key Restrictions and Limitations
|
||||
* Invalid Characters:
|
||||
* Avoid using the following characters in names of files and folders: `" * : < > ? / \ |`
|
||||
* Names should not start or end with spaces, nor should they end with a period `.`
|
||||
* Names should not start or end with spaces
|
||||
* Names should not end with a fullstop / period character `.`
|
||||
* Prohibited Names:
|
||||
* Certain names are reserved and cannot be used for files or folders: `.lock`, `CON`, `PRN`, `AUX`, `NUL`, `COM0 - COM9`, `LPT0 - LPT9`, `desktop.ini`, any filename starting with `~$`
|
||||
* Notably, `_vti_` cannot appear anywhere in a file name
|
||||
* `forms` is unsupported at the root level of a synchronisation directoryy
|
||||
* The text sequence `_vti_` cannot appear anywhere in a file or directory name
|
||||
* A files and folder called `forms` is unsupported at the root level of a synchronisation directory
|
||||
|
||||
Should a file or folder infringe upon these naming conventions or restrictions, synchronisation will skip the item, indicating an invalid name according to Microsoft Naming Convention. The only remedy is to rename the offending item. This constraint is by design and remains firm.
|
||||
|
||||
|
|
Loading…
Reference in a new issue