Could't agreement more: the two columns are a nightmare. They may have just 
fine in the printed edition 20 years ago but they are no good in an electronic 
version...

I'm puzzled by the strong reactions this thread evokes. To me it is so obvious 
that the current format does not work as a PDF (or similar format). The various 
suggestions and ideas just show that need some kind of dynamic, configurable 
format with several ways to locate and display the information (an app is an 
excellent idea). But It amazes me that there are actually people that think the 
current format is just fine and doesn't need any improvement...

Sent from my new iPad

> On Nov 14, 2014, at 18:44, Martin Packer <[email protected]> wrote:
> 
> Two column format is fine, literally, on paper. But for navigating as a 
> PDF it's a nightmare. GDDM manuals are similarly two-column and it drives 
> me nuts.
> 
> Cheers, Martin
> 
> Martin Packer,
> zChampion, Principal Systems Investigator,
> Worldwide Banking Center of Excellence, IBM
> 
> +44-7802-245-584
> 
> email: [email protected]
> 
> Twitter / Facebook IDs: MartinPacker
> Blog: 
> https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker
> 
> 
> 
> From:   Tom Marchant <[email protected]>
> To:     [email protected]
> Date:   14/11/2014 17:36
> Subject:        Re: Redesigning the Principles of Operation Manual
> Sent by:        IBM Mainframe Assembler List 
> <[email protected]>
> 
> 
> 
>> On Fri, 14 Nov 2014 09:03:59 -0500, Tony Thigpen wrote:
>> 
>> After thinking about this for a few days, the biggest 'complaint' I have
>> with the POP is the two columns. It makes me have to scroll up and down
>> just to read the end of the paragraph that started at the bottom of the
>> left side.
> 
> Some of us like it in two columns, some hate it. I happen to be in the 
> former group.
> 
>> The second issue is the way the "if 24bit, if 31 bit, if 64bit"
>> statements read.
> 
> For myself, I have no difficulty with the "for L, ... for LH, ..." kinds 
> of statements.
> 
>> Suggestions:
>> 1) Make each group of instructions (like ADD) start on a new page.
> 
> Not necessary, IMO
> 
>> 2) Use two columns for the instruction bit pictorials. Put 24/31 bit on
>> the left and 64 bit on the right.
> 
> Yuck.
> 
>> 3) Use a full width paragraph for things common to both 24/31 bit and 64
>> bit.
>> 4) Use the left column for 24/31 bit specifics and the right column for
>> 64 bit specifics. These groups are side by side for the same 'subject'.
>> If there is no 64 bit specifics, then leave a gap in the right side.
> 
> I really don't like this.
> 
>> 5) If possible, consider placing the simple examples directly after the
>> instructions.
> 
> Clutter. Please don't.
> 
> Clearly, there is no consensus here that any of the proposed changes are a 
> good idea.
> 
> -- 
> Tom Marchant
> 
> 
> 
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number 
> 741598. 
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------

Reply via email to