Hi mutt-dev, On Mon, Apr 20, 2020 at 11:03 AM Kevin J. McCarthy <ke...@8t8.us> wrote: > > On Mon, Apr 20, 2020 at 03:47:51AM +0200, Vincent Lefevre wrote: > >I have noticed a lack of consistency in message strings: > > * "GPG key" vs "gpg key" (this should be "GPG key") > > * "compose session" vs "editing session" > > > >Moreover, I think that "autocrypt" should be written with a capital > >letter (Autocrypt) like on the official website <https://autocrypt.org/>. > > Hi Vincent and welcome back! > > Corrections are welcome, but let's wait on translation string changes > until after the release. I've already received five of the translators' > updates for 1.14.
I'm working on ja.po with Japanese users. And I know Mutt has a few more inconsistent messages. In particular, the next release will add "pattern operator" against "modifier." https://gitlab.com/muttmua/mutt/-/blob/master/pattern.c#L897 vs http://www.mutt.org/doc/manual/#patterns-modifier https://gitlab.com/muttmua/mutt/-/blob/master/pattern.c#L1101 (There are already two messages using abbrv "op" which no one should see, though: https://gitlab.com/muttmua/mutt/-/blob/master/pattern.c#L1583 https://gitlab.com/muttmua/mutt/-/blob/master/pattern.c#L905 ) The source almost always calls them "op(erator)s" while the manual "modifiers." So it's not surprising that developers make an inconsistency in this case. If you are interested, I'll send you some more to be fixed after the release. But I understand it's little or no use merging "cannot" and "can't", "could not write" and "Write fault", or "No entry" and "No entry found." So I'd agree with you if you ignored the inconsistency. Mutt is more than twenty years old and everybody is happy using it. We translators sometimes feel itchy about inconsistencies, but users in general can live with them even without noticing them. Regards, tamo
