-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Binary reference files build system #2014
Conversation
NB: No idea why travis failed, but this has little to do with changes proposed here... |
@lierdakil Travis fails because of #2013 which depends on jgm/highlighting-kate#64 It would be fixed until either a new |
@ShabbyX, apparently, there is a new version of |
@lierdakil yes, John was a step ahead of us |
Triggered a rebuild by reopening PR. Let's see if it works now. |
This looks good. But when I tried to compile your branch, it didn't quite work. When I tried to open the generated files I switched back to master, and found that So, I think a recent commit involving this must have broken it. I'm not sure about the odt, because the reference.odt in master opens just fine, so maybe there is some additional problem with your build script. |
More on this: the error I have in master when I try to open |
Clue:
I see the problem, and I've got the fix. - archive <-
- getDirectoryContents "."
- >>= addFilesToArchive [OptRecursive] emptyArchive
+ archive <- addFilesToArchive [OptRecursive] emptyArchive ["."] I'll go ahead and merge this with this change. |
I have pushed these changes. Closing. Will open a new issue about the footnote issue in reference.docx. |
Thank you. And sorry about the mess. |
As in https://groups.google.com/forum/#!topic/pandoc-discuss/i9lconsh0yw
What it is:
A simple cabal post-build hook that zip-archives unpacked data for
data/reference.docx
anddata/reference.odt
. No additional dependencies, should work on all target platforms.Why:
I firmly believe this will greatly simplify working with reference files for binary formats, since most of the work on these is done by-hand anyway (to my experience, that is). As an added benefit, it offers proper revision-tracking, instead of "binary file differs".
All relevant code is in lierdakil/pandoc@4d1267a.