ASP.NET HTML Editor - Dictionary's phonetic rules

Each line in [Phonetic] section represents one replacement (transformation) rule. Words beginning with the same letter must be grouped together; the order inside this group does not depend on alphabetical issues but it gives priorities; the higher the rule the higher the priority. That's why the first rule that matches is applied. In the following example:

GH  _
G    K

'GH  _' has higher priority than 'G  K'

'_' represents the empty string "". If 'GH  _' came after 'G  K', the second rule would never match because the algorithm would stop searching for more rules after the first match. The above rules transform any 'GH' to an empty string (delete them) and transforms any other 'G' to 'K'.

At the end of the first string of a line (the search string) there may optionally stand a number of characters in brackets. One (only one!) of these characters must fit. It's comparable with the '[ ]' brackets in regular expressions. The rule 'DG(EIY)  J' for example would match any 'DGE', 'DGI' and 'DGY' and replace them with 'J'. This way you can reduce several rules to one.

At the end of the search string, one or more dashes '-' may be placed. Those search strings will be matched totally but only the beginning of the string will be replaced. The rule 'TCH--  _' will match any word containing 'TCH' (like 'match') but will only replace the first character 'T' with an empty string. The number of dashes determines how many characters from the end will not be replaced. After the replacement, the search for transformation rules continues with the not replaced 'CH'!

If a '<' is appended to the search string, the search for replacement rules will continue with the replacement string and not with the next character of the word. The rule 'PH<  F' for example would replace 'PH' with 'F' and then again start to search for a replacement rule for 'F...'. If there would also be rules like 'FO  O' and 'F  _' then words like 'PHOXYZ' would be transformed to 'OXYZ' and any occurrences of 'PH' that are not followed by an 'O' will be deleted like 'PHIXYZ -> IXYZ'.

The control character '^' says that the search string only matches at the beginning of words so that the rule 'RH^  R' will only apply to words like 'RHESUS' but not 'PERHAPS'. You can append another '^' to the search string. In that case the algorithm treats the rest of the word totally separately from the first matched string at the beginning. This is useful for prefixes whose pronunciation does not depend on the rest of the word and vice versa like 'OVER^^' in English for example.

The same way as '^' works does '$' only apply to words that end with the search string. 'GN$  N' only matches on words like 'SIGN' but not 'SIGNUM'. If you use '^' and '$' together, both of them must fit 'ENOUGH^$  NF' will only match the word 'ENOUGH' and nothing else.

Of course you can combine all of the mentioned control characters but they must occur in this order: '< ^ $'. All characters must be written in CAPITAL letters.

If absolutely no rule can be found — might happen if you use strange characters for which you don't have any replacement rule — the next character will simply be skipped and the search for replacement rules will continue with the rest of the word. Home
HTML Editor Home
HTML Editor Home
Why the best?
Site Map
Examples - 80
Appearance - 10
Full button set
Lite button set
Custom button set
Design-mode textbox
How to fit into small space
Page maker
Default font
Initially without toolbar
Preview mode
"Read only" mode New
Content - 16
Read-only and custom tags
Shadow for Image
External image gallery
Upload images
Copy/paste formatting
Preview Document appearance
Keys used for editing
.NET validation
Documents Generator
Upload documents
Convert to PDF
Editor and database
Spell Checker - 3
Spell checking
Spell Checker dictionaries
Several dictionaries
Localization - 2
RTL support
Integration - 9
Inside Flyout
Inside Grid
Inside Window
With Color PickerNew
Google AJAX Language API New
Inside AJAX Page
Inside CallbackPanel
ASP.NET AJAX ControlToolkit - 5
Collapsible panel
Editor in each TabPanel New
Modal popup
Server-Side API - 13
Content counters
Plain text length control
Show plain text
Enable editor on focus
Set caret position on load
Add CSS files New
Hide HTML Editor until needed
CSS file for quick format
Set HTML view on load
Enable browse button for images
Enable browse button for URLs
Disable Wait message New
Server-Side Events - 5
ClickSubmit event
ClickCancel event
ContentChanged event
Client-Side API - 10
Working with selected text
Set design/HTML view on load
Show/hide HTML Editor
Get/set content
Surround HTML
Insert HTML
Style selected content
Exec command
Query command
'Not Set' in dropdowns New
Customize - 17
Custom editor toolbar in VS
Custom fonts
Custom font sizes
How to add icons
Custom Popup Windows
Custom Buttons
Custom Context Menu
Popup Properties Disabling
Default Table Properties
Custom toggle button
Custom select button
Textarea popup
Custom 'Quote' button New
Show/hide submit button
Show/hide Design/HTML view
Show/hide quick format panel
Width & Height
Knowledge Base - 1
Knowledge Base
Documentation - 23
Server side
HTML Editor properties & events
HTML Editor inner properties
Custom toolbar
Custom fonts
Custom font sizes
Custom Context Menu
Dictionaries for spell checker
Hot keys definition
Disabling Context Menu items
Additional CSS files New
Client side
Main functions and interfaces
Custom Context Menu support
Custom Popup Window support
Top toolbar buttons' methods
State functions
Suppress Context Menu
Spelling dictionary
Dictionary structure
Affix rules
Phonetic rules
Generate phonetic code
How to add new word
Supported browsers
Tutorials - 6
Using the correct path
Autosave implementation
Full custom buttons set
Editor_data for several sites
Use with database
Template XML file use New