- From: Edward Moon <em@mooned.org>
- Date: Mon, 10 Jan 2000 10:05:27 -0800 (PST)
- To: Irene.Vatton@inrialpes.fr
- cc: www-amaya@w3.org
Thanks for adding jsp to the next release. Are you going to make a config file where a user can add an extension without waiting for a new release? Or perhaps an option to force Amaya to always assume files are HTML documents? The reason why I ask is as a consultant, I end up viewing and editing JSP, ASP, PHP, CFM, and other file formats that are HTML-like at various companies. In most cases, I can't edit files directly from the server (as the JSP/ASP/PHP code gets executed during the request) so manipulating the mime type doesn't help me. On Mon, 10 Jan 2000 Irene.Vatton@inrialpes.fr wrote: > In-reply-to: Your message of Mon, 10 Jan 2000 00:46:19 -0800." > <Pine.LNX.4.10.10001100043360.24623-100000@gate.mooned.org> > > I'd like to edit some Java Server Pages using Amaya. Because the files > > have a .jsp extension instead of .htm or .html, Amaya won't recognize them > > as a HTML type document and disables the HTML features and also won't > > syntax color the files. > > > > Is there a config fire I can edit to change Amaya's behavior? I've looked > > around and haven't found anything I can edit to do this. > > > > Thanks, > > > > > > The document type is fixed either by the mime-type given by the server or > the suffix. The suffix list is hard-coded. I added jsp in the list for the > next release. > Meanwhile if you have a server, you can solve your problem by loading these > files through the server with the mime-type. > Irene. > > >
Received on Monday, 10 January 2000 13:06:45 UTC