On Fri, Sep 24, 2010 at 12:38:30PM -0700, David Ellement wrote:
On 2010-09-24, Nicolas Williams wrote
On Fri, Sep 24, 2010 at 09:30:27AM -0700, Michael Elkins wrote:
> On Fri, Sep 24, 2010 at 10:06:00AM +0200, Matthias Apitz wrote:
> >#: commands.c:513
> >#, fuzzy
> >msgid ""
> >"Sort (d)ate/(f)rm/(r)ecv/(s)ubj/t(o)/(t)hread/(u)nsort/si(z)e/s(c)ore/s(p)"
> >"am?: "
> >msgstr ""
> >"Órden fech(a)/d(e)/(r)ecep/a(s)unto/(p)ara/(h)ilo/(n)ada/ta(m)año/punta(j)e:
"
>
> The problem seems to be that gettext() ignores the translation when
> the 'fuzzy' keyword appears. That attribution gets added when the
> gettext tools detect that the input string has been altered, and
> thus is no longer sure that the translated string is correct.
The above translation is not incorrect, except, maybe, for ...
Does it matter that the English string offers 10 options, while the
Spanish string only offers 9 options?
Yes, it does matter. The actual code is this:
switch (mutt_multi_choice (reverse ?
_("Rev-Sort
(d)ate/(f)rm/(r)ecv/(s)ubj/t(o)/(t)hread/(u)nsort/si(z)e/s(c)ore/s(p)am?: ") :
_("Sort
(d)ate/(f)rm/(r)ecv/(s)ubj/t(o)/(t)hread/(u)nsort/si(z)e/s(c)ore/s(p)am?: "),
_("dfrsotuzcp")))
Note the final string. These are the keys that actually accepted.
mutt_multi_choice() returns an integer offset into that string to note which
item the user selected. The order can not be changed.
me
