Re: Editing XML

Maarten Wiltink wrote:

You can download Saxon. Or Xalan. Or the MS XML SDK, which appears to
include the MSXSL utility.

Wikipedia says that Windows XP comes with the MSXML3 library, and the IE
also has something built in.

Put <?xml-style*** type="text/xsl" href="whatever.xslt" ?> near the top
of your XML documents. That should make the client run the transformation
'whatever.xslt' on the document.

Just to clarify my intention:

I want to implement a replacement for dexplore.exe, for use in BDS, for
all BDS users. The documents come from the shipped HxS help files,
either extracted on the fly, or extracted once using e.g. 7zip. The
documents are shown in a TWebBrowser component, i.e. most probably by
the installed IE.

The documents should not be modified permanently, instead all changes should be kept separate, for dynamic application to the current version of the online help. Then users can share their updates with other users, and with CodeGear, of course. Annotations, updates etc. can reside in an according directory, with the same file names as their related document. Perhaps permanently modified documents could reside in such an additional directory, which is searched before the actual help files.

If possible, changes to the documents should be kept in e.g. XSLT files,
so that they can be applied to the actual help documents, prior to
showing the resulting document in the browser. This would allow to e.g. add a reference list to (every) document, containing links to annotations, examples, and whatever a user feels missing in the shipped Delphi or third party component help.

Since a web browser component seems not to handle properly the MSHelp links, at least if the updated documents shall be used instead of the orignal ones, these elements must be replaced by links to either the new document, or by a reference to a list of related documents, which also will be created on the fly. These modifications are what I'm actually struggling with...


Since I'm not yet familiar with XML documents, all suggestions for the implementation of the above procedures are welcome.


Meaning lots of things can still go
wrong.

You are very encouraging me ;-)

DoDi
.