Missed labels to replace number of 'topicNNN' in anchors.

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

diff --git a/docs/latex/wx/tunicode.tex b/docs/latex/wx/tunicode.tex
index 5c6b2378a61196c80843a2b9580976c4dc9df8d3..0a4d94291fdd42a3c5ac4683f54fd4b5538f0304 100644 (file)
--- a/docs/latex/wx/tunicode.tex
+++ b/docs/latex/wx/tunicode.tex
@@ -15,7 +15,7 @@ This section briefly describes the state of the Unicode support in wxWidgets.
 Read it if you want to know more about how to write programs able to work with
 characters from languages other than English.
 
 Read it if you want to know more about how to write programs able to work with
 characters from languages other than English.
 

-\subsection{What is Unicode?}
+\subsection{What is Unicode?}\label{whatisunicode}

 
 Starting with release 2.1 wxWidgets has support for compiling in Unicode mode
 on the platforms which support it. Unicode is a standard for character
 
 Starting with release 2.1 wxWidgets has support for compiling in Unicode mode
 on the platforms which support it. Unicode is a standard for character


@@ -40,7 +40,7 @@ from using Unicode because they will work more efficiently - there will be no
 need for the system to convert all strings the program uses to/from Unicode
 each time a system call is made.
 
 need for the system to convert all strings the program uses to/from Unicode
 each time a system call is made.
 

-\subsection{Unicode and ANSI modes}
+\subsection{Unicode and ANSI modes}\label{unicodeandansi}

 
 As not all platforms supported by wxWidgets support Unicode (fully) yet, in
 many cases it is unwise to write a program which can only work in Unicode
 
 As not all platforms supported by wxWidgets support Unicode (fully) yet, in
 many cases it is unwise to write a program which can only work in Unicode


@@ -109,7 +109,7 @@ be done this way (try to imagine the number of {\tt \#ifdef UNICODE} an average
 program would have had!). Luckily, there is another way - see the next
 section.
 
 program would have had!). Luckily, there is another way - see the next
 section.
 

-\subsection{Unicode support in wxWidgets}
+\subsection{Unicode support in wxWidgets}\label{unicodeinsidewxw}

 
 In wxWidgets, the code fragment from above should be written instead:
 
 
 In wxWidgets, the code fragment from above should be written instead:
 


@@ -152,7 +152,7 @@ to an external function which doesn't accept wide-character strings.
 \item Use {\tt wxString} instead of C style strings.
 \end{itemize}
 
 \item Use {\tt wxString} instead of C style strings.
 \end{itemize}
 

-\subsection{Unicode and the outside world}
+\subsection{Unicode and the outside world}\label{unicodeoutsidewxw}

 
 We have seen that it was easy to write Unicode programs using wxWidgets types
 and macros, but it has been also mentioned that it isn't quite enough.
 
 We have seen that it was easy to write Unicode programs using wxWidgets types
 and macros, but it has been also mentioned that it isn't quite enough.


@@ -172,7 +172,7 @@ the Unicode string.
 
 % TODO describe fn_str(), wx_str(), wxCharBuf classes, ...
 
 
 % TODO describe fn_str(), wx_str(), wxCharBuf classes, ...
 

-\subsection{Unicode-related compilation settings}
+\subsection{Unicode-related compilation settings}\label{unicodesettings}

 
 You should define {\tt wxUSE\_UNICODE} to $1$ to compile your program in
 Unicode mode. Note that it currently only works in Win32 and GTK 2.0 and
 
 You should define {\tt wxUSE\_UNICODE} to $1$ to compile your program in
 Unicode mode. Note that it currently only works in Win32 and GTK 2.0 and