2018-07-23 Bruno Haible
doc: For module names, use texinfo markup @code{} or @samp{}.
* doc/alloca.texi: Mark gnulib module names with @code.
* doc/alloca-opt.texi: Likewise.
* doc/quote.texi: Likewise.
* doc/posix-functions/freopen.texi: Likewise.
Hi Werner,
> The attached patch fixes all overfull lines except the ones caused by
> overlong URLs.
Thanks! Applied.
> I hope using @inlinefmt (introduced 2013 in version 5.0) is OK.
Sure.
Bruno
Hi, Paul,
> Thanks for volunteering to do that.
I guess that's how it works, doesn't it :-)
> Glibc strfmon would be preferred; ideally with no changes if
> possible.
That's also my preference, as it then makes it easier to update if
Glibc does.
> Also, assuming you write a nontrivial amount o
Thanks for volunteering to do that. Glibc strfmon would be preferred; ideally
with no changes if possible. I suggest using Git to prepare your patches, using
'git format-patch' and then 'git send-email' to send them. Also, assuming you
write a nontrivial amount of glue in m4/whatever.m4 etc., yo
The attached patch fixes all overfull lines except the ones caused by
overlong URLs.[*] I've tested it with texinfo 6.5 – I hope using
@inlinefmt (introduced 2013 in version 5.0) is OK.
Werner
[*] The @url command produces overfull lines even if within a
@raggedright environment. I c
Hi, all,
I've done a quick search of the Gnulib discussion list archives and
have not seen this issue raised:
Is it worth adding strfmon(3) and possibly strfmon_l(3) for those
systems that do not have it? I'm thinking primarily OpenBSD, even
the latest version. This OS does not have either.
I
