[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
Subject: Re: WebDAV & FrameMaker Question
From: "Russ Wyllie" <russ_wyllie@xxxxxxxxxxxxx>
Date: Mon, 19 Aug 2002 13:07:27 -0700
In-Reply-To: <68282EFC-B13B-11D6-AE9E-000393971036@filemaker.com>
Sender: owner-framers@xxxxxxxxx
Jason Aiken replied directly to me with a suggestion: the "resource fork" files usually aren't too important, and it might be possible to simply delete them. I tried deleting the resource fork files, and the FrameMaker files (as well as the imported graphic files) are behaving fine without them. I can check out and check in FrameMaker files and graphic files just fine. -Russ On Friday, August 16, 2002, at 10:12 AM, Russ Wyllie wrote: > Our department is looking into using the new WebDAV features in > FrameMaker 7 to implement a simple checkout/checkin setup to manage > files. So far, it looks really promising, but FrameMaker exhibits one > annoying little problem. > > Our WebDAV server is hosted on Mac OS X Server, and we're using > FrameMaker 7 on Macs. For every file on the server, the Mac file > system creates a separate file that begins with a period and an > underline character, which I presume is a Mac "resource fork" file. > For example, if my WebDAV server contains a file named procedures.fm, > there is also a file named ._procedures.fm. > > The problem is that the WebDAV server contains a lot of FrameMaker > files, and all the "resource fork" files are sorted to the top of > "Open from Server" dialog box that writers use to check out files. > Writers have to scroll past all these files to get to the actual > FrameMaker files that they need to check out. > > So my question is, does anyone know how to get rid of these files? My > hunch is that this problem may be solvable in one of two ways: > > * Client side fix: Some way of setting FrameMaker to hide the resource > fork files so that they don't show up in the in the "Open from Server" > dialog box. (This is how Goliath, another WebDAV client application on > the Mac, seems to deal with this problem. It has a preference option > to not display hidden files.) > > * Server side fix: Some way setting the WebDAV server not to generate > the resource fork files in the first place. > > Any ideas how to correct this? Thanks for your help. > > -Russ Wyllie > ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **