Fix documentation generation #3
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This allows things like hGetContents to actually use the files. It also means that the author's name is no longer encoded in 4 different ways.
jorgecunhamendes
added a commit
that referenced
this pull request
Jan 10, 2014
Fix documentation generation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to the file encoding, hscolour could not run on the source files and Hackage calls hscolour when generating documentation so the docs could not get generated. See this Hackage build log for details.
Turning the files into UTF-8 (and doing some small fix-ups by hand) fixes the issue.
PS: The output seems mangled in the small diffs on this page but you can check the files and/or generated source and it renders properly.