Coder Social home page Coder Social logo

Comments (5)

tarwich avatar tarwich commented on July 20, 2024

Not urlencoding ~ sounds easy enough. I'm not sure I understand the edit you just did with the workaround, but I'll see if I can simply not strip the ~.

from qlmarkdown.

aagd avatar aagd commented on July 20, 2024

the workaround should just show that by using html syntax i can get around the ~ url encoding problem. sure it would be ideal if this could be fixed in the source.

from qlmarkdown.

tarwich avatar tarwich commented on July 20, 2024

After trying for an hour to reproduce your problem, I think there might be some confusion.

I don't see anywhere in the markdown reference that bare urls such as http://www.google.com/ are supposed to be converted into links. The GitHub markdown does automatically convert bare urls to links, but the discount module that QLMarkdown is using doesn't support it.

If you want to use a link, you have to write [Link text](http://www.google.com/) and it will show up like this: Link text.

Please let me know how you want to proceed with this. If you want the bare addresses converted, we should probably put it in the issues for the Discount module we're using.

from qlmarkdown.

BigEd avatar BigEd commented on July 20, 2024

I've just been hit by this (umm... in GitHub generally, so perhaps not this project at all! But anyway, for reference:) Our markdown contains ~, the HTML renders the HREF as %7E. Of three browsers tested, two send the %7E to the server and the other url-decodes to ~ before sending. This obscured what was going on. The server then failed to url-decode the %7e. Arguably the server is wrong. But even so, according to the latest applicable RFC, tilde is unreserved, and "Unreserved characters can be escaped without changing the semantics of the URI, but this should not be done unless the URI is being used in a context that does not allow the unescaped character to appear." (http://www.rfc-editor.org/rfc/rfc2396.txt)
The link in question was IBM 5110 Emulator which for me works with Chrome, not with Firefox and not with Safari.

from qlmarkdown.

deric avatar deric commented on July 20, 2024

There are many arguments why "tilde" ~ character should be encoded. On the other hand more recent RFC 3986 lists ~ as character that is not escaped by default (see Python's urllib change).

from qlmarkdown.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.