projectmallard / mallard-ducktype

Parser for the lightweight Ducktype syntax for Mallard
MIT License
10 stars 4 forks source link

validate Ducktype files? #18

Open fedelibre opened 4 years ago

fedelibre commented 4 years ago

There's any Ducktype validator? How can I debug what I'm writing? AFAIK now I must first convert to xml using mallard-ducktype and then use yelp-check validate. But this is cumbersome, as I have to check the .page file and then work on the .duck file.

I also wonder what's the adoption status of Ducktype. I think that all GNOME projects use the Mallard spec only, right? What is preventing the use of Ducktype?

shaunix commented 4 years ago

A validator would be very nice. For most of the checks in yelp-check, we could just teach yelp-check how to convert behind the scenes. But for validation, as you mention, there's line numbers involved, and that's annoying.

I'm going to move this issue to the mallard-ducktype repo, since that's where tooling like this would probably happen.

As for GNOME adoption, I think part of it is that the build system integration isn't there, especially for translations. But a bigger part is that there are only a few active contributors, and when there's already so many maintainable docs in XML, people don't see switching as a good use of time. Probably the most likely route is that some new apps will use it before you see a full conversion of something like gnome-user-docs.