When I click on PDF above problem, I only get blank page in new window. Why I can't print problems?
Thanks
created
last reply
- 9
replies
- 714
views
- 4
users
When I click on PDF above problem, I only get blank page in new window. Why I can't print problems?
Thanks
Now the problem set is too big, but before it was possible to compile the whole problem set to a single pdf.
We can find some editions with an Internet search
spoj classical filetype:pdf
This allows us (EB) to remind some old timings when Pyramid was the only cluster.
This could help us to find some images.
There's still some psetter that doesn't upload their images on spoj system, past shows that external storage is a fail.
===
For some problem I saw the comment : "serious psolver take a look at the pdf description"
as sometimes, for some old problems, the pdf description was cleaner than the html one, especially if some important
data were missing in html edition, but present on the pdf one. (I personally met only one case ; on an old problem ; some long time ago, so I don't remember the problem).
Now, for recent problems, the pdf is no more available, then only the html description is the law.
==
This thread could be archived, as I don't think the pdf will be again provided.
Beside that, it could be fine to provide a frozen snapshot of the whole problem sets, say every year.
And it should be possible to make a new snapshot that list :
1) modified old problems.
2) new problems of the year.
(and don't store redundant data)
Only for archive purpose. It's not very important, but maybe some people will find an interest.
(Past show us that it was helpful in some few cases)
Well, using PDF bootlet as backup for checking the changes in problems is not really the target way.
Instead there will be a feature which will allow EB members to see for every problem (with dates):
Are there any more uses for PDFs?
Excellent news ! Many thanks.
=
About pdf, I don't see any interest for new problems, nor recent ones.
=
One could add history of changes in description too. (But it's maybe difficult to implement)
Eg(a recent one) 1≤N<10^4, became 0≤N<10^4 , that can change some things !
=
More, it could be fine that a rss (or something similar, EB-only access) aggregate the history of all changes on spoj problem set, so we can 'check' very soon if something 'strange' or 'regular' happened and if psetter justified it or not, even on an 'old' problem.
=
Is it planned that EB/psetter comments can't be mutually edit, hidden or deleted ?
They can only delete their ones, or freeze the other (i.e. become un-deletable nor editable, only by admins)
I have an example of "apologies" of a psetter that delete them some few days/(hours?) after... (should we consider to accept those apologies in those conditions is another debate ; it's fine too to be forgotten for some mistakes ; nobody's perfect)
I really hope that it will 100% useless in fact, but as dissuasive it could be interesting.
I've added these ideas to the ticket. The first one seems too costly, though, but who knows.
EB will be able to do anything with all comments on main SPOJ. PS will be able to do anything with comments in his problems unless their author is an EB member. Is there a scenario in which this algorithm doesn't work?
Just to be fair, I though it could be nice that EB can't edit/delete psetter comments, as psetter will not be able. (reciprocity)
The only possible action could be "freeze" the comment, that make it undeletable by author. (eg some apologies disappeared from you know who ) (here too for reciprocity "freeze" could be done by EB or psetter)
"freeze" could be replaced by a "unfreeze" action to allow reverting.
[But this fair-reciprocity is only an option I thought about, it's not high priority I think]
===
When a problem have tons of comments it is painful to remove them, as we need several 'clic' per message and a refresh.
This discourage us to clean some problem comments. (I think)
It could be fine, if we (EB) could have a nicer list of comments on one page, with a check-box next to each comment,
and an action button like "delete selection". Mass Comment Destruction.
===
It's not the place here but I take the ball to ask a question.
What to do with a comment with a link to a code (ideOne most of time) ?
Even if it's a WA code, the real place for such a question should be the forum.
So the message should be edited by EB and replaced by "please see the notes below, and use forum".
Or should we let the comment as it is ? (I don't think so, but the question is open)
===
A nice option for comments could be :
* comments are by default given a lifetime of a week, after that time the comment is autodeleted, unless
* comment can be marked permanent by EB or psetter.
Why -> this will allow to let live such comments some few days, those who are nor useful nor useless.
Eg (recent ones)
I think it's a matter of personal preferences. I like PDF a lot, have several hundred SPOJ problems either printed or saved as PDF, but didn't make use of PDF recently as it mostly does not work any more. I would appreciate that PDF-feature, but I think I'm a bit old fashioned in that way (I like it to have a printed paper on my table with pencil in my hand ...).
That's a good idea. I've added it.
Suggested, thanks. That's a good one.
I am quite a radical person generally and thus I remove all such comments without even notifying users. But you can do whatever you feel like. We'll discuss the strategy when I finish some other work and we'll clean the comment section. Of course if you were willing to. If not, that's okay. On Polish SPOJ I've recently removed hundreds of useless comments and still over a thousand to go, I think.
I think that's risky. When all comments are cleaned it will be easier to manage them and remove useless ones on the go. And this feature won't be that necessary.
Thanks for your input, Francky!
@numerix - I've informed my superior about your view. We'll see (but I'm sceptical, to be honest). If that would be usefull, I'll make a tool for generating PDFs from problems that are formatted well enough. I like making SPOJ tools.