.snd's
Ken Case
kc
Sun Jan 19 11:48:55 PST 1997
> I think the problem is that OW does not recognize .snd files, and
> so takes a stab at Opener knowing what to do with it. So its OW
> that needs to be told what to do w/ .snd's... but how?
OmniWeb never messages a specific app to open a file, it just hands files off
to the Workspace and tells it to open the files. Thus, OmniWeb doesn't have
any configuration on how to open different file types: instead, one configures
Workspace to open them appropriately.
What's probably happening in this case is that the file is being sent as
audio/basic (remember, the web uses MIME content types: file extensions are
irrelevant, since the file could be coming from an operating system--MacOS,
say--where that extension has a completely different interpretation). OmniWeb
saves audio/basic files as .au (since the audio/basic content type can have
sampling rates which aren't allowed in NeXT .snd files). Presumably, you have
.au files set to open in Opener.app.
The most robust solution is to configure .au files to open in an application
(such as Resound, GISO, or Soundworks) which knows how to resample audio files
so that they can be played correctly under NEXTSTEP.
However, if you just want OmniWeb to assume that all audio/basic files are
sampled with rates valid for NeXT .snd files, you can edit
OmniWeb.app/Omni.dictionary and change the line
"audio/basic" = ("au", "snd");
to
"audio/basic" = ("snd", "au");
Hope this helps!
Ken
More information about the OmniWeb-l
mailing list