Re: Marking strings translatable in gucharmap
- From: Behdad Esfahbod <behdad behdad org>
- To: Wouter Bolsterlee <uws+gnome xs4all nl>
- Cc: gnome-i18n gnome org
- Subject: Re: Marking strings translatable in gucharmap
- Date: Fri, 25 Aug 2006 10:08:32 -0400
On Fri, 2006-08-25 at 03:49 -0400, Wouter Bolsterlee wrote:
> P�hu, Aug 24, 2006 at 01:28:52PM -0400, Behdad Esfahbod skrev:
> > I want to fix a bug in gucharmap that causes two new strings ("Next
> > Block", "Previous Block") being marked for translation. These strings
> > have been marked for translation before we switched to GtkUIManager
> > (about 9 months ago), so many translation files already have those
> > translated (grep suggests 33 out of 71 .po files contain them.)
> >
> > http://bugzilla.gnome.org/show_bug.cgi?id=352665
> >
> > May I?
>
> The issue outlined above (strings already in the app, but not marked as
> translateable) are not affected by string freeze [1]... so I guess you
> should go ahead and do it NOW!
>
> mvrgr, Wouter
>
> [1] Not marking those strings as such won't do any of us good, while marking
> them as such does not cause regressions.
Previously I've seen Danilo having concerns about marking new strings as
translatable as those change the statistics. Anyway, after checking the
reference:
http://live.gnome.org/TranslationProject/HandlingStringFreezes
I went on to commit the change, when I noticed that the bug reported has
committed it already. Yay for everyone can write to everyone's
approach :-(.
--
behdad
http://behdad.org/
"Commandment Three says Do Not Kill, Amendment Two says Blood Will Spill"
-- Dan Bern, "New American Language"
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]