H
Hans-Peter Diettrich
I wonder what this header does mean:
<?xml version="1.0" encoding="utf-8"?>
<HTML xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
<HEAD>
....
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=utf-8"/>
....
When such a file is saved as *.htm, it's displayed in an browser as
HTML. When saved as *.xml, it's displayed as XML. When streamed directly
into an browser, nothing is displayed at all. In the latter case, what's
missing so that the browser cannot determine how to handle the document?
(Maybe my streaming code doesn't work properly?)
The most puzzling element in such HTML Help documents is:
<MSHelp:link namespace= ...>Text</MSHelp:link>
"Text" is displayed, but what is the intended interpretation of the
surrounding decoration? It seems to be some XML element, that is ignored
by an ordinary browser.
What can or has to be done, in order to make such a construct have any
effect? Actually I edit the files, converting the "link" into "A" tags,
so that they work as HTML links. But that's a poor solution, couldn't
this be done in another (the intended) way?
DoDi
<?xml version="1.0" encoding="utf-8"?>
<HTML xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
<HEAD>
....
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=utf-8"/>
....
When such a file is saved as *.htm, it's displayed in an browser as
HTML. When saved as *.xml, it's displayed as XML. When streamed directly
into an browser, nothing is displayed at all. In the latter case, what's
missing so that the browser cannot determine how to handle the document?
(Maybe my streaming code doesn't work properly?)
The most puzzling element in such HTML Help documents is:
<MSHelp:link namespace= ...>Text</MSHelp:link>
"Text" is displayed, but what is the intended interpretation of the
surrounding decoration? It seems to be some XML element, that is ignored
by an ordinary browser.
What can or has to be done, in order to make such a construct have any
effect? Actually I edit the files, converting the "link" into "A" tags,
so that they work as HTML links. But that's a poor solution, couldn't
this be done in another (the intended) way?
DoDi