Difference between revisions of "Talk:Internationalization/translation function"

(Templates)
Line 10: Line 10:
 
Use STRING_32 instead of STRING for output. Use STRING_GENERAL whenever it is possible on input.
 
Use STRING_32 instead of STRING for output. Use STRING_GENERAL whenever it is possible on input.
 
--[[User:Manus|manus]] 16:23, 25 May 2006 (CEST)
 
--[[User:Manus|manus]] 16:23, 25 May 2006 (CEST)
 +
 +
== Templates ==
 +
 +
A new class (I18N_TEMPLATE_FORMATTER) has been writte by Trosim, but it would be nice to use existing ones. It happens that ST_FORMATTER (part of Gobo) is explicitly excluded from the library, somebody knows the reason?
 +
 +
At present when translating a template you must already give the variables that must be substituted. In many situations it is useful to separate translation from variable substitution. This is what I'm working on.
 +
--[[User:Carlo|Carlo]] 10:32, 10 June 2006 (CEST)

Revision as of 23:32, 9 June 2006

Globality

Content moved to class structure. Trosim 12:29, 24 May 2006 (CEST)

Propose

As I said, this is only a suggestion, I have syntactical and semantic criticism (tuple, tuple item types, names, plural form,...), too. But I made it to give our group a boost. So please make some changes and/or criticize my solution!! ETN talk 09:00, 25 May 2006 (CEST)


Use STRING_32 instead of STRING for output. Use STRING_GENERAL whenever it is possible on input. --manus 16:23, 25 May 2006 (CEST)

Templates

A new class (I18N_TEMPLATE_FORMATTER) has been writte by Trosim, but it would be nice to use existing ones. It happens that ST_FORMATTER (part of Gobo) is explicitly excluded from the library, somebody knows the reason?

At present when translating a template you must already give the variables that must be substituted. In many situations it is useful to separate translation from variable substitution. This is what I'm working on. --Carlo 10:32, 10 June 2006 (CEST)