Removed FLTK own character composition rules --> left to OSs. Closes STR #2421.

git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@7901 ea41ed52-d2ee-0310-a9c1-e6b18d33e121

documentation/src/events.dox

@@ -164,6 +164,7 @@ should return 1. If you
 return zero then FLTK assumes you ignored the key and will
 then attempt to send it to a parent widget. If none of them want
 it, it will change the event into a \p FL_SHORTCUT event.
+FL_KEYBOARD events are also generated by the character palette/map.
 
 To receive \p FL_KEYBOARD events you must also
 respond to the \p FL_FOCUS and \p FL_UNFOCUS
@@ -171,7 +172,7 @@ events.
 
 If you are writing a text-editing widget you may also want to call the
 Fl::compose()
-function to translate individual keystrokes into foreign characters.
+function to translate individual keystrokes into characters.
 
 \p FL_KEYUP events are sent to the widget that 
 currently has focus. This is not necessarily the same widget
@@ -411,21 +412,15 @@ window modal.
 
 \section events_compose_characters FLTK Compose-Character Sequences
 
-\todo Does Fltk Compose Character Sequences text need updating
-      after the addition of UTF-8 handling to FLTK-1.3.x ?
-
-The foreign-letter compose processing done by the Fl_Input widget's
-\ref Fl_Input_Compose_Character "compose"
-key handler is provided in a function that you can call if you are
+The character composition done by Fl_Input widget
+requires that you call the Fl::compose() function if you are
 writing your own text editor widget.
 
-FLTK uses its own compose processing to allow "preview" of
-the partially composed sequence, which is impossible with the
-usual "dead key" processing.
-
-Although currently only characters in the ISO-8859-1
-character set are handled, you should call this in case any
-enhancements to the processing are done in the future. The
+Currently, all characters made by single key strokes
+with or without modifier keys, or by system-defined character 
+compose sequences (that can involve dead keys or a compose key) can be input.
+You should call Fl::compose() in case any
+enhancements to this processing are done in the future. The
 interface has been designed to handle arbitrary UTF-8 encoded
 text.
 
@@ -434,6 +429,7 @@ The following methods are provided for character composition:
 \li Fl::compose()
 \li Fl::compose_reset()
 
+Under Mac OS X, FLTK "previews" partially composed sequences.
 
 \htmlonly
 <hr>