[Groff] Undocumended .if "feature"

2015-07-08 Thread carsten . kunze
Hello, in a manual page I found the commands .ie '\*[.T]'utf8' . ds Un \[cu] .el . ds Un U . The .ie and .el lines don't end with a backslash. Nethertheless this works with groff. Is this documented? If not this is a misleading "feature" since it doesn't tell the author that this code has

Re: [Groff] MIssion statement

2015-07-08 Thread Peter Schaffter
Hi, all. > > Are you aware that somenthing has happened to the mission statement > > PDF and that it is totally undreadable? > > > > http://www.gnu.org/software/groff/groff-mission-statement.pdf > > Uh, oh, no, this is new to me. Thanks for the report! > > Peter? I've been away for a couple of

Re: [Groff] MIssion statement

2015-07-08 Thread Chad Roseburg
It looks scrambled in Chrome's PDF viewer but looks fine if you download it and view it with Adobe Reader, Evince ...etc. On Wed, Jul 8, 2015 at 11:30 AM, Peter Schaffter wrote: > Hi, all. > > > > Are you aware that somenthing has happened to the mission statement > > > PDF and that it is totall

Re: [Groff] MIssion statement

2015-07-08 Thread Dave
On 7/8/15, Chad Roseburg wrote: > It looks scrambled in Chrome's PDF viewer but looks fine if you download it > and view it with Adobe Reader, Evince ...etc. When I view it with gv 3.7.3, all I see are headers, no body text. When I attempt to view it with acroread 9.5.5, the program locks up.

Re: [Groff] MIssion statement

2015-07-08 Thread Ralph Corderoy
Hi Peter, > > > http://www.gnu.org/software/groff/groff-mission-statement.pdf ... > When I check the link, the PDF is fine. It hasn't been touched > since it was uploaded. Anybody else getting "totally unreadable"? To confirm we're all using the same bytes, $ curl -sS http://www.gnu.org/so

Re: [Groff] MIssion statement

2015-07-08 Thread Keith Marshall
On 08/07/15 19:30, Peter Schaffter wrote: > Hi, all. > >>> Are you aware that somenthing has happened to the mission statement >>> PDF and that it is totally undreadable? >>> >>> http://www.gnu.org/software/groff/groff-mission-statement.pdf >> >> Uh, oh, no, this is new to me. Thanks for the repo

Re: [Groff] MIssion statement

2015-07-08 Thread Mike Bianchi
On Wed, Jul 08, 2015 at 12:14:10PM -0700, Chad Roseburg wrote: > It looks scrambled in Chrome's PDF viewer but looks fine if you download it > and view it with Adobe Reader, Evince ...etc. I have reading found PDFs are sometimes problematic in Linux. They are not the "just works" documents they on

Re: [Groff] MIssion statement

2015-07-08 Thread Dale Snell
On Wed, 08 Jul 2015 20:29:28 +0100, in message 20150708192928.4dc4828...@orac.inputplus.co.uk, Ralph Corderoy wrote: > Hi Peter, > > > > > http://www.gnu.org/software/groff/groff-mission-statement.pdf > ... > > When I check the link, the PDF is fine. It hasn't been touched > > since it was uploa

Re: [Groff] MIssion statement

2015-07-08 Thread Denis M. Wilson
xpdf also works, but produces several occurrences of Error: Illegal entry in bfrange block in ToUnicode CMap On Wed, 8 Jul 2015 14:30:42 -0400 Peter Schaffter wrote: > Hi, all. > > > > Are you aware that somenthing has happened to the mission > > > statement PDF and that it is totally undreada

[Groff] Mission statement PDF

2015-07-08 Thread Peter Schaffter
I've fixed the offending line in the Mission Statement pdf and tested it with a batch of viewers. Seems to be working fine. Uploaded the .pdf to the groff webpage. -- Peter Schaffter http://www.schaffter.ca

Re: [Groff] MIssion statement

2015-07-08 Thread Dave
On 7/8/15, Mike Bianchi wrote: > I have reading found PDFs are sometimes problematic in Linux. True though that may be in general, a PDF containing a mission statement for a GNU package really ought to be readable with common FLOSS packages. Further, if (as I presume) the document was generated

Re: [Groff] Mission statement PDF

2015-07-08 Thread Dave
On 7/8/15, Peter Schaffter wrote: > I've fixed the offending line in the Mission Statement pdf and > tested it with a batch of viewers. Seems to be working fine. Works for me now in both the packages that failed before. Thanks!

Re: [Groff] Mission statement PDF

2015-07-08 Thread Deri James
On Wed 08 Jul 2015 17:56:10 Peter Schaffter wrote: > I've fixed the offending line in the Mission Statement pdf and > tested it with a batch of viewers. Seems to be working fine. > Uploaded the .pdf to the groff webpage. How fixed? A) Editing line identified by Tadziu by hand, or B) Regenerating

Re: [Groff] MIssion statement

2015-07-08 Thread James Cloos
> "MB" == Mike Bianchi writes: MB> Occasionally I use the hack of extracting the PostScript with MB> pdf2ps(1) and then use ps2pdf12(1) to turn it back into PDF. If you want ghostscript to re-create a pdf, you can pass the pdf directly to ps2pdf. -JimC -- James Cloos OpenPGP: 0x99

Re: [Groff] MIssion statement

2015-07-08 Thread James Cloos
> "RC" == Ralph Corderoy writes: RC> To confirm we're all using the same bytes, RC> $ curl -sS http://www.gnu.org/software/groff/groff-mission-statement.pdf | >> sha1sum RC> 93cc5719150cfa2a74fbd265e26cb3876529b4b6 - Has it been updated since this started? I get c2f7a1b7bd3eac6e7

Re: [Groff] Mission statement PDF

2015-07-08 Thread Peter Schaffter
Deri -- On Wed, Jul 08, 2015, Deri James wrote: > On Wed 08 Jul 2015 17:56:10 Peter Schaffter wrote: > > > I've fixed the offending line in the Mission Statement pdf > > How fixed? > > A) Editing line identified by Tadziu by hand, or > > B) Regenerating from original source with current tools?