From 0e518f7f49011ab5a3aad9ed9ccd271961ecc566 Mon Sep 17 00:00:00 2001
From: engelsman <engelsman>
Date: Sat, 11 Oct 2008 08:14:59 +0000
Subject: more html to doxygen conversion for {fluid,advanced,unicode}.dox

git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@6407 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
---
 documentation/unicode.dox | 101 +++++++++++++++++++++-------------------------
 1 file changed, 46 insertions(+), 55 deletions(-)

(limited to 'documentation/unicode.dox')

diff --git a/documentation/unicode.dox b/documentation/unicode.dox
index 381dfdae2..03937464c 100644
--- a/documentation/unicode.dox
+++ b/documentation/unicode.dox
@@ -2,14 +2,14 @@
 
  \page unicode 11 - Unicode and utf-8 Support
 
-<P>This chapter explains how FLTK handles international 
-text via Unicode and utf-8.</P>
+This chapter explains how FLTK handles international 
+text via Unicode and utf-8.
 
-<P>Unicode support was only recently added to FLTK and is
+Unicode support was only recently added to FLTK and is
 still incomplete. This chapter is Work in Progress, reflecting
-the current state of Unicode support.</P>
+the current state of Unicode support.
 
-<H2>About Unicode and utf-8</H2>
+\section unicode_about About Unicode and utf-8
 
 The Unicode Standard is a worldwide accepted charatcer encoding 
 standard. Unicode provides access to over 100,000 characters 
@@ -26,62 +26,53 @@ over the world. By choosing utf-8 encoding, FLTK remains
 largely source-code compatible to previous iteration of the 
 library.
 
-<H2>Unicode in FLTK</H2>
+\section unicode_in_fltk Unicode in FLTK
 
 FLTK will be entirely converted to Unicode in utf-8 encoding.
 If a different encoding is required by the underlying operatings
 system, FLTK will convert string as needed.
 
-TODO:
-
-<UL>
-<LI> more doc on unicode, add links
-<LI> write something about filename encoding on OS X...
-<LI> explain the fl_utf8_... commands
-<LI> explain issues with Fl_Preferences
-<LI> why FLTK has no Fl_String class
-</UL>
-
-DONE:
-
-<UL>
-<LI> initial transfer of the Ian/O'ksi'D patch
-<LI> adapted Makefiles and IDEs for available platforms
-<LI> hacked some Unicode keybard entry for OS X
-</UL>
-
-ISSUES:
-
-<UL>
-<LI> IDEs:
-  <UL>
-  <LI> Makefile support: tested on Fedora Core 5 and OS X, but heaven knows  
-     on which platforms this may fail
-  <LI> Xcode: tested, seems to be working (but see comments below on OS X)
-  <LI> VisualC (VC6): tested, test/utf8 works, but may have had some issues  
-     during merge. Some additional work needed (imm32.lib)
-  <LI> VisualStudio2005: tested, test/utf8 works, some addtl. work needed  
+\par TODO:
+
+\li more doc on unicode, add links
+\li write something about filename encoding on OS X...
+\li explain the fl_utf8_... commands
+\li explain issues with Fl_Preferences
+\li why FLTK has no Fl_String class
+
+\par DONE:
+
+\li initial transfer of the Ian/O'ksi'D patch
+\li adapted Makefiles and IDEs for available platforms
+\li hacked some Unicode keybard entry for OS X
+
+\par ISSUES:
+
+\li  IDEs:
+    - Makefile support: tested on Fedora Core 5 and OS X, but heaven knows  
+      on which platforms this may fail
+    - Xcode: tested, seems to be working (but see comments below on OS X)
+    - VisualC (VC6): tested, test/utf8 works, but may have had some issues  
+      during merge. Some additional work needed (imm32.lib)
+    - VisualStudio2005: tested, test/utf8 works, some addtl. work needed  
      (imm32.lib)
-  <LI> VisualCNet: sorry, I have no longer access to that IDE
-  <LI> Borland and other compiler: sorry, I can't update those
-  </UL>
-<LI> Platforms:
-  <UL>
-  <LI> you will encounter problems on all platforms!
-  <LI> X11: many characters are missing, but that may be related to bad  
-     fonts on my machine. I also could not do any keyboard tests yet.  
-     Rendering seems to generally work ok.
-  <LI> Win32: US and German keyboard worked ok, but no compositing was  
-     tested. Rendering looks pretty good.
-  <LI> OS X: redering looks good. Keyboard is completely messed up, even in  
-     US setting (with Alt key)
-  <LI> all: while merging I have seen plenty of places that are not  
-     entirley utf8-safe, particularly Fl_Input, Fl_Text_Editor, and  
-     Fl_Help_View. Keycodes from the keyboard conflict with Unicode  
-     characters. Right-to-left rendered text can not be marked or edited,  
-     and probably much more.
-  </UL>
-</UL>
+    - VisualCNet: sorry, I have no longer access to that IDE
+    - Borland and other compiler: sorry, I can't update those
+
+\li  Platforms:
+    - you will encounter problems on all platforms!
+    - X11: many characters are missing, but that may be related to bad  
+      fonts on my machine. I also could not do any keyboard tests yet.  
+      Rendering seems to generally work ok.
+    - Win32: US and German keyboard worked ok, but no compositing was  
+      tested. Rendering looks pretty good.
+    - OS X: redering looks good. Keyboard is completely messed up, even in  
+      US setting (with Alt key)
+    - all: while merging I have seen plenty of places that are not  
+      entirley utf8-safe, particularly Fl_Input, Fl_Text_Editor, and  
+      Fl_Help_View. Keycodes from the keyboard conflict with Unicode  
+      characters. Right-to-left rendered text can not be marked or edited,  
+      and probably much more.
 
 <hr>
 <a class="el" href="index.html">[Index]</a> &nbsp;&nbsp;
-- 
cgit v1.2.3