Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • H HTMLevator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • XSweet
  • HTMLevator
  • Issues
  • #20

Closed
Open
Created Jul 28, 2019 by Alex Theg@athegOwner

Make list extraction and list detection consistent with each other

  • XSweet/applications/list-promote/PROMOTE-lists.xsl rebuilds true lists from Word as HTML lists.
  • HTMLevator/applications/list-detect/DETECT-ITEMIZE-LISTS.xsl detects plain-text versions of numbered lists, and creates true HTML ols out of them.

Their functionality should be standardized:

  • List extraction puts the list item text inside a p. List detection does not wrap the list item text in a p.
  • List extraction also extracts some additional information from the .docx, including list level. While it's not present on detected lists, the detection sheet should at least not remove these attributes, but it does.

List_test_2-7PROMOTELISTS.xhtml

List_test_2-8DETECTLISTS.xhtml

Assignee
Assign to
Time tracking