Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • E Editoria Typescript
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 3
    • Merge requests 3
  • 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
  • Editoria Typescript
  • Issues
  • #6

Closed
Open
Created Jan 05, 2017 by Wendell Piez@wendellOwner

Casting (some) links

To the extent that arbitrary cross-references and other links are represented in WordML, XSweet captures them and render them as HTML <a>. Also, <a> may also be generated by XSweet because it "needs to do so", for example to "glue together" a footnote with its referencing string.

There are two categories of potential links in the Word source, which fall into neither category. They could be marked with inline formatting (say, maybe blue and underlined?) which is expected to be "seen" as a link. In such cases there will be some indication that this is a link, but it won't be known ahead of time -- or necessarily reliable (bad data). Or worse (second category) - the link could be present but not explicitly marked in any way -- just an "http:// ..." run in otherwise plain text.

The first case is an "arbitrary mapping " problem and goes back to #3 (closed).

We could address the second case in a filter that detected and called out target substrings with a regular expression. Due to complications of mixed content, this is a bit trickier to define than a generic element/element mapping, so it has to be done with some care (probably in a separate module), but it is technically feasible. (This is the machine equivalent of a regex-based search/replace -- it works as long as there is no conflicting markup already there. BTW we can do this of course for any sort of matched content, not just links.)

(Note that this requirement is most common when dealing with citations, which puts it into an entirely different context from the 'main body' of text import.)

Assignee
Assign to
Time tracking