thousand separator doesn't work on reports

[Yug Faa]

Hi every body

from launguage form, in the separator input, make [3,3,-1]

On the system all amount are shown well 10000 => 10 000 with whitespace separator

On report, all of this doesn't work, and the reason is the bloc :

            while seps:
                sp = formatted.find(' ')
                if sp == -1: break
                formatted = formatted[:sp] + formatted[sp+1:]
                seps -= 1

this bloc, has no meaning, we separate the amount and this bloc come to remove separator, and the problem is that the varaible seps is given with the separator, this bloc has to be removed

File : res_lang Function : def format(.... Line : 214

[Cedric Le Brouster(OpenFire) (cedric-lebrouster)]

Hi Yug,

You should change your your separator for a non-breaking space (unicode 00A0).
It prevents number breaking in views and some reports, and protects you from this bug.

[Yug Faa (vim6574)]

Hi Cedric

Can you please explain more or give us an example, if we use u"\u0020" as separator, we need to add eval() in source code, so it's a bug,

Thanks

[Cedric Le Brouster(OpenFire) (cedric-lebrouster)]

I nerver said it's not a bug.
I only gave a way for you to make things work.
I had the same problem and I solved it this way :
- I open a python terminal (command in shell : python)
- I use command : print u'a\u00A0a'
(I use the 'a' chars as delimiters to "see" the space
- I copy/paste this text non-breaking space in the thousands separator field of my language, in openerp form.
Don't forget to remove the 'a' and the old previous whitespace.

There must be easier ways to do it, for example in SQL, but this is a quite easy one.

Of course you could also make or modify a module to make it for you.
For information, this thousands separator is read from your operating system language parameters. So the fact it's a whitespace instead of a non-breaking space is not a bug from openerp.

Nevertheless, I agree whitespaces should not be deleted on reports.

[Yug Faa (vim6574)]

Thank you so much, Cederic, that's work well