phpwebsite-developers

[Phpwebsite-developers] Coding Standards & Internationization

[Todd O. <to...@da...>]

Are we planning to standardize on Perl or POSIX-extended regular
expressions?  I thought someone said one was faster than the other, but I
don't remember which.

I am excited about this project offering internationalization, although I
only know English.  However, most of what I've seen has only been European
support.  How difficult would it be to offer Asian and Arabic character
support via Unicode?  Having never done this before, I don't know what's
involoved.  Can someone fill me in?

--Todd

Re: [Phpwebsite-developers] Coding Standards & Internationization

[Karsten D. <k.d...@tu...>]

On Sat, Apr 14, 2001 at 03:23:13PM -0400, Todd Owen wrote:
> Are we planning to standardize on Perl or POSIX-extended regular
> expressions?  I thought someone said one was faster than the other, but I
> don't remember which.

Perl! Perl! Perl! They are 1) faster 2) more powerful
                  and 3) way more cool :-)

Unless you do simple replacements, then str_replace can't be beaten. But I
have already seen people who do nl2br with preg_replace :-( Seems as if PHP
offers way too much functions! :-P

> I am excited about this project offering internationalization, although I
> only know English.  However, most of what I've seen has only been European
> support.  How difficult would it be to offer Asian and Arabic character
> support via Unicode?  Having never done this before, I don't know what's
> involoved.  Can someone fill me in?

No knwoledge about that issue on my side :-/

Karsten
--=20
Why do we have to hide from the police, daddy?
Because we use emacs, son. They use vi.
-----------------------------
mailto:k.d...@tu... w=B3: http://www.k-fish.de/
gpg: http://www.k-fish.de/mykeys.gpg

Re: [Phpwebsite-developers] Coding Standards & Internationization

[Todd O. <to...@da...>]

Has anyone looked at the following for internationalization?

http://www.gnu.org/software/gettext/

FYI, Postgresql 7.1 was just released today and contains some great new
enhancements !!!

Keep you eyes on phpShop.org for some interesting changes.  They're taking
their ecommerce package and making it a module for their new shop Core.
Although they use phplib, I believe their upcoming Commerce module could be
converted for use in phpWS--it's a great ecommerce tool.

--Todd

Re: [Phpwebsite-developers] Coding Standards & Internationization

[Karsten D. <k.d...@tu...>]

On Sat, Apr 14, 2001 at 10:22:06PM -0400, Todd Owen wrote:
> Has anyone looked at the following for internationalization?
>=20
> http://www.gnu.org/software/gettext/

Well, since the roadmap states we will write our own templating system,
(which I don't _really_ understand, since being dependant on a GPL template
system gives you all security against the developers giving up their product
you need, plus you can ship a "certified" copy with your product)... I think
gettext won't get accepted: It requires even one more thing, and thios time
it must be compiled into PHP, which is a major drawback considering the
amount of people being hosted at (sic!) mass/cheap hosters.

Although it might be interesting to look into the issue :-) Just for the
sake of "knowing what you are talking about" :-)

Karsten
--=20
Why do we have to hide from the police, daddy?
Because we use emacs, son. They use vi.
-----------------------------
mailto:k.d...@tu... w=B3: http://www.k-fish.de/
gpg: http://www.k-fish.de/mykeys.gpg

Re: [Phpwebsite-developers] Coding Standards & Internationization

[Todd O. <to...@da...>]

>Well, since the roadmap states we will write our own templating system,
>(which I don't _really_ understand, since being dependant on a GPL template
>system gives you all security against the developers giving up their
product
>you need, plus you can ship a "certified" copy with your product)...

I don't think Brian was saying we should reinvent the wheel as far as
templating is concerned.  There are only a few good templating systems out
there anyway (fasttemplate, phplib, smarty).  My vote is for Smarty.  I
think Brian is saying we should integrate the Smarty code (let's say) into
phpWS so WE are familiar enough with it to continue on if the original
project stalls.

Karsten, you're correct that we shouldn't use an internationalization
technique that requires specific compile time options to implement it.  I
wasn't aware gettext required that.

FYI, phpWS is #7 on the HotScripts.com's PHP  most popular list.  Other PHP
content management systems are up there with us with Nuke at #1.

http://www.hotscripts.com/PHP/

--Todd