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.
