On Thu, Aug 23, 2018 at 08:13:17AM -0400, Ineiev wrote:
>
> http://ftp.gnu.org/gnu/texinfo/htmlxref.cnf (which is in sync with
> Texinfo SVN repository) has links for two absent manuals: gcj (dropped
> in GCC 7 release series [0]) and info (the directory was removed
> from the we
Hello,
http://ftp.gnu.org/gnu/texinfo/htmlxref.cnf (which is in sync with
Texinfo SVN repository) has links for two absent manuals: gcj (dropped
in GCC 7 release series [0]) and info (the directory was removed
from the website about two years ago); could anybody update that file?
Thérèse Godefroy
On Tue, Aug 22, 2017 at 06:07:14PM +0200, Mathieu Lirzin wrote:
> Index: tp/Texinfo/Convert/HTML.pm
> ===
> --- tp/Texinfo/Convert/HTML.pm(revision 7934)
> +++ tp/Texinfo/Convert/HTML.pm(working copy)
> @@ -6330,11 +633
On Thu, Nov 24, 2016 at 11:02:18PM -0800, Per Bothner wrote:
>
>
> On 11/24/2016 10:53 PM, Ineiev wrote:
>
> >>This is another reason to replace the info program with a wrapper round
> >>'emaca -nw'.
> >
> >Why not improve the info program
On Thu, Nov 24, 2016 at 03:34:38PM -0800, Per Bothner wrote:
>
> On 11/24/2016 11:55 AM, Assaf Gordon wrote:
> >one minor annoyance that stems from the "info" format: the references
> >(@ref/@xref/@pxref).
> >
> >When writing a manual and using references, they are rendered differently in
> >eac
On Tue, Feb 09, 2016 at 05:37:24AM +, Gavin Smith wrote:
> Another problem is whether this use of "id" is valid for the version
> of HTML we target: the files are declared as "HTML 4.01 Transitional",
> but I read that this use of the "id" tag was only introduced in HTML5?
It looks like "id" w
On Fri, Dec 26, 2014 at 02:09:33AM +0900, Stephen J. Turnbull wrote:
> Ineiev writes:
>
> > GNU webmasters did receive reports from such visitors. I'm sure many
> > cases were not reported.
>
> If GNU websites are correctly configured and send the correct MIME
>
On Fri, Dec 26, 2014 at 12:58:24AM +0900, Stephen J. Turnbull wrote:
> Ineiev writes:
> > On Wed, Dec 24, 2014 at 12:27:25PM +0900, Stephen J. Turnbull wrote:
> > > AFAIK the encoding declaration is optional, defaulting to UTF-8. In
> > > that case, we can (and
On Wed, Dec 24, 2014 at 12:27:25PM +0900, Stephen J. Turnbull wrote:
> AFAIK the encoding declaration is optional, defaulting to UTF-8. In
> that case, we can (and IMHO *should*, but I am no longer an expert on
> current encoding practice) require that our software generate UTF-8
> and omit the de
Hello,
On Wed, Dec 24, 2014 at 12:59:32AM +0700, Yuri Khan wrote:
>
> What browsers are there that do not support CSS *and* at the same time
> have the capability of displaying proportional fonts?
They may not be able to exactly display proportional fonts, but they
may highlight it in a differen
On Thu, Dec 18, 2014 at 04:05:02PM +, Gavin Smith wrote:
> On Thu, Dec 18, 2014 at 3:57 PM, Ineiev wrote:
> > On Thu, Dec 18, 2014 at 03:41:40PM +, Gavin Smith wrote:
> >> I just tried the HTML output for @indentedblock in Lynx 2.8.7rel.1,
> >> and surprisi
On Thu, Dec 18, 2014 at 03:41:40PM +, Gavin Smith wrote:
> On Wed, Dec 17, 2014 at 10:42 PM, Karl Berry wrote:
> > (BTW, does lynx/etc. render CSS?)
> >
>
> I just tried the HTML output for @indentedblock in Lynx 2.8.7rel.1,
> and surprisingly the @indentedblock was indented (although by a
>
Hello,
I attach a test case which doesn't work with
makeinfo 4.13.91, though worked with makeinfo 4.13.
In makeinfo 4.13.91, no item captions come to the info
file (attached).
Is the feature going to be supported?
wt.info
Description: Binary data
wt.texi
Description: TeXInfo document
Hi, all;
I tried to build it on cygwin; it didn't find ncurses [0],
but configure exited successfully, and it was make that broke.
I'm not quite sure this is what Texinfo really wants in such cases.
[0] This is probably a problem of the system, and user should run
something like
configure LDFLAG
14 matches
Mail list logo
