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 47
    • Issues 47
    • 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
  • #12

Closed
Open
Created Sep 19, 2016 by Wendell Piez@wendellOwner

Internal cross-references

The discovery that processing references (to citations, i.e. endnotes) may require providing generated text where the .docx has only a placeholder suggests we are going to have to take similar care with cross-references. (Word supplies mechanisms to cross-reference to arbitrary sections or other targets, showing page numbers or generated text dynamically. These could well be represented by empty elements in the .docx.)

Specifically, we need to be sure that elements indicating cross-references are not removed in the scrub.xsl stage, probably by providing them with some kind of content in an earlier pipeline step.

Assignee
Assign to
Time tracking