OK, so I've done 2 pages, but then confuser had some issues with the includes, and although it would be easier (from a programmers point of view) to only include the code once in index or frame work, my original argument holds true, different files require different text..

I was looking about to see where (or how) the cookies are set, and I noticed a few functions that contain text output, which backups the "low overhead" argument for only including language files per page.. bah, more pages to be added, thankfully they are small

the question is, where are the language settings going to be made, and what should there actual names be, as what I have added does not seem to fit.. "define('COOKIE_LANG')" .. does not make sense with the current code

OK, I guess the question is really for confuser (or banancanard)

---

(..until someone comes online..)

I have thought about reducing the language include code, maybe to a function, but that just requires more code, and an include page can't be checked with $_PHP_SELF (or whatever it is)

so what about moving it to the index, well that would require loading one HUGE language file, and that would mean finding a way to distinguish between different "phrases" for the same thing, on different pages, which on the whole is just too much work, as there are just too many different pages and contexts on top of the memory required to hold everything..  again, bah

What I have done, works well with the installer, and best of all its lite. The bonus is, you can add language files one at a time, and each page can have language code added one at a time, until the whole system is in place, which brings me back to the original question, it needs to be sorted before I start making any more code changes..

(BTW the current code will work, pulling up english, if the code and language file is added)

hmm...  must be "that time of the month", as these posts are getting longer and longer.. sorry TGPEG, use the narrator assistant

hmmm having a file for each layout is nice in a way but when you want to edit something that is stated in multiple files it can be a real pain. Also its not just the Layouts which will require the languages but the functions as well like the function which displays whether the user is "Online" or "Offline". Having the includes in the index where it includes the layouts would make the Layouts neater yes. I like the idea of having one big file though, it makes more sense really, but maybe have core files in one big language file but Plugins have their own? No editing that way

a thought occured to me, there may be a way to get workablre solution that gives us both what we are looking for

the include goes in the index, because it knows what action is being performed, and hence it can pull a single "small" language include

note: the language file contains EVERY piece of text that is in the corresponding layout file, so the only "multi-page changes" going to be done, are according to how may language files there are..

OK, so the functions, well, they can be in a "functions.php" language file, that covers all the function related text, or, if possible, pull the text out of the functions and into the corresponding calling page (this depends on how the calls work I guess), either way would be ok tho, and it would not be too fat on server memory..

:P