[bug?] [ update all languages ] mix translation

9 views
Skip to first unread message

KMax

unread,
Jan 6, 2010, 6:13:53 PM1/6/10
to web2py-users
Hello
I have broke my translation file for second time while 'update all
languages'
Most translation are shifted to up heighbour. And at the and there
are 3-4 steps different: like

# coding: utf8 at the begining all fine
{
'"update" is an optional expression like "field1=\'newvalue\'". You
cannot update or delete the results of a JOIN':
'"\xd0\x98\xd0\xb7\xd0\xbc\xd0\xb5\xd0\xbd\xd0\xb8\xd1\x82\xd1\x8c" -
\xd0\xbd\xd0\xb5\xd0\x
'%Y-%m-%d': '%d-%m-%Y',
'%Y-%m-%d %H:%M:%S': '%d-%m-%Y %H:%M:%S',
---skip---
'record': 'record id',
'record does not exist': 'register',
'record id': 'remove from group',
'register': 'selected',
'remove from group': 'state',
'selected': '\xd1\x82\xd0\xb0\xd0\xb1\xd0\xbb
\xd0\xb8\xd1\x86\xd0\xb0',
'state': 'unable to parse csv file',
'table': '',
'unable to parse csv file': '',
}
#at the and
You can see translation for 'parse' are 2 steps away.

Please advise, what can I do to hunt down the bug.
Usualy update all language works just fine.

Thank you

mdipierro

unread,
Jan 6, 2010, 6:31:53 PM1/6/10
to web2py-users
Which web2py version?

mdipierro

unread,
Jan 6, 2010, 7:27:10 PM1/6/10
to web2py-users
I am a loss here. I need to your help.

Look into gluon/languages.py
There are two functions:

def read_dict(filename): ...

def write_dict(filename, contents): ...

Can you try reproduce the problem and see if read_dict returns the
correct data before it gets messed up and if write_dict gets the right
input. Since I cannot reproduce the problem I am trying to figure out
if the problem is in reading, writing or processing the data.

Would you also send a language file before and after it gets messed
up?

Massimo

On Jan 6, 5:13 pm, KMax <mkostri...@gmail.com> wrote:

KMax

unread,
Jan 6, 2010, 11:19:52 PM1/6/10
to web2py-users
The lastest version.
On 7 янв, 05:31, mdipierro <mdipie...@cs.depaul.edu> wrote:
> Which web2py version?

I made some patches to sql.py and dal.py ( timestamp->timestamp with
time zone, integer -> bigint, serial->bigserial), hardly belielive
this is cause.
Maybe ru locale is the reason? Webserver locale?
Did anyone with ru language has same issues?

I'L try to debug this, but first I have to find out how.

Reply all
Reply to author
Forward
0 new messages