Do you have control over the Dictionary in HTML Editor?

I would like to enter revision dates in the format of mm.dd.yyyy or yyyy.mm.dd, and every time I do, I get the choice of Add to dictionary. (yyyy even prompted that question here!)

Is that kind of modification possible?

Thanks!

I would like to see a pop up window with a notepad type app that lets you enter your text and check for both Spelling (better spell checker) and Grammar that you can copy into the HTML - so we don't have to always have MS Word open...I'm so bad at spelling that i don't even make a small Photo Caption without checking my spelling....

Also a button for "&" ("&) - i use this a lot ( verses "and") so i end up doing a seach/replace which end up going to a whole lot of script/ifame to weed out the "&" in my actual text

In fact it would be great if we could make some of our own custom buttons for things specific to a project (like keywords - an absolute Dir - Geo location) stuff you end up typing a lot ... same as we have with snippets.

This is an easy one ... have a short code put into 'FORMAT" section that would allow us to 'indent' the beginning of a paragraph; similar to the old <dd></dd> html codes.

The tool bar inserts <br> while the code menu inserts <br />. <br> will not validate in xhtml

One reason why I don't use many break tags. LOL. Also, Shift + Enter puts in a new line before writing <br> so you get two line breaks. Too bad the code can't be entered as determined by the document type being used. I think this could be done, but would take some recoding of the editor.

Look for the file that has your username and extension .adu. Click the Spell Check Icon at top of editor. Select "Spell Check Options". More info there. If you have dictionaries on your computer, under "Dictionaries:" scroll down to "Locate Dictionaries" to find them on your hard drive.

Haven't tried to edit file directly, but usually you can add new word when a word may be flagged as mis-spelled.

I agree. F11 should have the same toggle action as F12 which does show/hide the window.

Non-English characters, special characters, &#dddd; and &#xhhhh;

Besides open/edit/save in proper utf-8 or other Unicode charset encoding, the editor really needs to be able to change chars in a selection or a whole file back and forth from the actual char to the &#xhhhh; entity or the named entity, such as &thorn; or &eacute; or &rsquo; .

Why? Because whether you use only English, with proper typography, or you need one or more additional languages, you will always want to enter and view the text easily in native characters, or transform it into them if the file does not have them. If a program (erroneously) alters special characters into a ? or other char, it is very hard or unusable. (I have seen other programs make that mistake.)

Suppose you need to have English, plus a Latin alphabet with many accent marks (almost any European language), or Greek, or Russian (Cyrillic alphabet)... Or even more exotic, like any Asian or Indian or Middle Eastern script. Or suppose you need some really exotic thing from some obscure language or historical source available in Unicode.

Chances are, you require that in the native text characters. Chances are pretty good you also have to put that into &#xhhhh; or &named; entities at some point for display and compatibility. That assumes, of course, a &named; entity even exists. (There is none for schwa e lowercase or uppercase, or macron or breve vowel accents, for example.) And no one sane would suggest attempting to wade through a bunch of ampersand-pound-numerical-string-semicolon runs for, say, Japanese, or a paper on early writing systems.

That's why people are asking about foreign language characters. They need to see them natively *and* they need to transform on demand into the &-sign entities. Seeing a bunch of question marks instead of readable native language text, either in code view or browser preview is not helpful. Not if you are a native speaker who expects to see his/her own language, and not if you are a translator/linguist who expects the same, and not if you are someone trying to communicate and function with people, even if they don't happen to speak (American) English only. Go to any grocery store or mall in a major US city, and you will find US citizens, immigrants, and guest visitors or workers who speak, write, and think in another language (or many) besides English. Or, for that matter, Native American Indian folks use a few things other than English (Cherokee, for one). These are not just people in some foreign country. They are right here, and our friends, relatives, and trading partners.

The ability to transform a text selection or a whole file, back and forth, is really needed. How many registered users, and their contacts, use languages besides English? Nearly all of them, once you get to friend or friend of a friend especially.

It could come in handy for the next scholarly paper or the next historical or science fiction novel or video.

I still would love an easy menu command to get a New (Plain Old) Text file, .txt .

I still need a Code Cleaner that can properly change text case, indent reasonably, and do things like HTML4 / XHTML 1.1 / HTML5 conversion, and even Word HTML cleanup. Heck, maybe even EPUB3.

I want and sometimes need to be able to open an SVG drawing in the editor. Instead, I have to specifically File -> Open -> File Type ALL, then select the file. It would be great if the editor knew how to work with SVG as with any other image, but with the added bonus that it's another web text file at heart.

The EPUB 2 and 3 formats are web text files too. Hint, hint. Very big thing. Going to be crucial for web developers.

Wow, Word HTML cleanup, I have had to pull in tables done in word that I needed to post. The amount of duplicate html that word produces is staggering, you would almost need a separate tool to control the cleanup process. I have found it easier to use the "replace" to remove all of the duplicate code and then use CSS at the table level to replace all of the code that was duplicated at the Cell level. Not a bad idea, but, considering how often it might get used, maybe a separate tool might make more sense..