Krinkle wrote:
-- Tool developer workflow:
I'll describe how the system would work from a tool developers point
of view. [3]
So here's what you'd do to make it work, three easy steps:
1) The toolserver tool developer includes a single php file (eg. /
p_i18n/ToolStart.php). This makes the i18n class available.
2) A new instance of the class is created like $I18N = new
TsIntuition( 'mygroup' );
3) Messages can now be returned with either _('message-key') [2] or
$TSi18n->msg( 'message-key', $options ).
-- Other features
* Variable replacement ($1, $2, etc.)
* Fallback languages:
* Getting language names
* Escaping (ie. options = array( escape => html )
How much duplication will TsIntuition have with MediaWiki i18n code?
* Automated updates: Since the messages are
file-stored in the
messages-directory of the tool. There's no need to keep track or
update anything.
(...)
-- TranslateWiki
I'm currently in talks with TranslateWiki how to best set up the
syncing system. Although initial chat with Nikerabbit didn't bring up
any expected problem (as it's fairly similar other projects they
translate), it still needs to be set up. I expect to have something
going within one or two weeks.
Wouldn't DBA be preferible?