Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nocase nesting #104

Open
retorquere opened this issue Aug 13, 2019 · 2 comments
Open

nocase nesting #104

retorquere opened this issue Aug 13, 2019 · 2 comments

Comments

@retorquere
Copy link
Contributor

With this script:

const BibLatexParser = require('biblatex-csl-converter').BibLatexParser

const input = `
@article{Adams2001,
  title = {{The \\emph{physical} volcanology of the 1600 eruption of Huaynaputina, southern Peru}},
}
`

let parser = new BibLatexParser(input, {
    processUnexpected: true,
    processUnknown: { comment: 'f_verbatim' },
    processInvalidURIs: true,
});

let bib = parser.parse()
console.log(JSON.stringify(bib.entries['1'].fields.title, null, 2))

I'm getting

[
  {
    "type": "text",
    "text": "The ",
    "marks": [
      {
        "type": "nocase"
      }
    ]
  },
  {
    "type": "text",
    "text": "physical",
    "marks": [
      {
        "type": "em"
      }
    ]
  },
  {
    "type": "text",
    "text": " volcanology of the 1600 eruption of Huaynaputina, southern Peru"
  }
]

which leaves the part after the emph section unprotected. This isn't expected right?

@retorquere
Copy link
Contributor Author

It's not an effect of the change in 1.6.9, 1.6.8 exhibits the same behavior.

@retorquere
Copy link
Contributor Author

This goes back to at least 1.5.0. I don't honestly know enough about the parser to know where to begin to look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant