At 10:47 PM 4/30/2001 +0900, Rui Hirokawa wrote:
> > No I don't see a problem with this but please do it quickly. 4.0.6 has
> > already gone a long way since we started RC'ing 4.0.5 and I would like to
> > start RC'ing it pretty soon. You should probably also copy
> > dotnet/EXPERIMENTAL to your directory until it becomes completely stable.
>
>I did.
>
> >
> > By the way, do you think jstring is the right name? Is it only for
> Japanese?
>
>It includes some functions for japanese,but some functions are not
>only for japanese.
>For example, this module supports encoding conversion functionality between
>Unicode and some other encodings like ISO-8859-X.
>Currently, it includes encoding conversion filter for japanese and ISO-8859-X,
>but it is relatively easy task to add another conversion filter for some other
>language.
>
>I believe this module is small step for PHP internationalization.
>I think the name 'jstring' is right name now because it is existing
>for japanese string function now.
>But 'i18n' or 'wchar' or 'i18n-ja' are also the candidate for the name.
jstring sounds very Java'ish :)
I think a more descriptive name would be better especially if it is not
Japanese specific.
Let's wait and see what other people think.
I'm very happy to see this code being merged into PHP 4. Many Japanese
users have missed out on PHP 4 because these patches were mostly available
for PHP 3.
Andi
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
