[bug-gettext] [bug #45305] Add support for AppData specifications

2015-08-21 Thread Daiki Ueno
Update of bug #45305 (project gettext): Status:None => Fixed Open/Closed:Open => Closed ___ Follow-up Comment #7: Merged as: http://g

[bug-gettext] [sr #108864] gettext-0.19.5.1 compiling problem

2015-08-21 Thread Daiki Ueno
Update of sr #108864 (project gettext): Status:None => Done Open/Closed:Open => Closed ___ Follow-up Comment #3: Pushed a fix as: ht

Re: [bug-gettext] AM_GNU_GETTEXT_PREREQ

2015-08-21 Thread Daiki Ueno
Daiki Ueno writes: > I'm still not very happy with the name AM_GNU_GETTEXT_PREREQ and having > a separate macro in the first place, but I couldn't think of any better > way to implement the functionality without breaking compatibility. I've merged this after renaming it to AM_GNU_GETTEXT_REQUIRE

Re: [bug-gettext] Bug#682580: xgettext: fails to properly replace some placeholders in output .pot (PACKAGE, YEAR, C. HOLDER) (fwd)

2015-08-21 Thread Daiki Ueno
Daiki Ueno writes: > By the way, after looking into the history and the documentation more > closely, I realized that my argument on copyright notice was pointless. > I'm sorry. I'm now in favor of adding support for multiple copyright > holders, like the attached patch, which makes xgettext all

Re: [bug-gettext] Bug#682580: xgettext: fails to properly replace some placeholders in output .pot (PACKAGE, YEAR, C. HOLDER) (fwd)

2015-08-21 Thread Santiago Vila
On Fri, Aug 21, 2015 at 05:49:00PM +0900, Daiki Ueno wrote: > What else was remaining to close this bug? In Debian we usually close a bug when there is a new package available in "unstable" fixing the bug. This is what I will do for the Debian package but of course you might have different rules f

Re: [bug-gettext] Bug#682580: xgettext: fails to properly replace some placeholders in output .pot (PACKAGE, YEAR, C. HOLDER) (fwd)

2015-08-21 Thread Francesco Poli
On Fri, 21 Aug 2015 13:06:11 +0200 Santiago Vila wrote: > On Fri, Aug 21, 2015 at 05:49:00PM +0900, Daiki Ueno wrote: > > What else was remaining to close this bug? > > In Debian we usually close a bug when there is a new package available > in "unstable" fixing the bug. This is what I will do fo