[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: po / pot file integration: documentation
From: |
Bruno Haible |
Subject: |
Re: po / pot file integration: documentation |
Date: |
Sun, 29 Aug 2010 21:52:38 +0200 |
User-agent: |
KMail/1.9.9 |
Hello Ralf,
> > > > +The @code{AM_POT_TOOLS} macro performs tests for the @code{POTS}
> > > > primary.
> > > > +See @pxref{Programming Languages, , Programming Languages, gettext,
> > >
> > > @pxref prints a lower-case "see" in the PDF output, here you could best
> > > remove the initial "See" and use @xref.
> >
> > But then I get a makeinfo warning that I cannot fix without adding a
> > misplaced
> > comma.
>
> Which texinfo version are you using?
texinfo 4.13.
> > > > address@hidden@var{domain}.pot}. The @var{domain} is a identifier for
> > > > the
> > >
> > > @address@hidden
> >
> > In info and HTML output, @code and @file are identical. In PDF @file
> > produces
> > extra quotes around the string, which IMO is confusing here, because there's
> > enough font changes.
>
> But that's not something to hack around with bad markup, never.
> Instead, if that is confusing, then we should turn off the extra quotes
> globally
I disagree: It's frequent in documentation that you have to make a change on
one page but not on another page, simply because the context is different.
Ad-hoc tweaks are sometimes needed in doc, even if they disturb the consistency.
But if you want to override my changes, you can do it: they are on the
'pot-primary' branch.
Bruno