Closed hofbi closed 4 years ago
Removing the comments from latex definitions still keeps some blank character and keeps the style for alignment.
@emareg Maybe this is related with some UTF-8 encoding, but setting to UTF-8 as in the readme will break the travis build.
Switching the CI to docker will fix the issue mentioned above. I already created a container which works for the development build.
@emareg Currently the build fails for running in production mode which includes the hook for generating the TOC. Could you fix the TOC generator. This is the related error line
/srv/jekyll/_plugins/tex4tum_hooks.rb:273:in `partition': invalid byte sequence in US-ASCII (ArgumentError)
The error sounds like an encoding problem. I thought everything should be encoded and decoded as UTF-8. Is there something in the docker image that might read files as ASCII?
Not sure. I had to change <h1 class="text-primary">TeX4TUM – Interactive Knowledge Platform</h1>
to <h1 class="text-primary">TeX4TUM - Interactive Knowledge Platform</h1>
which was also an encoding error. Could be that there are more.
The gh-pages deployment build from travis contains strange latex comment at the beginning of each page. They have to be removed before we can use out deployment.
This images shows the diff between the correct build on the left and the build by travis on the right.
Once this is fixed we can remove the
docs
folder from master branch and change the sources for gh pages to gh-pages branch.