On further reflection, there is a huge internationalization issue here. The hyphenation rules and data driven exceptions are English specific. Some will work (minimally) for other languages, but are not good enough. Proper integration will be required, and language developers will need to have more knowledge about this corner domain. Due to my NDA/NC I cannot work on that part of it, but I do have a patch almost ready for django.utils.text.wordwrap to take an optional boolean argument to do word hyphenation.
Thankfully it is data driven and getting the data from the .po should not be too difficult. The problem will be getting the initial data. On Jul 9, 10:30 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Ned just posted the code for the tabblo hyphenate filter in the public > domain. This should be added as a builtin django filter with proper > attribution. I don't think wordwrap should use it by default, and > optional arguments don't work. I was thinking of just calling it > 'hyphenate' or 'hyphenatedwordwrap'. > > http://www.nedbatchelder.com/code/modules/hyphenate.html > > Thoughts? --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
