date:20130701

Bug#714439: poppler-data: pdf viewer, problem displaing pages, gdrive and windows acrobat work correctly

2013-07-01 Thread Alessandro Danzo

Ok, sorry I thought this package could be the problem in rendering the
page, better you re-route me to correct package expert :)

Thank you very much


2013/7/1 Hideki Yamane henr...@debian.or.jp

 Hi,

 On Sun, 30 Jun 2013 22:06:39 +0200
 Alessandro Danzo danzo@gmail.com wrote:
  The problem is the displaying of some pdf pages, it happened also in the
  previously attached PDF.
 
  The first page blinks for a fraction of second and then disappears, I can
  see it when getting back from second page to the first one.

  Okay,
   - evince, okular: not good, first page is blank
   - gv, imagemagick: ok


  But poppler-data is just a package to mapping only Chinese/Japanese/Korean
  character data to show in PDF, it seems that not related to this problem.
  I'll assign other package, okay?


 --
 Regards,

  Hideki Yamane henrich @ debian.or.jp/org
  http://wiki.debian.org/HidekiYamane

Bug#714232: tsort manual page does not describe input format

2013-07-01 Thread Bob Proulx

brian m. carlson wrote:
Bob Proulx wrote:
This illustrates a basic philosophical difference between GNU systems
and traditional Unix systems. In a traditional Unix system the
standard for documentation was the man page. Mostly because there
wasn't anything better. But as GNU is not Unix the GNU system
vision was to improve upon Unix. One area of improvement was
documentation. Man pages have been around for a very long time but
they also have a lot of drawbacks. It isn't suitable for printing as
a book. There is no linking between manuals. Other things.
Therefore in the upstream GNU system the preferred documentation
format is texinfo documentation which was specifically designed for
those needs.

I personally think man pages are fine for printing. groff formats them
very nicely indeed.

Note that I said printing as a book and man pages don't print well
as books. They print fine as reference pages.

But I'm aware of the philosophical difference between Debian and the
GNU project. I tend to agree with Debian on this one, and I far
prefer man pages over info documents.

Fair enough. As they say, there is no accounting for taste. :-)

I don't view info as an improvement on man, except maybe that its
HTML support is better.

I strongly disagree. Info is a huge improvement over man pages. Man
pages make good quick reference pages. But man pages are not well
suited to other types of documentation such as user guides and books.

On a Debian system that command will give you access to the full tsort
manual. If you don't like the default 'info' (because perhaps you are
a vi key user) then you may also use 'pinfo' or 'info --vi-keys'
instead to get vi-style keybinding.

pinfo coreutils 'tsort invocation'
info --vi-keys coreutils 'tsort invocation'

I honestly avoid info if at all possible. I was not aware of --vi-keys,
but even with that option, the keybindings are bizarre (like the fact
that Page Up and Page Down don't stop at the top of the page) which
makes it miserable to work with. pinfo's keybindings are not much
better.

Perhaps a vi user could improve the keybindings for those programs?

(Also, the pinfo invocation you provided doesn't actually work.)

Oh! Sorry. It does get to the coreutils section but not to tsort. I
guess it needs the node set as an option. This works:

pinfo coreutils --node='tsort invocation'

And 'j' and 'k' go up and down. It stops at the top and bottom of the
page. PageUp and PageDown work and both stop at the top and bottom of
the page. (shrug)

I probably should mention that the latest upstream version of the
documetantion is also available online as web pages:

http://www.gnu.org/software/coreutils/manual/

And tsort in particular is here:

http://www.gnu.org/software/coreutils/manual/html_node/tsort-invocation.html#tsort-invocation

But the latest upstream version and any particular packaged version
may be different. Therefore I still prefer to use the installed
documentation that matches the installed version of the programs.

The standards documents are also online.

http://pubs.opengroup.org/onlinepubs/009695399/utilities/tsort.html

And just because I will note that the FreeBSD man pages are also
available online too. A useful resource for an alternate free(dom)
implementation.

http://www.freebsd.org/cgi/man.cgi

I much prefer man and groff because they actually use my pager, which I
can configure with whatever keybindings and highlighting I'd like.

A good point.

I can go on and on about the reasons I don't like info, but that really
isn't relevant to this bug report.

Your bug report implies that there isn't any documentation on the
tsort input format. But that is incorrect since there *is*
documentation on it. The documentation is in texinfo format. And it
describes the input format that you are wishing to know about.

My bug report indicates clearly that the *manual page* is inadequate
because it does not specify the input format. I did not comment on the
info documentation, mostly because I don't care very much about its
adequacy.

Well... The man page documents that the full documentation is
elsewhere. It describes how to access it. The access does work. The
documentation is there. The information you are asking for is there.

It is frustrating to me that you are dismissing info out of hand due
to subjectively not liking it. That type of reasoning is symetrical
but opposite to the GNU reasoning for requiring info documentation.
But there is one difference that breaks the symmetry. The upstream
primary documentation format exists in info format not man format. To
do anything else requires work to do something else. So far no one
has decided to replace the upstream GNU man pages with something
different and continuously do the work keep them updated as the
programs change. That would be an unreasonable amount of effort.

1 2 3 >

1 - 100 of 290 matches

Mail list logo