Differences between revisions 17 and 33 (spanning 16 versions)
Revision 17 as of 2007-08-10 23:47:23
Size: 2042
Editor: vpn-113
Comment:
Revision 33 as of 2007-09-14 16:34:46
Size: 654
Editor: infno1613
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[wiki:Self:Installation Installation Guide] [wiki:Self:completesearch/Installation Installation Guide]
Line 3: Line 3:
= About character encoding (28May07 Markus) = [wiki:Self:CodingConventions Coding Conventions]
Line 5: Line 5:
CompletionSearch supports ISO-8859-1 and the multibyte character encoding UTF-8.
UTF-8 is the default encoding with the following consequences:
[wiki:Self:NewFeatures New Features that would be nice to have]
Line 8: Line 7:
 * 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/Markus Markus' comments / log]
Line 13: Line 9:
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/CVSHistory CVS history]
Line 20: Line 11:
=== Note: The form attribute accept-charset ===
If the form attribute accept-charset is set to "UTF-8" the form variables are UTF-8 encoded before sent to server (even if the page encoding is not UTF-8).
[wiki:Self:completesearch/TODO TODO list]
Line 23: Line 13:
== The PHP Apache extension php_mbstring == [wiki:Self:completesearch/ExcerptGenerator Excerpt Generator requirements]
Line 25: Line 15:
The use of the mb_strtolower function (and other mb_ functions) requires the extension php_mbstring in php.ini: [wiki:Self:completesearch/IndexBuilding Index Building: Tools, Formats, etc.]
Line 27: Line 17:
{{{
In windows:
extension=php_mbstring.dll
[wiki:Self:completesearch/DocumentFormats Document Formats: .docs, .words, .vocabulary, etc.]
Line 31: Line 19:
or in linux:
extension=php_mbstring.so
}}}

(On geek, the mb_... functions were available by default, on Markus' laptop the line above had to be added.)

If this is the first extension you use be sure to have specified the location of the extension with the extension_dir directive.
[wiki:Self:completesearch/Examples Example programs etc.]

[wiki:completesearch/Installation Installation Guide]

[wiki:CodingConventions Coding Conventions]

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

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

[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.]

CompleteSearch: FrontPage (last edited 2017-03-19 13:30:19 by Hannah Bast)