Re: i18n of Django admin message "was changed successfully"

It is probably safe to uppercase first letter. There are writing systems where there is no distinction between upper and lower case (e.g., Georgian). For such writing systems uppercasing is essentially a noop. Just tried that in python shell: >>> v = u"ქართული" >>> v.upper() == v True Not sure is

Re: i18n of Django admin message "was changed successfully"

Ok, I filed a bug and patch [1], 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 th

Re: i18n of Django admin message "was changed successfully"

I believe you should file a bug report. Cheers On Sat, Oct 1, 2011 at 7:09 PM, Erik Wognsen 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 wrote: > >> > Accord

Re: i18n of Django admin message "was changed successfully"

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 wrote: > > According to gettext manual[1] one can use \u to uppercase the next char. > >> > But I have no idea whether "\u%(nam

Re: i18n of Django admin message "was changed successfully"

> 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

Re: i18n of Django admin message "was changed successfully"

On Thu, Sep 29, 2011 at 2:46 PM, Sergiy Kuzmenko 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

Re: i18n of Django admin message "was changed successfully"

On Thu, Sep 29, 2011 at 19:46, Sergiy Kuzmenko 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. "\u" in my po-file gives me "invalid control sequence" when I compilemessages, whether "\u" is followed by "%(name)s

Re: i18n of Django admin message "was changed successfully"

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 On Thu, Sep 29, 2011 at 9:

Re: i18n of Django admin message "was changed successfully"

Yes, I have seen some of the languages use tricks like "object of type" and slashes for gender ("%(name)s \"%(obj)s\" modificato/a correttamente.") But many times the indefinite noun will do as well ('employee "Xyz" was changed...') , so maybe we can get the capitalization right? ('Employee "Xyz"

Re: i18n of Django admin message "was changed successfully"

In general noun interpolation is a non trivial task. It might be possible that for a limited subset of messages (addition, deletion and modification) there is a common denominator for an "alternative" verbose model name that will do the trick in all languages. But it might not be so. Different lang

i18n of Django admin message "was changed successfully"

Hi, django/contrib/admin/options.py contains the message 'The %(name)s "%(obj)s" was changed successfully.' and similar for "added" and "deleted" and some others. This works well in languages that only use an article for definiteness. But what about other languages? For example, in Danish "emplo