Then use the some variable in ur language files. That is templated
language elements that could hold variable in them.
e.g.
The article {ARTICLE_SUBJECT} was successfuly deleted !
It's dynamic now!
On Mon, 18 Oct 2004 09:10:35 -0200, Bruno B B Magalhães
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> I do
Hi,
I do have a flat file with all the translations for the interface and
everything, but the problem is de dynamic content that must be
multilingual...
Regards,
Bruno
On Oct 18, 2004, at 5:29 AM, M Saleh EG wrote:
I'd always preffer to keep language stuff in files instead of DB.
A question or a
I'd always preffer to keep language stuff in files instead of DB.
A question or a problem u might face later is: How are you going to
store the text in the proper Charset in ur tables?
I'd do it this way.
-A field in DB to keep the current default language
-Every module in the app should have it
Hi everone,
I am building a multilingual content management systen, and I am studying the best way
to have the content translated, with minimal Database queries and load.
So I have:
CONTENTS
contentId
contentCreationDate
contentModificationDate
translationId
contentStatus
CATEGORIES
categoryId
