Ok, I filed a bug and patch [1]<https://code.djangoproject.com/ticket/16973>, but it turned out there was already a ticket on this topic [2], which has a simpler patch that simply capitalizes the first letter of every message to the user. The things that needs to be answered by this list is:
Is this acceptable to do this for all languages and writing systems? Also, is it ok to do it for all messages, even in English? Is there a reason to start a message with lowercase? I think it's a bit intrusive to capitalize all messages. /Erik [1] https://code.djangoproject.com/ticket/16973 [2] https://code.djangoproject.com/ticket/16350 On Sun, Oct 2, 2011 at 01:23, Sergiy Kuzmenko <s.kuzme...@gmail.com> wrote: > I believe you should file a bug report. > Cheers > > > On Sat, Oct 1, 2011 at 7:09 PM, Erik Wognsen <r4m...@gmail.com> wrote: > >> Ok. Does the i18n group have the possibility of deciding and committing >> this or should it go through a regular bug report? >> >> On Sun, Oct 2, 2011 at 01:00, Sergiy Kuzmenko <s.kuzme...@gmail.com>wrote: >> >>> > According to gettext manual[1] one can use \u to uppercase the next >>> char. >>> >>>> > But I have no idea whether "\u%(name)s" works. If it does not, a small >>>> patch >>>> > for Django admin to fix this would be nice. >>>> > [1] >>>> http://www.gnu.org/software/gettext/manual/gettext.html#Interpolation-I >>>> >>>> That section of the documentation is Perl-specific AFAICT. >>>> >>> >>> Yes I goofed here. Now that I think again about the question, there is >>> nothing gettext can do about uppercasing. It simply returns a translated >>> string and variable interpolation happens in Python code. >>> >>> If the translation must start with the interpolated word the only way to >>> address it would be upper case the first character in Python code before >>> outputting the message. >>> >>> SK >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Django internationalization and localization" group. >>> To post to this group, send email to django-i18n@googlegroups.com. >>> To unsubscribe from this group, send email to >>> django-i18n+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/django-i18n?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django internationalization and localization" group. >> To post to this group, send email to django-i18n@googlegroups.com. >> To unsubscribe from this group, send email to >> django-i18n+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/django-i18n?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Django internationalization and localization" group. > To post to this group, send email to django-i18n@googlegroups.com. > To unsubscribe from this group, send email to > django-i18n+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-i18n?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django internationalization and localization" group. To post to this group, send email to django-i18n@googlegroups.com. To unsubscribe from this group, send email to django-i18n+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-i18n?hl=en.
