compilation fix after operator==() removal

[wxWidgets.git] / docs / latex / wx / richtextoverview.tex

diff --git a/docs/latex/wx/richtextoverview.tex b/docs/latex/wx/richtextoverview.tex
index 49f9b667cb2beb715ffaf465dd65ce509782554a..a7d7dfc766f5dd12d06658c478b1c1ab87612fec 100644 (file)
--- a/docs/latex/wx/richtextoverview.tex
+++ b/docs/latex/wx/richtextoverview.tex
@@ -12,6 +12,9 @@ Classes: \helpref{wxRichTextCtrl}{wxrichtextctrl}, \helpref{wxRichTextBuffer}{wx
 \helpref{wxRichTextFileHandler}{wxrichtextfilehandler}, \helpref{wxRichTextHTMLHandler}{wxrichtexthtmlhandler}, 
 \helpref{wxRichTextXMLHandler}{wxrichtextxmlhandler}, 
 \helpref{wxRichTextFormattingDialog}{wxrichtextformattingdialog}, 
 \helpref{wxRichTextFileHandler}{wxrichtextfilehandler}, \helpref{wxRichTextHTMLHandler}{wxrichtexthtmlhandler}, 
 \helpref{wxRichTextXMLHandler}{wxrichtextxmlhandler}, 
 \helpref{wxRichTextFormattingDialog}{wxrichtextformattingdialog}, 

+\helpref{wxRichTextPrinting}{wxrichtextprinting}, 
+\helpref{wxRichTextPrintout}{wxrichtextprintout}, 
+\helpref{wxRichTextHeaderFooterData}{wxrichtextheaderfooterdata}, 

 \helpref{wxSymbolPickerDialog}{wxsymbolpickerdialog}
 
 wxRichTextCtrl provides a generic implementation of a rich text editor that can handle different character
 \helpref{wxSymbolPickerDialog}{wxsymbolpickerdialog}
 
 wxRichTextCtrl provides a generic implementation of a rich text editor that can handle different character


@@ -370,11 +373,7 @@ caret.
 \item As the selection is expanded, the text jumps slightly due to kerning differences between
 drawing a single text string versus drawing several fragments separately. This could
 be improved by using wxDC::GetPartialTextExtents to calculate exactly where the separate fragments
 \item As the selection is expanded, the text jumps slightly due to kerning differences between
 drawing a single text string versus drawing several fragments separately. This could
 be improved by using wxDC::GetPartialTextExtents to calculate exactly where the separate fragments

-should be drawn.
-Alternatively, it might be possible to use the difference between the width of text from
-a to b+1, versus the width of the text from a to b added to the width of b to b+1.
-Note that this problem also applies to separation of text fragments due to difference in their attributes.
-\item Selection doesn't work properly for text that contains tabs.
+should be drawn. Note that this problem also applies to separation of text fragments due to difference in their attributes.

 \end{itemize}
 
 \wxheading{Features}
 \end{itemize}
 
 \wxheading{Features}


@@ -383,6 +382,8 @@ This is a list of some of the features that have yet to be implemented. Help wit
 
 \begin{itemize}\itemsep=0pt
 \item RTF input and output
 
 \begin{itemize}\itemsep=0pt
 \item RTF input and output

+\item Conversion from HTML
+\item Open Office input and output

 \item Floating images, with content wrapping around them
 \item A ruler control
 \item Standard editing toolbars
 \item Floating images, with content wrapping around them
 \item A ruler control
 \item Standard editing toolbars


@@ -390,6 +391,7 @@ This is a list of some of the features that have yet to be implemented. Help wit
 \item Bitmap bullets
 \item Borders
 \item Text frames
 \item Bitmap bullets
 \item Borders
 \item Text frames

+\item Justified text, in print/preview at least

 \end{itemize}
 
 There are also things that could be done to take advantage of the underlying text capabilities of the platform;
 \end{itemize}
 
 There are also things that could be done to take advantage of the underlying text capabilities of the platform;