I'm running iManage Desksuite under WINE, which is working quite well. iManage is a common document management system used in law offices (among other places). What I'd like to do is associate DOC files in iManage with my Linux version of OpenOffice. There is a 'less tightly integrated' mode for iManage whereby documents, when checked out, are saved to a temporary directory and then it calls the external program to open them. I've told iManage to open z:\usr\bin\openoffice (I never thought I'd see a z:\usr\bin!) and it does call openoffice properly. The problem is that it passes it a Windows path to open the file--i.e., c:\Windows\NRTEcho\etc.., which, of course, openoffice doesn't understand at all. Is there an easy way to have *linux* programs that are executed from a Windows program running under WINE get the proper path to the real file in the linux filesystem? I suppose I could have a wrapper for every linux app I want to call from a windows app in WINE that translates the path, but I'm wondering if there is a more sensible way to do this. -- Adam Kessel http://adam.rosi-kessel.org
Hello Adam, Friday, April 23, 2004, 9:48:52 PM, you wrote: AK> I'm running iManage Desksuite under WINE, which is working quite well. AK> iManage is a common document management system used in law offices (among AK> other places). AK> What I'd like to do is associate DOC files in iManage with my Linux AK> version of OpenOffice. There is a 'less tightly integrated' mode for AK> iManage whereby documents, when checked out, are saved to a temporary AK> directory and then it calls the external program to open them. AK> I've told iManage to open z:\usr\bin\openoffice (I never thought I'd see AK> a z:\usr\bin!) and it does call openoffice properly. The problem is that AK> it passes it a Windows path to open the file--i.e., AK> c:\Windows\NRTEcho\etc.., which, of course, openoffice doesn't understand AK> at all. AK> Is there an easy way to have *linux* programs that are executed from a AK> Windows program running under WINE get the proper path to the real file AK> in the linux filesystem? I suppose I could have a wrapper for every AK> linux app I want to call from a windows app in WINE that translates the AK> path, but I'm wondering if there is a more sensible way to do this. Hmm you could write a simple script as "translator" IManage should open this, and the program opens openoffice with the right params. Shouldn't be that prob at all (if you know how to prog scripts) -- Best regards, Robert mailto:syvox@chello.at
On Fri, 23 Apr 2004 15:48:52 -0400, you wrote:> I'm running iManage Desksuite under WINE, which is working quite well. > iManage is a common document management system used in law offices (among > other places). > > What I'd like to do is associate DOC files in iManage with my Linux > version of OpenOffice. There is a 'less tightly integrated' mode for > iManage whereby documents, when checked out, are saved to a temporary > directory and then it calls the external program to open them. > > I've told iManage to open z:\usr\bin\openoffice (I never thought I'd see > a z:\usr\bin!) and it does call openoffice properly. The problem is that > it passes it a Windows path to open the file--i.e., > c:\Windows\NRTEcho\etc.., which, of course, openoffice doesn't understand > at all. > > Is there an easy way to have *linux* programs that are executed from a > Windows program running under WINE get the proper path to the real file > in the linux filesystem? I suppose I could have a wrapper for every > linux app I want to call from a windows app in WINE that translates the > path, but I'm wondering if there is a more sensible way to do this.Included with wine is the tool 'winepath' which converts DOS to and from unix paths. You could create a script: #!/bin/sh openoffice $( /usr/winepath "$@" ) Name it perhaps openoffice-from-wine, and call the script from your wine application, with the DOS path as an argument. Rein. -- Rein Klazes rklazes@xs4all.nl