Thanks for the pointer. I think I found and fixed the problem. This was ONLY a problem if you opened the translation window, add a new translation string from another tab or from the shell, then submit the previous form that did not include the new strings. Anyway. Now even this problem should gone, please try trunk.
On Feb 26, 6:03 am, Iceberg <[email protected]> wrote: > How about this? http://groups.google.com/group/web2py/msg/94ab1188910ae303 > > On Feb26, 6:44pm, mdipierro <[email protected]> wrote: > > > > > > > Probably not because I cannot reproduce the problem. > > I need an example to be able to reproduce it. > > > Massimo > > > On Feb 26, 4:28 am, KMax <[email protected]> wrote: > > > > On 26 фев, 12:09, mdipierro <[email protected]> wrote:> Changelog > > > #1.75.5 > > > > > fixed behaviour with languages.py, thanks Iceberg > > > > I had an issue with shifting translation. > > > a=a > > > b=b > > > c=c > > > become > > > a=a > > > b=c > > > c= > > > Does this issue fixed or something else? -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
