Closed Artimisia closed 9 years ago
Will fix shortly.
On Apr 27, 2015, at 13:23, Artimisia notifications@github.com wrote:
Just heard from a user (and confirmed) - I cannot generate either a "brief PDF" or a full PDF schedule. The red "We're sorry, but something went wrong" message appears. According to the user - this is a problem with the custom schedules too.
— Reply to this email directly or view it on GitHub.
Thanks!
Sent from my iPhone
On Apr 27, 2015, at 8:58 PM, Michael Graff notifications@github.com wrote:
Will fix shortly.
On Apr 27, 2015, at 13:23, Artimisia notifications@github.com wrote:
Just heard from a user (and confirmed) - I cannot generate either a "brief PDF" or a full PDF schedule. The red "We're sorry, but something went wrong" message appears. According to the user - this is a problem with the custom schedules too.
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHub.
Sorry that shortly took 19 days. I think it works now.
I had to select Arial fonts (which will not be good for printing; we should use Arial for online looking but a serif font to print in the book as it's more readable at a smaller size) and I had to find ones which supported Unicode properly.
Thank you! I am headed out for a good bit of the day, but with a quick check it all seems to be working. I will let the person know. -Artis
On May 16, 2015, at 10:20 PM, Michael Graff notifications@github.com wrote:
Sorry that shortly took 19 days. I think it works now.
I had to select Arial fonts (which will not be good for printing; we should use Arial for online looking but a serif font to print in the book as it's more readable at a smaller size) and I had to find ones which supported Unicode properly.
— Reply to this email directly or view it on GitHub https://github.com/skandragon/thing/issues/106#issuecomment-102722342.
Just heard from a user (and confirmed) - I cannot generate either a "brief PDF" or a full PDF schedule. The red "We're sorry, but something went wrong" message appears. According to the user - this is a problem with the custom schedules too.