Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • XSweet XSweet
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • XSweet
  • XSweetXSweet
  • Issues
  • #27

Closed
Open
Created Oct 12, 2016 by Alex Theg@athegOwner

Capitalization & the `<caps>` tag

For the Bakker TOC, it looks like the author used both bolding and all caps to denote some structural elements (h1 & h2). Once it's been transformed, the caps text is carried over as <caps>, while the chapter headings are `

. These look the same in my browser.

Since the extracted HTML has upper and lower case letters and it's tagged as <caps>, I'm assuming the author typed it in normally, then chose to upcase it all after the fact. I'm guessing that if the author simply typed in caps in the first place, we wouldn't get the nice <caps> tag.

This seems good to keep in mind for post-processing and suggesting structure: pay attention to all caps, and really pay attention to <caps> tags.

Assignee
Assign to
Time tracking