Hey Martin,
- thanks a lot for the very detailed reply. I appreciate the great
efforts your team has made, and I understand that it's hard to keep
everything in check especially on a large scale. :)
I dug further into the issue, and eventually, it seems to be a problem
in the communication betwee
On 09/05/2017 10:35 AM, Nan Xiao wrote:
Hey Kasper,
- I really appreciate your help. Although it didn't help answer the
question directly, I think it would still be necessary to clarify
some facts:
1. I agree that using "non-standard fonts" could bring better aesthetics
for a particula
Hey Kasper,
- I really appreciate your help. Although it didn't help answer the
question directly, I think it would still be necessary to clarify
some facts:
1. I agree that using "non-standard fonts" could bring better aesthetics
for a particular group of people -- maybe not everyone. But
Build errors like these (related to processing of vignettes) happens
occasionally. I _strongly_ suggests not not using non-standard fonts or
advanced layout features. The small advantage of this (better aesthetics
according to the package writer, but not always according to everyone who
reads it)
Dear BioC,
- I see some very recent build errors for my packages (vignettes) which
use Google Fonts:
pandoc: Could not fetch
https://fonts.googleapis.com/css?family=Alegreya+Sans:400,400i,700
TlsExceptionHostPort (HandshakeFailed Error_EOF) "fonts.googleapis.com"
443
For example
https://biocondu
