There's no need for any serious patches to GNOME actually, since one line
of msgfilter with sed handles almost everything…
For the "those (other) software" part, I think I mentioned some non-GNOME
apps/developers using "..." in msgids, and for consistency with their big
brother MS Windows I prefer
On Mon, Nov 16, 2015 at 3:48 PM, Mingye Wang (Arthur2e5)
wrote:
> Sorry for my language anyway.
You know your behaviour is rude and not welcome here, and you do it
anyway. Please refrain and try to fix your attitude before you send
anything, instead of apologizing afterwards. The bad language won
On Fri, Nov 13, 2015 at 5:33 PM, Lubomir Rintel wrote:
> Hello,
Hey,
> network-manager-openswan.git:nm-1-0
Is this one supposed to be network-manager-libreswan?
And what about the other modules not on this list like -iodine and -applet?
--
Alexandre Franke
___
On Fri, 2015-11-13 at 15:39 -0200, Enrico wrote:
> Hello folks!
>
> Please, as far as I understood, the translations prior to Friday 20th
> will
> be considered in the next release?
Yes, sir! :)
> Thanks a lot,
> Enrico.
Regards,
Lubo
>
> 2015-11-13 15:23 GMT-02:00 Piotr Drąg :
>
> > 2015-11
Sorry for my language anyway.
For a clearer list-of-points, please refer to
http://en.arguman.org/correct-ellipses-u2026-should-be-used-for-gnome-zh_cn-l10n/15168.
On 11/16/2015 8:37 AM, Mingye Wang (Arthur2e5) wrote:
> For brief info on the whole thing, please read
> https://bugzilla.gnome.org/s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
For brief info on the whole thing, please read
https://bugzilla.gnome.org/show_bug.cgi?id=758122. All necessary info
on this can be found there and the basic point is that the 1.1 guide
is sh*t typographically.
> For [According to] our translation g
The branch 'gnome-3-18' was created.
Summary of new commits:
0e19e70... Fix NULL string dereference
bf645af... Release 3.18.1
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n
On Sat, Nov 14, 2015 at 11:33 PM, Matthias Clasen
wrote:
> I saw a number of commits go by for: Use ... instead of … for zh_CN
>
For our translation guide, for zh_CN, we should use `...' instead of `…',
as `…' is quite ugly when work with Chinese characters.
> May I ask what the rationale is ? T
