Den 2016-06-04 kl. 14:36, skrev Alexandre Franke:
> On Sat, Jun 4, 2016 at 12:34 PM, Anders Jonsson
> wrote:
>> In that case, is there a bug report for the GNOME Shell case? I
>> searched, but didn't find one.
> You're right that there should be a bug report about
On Sat, Jun 4, 2016 at 12:34 PM, Anders Jonsson
wrote:
> In that case, is there a bug report for the GNOME Shell case? I
> searched, but didn't find one.
You're right that there should be a bug report about that. I filed it.
Den 2016-06-03 kl. 14:08, skrev Alexandre Franke:
> 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
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
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
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
> 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
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.
It would be pretty frustrating to have to re-train your muscle memory just
because you've switched the system language. Or to find
You can also add an msgctxt to distinguish them. This makes them fuzzy.
Best regards
Ask
El 02/06/2016 13:13, "Michael Gratton" escribió:
> On Wed, Jun 1, 2016 at 4:51 PM, Baurzhan Muftakhidinov <
> baurthefi...@gmail.com> wrote:
>
>> Mark those messages as fuzzy, and then ask
On Wed, Jun 1, 2016 at 4:51 PM, Baurzhan Muftakhidinov
wrote:
Mark those messages as fuzzy, and then ask translators to revisit
them,
Okay, thanks. So I assume the best way to do that is to simply add a
"#, fuzzy" to the problematic lines manually and commit them to
Hello
To fix the bug, validate the translated string and use the English one if
necessary.
I think this should always be done when translations have the potential to
crash the application, particularly in complex cases like this.
Best regards
Ask
El 01/06/2016 08:52, "Baurzhan Muftakhidinov"
Hi,
Mark those messages as fuzzy, and then ask translators to revisit them,
Regards.
On Wed, Jun 1, 2016 at 11:47 AM, Michael Gratton wrote:
>
> Hi gnome-i18n,
>
> Recently in Geary a search feature was added where people could write a
> searches such as "is:unread" and have it
Hi gnome-i18n,
Recently in Geary a search feature was added where people could write a
searches such as "is:unread" and have it find all unread messages, also
"is:read" and "is:starred". This is implemented by parsing the string
separately, i.e. "is:read" is parsed as two separate strings,
14 matches
Mail list logo