[PHP-DOC] cvs: phpdoc /en/reference/mbstring encodings.xml
takagi Fri Nov 3 08:43:11 2006 UTC Modified files: /phpdoc/en/reference/mbstring encodings.xml Log: typo fix. http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/mbstring/encodings.xml?r1=1.2&r2=1.3&diff_format=u Index: phpdoc/en/reference/mbstring/encodings.xml diff -u phpdoc/en/reference/mbstring/encodings.xml:1.2 phpdoc/en/reference/mbstring/encodings.xml:1.3 --- phpdoc/en/reference/mbstring/encodings.xml:1.2 Sun Mar 14 11:19:32 2004 +++ phpdoc/en/reference/mbstring/encodings.xml Fri Nov 3 08:43:11 2006 @@ -1,5 +1,5 @@ - + Summaries of supported encodings @@ -144,14 +144,14 @@ -UTF-16BE +UTF-16LE Unicode See above. In contrast to UTF-16, strings are always assumed - to be in big endian form. + to be in little endian form.
Re: [PHP-DOC] cvs: phpdoc /en/reference/mbstring encodings.xml reference.xml /entities global.ent
On Tue, 16 Mar 2004, Nuno Lopes wrote: > Maybe... isn't even implemented in livedocs, so more work > for us!! :) I doubt we even have templates for phpweb for it. > Why not use a simple table? Right. Derick
Re: [PHP-DOC] cvs: phpdoc /en/reference/mbstring encodings.xml reference.xml /entities global.ent
> Agreed. I don't like redundancy either. Maybe using > for a list of this kind was wrong in the first place? > > Moriyoshi Maybe... isn't even implemented in livedocs, so more work for us!! :) Why not use a simple table? Nuno
Re: [PHP-DOC] cvs: phpdoc /en/reference/mbstring encodings.xml reference.xml /entities global.ent
On 2004/03/16, at 5:01, Nuno Lopes wrote: BTW, you seems to have combined the entry for encoding names in IANA charset registry with the mbstring encoding name that was put in the element of each segmentedlist. That's not what I meant and they are not always identical. So I think the original is right in some aspect. Have you got any idea to fulfill those requirements altogether? If you want, I may revert my changes, but I think that repeting all time the headers isn't very good. I've entered the title in IANA name, just to remove those headers. I think the best approach is to add a new parameter with the mbstring charset name. Agreed. I don't like redundancy either. Maybe using for a list of this kind was wrong in the first place? Moriyoshi
Re: [PHP-DOC] cvs: phpdoc /en/reference/mbstring encodings.xml reference.xml /entities global.ent
> Then it was a semantics issue. I placed a segmentedlist for every entry > because the rendered page with a unified segmentedlist didn't look neat. Yes, there weren't any kind of xml/docbook errors. > BTW, you seems to have combined the entry for encoding names in IANA > charset registry with the mbstring encoding name that was put in the > element of each segmentedlist. That's not what I meant and > they are not always identical. So I think the original is right > in some aspect. Have you got any idea to fulfill those requirements > altogether? If you want, I may revert my changes, but I think that repeting all time the headers isn't very good. I've entered the title in IANA name, just to remove those headers. I think the best approach is to add a new parameter with the mbstring charset name. > > Don't forget that some of that charsets aren't explained, they have > > only the > > name there. > Well, I have too few time to fill them at once. Any volunteers are > welcome :) Bah,... I'm full of work: finishing Tidy, Migration from PHP 4 to 5, closing the 3 bugs assigned to me (including improving the streams chapter), maybe SPL after all this... > Moriyoshi
Re: [PHP-DOC] cvs: phpdoc /en/reference/mbstring encodings.xml reference.xml /entities global.ent
On 2004/03/16, at 0:23, Nuno Lopes wrote: Modified files: /phpdoc/en/reference/mbstringencodings.xml reference.xml /phpdoc/entitiesglobal.ent Log: fixing docbook style adding entities for mbstring Just curious, what was wrong with the segmentedlist style? Seems like there was a kind of redundancy :) didou Firstly you were using URLs directly instead of entities. And you were repiting the header in every entry. You need only to add the header and then fill in the entries. (more info at: http://www.docbook.org/tdg/en/html/segmentedlist.html) Then it was a semantics issue. I placed a segmentedlist for every entry because the rendered page with a unified segmentedlist didn't look neat. BTW, you seems to have combined the entry for encoding names in IANA charset registry with the mbstring encoding name that was put in the element of each segmentedlist. That's not what I meant and they are not always identical. So I think the original is right in some aspect. Have you got any idea to fulfill those requirements altogether? Don't forget that some of that charsets aren't explained, they have only the name there. Well, I have too few time to fill them at once. Any volunteers are welcome :) Moriyoshi
Re: [PHP-DOC] cvs: phpdoc /en/reference/mbstring encodings.xml reference.xml /entities global.ent
> >> Modified files: > >> /phpdoc/en/reference/mbstringencodings.xml reference.xml > >> /phpdoc/entitiesglobal.ent > >> Log: > >> fixing docbook style > >> adding entities for mbstring > > > > > > Just curious, what was wrong with the segmentedlist style? > > > > Seems like there was a kind of redundancy :) > > didou > Firstly you were using URLs directly instead of entities. And you were repiting the header in every entry. You need only to add the header and then fill in the entries. (more info at: http://www.docbook.org/tdg/en/html/segmentedlist.html) Don't forget that some of that charsets aren't explained, they have only the name there. Nuno
Re: [PHP-DOC] cvs: phpdoc /en/reference/mbstring encodings.xml reference.xml /entities global.ent
Moriyoshi Koizumi wrote: On 2004/03/14, at 20:19, Nuno Lopes wrote: nlopessSun Mar 14 06:19:43 2004 EDT Modified files: /phpdoc/en/reference/mbstringencodings.xml reference.xml /phpdoc/entitiesglobal.ent Log: fixing docbook style adding entities for mbstring Just curious, what was wrong with the segmentedlist style? Seems like there was a kind of redundancy :) didou
Re: [PHP-DOC] cvs: phpdoc /en/reference/mbstring encodings.xml reference.xml /entities global.ent
On 2004/03/14, at 20:19, Nuno Lopes wrote: nlopess Sun Mar 14 06:19:43 2004 EDT Modified files: /phpdoc/en/reference/mbstring encodings.xml reference.xml /phpdoc/entitiesglobal.ent Log: fixing docbook style adding entities for mbstring Just curious, what was wrong with the segmentedlist style? Moriyoshi
Re: [PHP-DOC] cvs: phpdoc /en/reference/mbstring encodings.xml reference.xml
On 2004/03/14, at 19:37, Nuno Lopes wrote: TODO: maybe I'm not using correctly. docbook experts there? I'm not a docbook expert, but I've noticed that you used incorrectly. I'll correct this in a few minutes. Thanks. Moriyoshi
[PHP-DOC] cvs: phpdoc /en/reference/mbstring encodings.xml reference.xml /entities global.ent
nlopess Sun Mar 14 06:19:43 2004 EDT Modified files: /phpdoc/en/reference/mbstring encodings.xml reference.xml /phpdoc/entitiesglobal.ent Log: fixing docbook style adding entities for mbstring http://cvs.php.net/diff.php/phpdoc/en/reference/mbstring/encodings.xml?r1=1.1&r2=1.2&ty=u Index: phpdoc/en/reference/mbstring/encodings.xml diff -u phpdoc/en/reference/mbstring/encodings.xml:1.1 phpdoc/en/reference/mbstring/encodings.xml:1.2 --- phpdoc/en/reference/mbstring/encodings.xml:1.1 Sat Mar 13 18:33:07 2004 +++ phpdoc/en/reference/mbstring/encodings.xml Sun Mar 14 06:19:32 2004 @@ -1,9 +1,9 @@ - + Summaries of supported encodings - UCS-4 + Summaries of supported encodings Name in the IANA character set registry Underlying character set Description @@ -23,13 +23,6 @@ are represented. - - - UCS-4BE - Name in the IANA character set registry - Underlying character set - Description - Additional note ISO-10646-UCS-4 UCS-4 @@ -41,13 +34,6 @@ to be in big endian form. - - - UCS-4LE - Name in the IANA character set registry - Underlying character set - Description - Additional note ISO-10646-UCS-4 UCS-4 @@ -59,13 +45,6 @@ to be in little endian form. - - - UCS-2 - Name in the IANA character set registry - Underlying character set - Description - Additional note ISO-10646-UCS-2 UCS-2 @@ -81,13 +60,6 @@ are represented. - - - UCS-2BE - Name in the iana character set registry - Underlying character set - Description - Additional note ISO-10646-UCS-2 UCS-2 @@ -99,13 +71,6 @@ to be in big endian form. - - - UCS-2LE - Name in the iana character set registry - Underlying character set - Description - Ddditional note ISO-10646-UCS-2 UCS-2 @@ -117,13 +82,6 @@ to be in little endian form. - - - UTF-32 - Name in the iana character set registry - Underlying character set - Description - Additional note UTF-32 Unicode @@ -140,13 +98,6 @@ are represented. - - - UTF-32BE - Name in the iana character set registry - Underlying character set - Description - Additional note UTF-32BE Unicode @@ -156,13 +107,6 @@ to be in big endian form. - - - UTF-32LE - Name in the iana character set registry - Underlying character set - Description - Additional note UTF-32LE Unicode @@ -172,13 +116,6 @@ to be in little endian form. - - - UTF-16 - Name in the iana character set registry - Underlying character set - Description - Additional note UTF-16 Unicode @@ -195,13 +132,6 @@ are represented. - - - UTF-16BE - Name in the iana character set registry - Underlying character set - Description - Additional note UTF-16BE Unicode @@ -213,13 +143,6 @@ to be in big endian form. - - - UTF-16LE - Name in the iana character set registry - Underlying character set - Description - Additional note UTF-16BE Unicode @@ -231,13 +154,6 @@ to be in big endian form. - - - UTF-8 - Name in the iana character set registry - Underlying character set - Description - Additional note UTF-8 Unicode / UCS @@ -246,13 +162,6 @@ none - - - UTF-7 - Name in the iana character set registry - Underlying character set - Description - Additional note UTF-7 Unicode @@ -262,13 +171,6 @@ none - - - UTF7-IMAP - Name in the iana character set registry - Underlying character set - Description - Additional note (none) Unicode @@ -278,13 +180,6 @@ none - - - ASCII - Name in the iana character set registry - Underlying character set - Description - Additional note US-ASCII (preferred MIME name) / iso-ir-6 / ANSI_X3.4-1986 / @@ -297,13 +192,6 @@ (none) - - - EUC-JP - Name in the iana character set registry - Underlying character set - Description - Additional note EUC-JP (preferred MIME name) / @@ -325,13 +213,6 @@ For information interchange with those platforms, use EUCJP-WIN instead. - - - SJIS - Name in the iana character set registry - Underlying character set - Description - Additional note Shift_JIS (preferred MIME name) / MS_Kanji / csShift_JIS Compound of JIS X0201:1997 / JIS X0208:1997 @@ -345,13 +226,6 @@ For the CP932 codemap, use SJIS-WIN instead. - - - EUCJP-WIN - Name in the iana character set registry - Underlying character set - Description - Additional note (none) @@ -364,13 +238
Re: [PHP-DOC] cvs: phpdoc /en/reference/mbstring encodings.xml reference.xml
> TODO: maybe I'm not using correctly. docbook experts there? I'm not a docbook expert, but I've noticed that you used incorrectly. I'll correct this in a few minutes. Nuno
[PHP-DOC] cvs: phpdoc /en/reference/mbstring encodings.xml reference.xml
moriyoshi Sat Mar 13 18:33:08 2004 EDT Added files: /phpdoc/en/reference/mbstring encodings.xml Modified files: /phpdoc/en/reference/mbstring reference.xml Log: - Add "summaries of supported encodings" section. Be sure to rerun "configure". TODO: maybe I'm not using correctly. docbook experts there? - Updated the location of cjk.inf - Correct some silly typos. http://cvs.php.net/diff.php/phpdoc/en/reference/mbstring/reference.xml?r1=1.18&r2=1.19&ty=u Index: phpdoc/en/reference/mbstring/reference.xml diff -u phpdoc/en/reference/mbstring/reference.xml:1.18 phpdoc/en/reference/mbstring/reference.xml:1.19 --- phpdoc/en/reference/mbstring/reference.xml:1.18 Sat Mar 13 08:34:51 2004 +++ phpdoc/en/reference/mbstring/reference.xml Sat Mar 13 18:33:07 2004 @@ -1,8 +1,8 @@ - + - Multi-Byte String Functions - Multi-Byte String + Multibyte String Functions + Multibyte String @@ -110,7 +110,6 @@ scanner and the character encoding. - If you have some database connected with PHP, it is recommended that @@ -148,13 +147,13 @@ - In PHP 4.3.2 or earlier versions, mbstring - there is a limitation in this functionality that - mbstring does not perform character encoding - conversion in POST data if the enctype attribute in - the form element is set to - multipart/form-data. So you have to convert - the incoming data by yourself in this case if necessary. + In PHP 4.3.2 or earlier versions, there was a limitation in this + functionality that mbstring does not perform + character encoding conversion in POST data if the + enctype attribute in the form + element is set to multipart/form-data. + So you have to convert the incoming data by yourself in this case + if necessary. Beginning with PHP 4.3.3, if enctype for HTML form is @@ -257,300 +256,306 @@ - - Supported Character Encodings - - Currently the following character encodings are supported by the - mbstring module. Any of those Character encodings - can be specified in the encoding parameter of - mbstring functions. - - - The following character encoding is supported in this PHP - extension: - - - UCS-4 - UCS-4BE - UCS-4LE - UCS-2 - UCS-2BE - UCS-2LE - UTF-32 - UTF-32BE - UTF-32LE - UTF-16 - UTF-16BE - UTF-16LE - UTF-7 - UTF7-IMAP - UTF-8 - ASCII - EUC-JP - SJIS - eucJP-win - SJIS-win - ISO-2022-JP - JIS - ISO-8859-1 - ISO-8859-2 - ISO-8859-3 - ISO-8859-4 - ISO-8859-5 - ISO-8859-6 - ISO-8859-7 - ISO-8859-8 - ISO-8859-9 - ISO-8859-10 - ISO-8859-13 - ISO-8859-14 - ISO-8859-15 - byte2be - byte2le - byte4be - byte4le - BASE64 - HTML-ENTITIES - 7bit - 8bit - EUC-CN - CP936 - HZ - EUC-TW - CP950 - BIG-5 - EUC-KR - UHC (CP949) - ISO-2022-KR - Windows-1251 (CP1251) - Windows-1252 (CP1252) - CP866 (IBM866) - KOI8-R - - - &php.ini; entry, which accepts encoding name, - accepts "auto" and - "pass" also. - mbstring functions, which accepts encoding - name, and accepts "auto". - - - If "pass" is set, no character - encoding conversion is performed. - - - If "auto" is set, it is expanded to - the list of encodings defined per the NLS. - For instance, if the NLS is set to Japanese, - the value is assumed to be - "ASCII,JIS,UTF-8,EUC-JP,SJIS". - - - See also mb_detect_order - + +Supported Character Encodings + + Currently the following character encodings are supported by the + mbstring module. Any of those Character encodings + can be specified in the encoding parameter of + mbstring functions. + + + The following character encoding is supported in this PHP + extension: + + + UCS-4 + UCS-4BE + UCS-4LE + UCS-2 + UCS-2BE + UCS-2LE + UTF-32 + UTF-32BE + UTF-32LE + UTF-16 + UTF-16BE + UTF-16LE + UTF-7 + UTF7-IMAP + UTF-8 + ASCII + EUC-JP + SJIS + eucJP-win + SJIS-win + ISO-2022-JP + JIS + ISO-8859-1 + ISO-8859-2 + ISO-8859-3 + ISO-8859-4 + ISO-8859-5 + ISO-8859-6 + ISO-8859-7 + ISO-8859-8 + ISO-8859-9 + ISO-8859-10 + ISO-8859-13 + ISO-8859-14 + ISO-8859-15 + byte2be + byte2le + byte4be + byte4le + BASE64 + HTML-ENTITIES + 7bit + 8bit + EUC-CN + CP936 + HZ + EUC-TW + CP950 + BIG-5 +
