Re: [TurboGears] Re: FormEncode i18n translation integration in TurboGears
Gregor Horvath <gh-LfrpOBifzZo+ytmZ3SK/[email protected]>
| Newsgroups | gmane.comp.python.formencode,gmane.comp.web.turbogears |
|---|---|
| Organization | Ing. Gregor Horvath, Industrieberatung & Softwareentwicklung |
| Message-ID | <[email protected]> |
Jorge Godoy schrieb: > Ian Bicking <[email protected]> writes: > > >>I'm wondering how the releases should work. An update to a translation >>doesn't really warrant a new software release, and releases of >>FormEncode are otherwise going to be uncommon. Should the translations >>be shipped as separate packages (e.g., formencode.lang.de)? It's >>potentially a lot of packages, but that might be fine. They can be >>released and updated on their own schedule then. Does that sound feasible? > > > If there aren't that many changes to messages -- i.e., FormEncode's code > should change more than its messages --, then I don't see a reason for > separating things. ACK. At the moment I don't see any differences to normal Formencode development. I am a big believer in KISS. So I'd prefer to keep it simple. All is in trunk and released together. If this turns out to be inappropriate because language development is more dynamic than normal development than we can always change this. Backports of translations from trunk to a previous releases should not be a big problem for the users to make for themselfs, once the basic code is in the release. Maybe a good doc of this procedure is sufficient. -- Greg, Vienna ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV