Re: FormEncode and International Languages
Previously Jonathan Vanasco wrote: fair on some points, i disagree with others. i'm in the US. the formencode author seems to be as well. 'internationalization' on most things seems to be limited to swapping in text. There is internationalization and localization. You need to deal with both. many of the checks, such as PlainText allow for only a subset of ascii. Which subset would that be? Your example of é falls well outside of ASCII. anything else trips an error. short of making everything a unicode string (which I aready had done) - i'm specifically wondering how people are handling validating different form elements with these shortcomings. Without concrete examples of things that break there is little we can tell you. Wichert. -- Wichert Akkerman wich...@wiggy.netIt is simple to make things. http://www.wiggy.net/ It is hard to make things simple. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: FormEncode and International Languages
Previously Gustavo Narea wrote: On Monday January 26, 2009 23:20:37 Jonathan Vanasco wrote: Our project is dealing with a lot of French writers typing things like é , which fails many formencode tests. There is nothing special about the occasional accent in French: French is much simpler than, for example, Chinese. Use UnicodeString instead of String: http://www.formencode.org/class-formencode.validators.UnicodeString.html I don't think the problem will be present on other validators -- at least I guess so. OneOf can't deal with non-ascii values if I remember correctly. I have an open ticket in a project related to that. Wichert. -- Wichert Akkerman wich...@wiggy.netIt is simple to make things. http://www.wiggy.net/ It is hard to make things simple. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
FormEncode and International Languages
How are people dealing with FormEncode and International Languages? Our project is dealing with a lot of French writers typing things like é , which fails many formencode tests. This is more of an 'approach' issue: - how are you handling internationlization in Pylons from a business standpoint ? ie - what are you supporting and where ? - how are you handling this technologically ? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: FormEncode and International Languages
On Monday January 26, 2009 23:20:37 Jonathan Vanasco wrote: How are people dealing with FormEncode and International Languages? You write to an international mailing list talking about international languages. Then you assume English/Spanish/* means national language to us? Tell us where you're from so that we can know what languages are international to you. Better yet, stick to internationalization. Our project is dealing with a lot of French writers typing things like é , which fails many formencode tests. Use UnicodeString instead of String: http://www.formencode.org/class-formencode.validators.UnicodeString.html I don't think the problem will be present on other validators -- at least I guess so. This is more of an 'approach' issue: - how are you handling internationlization in Pylons from a business standpoint ? ie - what are you supporting and where ? In my case, I work for a non-profit and we try to support all possible languages. Translators are all volunteers. But anyway, I think the languages to be supported always depend your target audience. - how are you handling this technologically ? Given the context, I think you're looking for this: http://pylonsbook.com/alpha1/internationalization_and_localization HTH. -- Gustavo Narea http://gustavonarea.net/. Get rid of unethical constraints! Get freedomware: http://www.getgnulinux.org/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: FormEncode and International Languages
fair on some points, i disagree with others. i'm in the US. the formencode author seems to be as well. 'internationalization' on most things seems to be limited to swapping in text. many of the checks, such as PlainText allow for only a subset of ascii. anything else trips an error. short of making everything a unicode string (which I aready had done) - i'm specifically wondering how people are handling validating different form elements with these shortcomings. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
