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

TOC links to sections with special characters don't work. #3461

Closed
nachogt opened this issue Feb 9, 2020 · 3 comments
Closed

TOC links to sections with special characters don't work. #3461

nachogt opened this issue Feb 9, 2020 · 3 comments
Labels
needs investigation 🔬 Issue requires further investigation to locate or narrow down the problem.

Comments

@nachogt
Copy link

nachogt commented Feb 9, 2020

Current behavior

When a section of the note (line starting with one or more # characters) has a special character in it, the links generated in the TOC don't work for that section.

For example, if I have a section called:

Conceptos básicos

the TOC generates a link called "#Configuracion-basica" (without the á character). When clicked, a jump to that section does not happen. The rest of links to other sections do work, though.

I noticed this when clicking on links generated on an HTML exported note. The links on the TOC of the HTML don't work either for sections with at least these special characters in it (so, maybe that's two issues in one).

Expected behavior

Clicking on a TOC link should jump to that section.

Steps to reproduce

  1. Create a section with a special character in it
  2. Create the TOC
  3. Click on the link

Environment

  • Version : 0.14.0
  • OS Version and name : MacOS Catalina
@Flexo013
Copy link
Contributor

Strange, this does seem to work fine on Windows 10, with 0.14.0.

image

Could somebody with Mac double check if this issue is indeed Mac only?

@Flexo013 Flexo013 added the needs investigation 🔬 Issue requires further investigation to locate or narrow down the problem. label Feb 16, 2020
@ignaciogarcia
Copy link

I created a new note to replicate the problem and indeed, it worked correctly now.

Went back to the note originating the issue, and as described, it was not working. Updated the TOC and then everything started to working.

Maybe it was a problem of a previous version (the note was from over a year ago) and was fixed at some point. Sorry I didn't do this check before... I think the issue could be closed now.

Thank you and again sorry for the confusion.

@arcturus140
Copy link
Contributor

arcturus140 commented Feb 17, 2020

duplicate of #2582

affected versions: 0.11.12 and earlier. For notes with creation date 2018 and older TOC must be regenerated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs investigation 🔬 Issue requires further investigation to locate or narrow down the problem.
Projects
None yet
Development

No branches or pull requests

4 participants