Re: [PATCH] rtl
| From: | moshe doron | Date: | Mon, 03 May 2004 12:25:11 +0000 |
| Subject: | Re: [PATCH] rtl | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969360427@lists.php.net to get a copy of this message | ||
"Moshe Doron" <mosdoron@netvision.net.il> wrote in message
news:20040502124328.25946.qmail@pb1.pair.com...
>
> "Nuno Lopes" <nlopess@php.net> wrote in message
> news:003501c4303c$dd7a0930$0100a8c0@pc07653...
> > The old build system is used when you run build.sh in livedocs.
> > It does a ./configure --with-lang=$lang
> >
> > I don't know if we will ever get ride of this build system.
> >
> > The use of entities is a good idea, Goba! we may add the entites for
> > livedocs in language-snippets.ent, for example.
> >
> > Moshe: There won't be too many IFs.
> > We need just one if for the array $map and other IF to declare your
> special
> > functions. No real impact on performance and its much more manageable.
> > Anyway, any more opinions?
>
> i'm not realy care about this point. my initial intuition was to split the
> files but IFs also have gains.
>
> >
> > We need also to decide how to choose the encoding and how to choose if
RTL
> > or LTR for each language.
> > Create an array with this info? It's dificult to extract this info from
> the
> > old (actual) build system because livedocs can be used for more than one
> > language.
> >
>
> i'm +1 for array method.
>
more feedbacks?
goba, adding new i18n.php file that will hold the languages data is agreed?
> --/moshe.