sorry I dont understand.
I've change the language to en_GB but when I use the invoice report it bugs.
What should i change in the administration->translation?
In this menu we can only set text, and we want to use the format dd/mm/yy for date .

thanks for your help

Select Administration -> Translation -> Languages from the menu
Select the language you would like to change and then put the values you need in the date format like %d/%m/%Y

Ok I got It.

tks

I've created a new language called English_GB, with code en_GB, and set the date format to %d/%m/%Y (I didn't realise at first that there was a "Form" screen for this, because when I double-clicked on the name in the list, it didn't take me to the Form view - I had to click on the 'Form' button in the GTK client.

Then I set that "English_GB" as the language for my user account, but it only seems to have half worked.

EDIT - Sorry, I just sorted out my own problem, but will record it here for others.

I had set the language on my user account, but didn't close the GTK client. What happened was that the date format changed in some places and not others - grids used the new format, but entry screens did not. When I closed and restarted the GTK client, it works correctly, even the Invoice Date on the Invoice report is formatted correctly.

Using version 5.0.5, windows-all-one.

I'm not sure if I'm right about this, but my assumption is: Hard-coded into orm.py, OpenObject assumes the language of all translatable fields are by default en_US. If the user's language is en_US, no translation is done, and the field in the object's table is used, rather than looking up ir_translations.

When I did what I said in my previous post, the dates formatted correctly, but then I realised whenever I changed a translatable field, instead of changing the object's data, openERP was creating a translation in ir_translation table.

This is because the user had a different language to en_US. Now, this wouldn't be a problem, if there weren't various places where this translation system doesn't actually work (the tax summary on the invoice screen, for example)

So, what I did to workaround this - I did a find/replace of all "en_US" in the orm.py file to "en_AU". I created a new language called "English_Australia" with code "en_AU". I assigned this language to all users. (I also emptied the ir_translations table in the db after manually updating the fields of the objects themselves)

Now, my dates format as DMY, and I don't get unwanted "translations" when I change a field. I just hope this doesn't cause other problems elsewhere - I hate changing the source code like this.

If anyone can spot any problems, I'd be glad to know.