diff --git a/documentation/development.dox b/documentation/development.dox
index 302827c87..280c87fdf 100644
--- a/documentation/development.dox
+++ b/documentation/development.dox
@@ -92,4 +92,94 @@ From Duncan: (will be removed later, just for now as a reminder)
    and do that for all of the function documentation?)
 
 
+<H3>Example comment:</H3>
+
+\code
+The following text is a comment within a doxygen comment block and
+will not appear in the generated document:
+<!-- Editor's note:
+   ** Caution: the following text contains utf-8 encoded characters.
+-->
+This will be visible again.
+\endcode
+
+The following text is a comment within a doxygen comment block and
+will not appear in the generated document:
+<!-- Editor's note:
+   ** Caution: the following text contains utf-8 encoded characters.
+-->
+This will be visible again.
+
+\code
+<H1>Headline in big text</H1>
+<H2>Headline in big text</H2>
+<H3>Headline in big text</H3>
+<H4>Headline in big text</H4>
+\endcode
+
+<H1>Headline in big text</H1>
+<H2>Headline in big text</H2>
+<H3>Headline in big text</H3>
+<H4>Headline in big text</H4>
+
+
+<P>Assuming that the following source code was written on MS Windows, 
+this example will output the correct label on OS X and X11 as well.
+Without the conversion call, the label on OS X would read 
+<tt>Fahrvergn¸gen</tt> with a deformed umlaut u ("cedille",
+html "&cedil;").
+\code
+  btn = new Fl_Button(10, 10, 300, 25);
+  btn->copy_label(fl_latin1_to_local("Fahrvergnügen"));
+\endcode
+
+\note	If your application uses characters that are not part of both
+	encodings, or it will be used in areas that commonly use different
+	code pages, you might consider upgrading to FLTK 2 which supports
+	UTF-8 encoding. 
+
+\todo	This is an example todo entry, please ignore !
+
+\code
+
+<!-- Editor's note:
+   ** Caution: the following text contains utf-8 encoded characters.
+   ** be careful when using non-utf-8-aware editors !
+-->
+
+<P>Assuming that the following source code was written on MS Windows, 
+this example will output the correct label on OS X and X11 as well.
+Without the conversion call, the label on OS X would read 
+<tt>Fahrvergn¸gen</tt> with a deformed umlaut u ("cedille",
+html "&cedil;").
+\code
+  btn = new Fl_Button(10, 10, 300, 25);
+  btn->copy_label(fl_latin1_to_local("Fahrvergnügen"));
+\endcode
+
+\note	If your application uses characters that are not part of both
+	encodings, or it will be used in areas that commonly use different
+	code pages, you might consider upgrading to FLTK 2 which supports
+	UTF-8 encoding. 
+
+\todo	This is an example todo entry, please ignore !
+
+\endcode
+
+
+<H2>Creating Links</H2>
+
+\code
+see chapter \ref unicode creates a link to the named chapter unicode
+that has been created with a \subpage statement.
+	
+see <a href="drawing.html#character_encoding">chapter 5</a> creates
+a link to a named html anchor "character_encoding" within the same file.
+\endcode
+see chapter \ref unicode creates a link to the named chapter unicode
+that has been created with a \subpage statement.
+	
+see <a href="drawing.html#character_encoding">chapter 5</a> creates
+a link to a named html anchor "character_encoding" within the same file.
+
 */
diff --git a/documentation/drawing.dox b/documentation/drawing.dox
index 794438d7f..209ebf492 100644
--- a/documentation/drawing.dox
+++ b/documentation/drawing.dox
@@ -642,19 +642,36 @@ encodings. These functions are only required if your source
 code contains "C"-strings with international characters and 
 if this source will be compiled on multiple platforms.
 
+<!-- Editor's note:
+   ** Caution: the following text contains utf-8 encoded characters.
+   ** be careful when using non-utf-8-aware editors !
+-->
+
 <P>Assuming that the following source code was written on MS Windows, 
 this example will output the correct label on OS X and X11 as well.
 Without the conversion call, the label on OS X would read 
-<tt>Fahrvergn\\&cedil;gen</tt> with a deformed umlaut u.
+<tt>Fahrvergn¸gen</tt> with a deformed umlaut u ("cedille",
+html "&cedil;").
 \code
   btn = new Fl_Button(10, 10, 300, 25);
-  btn->copy_label(fl_latin1_to_local("Fahrvergn&uuml;gen"));
+  btn->copy_label(fl_latin1_to_local("Fahrvergnügen"));
 \endcode
 
-<P>If your application uses characters that are not part of both
-encodings, or it will be used in areas that commonly use different
-code pages, yoou might consider upgrading to FLTK 2 which supports
-UTF-8 encoding. 
+\note	If your application uses characters that are not part of both
+	encodings, or it will be used in areas that commonly use different
+	code pages, you might consider upgrading to FLTK 2 which supports
+	UTF-8 encoding. 
+
+\todo	drawing.dox: I fixed the above encoding problem of these \&cedil;
+	and umlaut characters, but this text is obsoleted by FLTK 1.3
+	with utf-8 encoding, or must be rewritten accordingly:
+	How to use native (e.g. Windows "ANSI", or ISO-8859-x)
+	encoding in embedded strings for labels, error messages
+	and more. Please check this (utf-8) encoding on different
+	OS'es and with different language and font environments.
+
+For more information about character encoding, unicode and utf-8
+see chapter \ref unicode.
 
 <H3><A name="overlay">Drawing Overlays</A></H3>