Re: Typos in eog.schemas.in
- From: Kjartan Maraas <kmaraas broadpark no>
- To: Danilo Segan <danilo gnome org>
- Cc: Andrew Sobala <aes gnome org>, Alessio Frusciante <algol tin it>,Christian Rose <menthos gnome org>,GNOME I18N List <gnome-i18n gnome org>, Jens Finke <jens triq net>,GNOME Release Team <release-team gnome org>
- Subject: Re: Typos in eog.schemas.in
- Date: Tue, 17 Feb 2004 22:44:09 +0100
tir, 17.02.2004 kl. 21.34 +0100, skrev Danilo Segan:
> Hi Andrew,
>
> Andrew Sobala <aes@gnome.org> writes:
>
> > Yes, I know; that's why string freeze breakage requires i18n team
> > approval. I personally think that a) we are fairly early into string
> > freeze and b) they are typos rather than people gratuitously adding
> > strings that they should be approved, but it's the i18n team's call.
>
> Ok, that's not really my call (apart from me expressing my opinion),
> but note that one new message or one changed message are completely
> equivalent from the translators POV.
>
> On the point "a)", we should probably define when does "early in the
> string freeze" actually end if that's how we're going to look at it —
> I don't mind that approach, but it's not really a freeze that way.
> I imagine this is something release team and I18N team need to tackle
> for the next release cycle.
>
My opinion on breaking string freeze is as follows:
- no changes to non-visible strings (schemas, atk descriptions etc)
- approval needed for changing strings visible in the GUI (still not
recommended to do so of course)
- marking existing strings for translation is ok (this is probably the
most controversial one to some)
How do others feel about this?
Cheers
Kjartan
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]