There is absolutely no need to copy/create template files manually and edit them in UltraEdit although that is possible because template files are XML files.

1. Click with secondary (right) mouse button into the Template List view in free area to open its context menu containing the menu item Modify Templates. This opens the Modify Templates dialog window.
2. Select at top right corner of the Modify Templates dialog window the syntax highlighting language respectively language template to create or modify.
3. Press on + below the Templates list, enter name for the template, and enter next template content and perhaps also a description, and perhaps check one or both options for this template.
4. Redo the third step as often as needed to define all templates.

The button Help at bottom right corner of Modify Templates dialog window opens the appropriate help page for this dialog explaining the format and options for tag contents.

The dialog is a modeless dialog which means it is possible to access also for example the document window below to select there text to copy and paste into tag Content field.

If configuration setting Disable drag & drop is not checked at Advanced - Settings or Configuration - Editor - Miscellaneous it is even possible to select a text snippet in current file and drag & drop the selected text into the template view to create a new template with a name to enter next with the selected text as template content. It depends on where the selected text is dropped in the template view if a global, a layout or a language template is created.

Please note that the context menu of template view depends on where exactly the secondary mouse button click is executed: on free area, on a template group name, or on a specific template.

See forum topic Smart templates management for detailed information about template files management.

The wordfiles on wordfiles download page which can be also downloaded and uploaded via GitHub and installed since UltraEdit v24.00 directly from within UltraEdit are user-submitted without any verification by IDM. Unfortunately this means many of the wordfiles contains lots of mistakes in language definition and some are so badly written that they can't be used for creation of smart language templates.

I quickly looked on all user-submitted ColdFusion wordfiles and they are all full of mistakes. Please compress your wordfile into a ZIP or RAR archive file and upload the archive file as attachment to your next post. I will look into it and fix all errors in the wordfile. Then it should be no problem to create the smart language templates file. On weekend I will look also on all other user-submitted ColdFusion wordfiles and fix all the errors to avoid that in future other users of UE/UES using them have the same problems as you.

It could be that I need your ColdFusion language knowledge for fixing all errors in the ColdFusion wordfiles because I know nothing about ColdFusion. I hope you help me when I stuck on a problem which I can't solve without knowledge of ColdFusion language.

---

Update on 2017-07-23:

I have attached the revised user-submitted ColdFusion wordfiles.

The most interesting one for me was the most likely oldest one coldfusion431.uew which contained the keyword Nocase twice and having no language name (very bad for many reasons nowadays).

I updated my macro SortLanguage to automatically remove Nocase duplicates from first line of a language file and handle languages without name by adding "Language Number" whereby the number is taken from the beginning of the language definition line. The later modification of my macro was really important as the language without name resulted on this wordfile with last color group also modified in an endless running loop near end of macro execution which needed to be broken by me with hitting key ESC. The updated macro SortLanguage is not yet published.

Most of the changes made on the files where done by my syntax tools macros.

I'm not sure if the changes made by me on function strings in coldfusion_sql.uew result in a better function list. I hope so, but I really don't know which strings should be matched and which ones ignored by the original UltraEdit regular expressions and which part of each matched string should be displayed in function list. Jamo, please let me know anything you can tell me about the function strings and what they should find and display in function list.

Later when having them perhaps further improved with your help I will send them IDM for upload on their server replacing the existing ones.

It is hard coded in source code of UltraEdit/UEStudio which tags in a section syntax highlighted with a language having language marker keyword HTML_LANG have no end tag according to HTML standards. So automatic closing of tags is not customizable. And a tag of an empty element which ends with /> is of course also not automatically closed.

It is only customizable which tags are displayed: opening tags without tags like <p>, opening tags without or with attributes like <p style="color:red">, opening tags which require at least one attribute like <a (<a> is missing in wordfile) and end tags like </p> if the element has one (otherwise missing in wordfile).