Hi, >I'm found while writing current application that this pattern is very >common (almost a 2/3 of my models are using some type of localized >name/description fields) and it will be great that i18n/model >framework supports that without any additional code.
I agree that this is a rather common pattern - but I don't think it's something that the i18n branch should solve, but something that could go into another patch. The reason being that "metamodels" like that are things where not everybody will agree on - it might be that some want to do it just by adding additional attributes to their model while others might want to normalize it out into a dependend table and stuff like that. So I'd opt to leave that stuff out of the i18n branch for now and to concentrate on the "translations for string constants" part and some other branch or patch can introduce the "multilinguality of models" patterns later. That way it's easier for Jacob and Adrian to see what the patch actually will do and to decide wether they need some changes before merging it into trunk. Oh, and I think I would quite like I18NCharField or I18NTextField - with automatic creation of the dependend table and a way in the admin to select what language content to edit. But that's just me. And maybe it should wait for the new_admin branch of rjwittams, as his stuff might make the extension of the admin to incorporate those I18N*Fields easier. bye, Georg
