stkb / Rewrap

Rewrap extension for VSCode and Visual Studio
https://marketplace.visualstudio.com/items/stkb.rewrap
Other
499 stars 58 forks source link

AsciiDoc Support #139

Open philsturgeon opened 5 years ago

philsturgeon commented 5 years ago

Hey, just making an issue here so I can get it up on BountySource.

Quotes

[quote,Foo,bar]
____
Both protocols are located at layer 7 in the OSI model and depend on TCP at layer 4. Although they are different, RFC 6455 states that WebSocket "is designed to work over HTTP ports 80 and 443 as well as to support HTTP proxies and intermediaries" thus making it compatible with the HTTP protocol. To achieve compatibility, the WebSocket handshake uses the HTTP Upgrade header to change from the HTTP protocol to the WebSocket protocol.
____

This will turn into:

[quote,Foo,Bar] ____ Both protocols
are located at layer 7 in the OSI model and depend on TCP at layer 4. Although
they are different, RFC 6455 states that WebSocket "is designed to work over
HTTP ports 80 and 443 as well as to support HTTP proxies and intermediaries"
thus making it compatible with the HTTP protocol. To achieve compatibility, the
WebSocket handshake uses the HTTP Upgrade header to change from the HTTP
protocol to the WebSocket protocol. ____

Fenced Code Blocks

Code should have formatting preserved:

[source,ruby]
----
workers Integer(ENV['WEB_CONCURRENCY'] || 2)
threads_count = Integer(ENV['RAILS_MAX_THREADS'] || 5)
threads threads_count, threads_count

rackup      DefaultRackup
port        ENV['PORT']     || 3000
environment ENV['RACK_ENV'] || 'development'
----

becomes:

[source,ruby] ---- workers Integer(ENV['WEB_CONCURRENCY'] || 2) threads_count =
Integer(ENV['RAILS_MAX_THREADS'] || 5) threads threads_count, threads_count

rackup      DefaultRackup port        ENV['PORT']     || 3000 environment
ENV['RACK_ENV'] || 'development' ----

Lists

Lists also get in-lined. #124

mosabua commented 4 years ago

I would love to get AsciiDoc support added.

stkb commented 2 years ago

Adding the help wanted label to this because supporting a new markup language is very time consuming. It's not the implementation that's the problem but the going through the specs for the language, deciding how everything should work, and the writing of specs for Rewrap.

If anyone wants to help, by creating spec documents for AsciiDoc, similar to those of markdown or reStructuredText, I'd be happy to collaborate and get AsciiDoc properly supported. Anyone willing to help should also read the specs readme and I can help with any further questions.