Re: [TurboGears] Re: FormEncode i18n translation integration in TurboGears

Ian Bicking <[email protected]>
Newsgroups gmane.comp.python.formencode,gmane.comp.web.turbogears
Message-ID <[email protected]>
Gregor Horvath wrote:
> 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.

I don't expect this to be the case.  FormEncode's code is not updated 
much, and releases are not frequent.  I don't want to change that.  You 
shouldn't want that either -- a nice stable and boring FormEncode means 
one less thing you have to worry about tracking.

So I feel pretty confident that translations will substantially increase 
the number of FormEncode releases.  Of course, if the code isn't 
changing then getting an updated FormEncode isn't really a problem 
either I suppose.  Only if people didn't want to upgrade FormEncode 
would this be a problem, and that shouldn't be a problem if I don't make 
backward-incompatible changes in FormEncode (and no such changes are 
planned).

> 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.

I do expect it to be, but maybe that's not a problem.  OTOH, making a 
release of a subpackage doesn't need to be hard either, just "python 
setup.py svntag --version=whatever-next --next-version=whatever-next+1; 
cd ../formencode.lang.de-whatever-next; python setup.py register sdist 
bdist_egg upload".

-- 
Ian Bicking | [email protected] | http://blog.ianbicking.org

-------------------------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.