Quotes around http: macro

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Quotes around http: macro

cristoper
Hi, I'm currently migrating a collection of asciidoc documents I maintain from Asciidoc (python) to Asciidoctor. One inconsistency I've found is in how the inline http:/https: macros are detected. Given this input (run with "-b html5 -s" options):

``http://http://asciidoctor.org/[Asciidoctor]''

asciidoc (8.6.9) outputs this html:

<div class="paragraph"><p>“<a href="http://http://asciidoctor.org/">Asciidoctor</a>”</p></div>

Whereas asciidoctor (0.1.4) ouptuts this html:

<div class="paragraph">
<p>“http://http://asciidoctor.org/[Asciidoctor]”</p>
</div>

In other words, asciidoc expands it to a link with quotation marks surrounding it, which is what I expect, whereas asciidoctor does not expand the http: macro.

How should I mark up http: links in asciidoctor so that the hyperlined text is surrounded by curly quotes? (And have I just been lucky that it works the way it does in asciidoc, or is it supposed to work that way in asciidoctor as well?)

I have tried, for example:

``{empty}http://http://asciidoctor.org/[Asciidoctor]{empty}''

With no luck.

Thanks!
Reply | Threaded
Open this post in threaded view
|

Re: Quotes around http: macro

mojavelinux
Administrator
cristoper,

The missing substitutions in the verse block is probably the most frequently-reported bug leading up to the 1.5.0 release, and I think you all for your patience. The good news is that it is resolved in the 1.5.0 preview releases. I recommend that you upgrade to the preview release so that you don't have to work around the problem. You can get the preview release using:

 $ gem install asciidoctor --pre

There are still a handful of enhancements that have to go into Asciidoctor before we can call it 1.5.0. Regardless, the 1.5.0 preview release is already more stable and compliant than 0.1.4, so it's certainly safe to use*.

-Dan

* What's likely to change before 1.5.0 are some of the APIs if you are use Asciidoctor as a Ruby, JavaScript or Java library.



On Wed, May 14, 2014 at 8:11 AM, cristoper [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Hi, I'm currently migrating a collection of asciidoc documents I maintain from Asciidoc (python) to Asciidoctor. One inconsistency I've found is in how the inline http:/https: macros are detected. Given this input (run with "-b html5 -s" options):

``http://http://asciidoctor.org/[Asciidoctor]''

asciidoc (8.6.9) outputs this html:

<div class="paragraph"><p>“<a href="http://http://asciidoctor.org/">Asciidoctor”</p></div>

Whereas asciidoctor (0.1.4) ouptuts this html:

<div class="paragraph">
<p>“http://http://asciidoctor.org/[Asciidoctor]”</p>
</div>

In other words, asciidoc expands it to a link with quotation marks surrounding it, which is what I expect, whereas asciidoctor does not expand the http: macro.

How should I mark up http: links in asciidoctor so that the hyperlined text is surrounded by curly quotes? (And have I just been lucky that it works the way it does in asciidoc, or is it supposed to work that way in asciidoctor as well?)

I have tried, for example:

``{empty}http://http://asciidoctor.org/[Asciidoctor]{empty}''

With no luck.

Thanks!


If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Quotes-around-http-macro-tp1736.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Reply | Threaded
Open this post in threaded view
|

Re: Quotes around http: macro

cristoper
Thank you, Dan! I don't think this issue is related to the verse block substitutions... but it is also fixed in 1.5.0 (which is working very well for me all around).

chris
Reply | Threaded
Open this post in threaded view
|

Re: Quotes around http: macro

mojavelinux
Administrator
On Sun, May 18, 2014 at 7:47 AM, cristoper [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Thank you, Dan! I don't think this issue is related to the verse block substitutions... but it is also fixed in 1.5.0 (which is working very well for me all around).

Excellent news!

-Dan

--