infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Schaefer (JIRA)" <>
Subject [jira] [Commented] (INFRA-9705) Remove elementid Markdown extension
Date Thu, 02 Jul 2015 04:09:04 GMT


Joe Schaefer commented on INFRA-9705:

The problem with diff3 is that it ignores headings because [TOC] "might be in play", which
does it's own thing with headings.  But it would be better to not use the TOC permalink stuff
and just enable this diff3 patch for all tags, and then strip the " &para;" trailing artifacts
in the TOC <li> entries in ASF::View with a simple regexp on the resulting html.  That
way you get permalinks that would work for every tag, but since it's an invasive change you
need to give projects lead time to adopt before enabling permalinks across the board in mdx_elementid
via diff3.

> Remove elementid Markdown extension
> -----------------------------------
>                 Key: INFRA-9705
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: CMS, Website
>         Environment:
>            Reporter: Sebb
>         Attachments: INFRA-9705.patch, diff, diff2, diff3
> The elementid Markdown extension appears to have been originally intended to handle Special
Attributes as per PHP Markdown Extras [1]. However it was not a complete implementation.
> The elementid extension code was later extended to try to handle permalinks as per Subversion
[2]. However it turned out that this code interfered with TOC processing.
> It would of course be possible to fix both of these issues, however there seems little
point as the Python Markdown module includes atttribute lists [3] as well as permalinks [4].
> I think it therefore makes sense to disable elementid by removing it from
> Attribute lists and permalinks can then be enabled separately; see related JIRAs.
> [1]
> [2]
> [3]
> [4]

This message was sent by Atlassian JIRA

View raw message