> This seems to be contradicting to me. I.e. you want some "essential" > part of Gnome to require ngettext (meaning it won't work without it), > yet one line is too much for you to achieve that same goal ;-) The point is that this same line will have to be duplicated in each module, and it will be forgotten in half of those modules, especially if the people doing the ngettext patches don't add the necessary check in their patches nor explicitly mentions the need for this check. Most module maintainers probably only know the strict minimum about i18n, and won't necessarily think about adding it (though it will probably become more difficult after this thread :p) Christophe > > This one line is all you need to do to get over with it. If there's no > ngettext, you're done, no need to check for anything else. Build fails. > > Sure, it would be nicer if we wouldn't have 10 of these lines, but just > one of those in one module, but I cannot see how this is any different > for you as an application developer -- if you depend on it being there, > you depend on it, regardless of where it is checked for. > > If it's too much of maintainance work for you, I'll gladly apply for > keeping up that one line in configure.in :-) > > Cheers, > Danilo > _______________________________________________ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://lists.gnome.org/mailman/listinfo/gnome-i18n > >
Ceci est une partie de message=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e=2E?=