> On Dec 27, 2021, at 9:14, Patrice Dumas wrote:
>
> On Mon, Dec 27, 2021 at 08:38:37AM +0900, Jean-Christophe Helary wrote:
>>
>>
>>> is the "anchor" tag which can represent either
>>> the source or destination of a link (maybe confusing terminology but
>>> that's how the word "anchor" is/
On Mon, Dec 27, 2021 at 08:38:37AM +0900, Jean-Christophe Helary wrote:
>
>
> > is the "anchor" tag which can represent either
> > the source or destination of a link (maybe confusing terminology but
> > that's how the word "anchor" is/was used in the context of hypertext).
> > Even if the WHAT
> On Dec 27, 2021, at 6:04, Gavin Smith wrote:
>
> On Sun, Dec 26, 2021 at 10:18:55AM -0800, Per Bothner wrote:
>>
>>
>> On 12/26/21 10:12, Patrice Dumas wrote:
>>> But there is nowhere where id in a lone element is proposed, so this
>>> argument is not very compelling not to use for that p
On 12/26/21 13:43, Gavin Smith wrote:
I just ran "emacs"
at the command line to see how long that took to start up, and I
counted 31 seconds for it to load up.
Wow. /usr/bin/emacs (i.e. not emacs-server) takes about half a second.
(OTOH I have recent laptop (bought this March) with lots of
On Sun, Dec 26, 2021 at 06:33:15PM +0100, Patrice Dumas wrote:
>
> Also I propose to add class to the anchors to distinguish their source.
I integrated the separate anchor of @float to the div, so I added the
following classes for separate anchors:
"anchor" for @anchor, "index-entry-anchor" for
(Accidentally forgot to Reply-All.)
On Sun, Dec 26, 2021 at 04:36:55PM +, Gavin Smith wrote:
> On Sun, Dec 26, 2021 at 08:48:30AM +0200, Eli Zaretskii wrote:
> > I guess my main point is that the move to HTML docs in the GNU project
> > is not a simple decision, and will need at least a close
(I accidentally forgot to Reply-All.)
Date: Sun, 26 Dec 2021 20:14:38 +0200
From: Eli Zaretskii
To: Gavin Smith
Subject: Re: The HTML-Info initiative
> From: Gavin Smith
> Date: Sun, 26 Dec 2021 16:36:55 +
>
> Maybe I should produce a document explaining all the issues involved
> based on
On Sun, Dec 26, 2021 at 12:18:18PM -0800, Per Bothner wrote:
> On 12/25/21 22:48, Eli Zaretskii wrote:
>
> Your comments are all on-point, but I'll just add a few notes.
>
> > > Date: Sat, 25 Dec 2021 11:44:34 -0800
> > > From: Per Bothner
>
> > > Note that using eww-mode running in a terminal
On Sun, Dec 26, 2021 at 10:18:55AM -0800, Per Bothner wrote:
>
>
> On 12/26/21 10:12, Patrice Dumas wrote:
> > But there is nowhere where id in a lone element is proposed, so this
> > argument is not very compelling not to use for that purpose.
> > was used for that semantically before, while
On 12/26/21 12:04, Patrice Dumas wrote:
On Sun, Dec 26, 2021 at 11:24:59AM -0800, Per Bothner wrote:
I believe putting the link on the sectioning command is slightly better (more
semantically meaningful and easier to work with) than putting it before
- and it is never worse.
I agree, and wh
On 12/25/21 22:48, Eli Zaretskii wrote:
Your comments are all on-point, but I'll just add a few notes.
Date: Sat, 25 Dec 2021 11:44:34 -0800
From: Per Bothner
Note that using eww-mode running in a terminal displays texi2any-generated
html work pretty decently, so that could potentially repl
On Sun, Dec 26, 2021 at 11:24:59AM -0800, Per Bothner wrote:
>
>
> On 12/26/21 10:29, Patrice Dumas wrote:
> > On Sun, Dec 26, 2021 at 10:08:50AM -0800, Per Bothner wrote:
> > > I don't remember, and I don't see how it could be better for navigation..
> >
> > It was some time ago, at least some
On 12/26/21 10:29, Patrice Dumas wrote:
On Sun, Dec 26, 2021 at 10:08:50AM -0800, Per Bothner wrote:
I don't remember, and I don't see how it could be better for navigation..
It was some time ago, at least some people expected the link to point to
the start of the header, and not to the hea
On Sun, Dec 26, 2021 at 10:08:50AM -0800, Per Bothner wrote:
>
>
> On 12/26/21 09:30, Patrice Dumas wrote:
> > On Sat, Dec 25, 2021 at 02:10:29PM -0800, Per Bothner wrote:
> > > Two requests:
> > > (1) Don't generates the implicit id="Electron-1" when it immediately
> > > follows
> > > an explic
On 12/26/21 10:12, Patrice Dumas wrote:
But there is nowhere where id in a lone element is proposed, so this
argument is not very compelling not to use for that purpose.
was used for that semantically before, while is explicitely
described as being relevant in relation to its content. For
On Sun, Dec 26, 2021 at 09:48:35AM -0800, Per Bothner wrote:
>
>
> On 12/26/21 09:33, Patrice Dumas wrote:
> > Hello,
> >
> > Currently is used for anchors, whether they
> > originate from @anchor, in some cases from @node and sectionning
> > @-commands, @*index, ... It is syntactically correc
On 12/26/21 09:30, Patrice Dumas wrote:
On Sat, Dec 25, 2021 at 02:10:29PM -0800, Per Bothner wrote:
Two requests:
(1) Don't generates the implicit id="Electron-1" when it immediately follows
an explicit id="Electron".
I do not think that it is a good idea, the @anchor anchor and id should
On 12/26/21 09:33, Patrice Dumas wrote:
Hello,
Currently is used for anchors, whether they
originate from @anchor, in some cases from @node and sectionning
@-commands, @*index, ... It is syntactically correct, but I think that
it would be semantically better to use and keep for inline
tex
Hello,
Currently is used for anchors, whether they
originate from @anchor, in some cases from @node and sectionning
@-commands, @*index, ... It is syntactically correct, but I think that
it would be semantically better to use and keep for inline
text that needs some kind of formatting informat
On Sat, Dec 25, 2021 at 02:10:29PM -0800, Per Bothner wrote:
> Two requests:
> (1) Don't generates the implicit id="Electron-1" when it immediately follows
> an explicit id="Electron".
I do not think that it is a good idea, the @anchor anchor and id should
stay different from the @node, or section
20 matches
Mail list logo
