On 23 October 2010 03:56, Nick Treleaven nick.treleaven@btinternet.com wrote:
On Fri, 22 Oct 2010 23:46:08 +1100 Ross McKay rosko@zeta.org.au wrote:
The following can be tacked onto the end of the html keywords line in filetypes.xml for the HTML5 new elements to be recognised:
article aside audio canvas command details datalist figure figcaption footer header hgroup keygen mark meter nav output progress section time video wbr
Done, thanks.
What would be quite nice is to be able to have different modes for HTML/XHTML to allow for the defined keywords of each doctype to be recognised as appropriate, e.g. HTML <=4 and XHTML won't know what a canvas is so it should appear as an error in those doctypes, and HTML5 won't know what center is (which is just as well because it's misspelled in all but Wronglish :)
Not sure about HTML5, but it might be nice to have a separate XHTML filetype. I don't know if making a custom filetype would work but it might be worth investigating if you like:
http://www.geany.org/manual/dev/index.html#custom-filetypes
Nick
Hi Ross, Nick,
The problem I see is identifying the filetype, lots of (most?) xhtml tools generate files with the .html extension so you would have to read the file contents to identify it. IIUC custom filetypes only use the extension not the contents. And I expect HTML5 would have the same problem.
Making them built in filetypes would allow the filetypes_detect_from* functions to be extended to distinguish the filetype.
Cheers Lex
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany