I18N support ?

Hi,
What is your position about i18n and tbs and generaly about the translation method with templates.

I need to translate the fieldanme of my data to present the pages.

Hi Peirgwnael,

Sorry for answering so late.
I didi know about i18n, I've read a bit about it but I can't figure out how it works. This is maybe intersting for TinyButsStrong, have you some examples or good links?

I know my need but not the solutions...
What I need is to present the pages with the presentation in the language of the user.
I thougt using the template system to convert the keywords in the good language (it's a way).
I fianly decide to use a merge block with a table what containt all the keyword or sentences in the language of the user.
An other way is to have a template file for each language but it's not really my preference...

there could be some [translate.keyword] tags.

then you have to tell tbs in which languagefile it has to look (i.E. $tbs->setLanguage("en"); ). this file is parsed from an ini-file like this (with parse_ini_file() ):

lang_de.lang:


lang_en.lang:

after this tbs will know which the text to replace the keywords

hope this helps...

No, no ini files please...
TBS supports databases, if any way then I would prefer a database over a flat file structure. If tbs would do it both ways thats fine too..

you don't need i18n support in a database: just use 'WHERE lang='en'" and you've got the chosen language... ;) what we need is especially i18n support for the use WITHOUT a database.

ok, I didn't get a lot further then the introduction beacause I have little time. But doesn't multilingual support just call for a database?

I use multiple tables for it that are maintained simultaniously, so I change the tablename (in a global variable). This way adding languages and making changes seemed most easy and overseeable (even thought the user gets an interface)

But I will not say anything more in this thread before I read more about I18N ;)
Sorry if I said something stupid :)

Hello,

I'm very instered with this discussion because they are several queries for a multi-language support with TBS.

What I'll probably add to next version is an extension for the MergeField() method.
Now:
Thinking of:
Then all 'fld' fields are merged with the value returned by function MyFunction().
Example:
HTML:
PHP:
What do you think about that?

hm, seems to be the way to go. but it would be nice to have a function-library shipping with tbs (i could add the ini-version and ruud could eventualy do his database-function).