tag:blogger.com,1999:blog-4345066302652424538.post7271892169571909573..comments2009-12-30T15:06:30.996+01:00Marc Garciahttp://www.blogger.com/profile/01286849404527531329noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-4345066302652424538.post-11087883817119238952009-12-30T15:06:30.996+01:002009-12-30T15:06:30.996+01:00Great ! I particularly love this snippet I saw in your slides : <br />{{my_date|date:&quot;SHORT_DATE_FORMAT }}<br /><br />It will fly directly into my code. <br /><br />Thank you for your work.Martin De Wulfhttp://multitasked.netnoreply@blogger.comtag:blogger.com,1999:blog-4345066302652424538.post-83642825512099598222009-12-29T14:50:55.311+01:002009-12-29T14:50:55.311+01:00Great to see this changes in trunk. I am tested the new feature and there are still a few problems I ran into the last days:<br /><br />http://code.djangoproject.com/ticket/12443<br />http://code.djangoproject.com/ticket/12444Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4345066302652424538.post-24961084628082064252009-12-28T22:56:39.604+01:002009-12-28T22:56:39.604+01:00Great! <br /><br />It really is a great feature for using Django internationally.<br /><br />I&#39;ve been hatchy-patching solutions for dates for years and now there is one definite solution, for comma-separated floats as well. Thanks!<br /><br />Wim Feijen<br />Go2PeopleWim Feijenhttp://www.blogger.com/profile/13178808432970957892noreply@blogger.comtag:blogger.com,1999:blog-4345066302652424538.post-39720983880983854242009-12-24T17:24:55.774+01:002009-12-24T17:24:55.774+01:00Great work! Thanks for the contribution. Internationalization support is one of less discussed but killer features of Django.Kevinhttp://blog.montylounge.comnoreply@blogger.comtag:blogger.com,1999:blog-4345066302652424538.post-27529467502777892992009-12-24T01:25:41.002+01:002009-12-24T01:25:41.002+01:00i18n is unfortunately something that has to be implemented in every environment separately, but IMO L10n should be outsourced as soon and early as possible. There are a lot of FOSS translation communities out there. &quot;Growing&quot; your own is a lot of work, and maintaining a localisation environment should not be every FOSS project&#39;s business; it takes valuable developer time away from developing the core product further.<br /><br />You&#39;ve already done the work now, and I do hope it will be a success. Don&#39;t get me wrong: any localisation is better than no localisation at all, but as an open source community as a whole, we should be able to do better...<br /><br />(I&#39;m from translatewiki.net)siebrandhttp://siebrand.myopenid.com/noreply@blogger.comtag:blogger.com,1999:blog-4345066302652424538.post-66616245202657060602009-12-23T00:45:09.355+01:002009-12-23T00:45:09.355+01:00Great work! Django was really lacking in the localization department.Fidelhttp://www.blogger.com/profile/04446782431744434521noreply@blogger.comtag:blogger.com,1999:blog-4345066302652424538.post-20530154328549233262009-12-23T00:18:21.424+01:002009-12-23T00:18:21.424+01:00Nice work Marc and Jannis!Anonymousnoreply@blogger.com