Hello Gavin,
Mathieu Lirzin writes:
> The website has been shutdown by my former university. The data is
> available on my previous laptop. I plan to make those articles available
> on the Web again soon. I will let you know when it is done.
The weekly reports I made during my GSoC in 2017 are
Hello Gavin,
Gavin Smith writes:
> On 4/2/19, Mathieu Lirzin wrote:
>>> I suggest trying just a simple "id selector":
>>>
>>> res = elem.querySelector("#" + linkid);
>>>
>>> This should work on any element with a match 'id' attribute.
>>> I'd like us to get away from using element fo
On 4/2/19, Mathieu Lirzin wrote:
>> I suggest trying just a simple "id selector":
>>
>> res = elem.querySelector("#" + linkid);
>>
>> This should work on any element with a match 'id' attribute.
>> I'd like us to get away from using element for link definitions.
>> For example (if we ca
Hello,
Per Bothner writes:
> On 1/28/19 12:05 PM, Gavin Smith wrote:
>> On Tue, Jan 01, 2019 at 05:46:11PM -0800, Per Bothner wrote:
>>
>> diff --git a/js/info.js b/js/info.js
>> index 10a2b1d..0175d35 100644
>> --- a/js/info.js
>> +++ b/js/info.js
>> @@ -1170,7 +1170,7 @@
>> if (linkid
On 1/2/19, Per Bothner wrote:
>>> I suggest two categories of elements:
>>> A "node" includes all the content of a single node,
>>> but *not* sub-nodes.leaves unanswered
>>> A "chapter" or "section" (or "part" or whatever)
>>> encloses the current node - and sub-nodes.
>>
>> This is not what you
On 1/28/19 12:05 PM, Gavin Smith wrote:
On Tue, Jan 01, 2019 at 05:46:11PM -0800, Per Bothner wrote:
diff --git a/js/info.js b/js/info.js
index 10a2b1d..0175d35 100644
--- a/js/info.js
+++ b/js/info.js
@@ -1170,7 +1170,7 @@
if (linkid === config.INDEX_ID)
{
hide_gra
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
On Thu, Jan 03, 2019 at 01:00:50PM +, Gavin Smith wrote:
> On Thu, Jan 03, 2019 at 12:23:21PM +0100, Patrice Dumas wrote:
> > I remember that there were validation errors. Maybe the problem is not
> > with node names (and for section when section names are used as anchors)
> > as they have g_t
On Thu, Jan 03, 2019 at 12:23:21PM +0100, Patrice Dumas wrote:
> I remember that there were validation errors. Maybe the problem is not
> with node names (and for section when section names are used as anchors)
> as they have g_t prepended but for other anchors, in particular for
> index entries,
On Wed, Jan 02, 2019 at 10:00:14PM +, Gavin Smith wrote:
>
> > Element names can contain any character (including letters and numbers)
> > Element names must not contain spaces
> > Element names must not begin with a number or punctuation character (for
> > example a comma or semi-colon etc)
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
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:
Using 'id' attributes on arbitrary elements is part of HTML 4, and I believe
i
On Tue, Jan 01, 2019 at 02:10: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? I assume that the DOCTYPE declaration would
> >need to be changed - currently it is
> >
> >
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 links in the following paragraph ("The NEWS file listing ...")
go to svn.sav
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? I assume that the DOCTYPE declaration would
need to be changed - currently it is
http://www.w3.org/TR/html4/loose.dtd";>
The recommendation seems to be just
On Mon, Dec 31, 2018 at 01:14:28PM -0800, Per Bothner wrote:
> See this old thread:
> https://lists.gnu.org/archive/html/bug-texinfo/2016-02/msg00056.html
>
> Attached is a simple patch to generate better-structured html.
>
> It wraps all nodes (anything processed by _convert_heading_command) in
On 12/31/18 1:14 PM, Per Bothner wrote:
If people are concerned about breaking things, I suggested adding --html4 and
--html5
as new output options. Only --html5 would create the new-style output.
The existing --html flag would be an alias to --html4. After a release or two
we could
change th
See this old thread:
https://lists.gnu.org/archive/html/bug-texinfo/2016-02/msg00056.html
Attached is a simple patch to generate better-structured html.
It wraps all nodes (anything processed by _convert_heading_command) in a
block.
It uses id="xx" instead of . When I could, I attached the i
25 matches
Mail list logo
