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

do we want to try symbol replacement in rendering plugins? #31

Open
josephholsten opened this issue Jul 1, 2016 · 1 comment
Open

Comments

@josephholsten
Copy link
Contributor

for example, vim-pandoc-syntax uses the following symbols instead of the raw markdown text:

    let s:cchars = { 
        \"newline": "↵", 
        \"image": "▨", 
        \"super": "ⁿ", 
        \"sub": "ₙ", 
        \"strike": "x̶", 
        \"atx": "§",  
        \"codelang": "λ",
        \"codeend": "—",
        \"abbrev": "→",
        \"footnote": "†",
        \"definition": " ",
        \"li": "•",
                \"html_c_s": "‹",
                \"html_c_e": "›"}
@driusan
Copy link
Owner

driusan commented Jul 1, 2016

I foresee two problems with this:

  1. How do you edit a character in buffer the middle of a string that's getting mangled by the renderer?
  2. The image->character map already has a bug where it doesn't map multibyte unicode characters properly. This couldn't use the default imagemap, but would need to write its own imagemap, since using the default one would have similar issues.

That said, I don't have any issues with an alternative markdown renderer that you can switch to with the Renderer command which tries to do magic like this, I just think the default should be as faithful as it can be to the bytes in the text since if you're opening a file in an editor, it's probably because you want to edit it.

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

No branches or pull requests

2 participants