On Mon, Jul 12, 2010 at 17:39, Jonathan Lundell <[email protected]> wrote: > That is, btw, my 'variant=' suggestion, above. If it's practical, I'd prefer > it. But embedding the variant/context into the string would be (I think) less > disruptive. > > T('canto [[my room]]') > T('canto [[music]]') > > Not as pretty, but almost identical in effect.
With this aproach we can pass the context via string - it is a good feature since we don't need to change code for changing the context (the string that will be translated can be in a database, can be 'variable' by user input etc.) - and it is good for this case. btw, if we use it, we'll be creating *another* "language" and have to interpret this language (a simple interpreter - but is an interpreter) - I don't know if we need more interpreters. We should see what other software do on this cases - Ubuntu, for example, uses PO files to translates almost all software on Launchpad - how they solve these problems (do they solve?)? -- Álvaro Justen - @turicas http://blog.justen.eng.br/ 21 9898-0141
