Rogier,

The thread that you started in this list has been moved over to the template working group board, where I can't post.

That alone says why it shouldn't be closed.  The dev list has a lot more members than the template working group, and it doesn't have 100's of posts per day.

I don't remember where the discussion about using the International macro took place; it may have been on IRC.  I remember JT saying that it provided a significant speed-up to WebGUI though, something on the order of 20% - 30% faster.

You're correct in that a list of i18n labels would need to be made available.  The i18n data format that we currently uses has a context field, which could be used to identify where and how labels should be used.  However, it would need to be pretty flexible, since words like "Submit", "Save", "Cancel" and the like would be used throughout the system.

I found that the International macro wiki entry is a bit er.. minimal. I think it needs updating. Could someone perhaps add a description of the params?

[\quote]

It's minimal because it doesn't do much :).  I added a few lines to it, about namespaces and what the optional namespace is.  I think I'll also add a macro aliasing entry, so that it's clear how to set up WebGUI so that you can type ^i18n instead of ^International all the time.

Yeah it seems like a difficult job. I suppose you could make a list of generic labels for those common words, with the possibility to overwrite these for specific templates?

Today, everything that is "common" goes into the WebGUI namespace.  Anything used by lots of Assets goes into Asset.  However, as Bart and the translators could tell you, there are still lots of duplicate labels in the system.

As far as template specific overriding, the options would be:

1. Use a different label from the current namespaces.
2. Add a new label in the namespace.
3. Just hardcode it (which shouldn't be an option for default WebGUI templates).

Colin