fix the damned escaping on C++

git-svn-id: https://tesseract-ocr.googlecode.com/svn/trunk@470 d0cd1f9f-072b-0410-8dd7-cf729c803f20
This commit is contained in:
joregan 2010-09-29 17:56:39 +00:00
parent ec7bc49cc1
commit 2c76f06155
2 changed files with 46 additions and 46 deletions

View File

@ -44,44 +44,44 @@ LANGUAGES
There are currently language packs available for the following languages:
[width="40%",options="header"]
|============================
|Code |Name
|bul |Bulgarian
|cat |Catalan
|ces |Czech
|chi_sim |Simplified Chinese
|chi_tra |Traditional Chinese
|dan |Danish
|dan-frak |Danish (Fraktur)
|deu |German
|ell |Greek
|eng |English
|fin |Finnish
|fra |French
|hun |Hungarian
|ind |Indonesian
|ita |Italian
|jpn |Japanese
|kor |Korean
|lav |Latvian
|lit |Lithuanian
|nld |Dutch
|nor |Norwegian
|pol |Polish
|por |Portuguese
|ron |Romanian
|rus |Russian
|slk |Slovakian
|slv |Slovenian
|spa |Spanish
|srp |Serbian
|swe |Swedish
|tgl |Tagalog
|tha |Thai
|tur |Turkish
|ukr |Ukrainian
|vie |Vietnamese
|============================
|=============================
|Code |Name
|bul |Bulgarian
|cat |Catalan
|ces |Czech
|chi_sim |Simplified Chinese
|chi_tra |Traditional Chinese
|dan |Danish
|dan-frak |Danish (Fraktur)
|deu |German
|ell |Greek
|eng |English
|fin |Finnish
|fra |French
|hun |Hungarian
|ind |Indonesian
|ita |Italian
|jpn |Japanese
|kor |Korean
|lav |Latvian
|lit |Lithuanian
|nld |Dutch
|nor |Norwegian
|pol |Polish
|por |Portuguese
|ron |Romanian
|rus |Russian
|slk |Slovakian
|slv |Slovenian
|spa |Spanish
|srp |Serbian
|swe |Swedish
|tgl |Tagalog
|tha |Thai
|tur |Turkish
|ukr |Ukrainian
|vie |Vietnamese
|=============================
HISTORY
-------
@ -90,12 +90,12 @@ Hewlett Packard Co, Greeley Colorado between 1985 and 1994, with some more
changes made in 1996 to port to Windows, and some C\+\+izing in 1998. A
lot of the code was written in C, and then some more was written in C\+\+.
Since then all the code has been converted to at least compile with a
C\+\+ compiler. Currently it builds under Linux with gcc4.0, gcc4.1 and
under Windows with VC++6 and VC++Express. The C\+\+ code makes heavy use of
C\++ compiler. Currently it builds under Linux with gcc4.0, gcc4.1 and
under Windows with VC\+\+6 and VC\+\+Express. The C\++ code makes heavy use of
a list system using macros. This predates stl, was portable before stl, and
is more efficient than stl lists, but has the big negative that if you do get
a segmentation violation, it is hard to debug. Another "feature" of the
C/C++ split is that the C\+\+ data structures get converted to C data
C/C\++ split is that the C\++ data structures get converted to C data
structures to call the low-level C code. This is ugly, and the C++izing of
the C code is a step towards eliminating the conversion, but it has not
happened yet.

View File

@ -54,7 +54,7 @@ rowsep="1" colsep="1"
<colspec colname="col_2" colwidth="85*"/>
<thead>
<row>
<entry align="left" valign="top">Code </entry>
<entry align="left" valign="top">Code </entry>
<entry align="left" valign="top">Name</entry>
</row>
</thead>
@ -210,13 +210,13 @@ Hewlett Packard Co, Greeley Colorado between 1985 and 1994, with some more
changes made in 1996 to port to Windows, and some C++izing in 1998. A
lot of the code was written in C, and then some more was written in C++.
Since then all the code has been converted to at least compile with a
C+\+ compiler. Currently it builds under Linux with gcc4.0, gcc4.1 and
under Windows with VC<literal>6 and VC</literal>Express. The C+\+ code makes heavy use of
C++ compiler. Currently it builds under Linux with gcc4.0, gcc4.1 and
under Windows with VC++6 and VC++Express. The C++ code makes heavy use of
a list system using macros. This predates stl, was portable before stl, and
is more efficient than stl lists, but has the big negative that if you do get
a segmentation violation, it is hard to debug. Another "feature" of the
C/C<literal> split is that the C+\+ data structures get converted to C data
structures to call the low-level C code. This is ugly, and the C</literal>izing of
C/C++ split is that the C++ data structures get converted to C data
structures to call the low-level C code. This is ugly, and the C++izing of
the C code is a step towards eliminating the conversion, but it has not
happened yet.</simpara>
<simpara>The most important changes in version 2.00 were that Tesseract can now