GNOME Bugzilla – Bug 371043
Documentation maintenance
Last modified: 2011-04-13 18:19:15 UTC
Is the Evince team maintaining its docs itself, or does it want the GDP to handle them? If the latter, please set the default assignee for documentation bugs to gnome-user-docs-maint@gnome.bugs
We are maintaining them ourselves right now. Currently the docs are outdated, but rewriting them has been on my TODO list for a while.
Reinout and I are rewriting the docs.
*** Bug 371440 has been marked as a duplicate of this bug. ***
Wouter, any news on this task ?
Not really, sorry. Too many other things to do :)
I've started working on new Mallard docs for Evince. Some initial work can be found here: http://gitorious.org/evince-mallard-docs Review/comments/suggestions appreciated.
The "noprint.page" is not required since this setting has been the default for quite a while now: http://gitorious.org/evince-mallard-docs/evince-mallard-docs/blobs/master/noprint.page
Thanks for the feedback, Wouter. I'm not quite sure which setting you're referring to, though - do you mean that evince automatically overrides PDF printing restrictions?
Yes, since more than two years. See bug #382700 for more information.
Thanks Wouter. Are there any other features that I've missed that users should be aware of? Hidden/difficult-to-discover features in particular. Also, are there any bugs or support requests that you frequently see? They should be covered too.
Amendments made to the docs. These are ready for review.
(In reply to comment #11) > Amendments made to the docs. These are ready for review. Are the docs in gitorious supposed to be distributed with Evince 2.32? If so, the docs are still outdated feature-wise. We need to add documentation for the new features, most notably Annotation support and probably also SyncTeX support.
The docs currently target 2.30 because I don't have a build for 2.32 yet. They are intended to be distributed with 2.32 though. Annotations are on my todo list, but I strongly suggest committing these docs soon, to give the translators some time to work on them for 2.32. When the Annotations topics are added, only index.page should see any string changes. Likewise with SyncTeX topics. It's possible that there will be other minor string changes to catch up with 2.32 UI changes too.
Phil, the documentation looks great. I like the friendly style of writing very much. However, there some wrong info. I quote: "Some documents are not searchable because the original text of the document has been converted into a different format. For example, many PostScript (.ps) files are not searchable". If I understand correctly (other dev confirm this please). The search feature in evince is only implemented for "non-scanned" pdf files (some pdf have pages that are just images and therefore are not searchable, but NO Postscript file is searchable in Evince). "If the search bar says 0 found on this page, and clicking the Find Next button has no effect, then your search word has not been found in the document". Well, this phrase reflects an small usability bug (IMO) in Evince. When the search bar says 0 found on this page, clicking will have not effect. So the message in the search bar should say "not found" or something similar. I added bug #626334 to track this in Evince, and if this get accepted, we could erase this hole paragraph from the doc. * The Search feature is only available for pdf files. so
Closing this as the new mallard documentation has already been merged.