Sure, there are i18n and l10n guides that tells developers about this, even things like Gnome HIG deal with this as well, but not every developer will follow it all the time, and we had to point the offending cases out to the developers to get them fixed.
On Tue, Apr 07, 2009 at 10:14:43AM +0400, Oleg Koptev wrote: > prophylaxis is better then surgery. > > 2009/4/7, Khaled Hosny <[email protected]>: > > On Tue, Apr 07, 2009 at 09:46:57AM +0400, Oleg Koptev wrote: > >> In reference to upstream teams - dunno, but I think somebody from here > >> are in tight contact with them (as I see at Og e-mail adress for > >> example). So it could be figured out there in any case. > > > > You don't need "tight contact with" upstream to report bugs (non-obvious > > strings lacking context is a bug), just open and account in, say, gnome > > bugzilla and file bug report(s) against the relevant module(s), this way > > you know for sure that the developers know about the issue and can work > > on it. > > > > Rgerds, > > Khaled > > > > > > -- > > Khaled Hosny > > Arabic localiser and member of Arabeyes.org team > > Free font developer > > > > > -- > C уважением, Коптев Олег > With respect, Koptev Oleg > > Jabber ID - [email protected] > WWW — http://ktulhuntu.blogspot.com -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer
signature.asc
Description: Digital signature
-- ubuntu-translators mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
