Hi Anita,
On Fri, Jun 3, 2016 at 4:02 PM, Anita Reitere
wrote:
Are you sure that translating these strings is a good idea? We don't
translate option flags for command-line programs, or formula markup
in LaTeX or LibreOffice.
True, but the search box is very much part of the end-user UI, ra
Hi Ask,
On Thu, Jun 2, 2016 at 9:15 PM, Ask Hjorth Larsen
wrote:
You can also add an msgctxt to distinguish them. This makes them
fuzzy.
Ah, that's a good idea, thanks. All of the search operator strings are
have a context specified now, hopefully they'll be useful for future
translatio
The branch 'gnome-3-20' was created pointing to:
de4f14e... Updated Occitan translation
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n
On Fri, Jun 3, 2016 at 12:18 PM, Anita Reitere wrote:
>> That, however, sounds like a good idea. I wish GNOME Shell did the same.
>
> For GNOME Shell, translators can make it happen -- by adding
> translations to the keyword string without removing the original
> keywords. But in Geary, some devel
> Re-train? So you mean you've been using is:unread in Geary for long
> already? I don't think this argument is relevant here.
Well, I've been using them in Gmail. And someday in the future someone
will have been using them in Geary as well.
I guess we'll have to agree to disagree on the general
On Fri, Jun 3, 2016 at 8:02 AM, Anita Reitere wrote:
> Hi,
Hi,
> Are you sure that translating these strings is a good idea? We don't
> translate option flags for command-line programs, or formula markup in LaTeX
> or LibreOffice.
Function names are localized in LibreOffice. If your LibreOffice