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

Documentation of odoc is bad #573

Closed
jonludlam opened this issue Jan 28, 2021 · 4 comments
Closed

Documentation of odoc is bad #573

jonludlam opened this issue Jan 28, 2021 · 4 comments
Assignees
Milestone

Comments

@jonludlam
Copy link
Member

Some considerable effort needs to be made to improve it.

@jonludlam jonludlam added this to the 2.0.0 milestone Jan 28, 2021
@avsm
Copy link
Member

avsm commented Feb 3, 2021

Progress towards this in #571 to document the supported interfaces.

@jonludlam jonludlam self-assigned this Feb 12, 2021
@lubegasimon lubegasimon assigned lubegasimon and unassigned jonludlam Apr 9, 2021
@kenichi-asai
Copy link

Is odoc documentation available somewhere now? I want to know whether odoc supports custom tags found in ocamldoc (or any other way to produce documents in two languages), because it seems customs tags in ocamldoc are no longer developed: ocaml/ocaml#6707

@Columbus240
Copy link

Columbus240 commented Jul 13, 2021

A concrete problem: odoc currently links to the syntax reference of ocamldoc, but doesn't accept precisely the same syntax. The differences should be explained somewhere (or be linked in the README if such a document already exists).

I found the following differences between the syntax reference and odoc v1.5.3:

  • ocamldoc allows arbitrary heading levels, but odoc only allows levels from 0 to 5.
  • odoc doesn't interpret target-specific formatting as ocamldoc did. Namely {%latex: ...%} throws a warning and instead of ignoring the contents of the braces, the contents are printed.

Edit: The second point is fixed in the master branch. odoc now behaves like ocamldoc in this respect.

@asavahista asavahista mentioned this issue Sep 23, 2021
@jonludlam
Copy link
Member Author

Fixed by #733. Or at least, the situation is better than it was!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants