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

PDF manual has wrong references #7843

Closed
vicuna opened this issue Aug 31, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@vicuna
Copy link

commented Aug 31, 2018

Original bug ID: 7843
Reporter: matt
Assigned to: @Octachron
Status: resolved (set by @Octachron on 2018-09-02T17:12:04Z)
Resolution: fixed
Priority: normal
Severity: minor
Platform: na
OS: na
OS Version: na
Version: 4.07.0
Fixed in version: 4.08.0+dev/beta1/beta2
Category: ocamldoc
Monitored by: @nojb

Bug description

Example:

24.13 Module Format : Pretty-printing.
This module implements a pretty-printing facility to format values within [24.13] and [24.13] com-
bined with a set of [24.13]. The pretty-printer splits lines at specified [24.13], and indents lines
according to the box structure. Similarly, [24.13] can be used to decouple text presentation from
its contents.

I did not investigate more than that: opened this ticket to not forget the problem.

@vicuna

This comment has been minimized.

Copy link
Author

commented Aug 31, 2018

Comment author: @Octachron

This seems to be a problem with the latex backend of ocamldoc which has trouble with {{!ref}text}.

@vicuna

This comment has been minimized.

Copy link
Author

commented Aug 31, 2018

Comment author: @Octachron

See #2013 for a potential fix.

@vicuna

This comment has been minimized.

Copy link
Author

commented Sep 2, 2018

Comment author: @Octachron

The PR above has been merged in the dev version of the compiler, the missing text should reappear in time for 4.08 .

@vicuna vicuna closed this Sep 2, 2018

@vicuna vicuna added the ocamldoc label Mar 14, 2019

@vicuna vicuna added the bug label Mar 20, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.