Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

Viewing and linking to Office Documents from HTML

0 views

Skip to first unread message

Stuart Macandrew

unread,

Oct 21, 1996, 3:00:00 AM10/21/96

I am on a corporate intranet, where we wish to make Microsoft Office
documents available (as well as HTML) without converting the Office
documents to HTML format.

Web server is IIS, browsers are IE 3.0. We are using FrontPage as the HTML
editor.

By default a link to an Office document will spawn the associated tool (eg
doc will start Word). What other options are there?
eg.
- read-only - can I ensure that only a viewer is spawned? Is this a browser
option or an option in the HTML?

- how do I get the Word document to open inside the browser frame - is this
a browser or HTML option?

- for the "file" protocol in a link eg. "file://c:\docs\test.doc", it does
not accept embedded spaces - what if I have long folder names eg.
"file://C:\My Documents\test.doc"? Or UNC names (eg.
"\\server\share\test.doc")?

tyia
Stuart Macandrew
maca...@wcc.govt.nz

Harald Joerg

unread,

Oct 21, 1996, 3:00:00 AM10/21/96

to Stuart Macandrew

Stuart Macandrew wrote:
> [...]

> By default a link to an Office document will spawn the associated tool (eg
> doc will start Word). What other options are there?
> eg.
> - read-only - can I ensure that only a viewer is spawned?

As a Web author: No.
As a Web reader: yes. Configure your browser to spawn
e.g. the word viever instead of Word.

> Is this a browser option or an option in the HTML?

It is a co-operation between your browser and your server:
- the server sends documents together with MIME type and subtype
(that's HTTP - HyperText Transfer Protocol, but not HTML)
For local files, browsers usually guess the file type from
its extension.
- the browser allows how to handle each type.

> - how do I get the Word document to open inside the browser frame - is this
> a browser or HTML option?

I'd say it's a Microsoft option: Neither (other) browsers nor HTML
know what a Word document is.

> - for the "file" protocol in a link eg. "file://c:\docs\test.doc", it does
> not accept embedded spaces - what if I have long folder names eg.
> "file://C:\My Documents\test.doc"? Or UNC names (eg.
> "\\server\share\test.doc")?

RFC1738 says that spaces have to be encoded as "%20".
In addition, RFC1738 says that the backslash is "unsafe"
and that the colon is "reserved" (e.g. to separate
the "host" and "port" parts). Maybe you have to do a little
more encoding to get things working.

--haj-- (http://www.sni.de)

0 new messages