2014-12-30 14:39 GMT+01:00 Cédric Krier <cedric.kr...@b2ck.com>: > On 30 Dec 13:58, Jean C wrote: > > 2014-12-30 13:00 GMT+01:00 Vincent Bastos <vinc...@lavalab.com.au>: > > > > > I am not saying that they are correct, but I curious to hear people's > > > thoughts around this topic. > > > > > > Names are tough : > > > http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ > > I even think we should remove the required on the name of Party. > We have code for this case. > > > That said, we had the same requirements from our (french speaking) > clients. > > We dealt with it by adding a first_name field, using the name field for > the > > last name, and overriding get_rec_name to display both if needed. > > The best solution is to convince your customer that their requirements > are wrong. >
If you want to integrate Tryton with some official system, for example, you must to manage the names correctly. It is; know each part of name (in Spain, for example, first name, first last name and second last name) A possible generic solution will be to use a list of type of name (maybe > a Dict field) that could be used to autofill the real name with maybe > some sort of formatting depending on some context like the language, the > primary country etc. > It sounds good. It could be something similar to Gmail contacts (but not limited to the 5 fields that there are in Gmail). -- Guillem Barba http://www.guillem.alcarrer.net
