[CM] problems connecting to documentation via Grace.

[Juan Reyes]

Sure Rick, on Linux and OSX we can use pathname variables, or may be
include them in the init file. 

Thank god, I am not windoze user, and I don't have to use it most of the
time (knock on wood).

Sometimes this internationalization issue is very painful. On the QWERTY
keyboard mappings are also very different. For example Emacs keybindings
not often coincide, and you have to customize. But if I recall, with a
single windOS update you can screw up and wipe out any customization you
make. I can't even deal with back slashes because I use them as TeX
commands.

I didn't know Juce was so up-to-date with globalization. As far as for
what you are telling us, Juce will look for standard program
installation directories, perhaps:

C:\Program Files\Mozilla Firefox\firefox.exe
C:\Program Files\Internet Explorer\iexplore.exe

or its translation in Spanish (which I don't recall at the moment).

  --* Juan  

On Mon, 2010-11-08 at 16:01 -0600, Heinrich Taube wrote:
> hi juan -- no it should work, i just gave the example on my machine.   
> Grace uses a juce call to return the directory in which it will unpack  
> its documentation in so it does not depend on english pathnames.
> 
> however the browser location is a problem -- on windows there is no  
> way that i can find to launch a browser with a local url (eg  
> 'file:///....")
> so i had to use a stupid test to get anything to work.
> (on osx i just use 'open ...'). on linux i cant remember , maybe i  
> just look in /usr/local/bin and /usr/bin for firefox.
>