Paolo Bonzini wrote:
> >> gettext should be changed to use them by default
> >
> > I don't understand what you mean here. gettext() in libc or libintl has
> > generic
> > mechanisms for dealing with locale names and understands @quot suffixes.
>
> I meant embedding the transformation rules in get
On 11/26/2011 03:27 PM, Bruno Haible wrote:
- gnulib needs to add support for en@quot and en@boldquot in gnulib's
bootstrap script.
If you want so, why not. It's not that complicated. Take the rules from
gettext's Rules-quot, quot.sed, boldquot.sed files.
Yes, I'll look into it.
- perhaps i
[Dropping bug-texinfo from CC.]
The en@quot and en@boldquot mitigate the problem that
- For English, there is no translation team,
- Source code that contains gettext calls, like in _("hello `world'"),
use ASCII quotation mark approximations.
Paolo Bonzini wrote:
> [gettext should] build
[Cc bug-gnulib/gettext/standards/texinfo, Bcc gnu-prog-discuss]
On 11/25/2011 02:51 PM, Thien-Thi Nguyen wrote:
GNU programs are urged to use `symbol' (grave, symbol, apostrophe)
in README, Texinfo uses those to implement @code in Info files, etc.
I propose GNU adopt U+2018 symbol U
