don't call wxYield() from EnsureVisible(), this is too dangerous - and unnecessary...

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

diff --git a/docs/latex/wx/htmlhlpf.tex b/docs/latex/wx/htmlhlpf.tex
index 03c206e6e3afb1105f3e17c583d2b4ac524f7a97..d4fbfbdb463ee2756e44b3aea72910a773ac28a4 100644 (file)
--- a/docs/latex/wx/htmlhlpf.tex
+++ b/docs/latex/wx/htmlhlpf.tex
@@ -1,4 +1,4 @@
-\membersection{Help Files Format}\label{helpformat}
+\section{Help Files Format}\label{helpformat}

 
 wxHTML library uses a reduced version of MS HTML Workshop format.
 Tex2RTF can produce these files when generating HTML, if you set {\bf htmlWorkshopFiles} to {\bf true} in
 
 wxHTML library uses a reduced version of MS HTML Workshop format.
 Tex2RTF can produce these files when generating HTML, if you set {\bf htmlWorkshopFiles} to {\bf true} in


@@ -6,7 +6,9 @@ your tex2rtf.ini file.
 
 (See \helpref{wxHtmlHelpController}{wxhtmlhelpcontroller} for help controller description.)
 
 
 (See \helpref{wxHtmlHelpController}{wxhtmlhelpcontroller} for help controller description.)
 

-A {\bf book} consists of three files : header file, contents file and index file.
+A {\bf book} consists of three files: header file, contents file and index file.
+You can make a regular zip archive of these files, plus the HTML and any image files,
+for wxHTML (or helpview) to read; and the .zip file can optionally be renamed to .htb.

 
 \wxheading{Header file (.hhp)}
 
 
 \wxheading{Header file (.hhp)}
 


@@ -19,15 +21,25 @@ Title=@title of your book@
 Default topic=@default page to be displayed.htm@
 \end{verbatim}
 
 Default topic=@default page to be displayed.htm@
 \end{verbatim}
 

-All filenames (including the Default topic) are relative to the location of .hhp file.
+All filenames (including the Default topic) are relative to the 
+location of .hhp file.

 
 

-For larger projects I recommend storing everything but .hhp file into one .zip archive. (The contents file 
-would then be referred to as myhelp.zip\#zip:contents.hhc)
+{\bf Localization note:} In addition, .hhp file may contain line
+
+\begin{verbatim}
+Charset=@rfc_charset@
+\end{verbatim}
+
+which specifies what charset (e.g. "iso8859\_1") was used in contents
+and index files. Please note that this line is incompatible with
+MS HTML Help Workshop and it would either silently remove it or complain
+with some error. See also 
+\helpref{Writing non-English applications}{nonenglishoverview}.

 
 \wxheading{Contents file (.hhc)}
 
 Contents file has HTML syntax and it can be parsed by regular HTML parser. It contains exactly one list
 
 \wxheading{Contents file (.hhc)}
 
 Contents file has HTML syntax and it can be parsed by regular HTML parser. It contains exactly one list

-(\verb$<ul>$....\verb$</ul>$ statement):
+(\tt{<ul>}....\tt{</ul>} statement):

 
 \begin{verbatim}
 <ul>
 
 \begin{verbatim}
 <ul>


@@ -48,10 +60,10 @@ Contents file has HTML syntax and it can be parsed by regular HTML parser. It co
 \end{verbatim}
 
 You can modify value attributes of param tags. {\it topic name} is name of chapter/topic as is displayed in
 \end{verbatim}
 
 You can modify value attributes of param tags. {\it topic name} is name of chapter/topic as is displayed in

-contents, {\it filename.htm} is HTML page name (relative to .hhp file) and {\it numeric_id} is optional 
+contents, {\it filename.htm} is HTML page name (relative to .hhp file) and {\it numeric\_id} is optional 

 - it is used only when you use \helpref{wxHtmlHelpController::Display(int)}{wxhtmlhelpcontrollerdisplay}
 
 - it is used only when you use \helpref{wxHtmlHelpController::Display(int)}{wxhtmlhelpcontrollerdisplay}
 

-Items in the list may be nested - one \verb$<li>$ statement may contain a \verb$<ul>$ sub-statement:
+Items in the list may be nested - one \tt{<li>} statement may contain a \tt{<ul>} sub-statement:

 
 \begin{verbatim}
 <ul>
 
 \begin{verbatim}
 <ul>