From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18385 invoked by alias); 29 Jan 2002 15:58:20 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 18347 invoked from network); 29 Jan 2002 15:58:16 -0000 Received: from unknown (HELO localhost.cygnus.com) (216.138.202.10) by sources.redhat.com with SMTP; 29 Jan 2002 15:58:16 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id A54C03D61; Tue, 29 Jan 2002 00:40:22 -0500 (EST) Message-ID: <3C5635C6.90409@cygnus.com> Date: Tue, 29 Jan 2002 07:58:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Jim Blandy Cc: Eli Zaretskii , gdb-patches@sources.redhat.com Subject: Re: [rfa/doco] Srink the overlay diagram References: <3C4C6FF4.7040108@cygnus.com> <3791-Tue22Jan2002111309+0200-eliz@is.elta.co.il> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00756.txt.bz2 > "Eli Zaretskii" writes: > >> Leave the text outside the @example, and instead put "@need NUMBER" >> before the @example which starts the diagram, where NUMBER is enough >> to allow for both the diagram and the text after it. I'd use 10000 >> for NUMBER, but if you can easily print that page after TeXing it, >> simply measure how many inches of vertical space does the diagram and >> the text take, and multiply that by 1000. > > > As to the original "what's that doing there?" question: It's a > caption. Diagrams often have explanatory text, outside of the main > flow of text. They tend to be just figure titles. > As to the formatting: anything that keeps that text immediately after > the diagram is fine It currently reads: ``To map an overlay, copy its code from the larger address space to the instruction address space. Since the overlays shown here all use the same mapped address, only one may be mapped at a time. This diagram shows a system with separate data and instruction address spaces. For a system with a single address space for data and instructions, the diagram would be similar, except that the program variables and heap would share an address space with the main program and the overlay area.'' which to me is a little strange. ``This diagram ...'' is the text straight after the diagram (but appears on the following page in the printed document). I think: @example @group
@anchor{x-spot the title} @end end Diagram @xref{x-spot the title} .... would work better. Andrew -- PS: I've adjusted the diagram to have different size overlays. Also added an @c comment explaining that it was intentional. The reason for srinking the diagram height was to get it all onto one page. PPS: Suggestions for a figure title welcome.