|
|
Posted by Tony Marston on 03/09/06 10:55
I wouldn't. There is more of an overhead of opening and reading several
small files than there is in opening an reading one large file.
I avoid that in my application as it is broken down into subsystems, and
each subsystem has its own language file. When you consider that only one
script from one subsystem is running at any one time this means that I only
open the one file hat is relevant to the current script.
--
Tony Marston
http://www.tonymarston.net
"Bob Bedford" <bob@bedford.com> wrote in message
news:440ee732$0$723$5402220f@news.sunrise.ch...
> "Tony Marston" <tony@NOSPAM.demon.co.uk> a ιcrit dans le message de news:
> dum949$3ps$1$8302bc10@news.demon.co.uk...
>> With my internationalisation feature I do not put all the text into a
>> single file, I have a separate file for each language. This means that
>> each file is no bigger than it need be, and it is also much easier to
>> give someone a copy of a small file for translation purposes.
>
> Thanks for replying Tony.
>
> It's the structure I've: 1 file for every language, and they will be 100ko
> each quite soon.
>
> My question is: Should I split every large language (engmysite.inc,
> germysite.inc,itamysite.inc) in many little files (engindex.inc,
> engcontact.inc....) ?
>
>
>
>
[Back to original message]
|