| Re: [asciidoc-wg] AsciiDoc implementation for the Java/JVM ecosystem / project proposal |
Hello Torkild,
thank you for your interest. The grammar and a technology
compatibility kit (TCK) will be part of the AsciiDoc Languge
specification, this would be outside of this project proposal.
That being said, this project will have a big interest to work
towards something reusable in the language specification.
The aim for this project proposal would be "just" to provide an
implementation for th JVM. Maybe we can re-use a grammar, or
tranform it to ANTLR or a different tool, let's see. From what I
hear there will also be other implementations for other platform.
For now I am keen to find out why we need a JVM implementation, and what behaviour it should provide at its APIs. Looking at an editor, it should probably provide error messages to the line and character. How this is implemented on the inside (with ANTLR or something else) would be the next step.
What would highlights or deal breakers from a Eclipse Mylyn Docs
perspective?
I'll add both you and the project to the list!
Best regards,
Alexander
Hi all, I think having an ANTLR [1] grammar for AsciiDoc would be a good start. In addition to providing the foundation for the AsciiDoc JVM implementation it could form the foundation of all kinds of tools and generators that deal with the AsciiDoc language. The ANTLR generator is not limited to Java, so such a grammar could also be used for C#, Python, _javascript_, Go, C++ and Swift targets. I have experience in writing Eclipse based editors and tools using ANTLR grammars and found it very helpful being able to separate the parser and document model/generator in this way. Please add Eclipse Mylyn Docs and myself to the list of interested parties. Best regards, Torkild Ulvøy Resheim [1] https://www.antlr.org10. jun. 2020 kl. 17:08 skrev Alexander Schwartz <alexander.schwartz@xxxxxxx>: Hi AsciiDoc enthusiasts, the AsciiDoc WG is an exciting effort to standardize the language and to allow the ecosystem to grow on the basis of a common specification. After talking to Dan Allen I volunteered to write a project proposal for an AsciiDoc implementation for the Java/JVM ecosystem. As a maintainer of the AsciiDoc plugin for IntelliJ I have experience in parsing AsciiDoc and using AsciidoctorJ, but I also know he areas where parsing and good tool support is difficult today. What use cases do you see for an AsciiDoc JVM implementation? What contributions do you want to make or see necessary? Please collaborate with me on this draft: https://docs.google.com/document/d/1Jifb3Dd6HS6CbABiRaUKHCySEJBu5AUSWHVg6-mt6Ms/edit?usp=sharing To edit the document request access or discuss it on this mailing list. Don't forget to add you and your company to the "Interested Parties" section! For those who want to have a synchronous communication, please join me on a Jitsi video conference call next week: When: June 16th, 17:00 UTC - Convert to your time zone: https://www.thetimezoneconverter.com/?t=17%3A00%20pm&tz=UTC Where: https://meet.jit.si/AsciiDocImplementationForTheJvmJune16 Please get in contact before the call with all the questions you might have. Best regards, Alexander -- Alexander Schwartz (alexander.schwartz@xxxxxxx) https://www.ahus1.de _______________________________________________ asciidoc-wg mailing list asciidoc-wg@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/asciidoc-wg
_______________________________________________ asciidoc-wg mailing list asciidoc-wg@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/asciidoc-wg
-- Alexander Schwartz (alexander.schwartz@xxxxxxx) https://www.ahus1.de