Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Administrator
|
At last, we have a release candidate! If all goes well, I'll release the final version this week. Please give it a try, experiment with it, abuse it, whatever you need to do. We want to put our best foot forward for 1.5.0. For the Groovy folks, the release candidate will have the relative leveloffset feature for you to try. Once Alex releases the AsciidoctorJ 1.5.0.rc.1, you can try it...or you can try a local snapshot.
NOTE: I'm aware of a parse error when attempting to compile Asciidoctor.js. I'll likely push an rc.2 once we get that resolved. If we notice any other problems, I'll try to include fixes for them in rc.2 as well.
There are now 6 open issues remaining, several of which are documentation or infrastructure issues. Here's where we stand with the original list I posted (using the Asciidoctor task list syntax, [*] means done)
* [*] Ensure the default stylesheet delivers a consistent appearance by switching the font family to Noto and retrieve the fonts from Google Web Fonts (#879)
* [*] Upgrade Font Awesome to 4.1 (#752) * [*] Add source map information to blocks (critical for writing plugins) (#861)
* [*] Add option or attribute to swap role of backtick and plus characters for inline literals (#714 and 718)
* [*] Add option to control use of single quote as a formatting character, disable by default (#717) * [*] Enable embedding of remote images when data-uri and allow-uri-read is set (#612)
* [ ] Move parsing of document subtitle to main parser, expose via Document API
* [ ] Ensure compatibility with Asciidoctor.js (mostly done) and AsciidoctorJ * [ ] Update the changelog (and README)
* [ ] Write a blog entry to announce the release and highlights key improvements and changes The really hard stuff is done. We just need to put the final touches on it and run it through QA! It's important for me to emphasize that this release candidate includes two changes to the AsciiDoc syntax. When you upgrade to Asciidoctor 1.5.0, the first thing you should do is add the following attribute entry to the top (or header) of existing documents:
```
:compat-mode: legacy ```
Then, you should verify that you have updated to the new syntax for italic and monospaced text. For italic text, you should replace single quotes with underscores. ```asciidoc
Use _italic_ instead of 'italic'. ``` For monospaced text, follow the recommendations in the following comment: Once you've switched to the new syntax (or the transitional syntax), then remove the compat-mode attribute entry from your document.
For new documents, I strongly urge you to use the new (or transitional) syntax.
If you have any questions or concerns, please feel free to chime in!
-Dan On Fri, Jun 20, 2014 at 6:13 PM, Dan Allen <[hidden email]> wrote:
... [show rest of quote] Dan Allen | http://google.com/profiles/dan.j.allen |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
From AsciidoctorJ I need to integrate some changes on extension API (IncludeProcessor), I will try to do it during this week, but if I can't this weekend I will spend one night in finishing the integration for sure.
|
Free forum by Nabble | Edit this page |