Simon Josefsson josefsson.org> writes:
> +2009-01-22 Simon Josefsson josefsson.org>
> +
> + * lib/version-etc.h: Add emit_bug_reporting_address.
> + * lib/version-etc.c (emit_bug_reporting_address): New function.
> + * modules/version-etc (Description): Reflect new features.
The c
Simon Josefsson ha escrit:
> Ah, interesting, I wasn't aware of this feature. Do I as maintainer of
> projects using gnulib have to do anything special to make this usable
> for translators?
Nothing special, only make sure the files imported from gnulib are
listed in your po/POTFILES.in.
Regar
Jim Meyering writes:
> Simon Josefsson wrote:
>> l...@gnu.org (Ludovic Courtès) writes:
> ...
>>> Is there any reason this cannot be made part of `version-etc'?
>>
>> No reason. It seems like a better place actually. Jim, how about this
>> patch?
>
> Hi Simon,
>
> That looks fine.
> However, p
Simon Josefsson wrote:
> l...@gnu.org (Ludovic Courtès) writes:
...
>> Is there any reason this cannot be made part of `version-etc'?
>
> No reason. It seems like a better place actually. Jim, how about this
> patch?
Hi Simon,
That looks fine.
However, please make the three changes like this:
"Stefan Monnier" writes:
+ printf (_("\nReport bugs to <%s>.\n"), PACKAGE_BUGREPORT);
> [...]
>> However, as far as I know there isn't a gnulib translation domain that
>> is automatically used for messages in gnulib code when you import it to
>> a project. So the strings above will end up
Karl Berry ha escrit:
> However, as far as I know there isn't a gnulib translation domain that
>
> There actually is, although I admit I don't know how the messages get
> integrated into the gnulib-using packages:
> http://translationproject.org/domain/gnulib.html
It is a "compendium" domai
>>> + printf (_("\nReport bugs to <%s>.\n"), PACKAGE_BUGREPORT);
[...]
> However, as far as I know there isn't a gnulib translation domain that
> is automatically used for messages in gnulib code when you import it to
> a project. So the strings above will end up in every project's *.po
> files,
OTOH, Karl's message suggests that it's the job of
`--help', not `--version', so it may not be a good idea.
I don't see a reason to have it in --version. But if people think it's
a good idea to optionally have it there, we could ask rms.
It should definitely be in --help.
However, as far as I know there isn't a gnulib translation domain that
There actually is, although I admit I don't know how the messages get
integrated into the gnulib-using packages:
http://translationproject.org/domain/gnulib.html
If this is incorporated into a project as a Gnulib modul
2009/1/22 Simon Josefsson :
>
> I don't follow? The comment is aimed at translators, and translators
> will add the 'Report translation bugs ...' line in the particular
> gettext translation file. Thus, source code is not modified.
Thanks, I understand now. I thought the instruction meant to ad
Neil Jerram writes:
> 2009/1/22 Simon Josefsson :
>> Here it is. The module name and source filenames are rather long, but I
>> couldn't think of anything better. Untested, beware!
>
>> +void
>> +emit_bug_reporting_address (void)
>> +{
>> + /* TRANSLATORS: The placeholder indicates the bug-rep
2009/1/22 Simon Josefsson :
> Here it is. The module name and source filenames are rather long, but I
> couldn't think of anything better. Untested, beware!
> +void
> +emit_bug_reporting_address (void)
> +{
> + /* TRANSLATORS: The placeholder indicates the bug-reporting address
> + for this
l...@gnu.org (Ludovic Courtès) writes:
> Simon Josefsson writes:
>
>> l...@gnu.org (Ludovic Courtès) writes:
>
>>> Is there any reason this cannot be made part of `version-etc'?
>>
>> No reason. It seems like a better place actually. Jim, how about this
>> patch?
>
> And while we're at it, can'
Simon Josefsson writes:
> l...@gnu.org (Ludovic Courtès) writes:
>> Is there any reason this cannot be made part of `version-etc'?
>
> No reason. It seems like a better place actually. Jim, how about this
> patch?
And while we're at it, can't `version_etc ()' print the bug-reporting
informati
l...@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> Simon Josefsson writes:
>
>> I suggest a new gnulib module emit-bug-reporting-address. I have the
>> following code in GNU Libidn, which is strongly influenced by GNU
>> CoreUtils. Removing the 'static' keyword and putting it in a gnulib
>> mo
Hello,
Simon Josefsson writes:
> I suggest a new gnulib module emit-bug-reporting-address. I have the
> following code in GNU Libidn, which is strongly influenced by GNU
> CoreUtils. Removing the 'static' keyword and putting it in a gnulib
> module would make it easy to re-use the code, and po
Here it is. The module name and source filenames are rather long, but I
couldn't think of anything better. Untested, beware!
/Simon
>From 52901a4bf1eb6dbbac9aa5a8676e120da3d3c134 Mon Sep 17 00:00:00 2001
From: Simon Josefsson
Date: Thu, 22 Jan 2009 10:18:33 +0100
Subject: [PATCH] Add new modul
l...@gnu.org (Ludovic Courtès) writes:
> Hi,
>
> Eric Blake writes:
>
>> Would it help if autoconf were taught to make the package homepage into an
>> automatic C preprocessor macro by providing it as an optional argument of
>> AC_INIT, similar to other variables like PACKAGE_NAME, PACKAGE_TARNAM
18 matches
Mail list logo
