Diff for "FrontPage" - completesearch

Differences between revisions 10 and 39 (spanning 29 versions)

[wiki:completesearch/Installation Installation Guide]

[wiki:CodingConventions Coding Conventions]

[wiki:completesearch/DesignConventions OO and C++ Design Conventions]

[wiki:completesearch/Templates Template pecularities in the CompleteSearch code]

[wiki:NewFeatures New Features that would be nice to have]

[wiki:completesearch/Markus Markus' comments / log]

[wiki:completesearch/SeleniumRC Testing with SeleniumRC]

[wiki:completesearch/CVSHistory CVS history]

[wiki:completesearch/TODO TODO list]

[wiki:completesearch/ExcerptGenerator Excerpt Generator requirements]

[wiki:completesearch/IndexBuilding Index Building: Tools, Formats, etc.]

[wiki:completesearch/DocumentFormats Document Formats: .docs, .words, .vocabulary, etc.]

[wiki:completesearch/Examples Example programs etc.]

[wiki:completesearch/GNUBuildSystem How to use the autoconf/automake tools to build and deliver the project.]

-  ⇤ ← Revision 10 as of 2007-05-28 15:08:06 → 
  Size: 1660
  Editor: dslb-084-058-237-229
  Comment:
+   ← Revision 39 as of 2007-09-28 13:02:20 → ⇥
  Size: 1004
  Editor: dslb-084-058-232-124
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-= About character encoding (28May07 Markus)=
+[wiki:Self:completesearch/Installation Installation Guide]
 Line 3:
-CompletionSearch supports ISO-8859-1 and the multibyte character encoding UTF-8.
UTF-8 is the default encoding with the following consequences:
+[wiki:Self:CodingConventions Coding Conventions]
-Line 6:
+Line 5:
- * The $AC->settings->encoding is 'utf-8' unless overriden in autocomplete_config.php
 * The texts in text.php are saved as UTF-8
 * The css file uses '@charset "utf-8";'
 * We use mb_strtolower (instead of strtolower) with parameter $AC->settings->encoding to enable UTF-8
+[wiki:Self:completesearch/DesignConventions OO and C++ Design Conventions]
-Line 11:
+Line 7:
-We do the following depending on the defined encoding:
 * We UTF-8 encode $AC->settings->capitals if $AC->settings->encoding is UTF-8
 * In ajax.php we UTF-8 encode the query string if $AC->settings->encoding is UTF-8 and the charset of content_type is not UTF-8 (means the request is sent as a non-UTF-8 type)
 * We set the page encoding of index.php, options.php and change_options.php according to $AC->settings->encoding (<meta http-equiv="content-type" content="text/html;charset=<?php echo $AC->settings->encoding; ?>">
)
 * Texts from text.php are UTF-8 decoded by $AC->get_text() if $AC->settings->encoding is ISO-8859-1
 * We url encode the javascript code in function javascript_rhs (in generate_javascript.php) if $AC->settings->encoding is not UTF-8 (this is not necessary if utf-8 is used)
+[wiki:Self:completesearch/Templates Template pecularities in the CompleteSearch code]
-Line 19:
+Line 9:
+[wiki:Self:NewFeatures New Features that would be nice to have]
-Line 20:
+Line 11:
+[wiki:Self:completesearch/Markus Markus' comments / log]
-Line 21:
+Line 13:
-== The PHP Apache extension php_mbstring ==
+[wiki:Self:completesearch/SeleniumRC Testing with SeleniumRC]
-Line 23:
+Line 15:
-The use of the mb_strtolower function (and other mb_ functions) requires the extension php_mbstring in php.ini:
+[wiki:Self:completesearch/CVSHistory CVS history]
-Line 25:
+Line 17:
-{{{
In windows:
extension=php_mbstring.dll
+[wiki:Self:completesearch/TODO TODO list]
-Line 29:
+Line 19:
-or in linux:
extension=php_mbstring.so
}}}
+[wiki:Self:completesearch/ExcerptGenerator Excerpt Generator requirements]
-Line 33:
+Line 21:
-(On geek, the mb_... functions were available by default, on Markus' laptop the line above had to be added.)
+[wiki:Self:completesearch/IndexBuilding Index Building: Tools, Formats, etc.]

[wiki:Self:completesearch/DocumentFormats Document Formats: .docs, .words, .vocabulary, etc.]

[wiki:Self:completesearch/Examples Example programs etc.]

[wiki:Self:completesearch/GNUBuildSystem How to use the autoconf/automake tools to build and deliver the project.]