Microsoft Office can not save reliably without creating multiple. So - it seems that when saving to a file system that does not support those values in a extended attribute: The most recent version of Office requires an HFS type code and HFS creator code when a format such as Microsoft Word (. Hint: where Microsoft Office fails with webdav to save to Microsoft SharePoint (see below), NeoOffice succeeds. the save by NeoOffice to the webdav file system did not involve an extended attribute. gjp22% xattr -l /Volumes/dav/product\ of\ NeoOffice\ 3.2.1\ Patch\ 5.docx on /Volumes/dav (webdav, nodev, noexec, nosuid, mounted by gjp22) 
NeoOffice 3.2.1 Patch 5 save to a volume mounted by OS X with file system type webdav, not SharePoint, cleaning by BlueHarvest: gjp22% mount | grep dav _product of NeoOffice 3.2.1 Patch 5.docx in /Volumes/FAT32/example. NeoOffice 3.2.1 Patch 5 save to a USB flash drive with MS-DOS FAT32, cleaning by BlueHarvest: 06:42:08.349 BlueHarvest: Deleted.
used considerately, only where appropriate. HFS type code NO%F without a creator code is: See my answer to a question on Stack Overflow. In addition to the purposes outlined in geekosaur's accepted answer, here are a few examples of how Apple and third party apps either use or require. not acceptable to have things "vanish into the ether". _ counterparts are prevented or lost, I agree that it's: 
Since I have seen loss of user data (document content) where. For an annotated view of where Matt Deatherage ( a former engineer at Apple) offers explanations.
0 kommentar(er)
