On Mon, 24 Feb 2014, Trần Ngọc Quân wrote:
> Hello,
> -c option display fatal error for (Vé domain in TranslationProject.org):
>
> msgid "for Google's usual 30% share."
> msgstr "30% chia sẻ cho Google."
>
> Note: I truncated (edited) this string!
> This isn't a format string, so msgfmt should
On Mon, 24 Feb 2014, Trần Ngọc Quân wrote:
> You can find and test this string by use git command:
>
> $ git grep -n "30%"
Thanks. I already reported this here:
https://github.com/pryds/ve/issues/15
Hello.
While updating the Debian package, I noticed that docs are now installed
in PREFIX/share/doc/gettext-runtime, etc. and not PREFIX/share/doc/gettext/
as it used to be. I'm running configure from the top level directory.
Is this really expected/desirable?
Thanks.
possible to have some sort of option which I
can pass to ./configure to achieve this behaviour so that modifying
msgfmt.c directly was not needed.
Thanks.
From: Santiago Vila
Subject: Modified msgfmt to always create little endian .mo files
Bug-Debian: http://bugs.debian.org/671257
X-Debian-version
Hello.
I got an empty msgfmt.1.html. This is because I modify msgfmt.c, which
in turn makes msgfmt.1 outdated. Then it tries to renerate it using
groff and the result was an empty file because I didn't have groff
installed in my chroot. I discovered this by using lintian on the
generated gettext-d
On Fri, May 16, 2014 at 03:58:22PM +0900, Daiki Ueno wrote:
> After reading the discussion, I was left with a question.
>
> When the GNU gettext infrastructure is used, upstream tarballs include
> *.gmo files, which could have been generated in a different byte-order.
> Does the recent Debian buil
Hello.
I received this report from the Debian bug system.
The report included two patches to choose from. One of them is a patch
to the Debian packaging so that it uses autoreconf.
The other one, which is the one I was planning to apply to Debian
gettext 0.18.3.2, updates m4/libtool.m4 and rela
Hello.
I received this from the Debian bug system:
Mensaje reenviado
Subject: Bug#763820: gettext: msgunfmt aborts on incomplete UTF-8 character
Date: Thu, 2 Oct 2014 23:31:33 +0200
From: Jakub Wilk
Package: gettext
Version: 0.19.2-2
Severity: minor
Usertags: afl
msgunfmt ab
Hello.
I received this from the Debian bug system:
-- Forwarded message --
From: Guillem Jover
To: sub...@bugs.debian.org
Date: Wed, 8 Oct 2014 16:14:40 +0200
Subject: Bug#764483: gettext: Please support setting COPYRIGHT_HOLDER from an
autoconf variable
Source: gettext
Sour
Hello.
I received this report from the Debian bug system.
-- Forwarded message --
From: Jakub Wilk
To: Debian Bug Tracking System
Date: Fri, 5 Dec 2014 00:33:19 +0100
Subject: Bug#772088: gettext: msgunfmt segfaults (system-dependent messages)
Package: gettext
Version: 0.19.3-
Hello.
A long time ago I received this from the Debian bug system.
(Yes, I apologize for taking so long to forward this upstream).
-- Forwarded message --
From: "Francesco Poli (wintermute)"
To: Debian Bug Tracking System
Date: Mon, 23 Jul 2012 23:32:08 +0200
Subject: Bug#682580
Hello.
I have a number of bugs reported to Debian for which I have not
received any kind of reply yet. This is the list of all bugs:
https://bugs.debian.org/src:gettext
At this point, I've forwarded all of them here, which is what the
output from "gettext --help" says I should do.
I would appre
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
Hello.
What's the status of this bug?
I see it's mentioned in the logs for Bug #682580.
Should I consider it fixed by the $(DOMAIN).pot-update feature?
Thanks.
Hello.
I received this report from the Debian bug system.
This bug makes the "roxterm" package not to build anymore, as reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809570
Thanks.
- Forwarded message from Tony Houghton -
Date: Mon, 04 Jan 2016 15:55:29 +
From:
On Tue, Jan 05, 2016 at 06:00:21AM +0900, Daiki Ueno wrote:
> This is a packaging problem; the gettext package now needs to install
> version specific data files from /usr/share/gettext-0.19.7 directory,
> like the attached patch.
Thanks a lot! I'm going to apply the patch as is.
Simple question:
Hello.
While fixing the previous bug I noticed that the build process
modifies msgfmt.1. This is because we modify msgfmt so that it always
output little endian.
But I don't really want msgfmt.1 to be modified just because of this.
In the past I used to insert a suitable "touch" command somewher
a lot better than nothing, see the previous email
where I explain the undesired msgfmt.1 regeneration that happens
during the build.
Thanks.From: Santiago Vila
Subject: Modified msgfmt to always create little endian .mo files
Bug-Debian: http://bugs.debian.org/671257
X-Debian-version: 0.18.1.1-8
---
On Sat, Feb 13, 2016 at 01:09:41PM +0100, Jakub Wilk wrote:
> Do li.org mailing lists still exist? Contents of the li.org website
> ("Something broken. You're on default site.") and the fact that there are no
> such lists included on Translation Project's teams page[0] makes me think
> they are gon
Dear gettext maintainers:
I applied commit d13f165b8370 to the Debian gettext package, as
suggested by Bruno Haible, and several things happened.
One of them is that now glibc does not build because the gettext tests
still expect the POT-Creation-Date header to be there.
This has been reported he
20 matches
Mail list logo
