Open de-jcup opened 5 years ago
There seems to be attempts to create an asciidoctor parser in java in future. So I will stop implementing here a simple version and wait until it java library is available. With a correct parser formatting should be much easier.
@mojavelinux in your last mail we have talked about possibility to establish a java based parser for asciidoctor. Exists there already a project at github or eclipse? Please give me a hint. Maybe I could be able to conrtibute.
At long last, we're about to submit the project proposal to Eclipse. I'd like to invite you as a committer on that project.
@mojavelinux : Thank you. Was very busy in the last weeks(even months..) - so sorry for late response. And of course: I am interested.
I think you are talking about https://projects.eclipse.org/proposals/asciidoc-language ? I tried to find the github repository, but "Source Repository Type: GitHub" points to https://projects.eclipse.org/source-repository-type/github were I didn't find the repo.
After searching at github I only found: https://github.com/EclipseFdn/asciidoc-wg.eclipse.org
Is this the repository for the language project as well? I thought this is the repository for the working group (developing/enhancing asciidoc specifications) - and not for the language project.
I tried to find the github repository, but "Source Repository Type: GitHub" points to projects.eclipse.org/source-repository-type/github were I didn't find the repo.
That's the proposal. The project is here: https://projects.eclipse.org/projects/technology.asciidoc
Currently, there are three entities:
In my previous message, I was referring Eclipse Austen.
(Ideally, the AsciiDoc WG site will provide access to all of these locations, but it is still being worked on).
Has anyone do this?
@cathaysia Hm... seems everybody has the same problem as myself: running out of time...
https://gitlab.eclipse.org/eclipse/austen/austen/-/issues/1 is currently still the only issue and there seems to be no further thoughts about it today.
The specification is now underway (with a first milestone coming sometime next month). We anticipate that by mid-summer, we should be ready to start getting Austen moving. It has been waiting on several key decisions to be made in the language project before it was possible to start laying down code. But it's not far off now.
Whatever the formatter is a very important thing.I have tried to use asciidoc.js to write a formatting tool, but it seems to miss some APIs I need, and I don't know about Ruby, so I can only put it on this way.
At present, I can only use some VIM scripts format documents, but this is not a good idea.
It happens very often that I write adoc text and then changes something - e.g. add or remove an admoniton and I have to manually rearrange the source to make it readable again.
Those manual beautifying should be automatically possible by an formatter