Full localization
I am working in the localization. It is in developing but I need some help, by now I would comments. Please read the next thread: http://groups.google.com/group/django-ecommerce/browse_thread/thread/ed90b6f909964621/0a04618cec26ad21 I started to show the correct addresses of every country in Satchmo but I'll make a full localization. Now, Django has two field types for USA, USStateField, PhoneNumberField. But we could have validators for phones of each country, a drop list as USStateField for another countries where it is necessary as Canada, Mexico, Italy, and validators for postal/zip code. With those validators, that becomes less errors and therefore more productivity. Once it is finished, it would be the first framework with this capacity. We can have a better system for localization than any other web framework. Why to follow to others when we can follow our own way. Let us cause that other they follow to us. Greetings! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Support for Native XML Database (NXD)
http://www.xml.com/pub/a/2001/10/24/follow-yr-nose.html?page=2 "Relational databases are particularly good for storing highly structured information, and not particularly good at managing semi-structured data. Semi-structured data is data that has some structure, but is not rigidly structured. An example of semi-structured data is a health record. For example, one patient might have a list of vaccinations, another might have height and weight, another might have a list of operations they have had. Other examples of semi-structured data are legal documents and genealogical records... Semi-structured data is difficult to store in a relational database because it means you either have many different tables (which means many joins and slow retrieval time) or a single table with many null columns. Semi-structured data is very easy to store as XML and is a good fit for a native XML database." I think that would be a big step if we could implement a NXD in Django, but I don't speak of substitute a RDBMS by NXD else of using NXD when it was really necessary. http://www.xml.com/pub/a/2001/10/31/nativexmldb.html Some potential application areas include * Corporate information portals * Catalog data * Manufacturing parts databases * Medical information storage * Document management systems * B2B transaction logs * Personalization databases and of course for the mail addresses. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Support for Native XML Database (NXD)
http://www.xml.com/pub/a/2001/10/24/follow-yr-nose.html?page=2 "Relational databases are particularly good for storing highly structured information, and not particularly good at managing semi-structured data. Semi-structured data is data that has some structure, but is not rigidly structured. An example of semi-structured data is a health record. For example, one patient might have a list of vaccinations, another might have height and weight, another might have a list of operations they have had. Other examples of semi-structured data are legal documents and genealogical records... Semi-structured data is difficult to store in a relational database because it means you either have many different tables (which means many joins and slow retrieval time) or a single table with many null columns. Semi-structured data is very easy to store as XML and is a good fit for a native XML database." I think that would be a big step if we could implement a NXD in Django, but I don't speak of substitute a RDBMS by NXD else of using NXD when it was really necessary. http://www.xml.com/pub/a/2001/10/31/nativexmldb.html Some potential application areas include * Corporate information portals * Catalog data * Manufacturing parts databases * Medical information storage * Document management systems * B2B transaction logs * Personalization databases and of course for the mail addresses. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Support for Native XML Database (NXD)
[EMAIL PROTECTED] wrote: > I can't see any reason why you cant use an object database in Django, > its just that the admin interface to it won't work like the current > admin interface. As you can read in the down link I am trying to implementig the free specifications of OASIS (xNAL, xPIL). They are a set of XML specifications for defining and managing Customer (also called "Party") information/profile (including customer/party relationships) that are truly open, vendor neutral, application independent and importantly "Global". Including the capability of handling about 36+ customer name formats and addresses of 241+ countries with about 130+ Address formats and represented in 5,000+ languages. http://groups.google.com/group/django-ecommerce/browse_thread/thread/cdf513c26cc78f7e --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Support for Native XML Database (NXD)
[EMAIL PROTECTED] wrote: > GinTon wrote: > > > I think that would be a big step if we could implement a NXD in Django, > > but I don't speak of substitute a RDBMS by NXD else of using NXD when > > it was really necessary. > > I think you'd first have to go 'up' a layer, and define an API onto > semi-structured data, and then you could plug in some other database > system. For example Zope's ZODB, or an NXD storing as XML. In fact if > you use ZODB in Django you could also use Zope Page Templates and > then No, I wont go there. > ZODB is a powerful OO-db that allows you to store objects without the need for any schema definition whatsoever. What do you think about Durus (the interface is simpler) and Schevo? http://www.mems-exchange.org/software/durus/ http://schevo.org/trac/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Support for Native XML Database (NXD)
My conclusion is that for storing XML data would be usefull ut using a ODBMS based on the ODMG 3.0 specification that incorporates advances in object database technology (e.g., replication), data management (e.g., spatial indexing), and data formats (e.g., XML) and to include new features into these standards that support domains where object databases are being adopted (e.g., real-time systems). http://en.wikipedia.org/wiki/Object_database Althought there is only one free ODBMS, ozone, that provides a ODMG 3.0 interface but it has been built in java http://www.ozone-db.org/frames/home/what.html --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
RDBMS vs ODBMS
I have seen that for web applications is best far using a ODBMS: 1- Objects in an OODBMS can store an arbitrary number of atomic types as well as other objects. The fact that an OODBMS is better suited to handling complex,interrelated data than an RDBMS means that an OODBMS can outperform an RDBMS by ten to a thousand times depending on the complexity of the data being handled. 2- Data in the real world is usually has hierarchical characteristics. The ever popular Employee example used in most RDBMS texts is easier to describe in an OODBMS than in an RDBMS. 3- A query language is not necessary for accessing data from an OODBMS unlike an RDBMS since interaction with the database is done by transparently accessing objects. It is still possible to use queries in an OODBMS however. 4- In a typical application that uses an object oriented programming language and an RDBMS, a signifcant amount of time is usually spent mapping tables to objects and back. This "impedance mismatch" is completely avoided when using an OODBMS. 5- The user of an RDBMS has to worry about uniquely identifying tuples by their values and making sure that no two tuples have the same primary key values to avoid error conditions. 6- With an RDBMS it is not possible to model the dynamic operations or rules that change the state of the data in the system because this is beyond the scope of the database. With an OODBMS there is no disconnect between the database model and the application model because the entities are just other objects in the system. http://www.kuro5hin.org/?op=displaystory;sid=2001/5/3/32853/11281 http://www.odbms.org/introduction_whenODBMS.html http://en.wikipedia.org/wiki/Object_database --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: RDBMS vs ODBMS
Ian Holsman wrote: > yes.. > what exactly are you proposing here? > > with a OODBMS you shouldn't need any of the ORM functionality.. you > should be able to just use the other sections without > much worry i would suspect. > I wanted to know your opinions. Since of my view point I think that the web frameworks with ODBMS will be the next big step. The problem is that today it is not a true option since that it only exists a free ODBMS based on the ODMG 3.0 specification, ozone, that has been built in java. http://en.wikipedia.org/wiki/Object_database http://www.ozone-db.org/frames/home/what.html As it is said in 4 point, It's true that using a ODBMS would not be necessary the ORM functionality, another more advantage. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
About licenses
When I began to create several tables of data for the globalization I wanted to use a license of CC because GPL or BSD are more specific of software. I repeat, a license for data. http://satchmo.python-hosting.com/browser/trunk/satchmo/G11n/data/ http://creativecommons.org/licenses/by-sa/2.5/ After of a little discussing here http://groups.google.com/group/django-ecommerce/browse_thread/thread/ed90b6f909964621/087cb9f3da54c60c it did not matter to me to use the New BSD license, although I would prefer to use the following one of CC who is compatible with BSD and not viric (it's different of avobe) http://creativecommons.org/licenses/by/2.5/ But David Pratt demands in the next message the exclusive use of the BDS license http://groups.google.com/group/django-ecommerce/tree/browse_frm/thread/ed90b6f909964621/768c2c4fc956dd2e?rnum=31&_done=%2Fgroup%2Fdjango-ecommerce%2Fbrowse_frm%2Fthread%2Fed90b6f909964621%3Ftvc%3D1%26#doc_d39bacb4bcd0093a and my surprise has been great when I have seen that to the projects of google that license is not demanded to them althought it is advised http://code.google.com/soc/django/about.html Then: 1) Has more preference the contributors of Google summer code that the one independents? 2) Is possible use licenses compatibles con BSD as MIT or CC-by? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
About licenses
When I began to create several tables of data for the globalization I wanted to use a license of CC because GPL or BSD are more specific of software. I repeat, a license for data. http://satchmo.python-hosting.com/browser/trunk/satchmo/G11n/data/ http://creativecommons.org/licenses/by-sa/2.5/ After of a little discussing here http://groups.google.com/group/django-ecommerce/browse_thread/thread/ed90b6f909964621/087cb9f3da54c60c it did not matter to me to use the New BSD license, although I would prefer to use the following one of CC who is compatible with BSD and not viric (it's different of avobe) http://creativecommons.org/licenses/by/2.5/ But David Pratt demands in the next message the exclusive use of the BDS license http://groups.google.com/group/django-ecommerce/tree/browse_frm/thread/ed90b6f909964621/768c2c4fc956dd2e?rnum=31&_done=%2Fgroup%2Fdjango-ecommerce%2Fbrowse_frm%2Fthread%2Fed90b6f909964621%3Ftvc%3D1%26#doc_d39bacb4bcd0093a and my surprise has been great when I have seen that to the projects of google that license is not demanded to them althought it is advised http://code.google.com/soc/django/about.html Then: 1) Has more preference the contributors of Google summer code that the one independents? 2) Is possible use licenses compatibles con BSD as MIT or CC-by? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
About licenses
When I began to create several tables of data for the globalization I wanted to use a license of CC because GPL or BSD are more specific of software. I repeat, a license for data. http://satchmo.python-hosting.com/browser/trunk/satchmo/G11n/data/ http://creativecommons.org/licenses/by-sa/2.5/ After of a little discussing here http://groups.google.com/group/django-ecommerce/browse_thread/thread/ed90b6f909964621/087cb9f3da54c60c it did not matter to me to use the New BSD license, although I would prefer to use the following one of CC who is compatible with BSD and not viric (it's different of avobe) http://creativecommons.org/licenses/by/2.5/ But David Pratt demands in the next message the exclusive use of the BDS license http://groups.google.com/group/django-ecommerce/tree/browse_frm/thread/ed90b6f909964621/768c2c4fc956dd2e?rnum=31&_done=%2Fgroup%2Fdjango-ecommerce%2Fbrowse_frm%2Fthread%2Fed90b6f909964621%3Ftvc%3D1%26#doc_d39bacb4bcd0093a and my surprise has been great when I have seen that to the projects of google that license is not demanded to them althought it is advised http://code.google.com/soc/django/about.html Then: 1) Has more preference the contributors of Google summer code that the one independents? 2) Is possible use licenses compatibles con BSD as MIT or CC-by? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: About licenses
Sorry this message was sent 3 times by a google error. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: About licenses
Ian Holsman wrote: > the only 'viral' in my reading is '4b > as long as chris (the owner of the ecommerce code) is happy with the > type of CC license you put in there it should be fine. > The '4b' section simply leaves the author attribution very clear http://creativecommons.org/licenses/by/2.5/legalcode "Attribution. You must attribute the work in the manner specified by the author or licensor." It would be the same that in your BSD license: http://code.djangoproject.com/browser/django/trunk/LICENSE "Copyright (c) 2005, the Lawrence Journal-World All rights reserved. Redistributions of source code must retain the above copyright notice,..." --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: RDBMS vs ODBMS
Zopdb is not based on the ODMG 3 specification but I have found a free ODBMS based on the ODMG 3 specification althought it only has programming interfaces for C++ and Java, but we would ask to authors an interface for python. http://www.eyedb.org/ It is very powerful, mature, safe, stable. I was made a vey well impression with its characteristics: http://doc.eyedb.org/manual/html/Overview/index.html It was developed in 1992 for the Genome View project, rewritten in 1994 , and has been used in a lot of bioinformatics projects http://www.eyedb.org/history.php If you want to know more about ODMS here you hace some interesting links: http://www.dacs.dtic.mil/techs/oodbms2/oodbms-toc.shtml http://archive.devx.com/dbzone/articles/sf0801/sf0801-1.asp --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: RDBMS vs ODBMS
Ian Holsman wrote: > On 08/09/2006, at 8:03 PM, GinTon wrote: > > > > > Zopdb is not based on the ODMG 3 specification but I have found a free > > ODBMS based on the ODMG 3 specification althought it only has > > programming interfaces for C++ and Java, but we would ask to > > authors an > > interface for python. > > http://www.eyedb.org/ > > > > I believe eyedb can do python via SWIG. > it's one of those things I keep meaning to learn when I get some > spare time. > It would be great because somebody could work into a Django trunk for the implementation of this ODBMS, is there any volunteer? Anyway I contacted with eyedb.org in order to know its opinion about a Python interface and the XML support. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: RDBMS vs ODBMS
[EMAIL PROTECTED] wrote: > If it has C++ bindings then maybe SIP could help - > http://www.riverbankcomputing.co.uk/sip/ > > PyQT4 bindings made with SIP are realy nice :) These are the conclusions of several Python wrappers that shows that SIP generates the fastest wrappers: * Manual wrapping is still fastest and most versatile * SIP, Boost and Babel generate native extension modules with low overhead * SWIG-generated modules rely on pure Python wrapper module and introduce a large overhead * Wrapper tool highlights: - SIP generates the fastest wrappers - SWIG is mature and well documented - Boost.Python most elegant integration of C++ and Python - Babel supports languages as both target and source http://people.web.psi.ch/geus/talks/europython2004_geus.pdf --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: RDBMS vs ODBMS
GinTon wrote: > Anyway I contacted with eyedb.org in order to know its opinion about a > Python interface and the XML support. I received the following answer of Eric Viara, EyeDB.org: "We planned to introduce soon a plugin mechanism to facilitate the way to write language bindings such as PHP5, Python, PERL and so on. But we do not know yet if the Python binding will be written by the core staff. We do not plan to support XML in the few months. But as eyedb is an open source project, we expect that somebody else will write supports for XML." In any case I advised to him that the creation of a Google group would be positive to obtain a community interested in that project. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Data for globalization
I have been working in creating tables in format CSV for the globalization (G11n), so that they can be used in any project where it could be necessary or useful. You can see the tables on: http://satchmo.python-hosting.com/browser/trunk/satchmo/G11n/data/ And here you have the files for add/integrate them to any Django project: http://satchmo.python-hosting.com/file/trunk/satchmo/G11n/ http://satchmo.python-hosting.com/file/trunk/satchmo/load_G11n.py Some cool things that can be done with all those data: * area.csv, phone.csv Now, Django has two field types for USA, USStateField and PhoneNumberField. But we could have validators for phones of each country. And a drop list as USStateField for another countries where it is necessary for the potstal address as Canada, Mexico, Italy, etc. * country-language.csv, timezone.csv Now, there is to edit the 'settings.py' file to choosing both the language code and local time zone for the installation. But the administrator has to go to a web for looking those data, and then edit that file. It's clear that it would be more easy and cool if the administrator could to choosing both data from Django admin, with the help of those tables. In addition, we could use timezone.csv to show to the users its local time according to its configuration. In the users registry it must have an option so that the user could choose his/her time zone. With country-language.csv, we also could to know directly the language and country of the user (using the HTTP header). * country.csv, language.csv With those tables we could show to the user a drop list fot that could choosing those data. In addition with country.csv we can show the correct name for each country about the area. The area is the primary subdivision of a country called state in USA, or province in Canada. But the best interesting is that instead of have a drop list with all countries _it's very heavy that a user is looking for a country into a list of 230+ countries_, we could to have a drop list with the geographical region. In the first a drop list with continents (America), then with its subdivisions (Caribbean, Central America, South America, Northern America), and finally the countries of that subdivision. There will be another table about postal codes. And I have compiled all flags images (SVG format) of all countries that are in globalization files. Now I would that Django developers could to integrate these tables with django, because without a doubt it has many advantages to both the administrators and the users. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Data for globalization
I see that it isn't interesting for django developers so "I go away with the music to another part". In the first I prefer to work with another community where there is more support. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Data for globalization
Thanks Russ for your message. I became angry because I have been working very hard during 2 or 3 months. I hoped that somebody said some idea for its possible implementation Using those data we could have fields as USStateField and PhoneNumberField for all countries (and validators). But I don't see a solution very clean. Any idea? For the others tables (countries, languages, time zones), I believe that it would be cool if it were used from an AJAX widget. What do you think? I only want ideas to begin to look for the best solution and to begin with the implementation. And better if it's a solution that can be used for any project in general. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Data for globalization
Jeremy Dunck wrote: > On 10/15/06, GinTon <[EMAIL PROTECTED]> wrote: > > And here you have the files for add/integrate them to any Django > > project: > > http://satchmo.python-hosting.com/file/trunk/satchmo/G11n/ > > http://satchmo.python-hosting.com/file/trunk/satchmo/load_G11n.py > > It may be too much work, or you may not be interested, but consider > adding these to your language table: > > MARC > http://www.loc.gov/marc/languages/langascii.html > > IANA > http://www.iana.org/assignments/language-subtag-registry > > MARC is a standard for bibliographic records, and that IANA registry > is the internet code. (I think 630-2 and 3066 may have a strong > overlap. Those data are included in http://satchmo.python-hosting.com/file/trunk/satchmo/G11n/data/language.csv and I used http://www.loc.gov/standards/iso639-2/ I added only the official languages of countries although I've to add some more that have only the 2 letter iso code. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Data for globalization
Todd O'Bryan wrote: > I've actually been thinking about this, recently. How would people feel > about a Field type that took a regex to validate input against. > > Or, to be even more wacky, how about providing callables that would > validate the input and normalize it? Something like > > def __init__(self, validator=lambda x: true, normalizer=lambda x: x): > > So, by default, it doesn't validate or normalize, but you can provide a > function for each. > > Or am I being overly complicated? Thanks Todd. I believe that is a good starting point. I've been busy with the configuration of the web and SVN to put the project in an independent site. I hope that tomorrow or the friday is ready. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Data for globalization
USStatefield. This field is used to validating the U.S. states (areas). http://code.djangoproject.com/browser/django/trunk/django/db/models/fields/__init__.py#L778 http://code.djangoproject.com/browser/django/trunk/django/forms/__init__.py#L941 http://code.djangoproject.com/browser/django/trunk/django/core/validators.py#L238 It would be better if the user could choose it from a drop list. In addition there would not necessary the validating. And we couldshow a drop list for all countries where it is necessary for the potstal address _all countries that are in area.csv_. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Data for globalization
I've moved all files about globalization to http://svn.webda.python-hosting.com/trunk/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Data for globalization
I've created a new group for integrating G11n data in Django and Turbogears: http://groups.google.com/group/webda Please I need ideas to get the best possible integration. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Data for globalization
Please, post your message in this group http://groups.google.com/group/webda I would to have all discussion related to globalization data in the same group. So it could be usefull for that anothers frameworks could implementing those data too. Thanks! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Integration of globalization data in Django/TurboGears
I have created several tables in CSV format with globalization data (G11n). There are tables for countries, areas, languages, countries & languages, time zones, phones. And they are licensed under a Creative Commons license. http://svn.webda.python-hosting.com/trunk/G11n_data/ I created a new discussion group in order to facilitate the integration of G11n data in any framework. It's focused on integrate it on Django and TurboGears, but it could be integrated in whatever application with the help of the discussions on this group. It's necessary to discuss several subjects before beginning with the integration in the web frameworks. So I ask your collaboration. Thanks! http://groups.google.com/group/webda P.S.: I hope that you don't see this post as SPAM. This is something very interesting for administrators and users of those web frameworks. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Integration of globalization data in Django/TurboGears
The project web is activated http://webda.python-hosting.com/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Data for globalization
I have been working in creating tables in format CSV for the globalization (G11n), so that they can be used in any project where it could be necessary or useful. You can see the tables on: http://satchmo.python-hosting.com/browser/trunk/satchmo/G11n/data/ And here you have the files for add/integrate them to any Django project: http://satchmo.python-hosting.com/file/trunk/satchmo/G11n/ http://satchmo.python-hosting.com/file/trunk/satchmo/load_G11n.py Some cool things that can be done with all those data: * area.csv, phone.csv Now, Django has two field types for USA, USStateField and PhoneNumberField. But we could have validators for phones of each country. And a drop list as USStateField for another countries where it is necessary for the potstal address as Canada, Mexico, Italy, etc. * country-language.csv, timezone.csv Now, there is to edit the 'settings.py' file to choosing both the language code and local time zone for the installation. But the administrator has to go to a web for lookiing those data, and then edit that file. It's clear that it would be more easy and cool if the administrator could to choosing both data from Django admin, with the help of those tables. In addition, we could use timezone.csv to show to the users its local time according to its configuration. In the users registry it must have an option so that the user could choose his/her time zone. With country-language.csv, we also could to know directly the language and country of the user (using the HTTP header). * country.csv, language.csv With those tables we could show to the user a drop list fot that could choosing those data. In addition with country.csv we can show the correct name for each country about the area. The area is the primary subdivision of a country called state in USA, or province in Canada. But the best interesting is that instead of have a drop list with all countries _it's very heavy that a user is looking for a country into a list of 230+ countries_, we could to have a drop list with the geographical region. In the first a drop list with continents (America), then with its subdivisions (Caribbean, Central America, South America, Northern America), and finally the countries of that subdivision. There will be another table about postal codes. And I have compiled all flags images (SVG format) of all countries that are in globalization files. Now I would that Django developers could to integrate these tables with django, because without a doubt it has many advantages to both the administrators and the users. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Data for globalization
I also developed the Django models for those data: http://webda.python-hosting.com/browser/trunk/Django/I18n Please, post your message in this group http://groups.google.com/group/webda I would to have all discussion related to globalization data in the same group. So it could be usefull for that anothers frameworks could implementing those data too. Thanks! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Data for globalization
James Bennett wrote: > If you'd be interested in helping to develop useful models for that > using this data, that'd be great :) James, I also developed the Django model and a loader. http://webda.python-hosting.com/browser/trunk/Django/I18n But now it's necessary that Django developers help with the integration. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
