Lines Matching refs:to
14 Currently, this I18N version of PHP only adds Japanese support to base
15 PHP. It allows you to use Japanese in scripts, as well as conversion
18 to UNICODE table). The basic design aproach is to allow for other
19 languages to be added in the future. Developers are encourage to join
22 For more information on Japanese encodings, please refer to the
28 This package allows you to handle multiple Japanese encodings (SJIS, EUC,
30 them to the appropriate mailing list. For now, the PHP-jp mailing list
40 Due to lack of documentation, it's not intended for beginners. If
41 something goes wrong, be prepared to fix it on your own.
48 Please refer to the source code for the copyrights. In general, each
50 copyright holders restrictions, you are not allowed to use it in any
57 allowed to be redistributed with certain restrictions.
59 Due to this package being still in beta, please try to redistribute
60 it as an entire package. Please try not to distribute it as a form
61 of patch. Because we would prefer to have this package distributed
63 any patch to this package.
69 their free time producing it. Although we are not related to the core
70 PHP programmers, we are hoping to have our modifications merged into the
72 "Japanese Patch" (or distribution). Our final goal is to have true
79 (Discussions are in Japanese, but feel free to write us in English)
104 o Special Thanks to
118 - allows you to use various character encodings for script files and
137 Don't forget to copy php3.ini-dist to desired location.
141 which start with "i18n.xxxx" to php3.ini.
210 If http output encoding is set to other than 'pass', conversion of encoding
211 from internal encoding to http output is done automatically. Thus,
212 if you prefer to spit out anything in raw binary format, your data
213 may be corrupted. In such event, set http_output to 'pass'.
233 made prior to this, proper header may have been sent out to the
240 It may help us to track the problem if you send us the script as well.
250 Due to historical reason, there are multiple character encodings used
261 similar to EUC
275 Because of having all these character encodings, PHP needs to translate
277 library allows you to handle mb strings without fear of getting mb char
281 encourage other developers to modify our code to suit your needs. We
282 definitely need people to work with Korean, Chinese (both traditional
292 The following init options will allow you to change the default settings.
371 encodings, following conditions have to be satisfied in order
372 to use them:
382 PHP scripts to URL encoding, BASE64 or Quoted-Printable, encoding
384 prefer to encode in compliance with i18n.http_output, you need
385 to manually convert encoding.
407 The script's encoding is converted to i18n.internal_encoding before
422 If set to pass, no conversion will take place.
423 If set to auto, it will automatically detect the encoding. If
424 detection is successful, it will convert to the proper internal
438 This option is only effective as long as i18n.http_input is set to
440 assumption to convert the http input to the internal encoding.
441 If set to pass, no conversion will take place.
506 pass: no conversion (only if i18n.http_input is set to pass)
514 string is assumed to be in internal encoding.
542 pass: unable to determine (text is too short to determine)
550 the encoding of string is assumed to be the internal encoding.
565 is assumed to be the internal encoding.
578 is assumed to be the internal encoding.
592 is assumed to be the internal encoding.
608 set length to 5, you will only get two mb characters. If no encoding
609 is defined, the encoding of string is assumed to be the internal encoding.
663 If no encoding is defined, the encoding of string is assumed to be
695 If you need to assign Japanese text in GET method with argument, such as;
706 in php3.ini from On to Off. An alternative work around to this problem
707 is to use StripSlashes().
709 If $quote_str is in SJIS and you would like to extract Japanese text,
720 If i18n_http_input() returns 'pass', it's likely that PHP failed to
722 value="some Japanese text"> to properly detect the incoming text's
744 Kuwamura applied to original php-3.0.18. It also includes following fixes:
746 1) allows you to set charset in mail().
747 2) fixed mbregex definitions to avoid conflicts with system regex
753 Following setups are known to work:
756 ImageTTFText($im,$size,$angle,$x1,$y1,$color,"/path/to/font.ttf",
761 ImageTTFText($im,$size,$angle,$x1,$y1,$color,"/path/to/font.ttf","���ܸ�");
765 For any gd libraries before 1.6.2, you need to use i18n_convert. For
766 gd-1.5.2/3, upgrade to anything above 1.7 to use ImageTTFText without
767 using i18n_convert. As long as you have internal_encoding set to EUC or
