[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: automake.texi and @acronym
From: |
Eric Blake |
Subject: |
Re: automake.texi and @acronym |
Date: |
Wed, 17 Mar 2010 15:52:22 -0600 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Lightning/1.0b1 Thunderbird/3.0.3 |
On 03/17/2010 03:50 PM, Karl Berry wrote:
> I'm okay with changing the m4 and autoconf manuals with
> s/@acronym{GNU}/GNU/
>
> s/@acronym{(.*)}/\1/
>
> if we agree that it is easier to maintain,
>
> Is to me.
>
> and doesn't buy much typographically.
>
> I think having the (minor) benefit of consistency between GNU manuals
> outweighs the (minor) typographic refinement.
What about @sc{gnu}, which also appears in some but not all GNU manuals?
Is there any difference between @acronym and @sc?
--
Eric Blake address@hidden +1-801-349-2682
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
- automake.texi and @acronym, Karl Berry, 2010/03/06
- Re: automake.texi and @acronym, Ralf Wildenhues, 2010/03/13
- Re: automake.texi and @acronym, Karl Berry, 2010/03/16
- Re: automake.texi and @acronym, Ralf Wildenhues, 2010/03/19
- Re: automake.texi and @acronym, Simon Josefsson, 2010/03/19
- Re: automake.texi and @acronym, Karl Berry, 2010/03/19
- Re: automake.texi and @acronym, Ralf Wildenhues, 2010/03/28