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

asciidoc should handle inline literals #30

Closed
peff opened this issue May 2, 2012 · 2 comments
Closed

asciidoc should handle inline literals #30

peff opened this issue May 2, 2012 · 2 comments

Comments

@peff
Copy link
Member

peff commented May 2, 2012

There's a pending change in upstream git to turn on asciidoc's "inline literal" feature. The source files are being tweaked accordingly; you can see the result at git/git@6cf378f. When this hits, we'll have to adjust our parser to handle the new syntax (but keep using the old syntax for older versions).

/cc @nickh

@ghost ghost assigned nickh May 5, 2012
nickh added a commit that referenced this issue May 16, 2012
We'll need this when git/git 6cf378 is released,
see #30 for more info.
@nickh
Copy link
Contributor

nickh commented May 29, 2012

@peff it looks like 1.7.10.3 has the new inline literal asciidoc and that it converted properly. Do things look OK to you?

@peff
Copy link
Member Author

peff commented Jun 4, 2012

I spot checked a few of the trickier spots, and all looked good to me. Thanks.

@peff peff closed this as completed Jun 4, 2012
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