On 1/2/19 2:00 PM, Gavin Smith wrote:
Nevertheless this issue is never going to go away, so we may as well
deal with it now. (If me or somebody else comes back to this in the
future, they will probably have forgotten the details again.)
First, is the ID type really too restrictive?
https://www
On Wed, Jan 02, 2019 at 05:32:15PM +, Gavin Smith wrote:
> On Tue, Jan 01, 2019 at 05:46:11PM -0800, Per Bothner wrote:
> > On 1/1/19 1:49 PM, Gavin Smith wrote:
> > >Thanks for working on this. What else needs to be changed so that the
> > >output is valid for HTML 5?
> >
> > It's worth clar
On 1/2/19 11:40 AM, Gavin Smith wrote:
On Mon, Dec 31, 2018 at 01:14:28PM -0800, Per Bothner wrote:
It wraps all nodes (anything processed by _convert_heading_command) in a
block.
Previously you wanted to have different 's for @chapter and @node:
https://lists.gnu.org/archive/html/bug-texin
On Mon, Dec 31, 2018 at 01:14:28PM -0800, Per Bothner wrote:
> It wraps all nodes (anything processed by _convert_heading_command) in a
> block.
Previously you wanted to have different 's for @chapter and @node:
https://lists.gnu.org/archive/html/bug-texinfo/2016-02/msg00056.html
> I suggest t
On 1/2/19 10:57 AM, Gavin Smith wrote:
On Mon, Dec 31, 2018 at 01:14:28PM -0800, Per Bothner wrote:
It wraps all nodes (anything processed by _convert_heading_command) in a
block.
- $result .= "\n"
+ $result .= "
What is the thinking behind the 'cmdname' attribute? I could find no
refe
On Mon, Dec 31, 2018 at 01:14:28PM -0800, Per Bothner wrote:
> It wraps all nodes (anything processed by _convert_heading_command) in a
> block.
> - $result .= "\n"
> + $result .= "https://developer.mozilla.org/en-US/docs/Web/HTML/Element/div
or
https://developer.mozilla.org/en-US/docs/Web/
On Tue, Jan 01, 2019 at 02:31:32PM -0800, Per Bothner wrote:
> On 1/1/19 1:49 PM, Gavin Smith wrote:
> >PS Texinfo is using git now for its development.
>
> In https://www.gnu.org/software/texinfo/ the link for
> "The development source tree." is a (broken) link to the svn tree.
>
> Also, the lin
On Tue, Jan 01, 2019 at 05:46:11PM -0800, Per Bothner wrote:
> On 1/1/19 1:49 PM, Gavin Smith wrote:
> >Thanks for working on this. What else needs to be changed so that the
> >output is valid for HTML 5?
>
> It's worth clarifying that all of the changes in my patch produce valid HTML
> 4:
> Usi
