@BonRougeNov 27.2004 — #What is the question exactly?
You're right - you don't see it on the page you receive. The point of it is that the server replaces it with the text that you asked it to put in before it reaches the browser.
@toicontienNov 27.2004 — #The <!-- #include --> statement is for Server Side Includes. You'll need Server Side Includes, or SSI, enabled on your Web server, then you'll also need HTML files named with the .shtml or .shtm file extensions for SSI to work.
In other words, the HTML file you want to use to include other files should be named something.shtm or something.shtml. Then in that file, you'll have <!-- #include file="path/to/file.txt" -->.
You can pass variable-value pairs in a URL to a server side script using <!-- #include virtual="path/to/script.php?variable=value" -->
@toicontienNov 29.2004 — #The backslash probably won't work. Since early Web servers were all Unix-based, the forward-slash was used for file paths in URLs. Windows servers inherited that functionality, so the forward slash is still the correct character to use to separate folder names. First do the things I mentioned in my first post. Then write back if that doesn't work.
@Hammer65Nov 29.2004 — #If you must do this client side reformat to make your text a .js file with the text assigned to a variable that you can then use with document.write() to write into the page while it's loading. HTML doesn't really have any other way to include files besides js and css documents.
@toicontienNov 29.2004 — #Use the JavaScript method as a last resort. Between 5 and 10 percent of Web surfers have JS disabled (depending on who you ask). Also, search engines won't read your JavaScript. If the content that gets written with JavaScript is part of your main content, definitely go the Server Side Includes route because the browser (and search engine) gets a complete HTML document, no matter how many files were included using SSI.