Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| incompatiblecharacters [2019_12_09 17:34] – [Incompatible Characters] jim | incompatiblecharacters [2024_02_28 01:03] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | # Incompatible Characters | + | # File Naming Conventions / Incompatible Characters |
| - | Don' | + | The Access Anywhere covers a myriad of storage solution in addition to being able to be presented on files systems on a multitude of Operating Systems. There is no guarantee that naming conventions from back-end storage solutions will be honoured on end user file systems. |
| + | |||
| + | Generally you should not name your files or folders with the following characters: | ||
| < | < | ||
| Line 23: | Line 25: | ||
| Files or folders that begin with a period will meta-sync properly but Mac, Linux, Windows operating systems may regard them as system files and hide them automatically. You may not be able to see them without modifying advanced settings on your PC. | Files or folders that begin with a period will meta-sync properly but Mac, Linux, Windows operating systems may regard them as system files and hide them automatically. You may not be able to see them without modifying advanced settings on your PC. | ||
| - | Also please be aware of other character issues that are not immediately obvious but can cause conflicts or issues such as trailing spaces in directory names for example. | + | Also please be aware of other character issues that are not immediately obvious but can cause conflicts or issues such as leading or trailing spaces in directory names or files for example. |
| + | |||
| + | Also be aware of using characters that are not generally considered best practice, such as tildes(~)for example, which should not really be used in a file / folder, as on many file systems a file/folder name may contain a tilde within each component of the name that is too long to comply with normal naming rules. | ||
| + | |||
| + | ## Desktop File System Compliance | ||
| + | |||
| + | As The Access Anywhere supports data that may already exist on a storage endpoint that data may not honour the data integrity semantics of the Windows / Mac / Linux operating systems. | ||
| + | |||
| + | Examples include duplicate file names, limitation on long file names, duplicate path etc. | ||
| + | |||
| + | This may lead to issues being able to access data through the drive as the windows / Mac operating system is unable to present it. | ||
| + | |||
| + | If this is the case then consider using Access Anywhere web interface or the Cloud Explorer Application for such files, and additionally if you intend to work with such storage from a desktop files system consider naming conventions that will not trip up the operating system (note this is only applicable to the drives not other self contained desktop applications). | ||
| ##Ignored Files | ##Ignored Files | ||
| Line 35: | Line 49: | ||
| ##Case Conflicts | ##Case Conflicts | ||
| - | Linux operating systems enable users to have two files or folders with the same name but different capitalization. By default, Mac and Windows do not differentiate file or folder names by case. If the File Fabric | + | Linux operating systems enable users to have two files or folders with the same name but different capitalization. By default, Mac and Windows do not differentiate file or folder names by case. If Access Anywhere |
| ##Temporary Files | ##Temporary Files | ||
| Line 45: | Line 59: | ||
| * Name begins with a tilde and ends in .tmp, such as ~filename.tmp | * Name begins with a tilde and ends in .tmp, such as ~filename.tmp | ||
| - | * The File Fabric | + | * The Access Anywhere |