From MAILER-DAEMON Tue Jan 02 19:44:42 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H1uFG-0002Yd-NQ for mharc-help-texinfo@gnu.org; Tue, 02 Jan 2007 19:44:42 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H1uFF-0002YD-67 for help-texinfo@gnu.org; Tue, 02 Jan 2007 19:44:41 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H1uFC-0002Xh-O1 for help-texinfo@gnu.org; Tue, 02 Jan 2007 19:44:39 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H1uFC-0002Xe-Ik for help-texinfo@gnu.org; Tue, 02 Jan 2007 19:44:38 -0500 Received: from [64.34.169.74] (helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H1uFB-0002cb-Dt for help-texinfo@gnu.org; Tue, 02 Jan 2007 19:44:38 -0500 X-Envelope-From: karl@freefriends.org X-Envelope-To: help-texinfo@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l030iYH04256; Tue, 2 Jan 2007 18:44:34 -0600 Date: Tue, 2 Jan 2007 18:44:34 -0600 Message-Id: <200701030044.l030iYH04256@f7.net> From: karl@freefriends.org (Karl Berry) To: per@bothner.com In-Reply-To: <4598690E.3010701@bothner.com> Cc: help-texinfo@gnu.org Subject: [help-texinfo] Re: xml id characters X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jan 2007 00:44:41 -0000 I see little point in emitting DocBook-SGML. Right. makeinfo only emits docbook/xml (these days), as far as I know. So the SGML rule doesn't matter. I.e. colons are not allowed for "xml:id" attributes and that is probably a good idea for DocBook "id" attributes too. Ok. I guess I will change the code accordingly. How well does texinfo handle Unicode characters? As far as makeinfo goes, it just passes along whatever it sees in the input to the output, and dumps the @documentencoding value into the output as well. It doesn't try to interpret characters in any way. No doubt it'll be a problem at some point, but it seems to have more or less sufficed so far. Thanks much for the info. Karl From MAILER-DAEMON Tue Jan 02 20:03:02 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H1uX0-0006T9-K0 for mharc-help-texinfo@gnu.org; Tue, 02 Jan 2007 20:03:02 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H1uWy-0006S7-K1 for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:03:00 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H1uWu-0006Ro-18 for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:03:00 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H1uWt-0006Rl-Vm for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:02:55 -0500 Received: from [208.97.132.83] (helo=spunkymail-a2.dreamhost.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H1uWt-0006Hh-Cp for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:02:55 -0500 Received: from [192.168.1.10] (adsl-216-102-199-253.dsl.snfc21.pacbell.net [216.102.199.253]) by spunkymail-a2.dreamhost.com (Postfix) with ESMTP id 1523F8797A; Tue, 2 Jan 2007 17:02:49 -0800 (PST) Message-ID: <459B0101.5080504@bothner.com> Date: Tue, 02 Jan 2007 17:04:01 -0800 From: Per Bothner User-Agent: Thunderbird 1.5.0.9 (X11/20061219) MIME-Version: 1.0 To: Karl Berry References: <200701030044.l030iYH04256@f7.net> In-Reply-To: <200701030044.l030iYH04256@f7.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: help-texinfo@gnu.org Subject: [help-texinfo] Re: xml id characters X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jan 2007 01:03:00 -0000 Karl Berry wrote: > How well does texinfo handle Unicode characters? > > As far as makeinfo goes, it just passes along whatever it sees in the > input to the output, and dumps the @documentencoding value into the > output as well. It doesn't try to interpret characters in any way. > No doubt it'll be a problem at some point, but it seems to have more or > less sufficed so far. Of course you have to known the encoding if you want to check validity of base attributes, though for id attributes I guess you can cheat and assume that any bytes with the high bit set are probably ok, at least in terms of conflicting with delimiters etc. Texinfo doesn't support UTF-8, according to the manual. That is arguably a problem. In fact, UTF-8 should probably be the default: It is the default for HTML, XML, and at least some GNU/Linux systems (including Fedora). -- --Per Bothner per@bothner.com http://per.bothner.com/ From MAILER-DAEMON Tue Jan 02 20:09:28 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H1udE-0000qp-GN for mharc-help-texinfo@gnu.org; Tue, 02 Jan 2007 20:09:28 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H1udC-0000qi-Sn for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:09:26 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H1udB-0000py-B3 for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:09:26 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H1udB-0000pv-58 for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:09:25 -0500 Received: from [213.41.140.150] (helo=reno.oxstone.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H1ud9-0007F1-HM for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:09:24 -0500 Received: from localhost (localhost [127.0.0.1]) by reno.oxstone.com (Postfix) with ESMTP id 135D615009B for ; Wed, 3 Jan 2007 02:09:21 +0100 (CET) Received: from reno.oxstone.com ([127.0.0.1]) by localhost (reno.oxstone.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02d1Od6NJ2FR for ; Wed, 3 Jan 2007 02:09:21 +0100 (CET) Received: by reno.oxstone.com (Postfix, from userid 1000) id 02B0A150047; Wed, 3 Jan 2007 02:09:21 +0100 (CET) Date: Wed, 3 Jan 2007 02:09:20 +0100 From: Nicolas Maufrais To: help-texinfo@gnu.org Subject: Re: [help-texinfo] Some other bugs related to accents too Message-ID: <20070103010920.GA24237@oxstone.com> Mail-Followup-To: help-texinfo@gnu.org References: <20061229172603.GB31390@oxstone.com> <200612292337.kBTNb2406621@f7.net> <20061230000920.GB20054@oxstone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061230000920.GB20054@oxstone.com> X-Operating-System: GNU/Linux Debian User-Agent: Mutt/1.5.13 (2006-08-11) X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jan 2007 01:09:27 -0000 On Sat, Dec 30, 2006 at 01:09:20AM +0100, Nicolas MAUFRAIS wrote: > On Fri, Dec 29, 2006 at 05:37:02PM -0600, Karl Berry wrote: > > XML file. Here is what's in the French XML file: > > > > I'll take a look. > > Thanks! > > > Accents do not appear in the navigation panel of the French PDF manual, > > Yes, I mentioned that in my previous reply. > > Oh! You're right! Shame on me. :-/ > > > I know it is suboptimal, but fixing it seemed like it would be hard, > > and I can't look at it right now. If another TeX hacker would like to > > look at texinfo.tex about it, that would be great. > > Anyway, that's not that important. Fortunately, the letters do appear, > even if there's no accent. > > Thank you, Karl. > Your help is *really* appreciated. > > Nicolas Maufrais. Hello, I just downloaded the latest makeinfo CVS version: makeinfo (GNU texinfo) 4.8.90 I tried again, and indeed the accented characters are now displayed in the xml output! =) Thank you very much. However, I wonder if it's normal that, when this is written in the texinfo file: @documentlanguage fr @documentencoding ISO-8859-15 ... this is written in the XML file: 1st line: 6th line: As for the 1st line, it should be I think. We can easily fix this by editing the XML output though. Thank you, we'll now work on the contextual help! =) Nicolas Maufrais. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~ BOYCOTT SUSE & NOVELL (C)(TM)(R) MICRO$OFT ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From MAILER-DAEMON Tue Jan 02 20:14:34 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H1uiA-0002rK-BD for mharc-help-texinfo@gnu.org; Tue, 02 Jan 2007 20:14:34 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H1ui7-0002pD-3O for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:14:31 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H1ui5-0002oF-JL for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:14:30 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H1ui5-0002oB-9B for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:14:29 -0500 Received: from [64.34.169.74] (helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H1ui4-000804-Vh for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:14:29 -0500 X-Envelope-From: karl X-Envelope-To: help-texinfo@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l031ERo13849; Tue, 2 Jan 2007 19:14:27 -0600 Date: Tue, 2 Jan 2007 19:14:27 -0600 Message-Id: <200701030114.l031ERo13849@f7.net> From: karl@freefriends.org (Karl Berry) To: e.conti@gmx.net Subject: Re: [help-texinfo] Some other bugs related to accents too In-Reply-To: <20070103010920.GA24237@oxstone.com> Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jan 2007 01:14:32 -0000 As for the 1st line, it should be I think. Are you writing to stdout by chance? I think if you write to a file, the encoding will appear. At least it does for me. From MAILER-DAEMON Tue Jan 02 20:24:22 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H1ure-0001z6-2s for mharc-help-texinfo@gnu.org; Tue, 02 Jan 2007 20:24:22 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H1urc-0001yh-E2 for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:24:20 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H1urc-0001yE-0H for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:24:20 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H1urb-0001yB-Qb for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:24:19 -0500 Received: from [213.41.140.150] (helo=reno.oxstone.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H1urb-0001UN-7M for help-texinfo@gnu.org; Tue, 02 Jan 2007 20:24:19 -0500 Received: from localhost (localhost [127.0.0.1]) by reno.oxstone.com (Postfix) with ESMTP id 7FCB715009B for ; Wed, 3 Jan 2007 02:24:17 +0100 (CET) Received: from reno.oxstone.com ([127.0.0.1]) by localhost (reno.oxstone.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w09jvhVTs35h for ; Wed, 3 Jan 2007 02:24:17 +0100 (CET) Received: by reno.oxstone.com (Postfix, from userid 1000) id 70391150047; Wed, 3 Jan 2007 02:24:17 +0100 (CET) Date: Wed, 3 Jan 2007 02:24:17 +0100 From: Nicolas Maufrais To: help-texinfo@gnu.org Subject: Re: [help-texinfo] Some other bugs related to accents too Message-ID: <20070103012417.GA532@oxstone.com> Mail-Followup-To: help-texinfo@gnu.org References: <20070103010920.GA24237@oxstone.com> <200701030114.l031ERo13849@f7.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200701030114.l031ERo13849@f7.net> X-Operating-System: GNU/Linux Debian User-Agent: Mutt/1.5.13 (2006-08-11) X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jan 2007 01:24:20 -0000 On Tue, Jan 02, 2007 at 07:14:27PM -0600, Karl Berry wrote: > As for the 1st line, it should be encoding="ISO-8859-15"?> I think. > > Are you writing to stdout by chance? I think if you write to a file, > the encoding will appear. At least it does for me. Karl, Here's what I did: /usr/local/bin/makeinfo_cvs --docbook --no-number-sections --no-warn cinelerra_cv_manual_fr.texi I just tried: /usr/local/bin/makeinfo_cvs --docbook --no-number-sections --no-warn -o cinelerra_cv_manual_fr.xml cinelerra_cv_manual_fr.texi But still no encoding specified in the XML output. I do not install makeinfo CVS. The make process fails, but the makeinfo CVS binary is made. So I manually copy the binary to /usr/local/bin/makeinfo_cvs and run it from there. That's strange indeed, because: - I notice that bug in the past - I then did some other test, and saw the encoding in the XML output However, I did some tests, and it's possible I did add manually the encoding in the XML output. Nicolas Maufrais. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~ BOYCOTT SUSE & NOVELL (C)(TM)(R) MICRO$OFT ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From MAILER-DAEMON Wed Jan 03 18:07:04 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H2FCJ-00055X-PR for mharc-help-texinfo@gnu.org; Wed, 03 Jan 2007 18:07:03 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H2FCH-00053i-Rt for help-texinfo@gnu.org; Wed, 03 Jan 2007 18:07:01 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H2FCE-00053H-Go for help-texinfo@gnu.org; Wed, 03 Jan 2007 18:07:01 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H2FCE-00053E-9e for help-texinfo@gnu.org; Wed, 03 Jan 2007 18:06:58 -0500 Received: from [64.34.169.74] (helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H2FCD-00062y-Ss for help-texinfo@gnu.org; Wed, 03 Jan 2007 18:06:58 -0500 X-Envelope-From: karl@freefriends.org X-Envelope-To: help-texinfo@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l03N6of21199; Wed, 3 Jan 2007 17:06:50 -0600 Date: Wed, 3 Jan 2007 17:06:50 -0600 Message-Id: <200701032306.l03N6of21199@f7.net> From: karl@freefriends.org (Karl Berry) To: per@bothner.com In-Reply-To: <459B0101.5080504@bothner.com> Cc: help-texinfo@gnu.org Subject: [help-texinfo] Re: xml id characters X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jan 2007 23:07:02 -0000 though for id attributes I guess you can cheat Yes, that is definitely my plan, until some practical problem arises. Texinfo doesn't support UTF-8, according to the manual. Things have improved since 4.8, although they are far from ideal. I'll review the manual. Thanks, k From MAILER-DAEMON Wed Jan 03 18:34:55 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H2FdG-00025h-V4 for mharc-help-texinfo@gnu.org; Wed, 03 Jan 2007 18:34:55 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H2FdF-00024Z-01 for help-texinfo@gnu.org; Wed, 03 Jan 2007 18:34:53 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H2FdA-00023a-Gd for help-texinfo@gnu.org; Wed, 03 Jan 2007 18:34:52 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H2FdA-00023X-Bp for help-texinfo@gnu.org; Wed, 03 Jan 2007 18:34:48 -0500 Received: from [213.41.140.150] (helo=reno.oxstone.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H2Fd9-0002Is-5u for help-texinfo@gnu.org; Wed, 03 Jan 2007 18:34:48 -0500 Received: from localhost (localhost [127.0.0.1]) by reno.oxstone.com (Postfix) with ESMTP id 5EB561500E0 for ; Thu, 4 Jan 2007 00:34:45 +0100 (CET) Received: from reno.oxstone.com ([127.0.0.1]) by localhost (reno.oxstone.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iPSmpwZF2oBt for ; Thu, 4 Jan 2007 00:34:45 +0100 (CET) Received: by reno.oxstone.com (Postfix, from userid 1000) id 4E2E41500CF; Thu, 4 Jan 2007 00:34:45 +0100 (CET) Date: Thu, 4 Jan 2007 00:34:45 +0100 From: Nicolas Maufrais To: help-texinfo@gnu.org Message-ID: <20070103233445.GA7931@oxstone.com> Mail-Followup-To: help-texinfo@gnu.org References: <20070103010920.GA24237@oxstone.com> <200701030114.l031ERo13849@f7.net> <20070103012417.GA532@oxstone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070103012417.GA532@oxstone.com> X-Operating-System: GNU/Linux Debian User-Agent: Mutt/1.5.13 (2006-08-11) Subject: [help-texinfo] Country code and encoding in Docbook output: solution X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jan 2007 23:34:53 -0000 Hello, I did some tests about the encoding missing in the French XML manual, and the language code not being copied into. Here's my conclusion: The following commands: @documentlanguage (country code) @documentencoding (encoding) have to be located on a line below @setfilename xyz For example: @setfilename cinelerra_cv_manual_fr.info @documentencoding ISO-8859-15 @documentlanguage fr And then, everything's properly set in the XML output: ... So, if you want to produce a Docbook file from a texinfo file whose language and encoding isn't English and US-ASCII, don't forget to use those 2 commands and put them just below the @setfilename command. The place where they should be isn't explained in the texinfo manual. Nicolas Maufrais. On Wed, Jan 03, 2007 at 02:24:17AM +0100, Nicolas MAUFRAIS wrote: > On Tue, Jan 02, 2007 at 07:14:27PM -0600, Karl Berry wrote: > > As for the 1st line, it should be > encoding="ISO-8859-15"?> I think. > > > > Are you writing to stdout by chance? I think if you write to a file, > > the encoding will appear. At least it does for me. > > Karl, > > Here's what I did: > /usr/local/bin/makeinfo_cvs --docbook --no-number-sections --no-warn > cinelerra_cv_manual_fr.texi > > I just tried: > /usr/local/bin/makeinfo_cvs --docbook --no-number-sections --no-warn -o > cinelerra_cv_manual_fr.xml cinelerra_cv_manual_fr.texi > > But still no encoding specified in the XML output. > > I do not install makeinfo CVS. The make process fails, but the makeinfo > CVS binary is made. So I manually copy the binary to > /usr/local/bin/makeinfo_cvs and run it from there. > > That's strange indeed, because: > - I notice that bug in the past > - I then did some other test, and saw the encoding in the XML output > However, I did some tests, and it's possible I did add manually the > encoding in the XML output. > > Nicolas Maufrais. > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ~ BOYCOTT SUSE & NOVELL (C)(TM)(R) MICRO$OFT ~ > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > _______________________________________________ > Texinfo home page: http://www.gnu.org/software/texinfo > help-texinfo@gnu.org > http://lists.gnu.org/mailman/listinfo/help-texinfo > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~ BOYCOTT SUSE & NOVELL (C)(TM)(R) MICRO$OFT ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From MAILER-DAEMON Sun Jan 14 08:23:45 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H65Kr-00007n-Av for mharc-help-texinfo@gnu.org; Sun, 14 Jan 2007 08:23:45 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H65Kp-00006J-37 for help-texinfo@gnu.org; Sun, 14 Jan 2007 08:23:43 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H65Kh-0008Vs-6c for help-texinfo@gnu.org; Sun, 14 Jan 2007 08:23:42 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H65Kg-0008Vp-VH for help-texinfo@gnu.org; Sun, 14 Jan 2007 08:23:35 -0500 Received: from [200.175.8.220] (helo=smtp5.pop.com.br) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H65Kc-0008LQ-EQ for help-texinfo@gnu.org; Sun, 14 Jan 2007 08:23:34 -0500 Received: from localhost (localhost [127.0.0.1]) by smtp5-1 (Postfix) with ESMTP id 6710D9379C for ; Sun, 14 Jan 2007 11:23:29 -0200 (EDT) Received: from smtp5.pop.com.br (localhost [127.0.0.1]) by smtp5 (WCVirscan) with SMTP id 000026ef45aa2ed1 ; Sun, 14 Jan 2007 11:23:29 -0300 Received: from filho1.server.net (200.175.183.4.dialup.gvt.net.br [200.175.183.4]) by smtp5 (Postfix) with ESMTP id DA1BC93788 for ; Sun, 14 Jan 2007 11:21:39 -0200 (EDT) From: Jorge Barros de Abreu Organization: Professor do Ensino =?iso-8859-1?q?M=E9dio?= To: help-texinfo@gnu.org Date: Sun, 14 Jan 2007 08:24:57 -0200 User-Agent: KMail/1.7.2 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_5TgqFnyKa5ENh63" Message-Id: <200701140824.57269.ficmatin01@solar.com.br> X-DCC-POPInternet-Metrics: dcc 1259; Body=1 Fuz1=1 Fuz2=1 Subject: [help-texinfo] descriptive.texi @node iso-8859-1 X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jan 2007 13:23:43 -0000 --Boundary-00=_5TgqFnyKa5ENh63 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Robert. In descriptive.texi (wrong) if: @menu * Defini@value{cedilha}@~oes para estatistica descritiva:: @end menu the output from texi2dvi is OK. But if the line is changed ( the correct form) to: @menu * Defini@value{cedilha}@~oes para estat@'istica descritiva:: @end menu texi2dvi not work and the maxima.pdf output is generated but the indexes in= =20 this file are broken. The correct maxma.pdf have 760 pages and the generate= d=20 file with indexes broken have 736 pages. I am working for now with the wrong form. It occurs also with stringproc.texi. Can you help me for use the correct form (estat@'istica) ? This opportunity also can be used to clean maxima.log output file from=20 texi2dvi command. If there is something that i can make to clean this file= =20 please tell to me. The maxima.log generated on my machine is attached in this message. Thanks. =2D-=20 Data Estelar 2454112,944306 http://usr.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. --Boundary-00=_5TgqFnyKa5ENh63 Content-Type: text/x-log; charset="iso-8859-1"; name="maxima.log" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="maxima.log" This is pdfeTeXk, Version 3.14159-1.10b-2.1 (Web2C 7.4.5) (format=pdfetex 2003.3.8) 14 JAN 2007 08:20 entering extended mode file:line:error style messages enabled. **\nonstopmode \input /tmp/t2d9219/src/maxima.texi (/tmp/t2d9219/src/maxima.texi (./texinfo.tex Loading texinfo [version 2002-06-04.06]: Basics, \bindingoffset=\dimen16 \normaloffset=\dimen17 \pagewidth=\dimen18 \pageheight=\dimen19 \outerhsize=\dimen20 \outervsize=\dimen21 \cornerlong=\dimen22 \cornerthick=\dimen23 \topandbottommargin=\dimen24 \headlinebox=\box16 \footlinebox=\box17 \margin=\insert252 \EMsimple=\toks13 \singlespaceskip=\skip18 \groupinvalidhelp=\toks14 \mil=\dimen25 \exdentamount=\skip19 \inmarginspacing=\skip20 pdf, \tempnum=\count27 \lnkcount=\count28 \filename=\toks15 \filenamelength=\count29 \pgn=\count30 \toksA=\toks16 \toksB=\toks17 \toksC=\toks18 \toksD=\toks19 \boxA=\box18 \countA=\count31 (/usr/share/texmf/pdftex/plain/misc/pdfcolor.tex) fonts, \sffam=\fam8 \textleading=\dimen26 \mainmagstep=\count32 \fontdepth=\count33 page headings, \titlepagetopglue=\skip21 \titlepagebottomglue=\skip22 \evenheadline=\toks20 \oddheadline=\toks21 \evenfootline=\toks22 \oddfootline=\toks23 tables, \tableindent=\dimen27 \itemindent=\dimen28 \itemmargin=\dimen29 \itemmax=\dimen30 \itemno=\count34 \multitableparskip=\skip23 \multitableparindent=\skip24 \multitablecolspace=\dimen31 \multitablelinespace=\skip25 \colcount=\count35 conditionals, indexing, \secondaryindent=\skip26 \partialpage=\box19 \doublecolumnhsize=\dimen32 sectioning, \chapno=\count36 \secno=\count37 \subsecno=\count38 \subsubsecno=\count39 \appendixno=\count40 \absseclevel=\count41 \secbase=\count42 \chapheadingskip=\skip27 \secheadingskip=\skip28 \subsecheadingskip=\skip29 toc, \tocfile=\write0 \contentsrightmargin=\skip30 \savepageno=\count43 \lastnegativepageno=\count44 \shortappendixwidth=\dimen33 \tocindent=\dimen34 environments, \errorbox=\box20 \lispnarrowing=\skip31 \envskipamount=\skip32 \circthick=\dimen35 \cartouter=\dimen36 \cartinner=\dimen37 \normbskip=\skip33 \normpskip=\skip34 \normlskip=\skip35 \lskip=\skip36 \rskip=\skip37 \tabw=\dimen38 \copyingbox=\box21 defuns, \defbodyindent=\skip38 \defargsindent=\skip39 \deftypemargin=\skip40 \deflastargmargin=\skip41 \parencount=\count45 macros, \paramno=\count46 \macname=\toks24 cross references, \auxfile=\write1 \savesfregister=\count47 \footnoteno=\count48 (/usr/share/texmf/tex/generic/misc/epsf.tex \epsffilein=\read1 \epsfframemargin=\dimen39 \epsfframethickness=\dimen40 \epsfrsize=\dimen41 \epsftmp=\dimen42 \epsftsize=\dimen43 \epsfxsize=\dimen44 \epsfysize=\dimen45 \pspoints=\dimen46 \epsfnoopenhelp=\toks25 ) \noepsfhelp=\toks26 localization, \nolanghelp=\toks27 \defaultparindent=\dimen47 and turning on texinfo input format.) (./maxima.aux ./maxima.aux:49: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:50: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:51: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:52: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:53: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:54: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:94: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:95: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:96: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:97: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:98: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:99: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:100: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:101: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:102: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:103: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:104: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:105: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:106: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:107: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:108: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:112: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:113: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:114: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:142: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:143: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:144: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:145: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:146: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:147: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:151: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:152: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:153: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:169: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:170: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:171: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:172: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:173: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:174: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:175: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:176: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:177: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:178: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:179: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:180: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:235: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:236: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:237: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:238: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:239: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:240: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:244: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:245: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:246: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:247: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:248: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:249: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:250: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:251: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:252: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:253: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:254: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:255: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:262: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:263: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:264: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:265: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:266: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:267: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:277: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:278: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:279: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:313: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:314: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:315: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:316: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:317: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:318: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:319: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:320: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:321: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:322: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:323: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:324: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:325: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:326: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:327: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:550: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:551: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:552: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:586: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:587: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:588: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:607: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:608: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:609: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:826: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:826: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:827: Undefined control sequence The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ./maxima.aux:827: Undefined control sequence (That makes 100 errors; please try again.) No pages of output. --Boundary-00=_5TgqFnyKa5ENh63 Content-Type: text/plain; charset="iso-8859-1"; name="maxima_ok.texi" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="maxima_ok.texi" \input texinfo @c /maxima.texi/1.39/Mon Jan 8 04:17:51 2007/-ko/ @c Language: Brazilian Portuguese, Encoding: iso-8859-1 @c -*-texinfo-*- @c 2000-04-17 Jim Van Zandt Added header, @c info directory entry, reference to introduction chapter, and menu @c descriptions. Rearranged chapters. @c to update the menus do: @c (texinfo-multiple-files-update "maxima.texi" t t) @c @c texinfo-multiple-files-update will delete the detailed node listing! @c texinfo Coodinator Robert Dodier @c Portuguese Translator Jorge Barros de Abreu @c %**start of header @setfilename maxima.info @synindex vr fn @c @documentencoding ISO-8859-15 @documentencoding ISO-8859-1 @set cedilha @,{c} @set i_agu @'i @set I_agu @'I @set a_til @~a @set a_agu @'a @set o_til @~o @set mail @settitle Manual do Maxima @c %**end of header @setchapternewpage odd @ifinfo Esse @'e um Manual do Maxima no formato Texinfo Copyright 1994,2001 William F. Schelter @format START-INFO-DIR-ENTRY * Maxima: (maxima). Um sistema de @'algebra computacional. END-INFO-DIR-ENTRY @end format @end ifinfo @ifinfo @macro var {expr} <\expr\> @end macro @end ifinfo @titlepage @sp 10 @comment The title is printed in a large font. @center @titlefont{Manual do Maxima} @page @vskip 0pt plus 1filll Maxima @'e um sistema de @'algebra computacional, implementado em Lisp. Maxima @'e derivado do sistema Macsyma, desenvolvido no MIT nos anos de 1968 a 1982 como parte do Projeto MAC. MIT remanejou uma c@'opia do c@'odigo fonte do Macsyma para o Departamento de Energia em 1982; aquela vers@~ao @'e agora conhecida como Macsyma DOE. Uma c@'opia do Macsyma DOE foi mantida pelo Professor William F. Schelter da Universidade do Texas de 1982 at@'e sua morte em 2001. Em 1998, Schelter obteve permiss@~ao do Departamento de Energia para liberar o c@'odigo fonte do Macsyma DOE sob a Licen@value{cedilha}a P@'ublica GNU, e em 2000 ele iniciou o projeto Maxima no SourceForge para manter e desenvolver o Macsyma DOE, agora chamado Maxima. Notas de tradu@,{c}@~ao: Com o t@'ermino da tradu@,{c}@~ao inicia-se o processo de revis@~o da mesma. Est@'a aberta a temporada de ca@,{c}a aos erros de tradu@,{c}@~ao, erros de hifeniza@,{c}@~ao e de adequa@,{c}@~ao entre a linguagem matem@'atica inglesa e a linguagem matem@'atica brasileira. Caso voc@^e me envie alguma corre@,{c}@~ao ou melhoria a comunidade matem@'atica que utiliza o Sofware Livre lhe ficar@'a muito grata ( e n@'os, da equipe do Maxima, tamb@'em). O c@'odigo fonte deste documento encontra-se no formato texinfo. Para contribuir com a equipe do Maxima na tarefa de manter a tradu@,{c}@~ao para o portugu@^es sempre atualizada envie um e-mail para @value{mail}. Em caso de d@'uvida sobre algum trecho deste manual consulte o original ingl@^es. Caso sua d@'uvida persista ou tenha alguma sugest@~ao/aperfei@,{c}oamento/ cr@'{@dotless{i}}tica mande por e-mail para Jorge Barros de Abreu Mantenedores: @itemize @bullet @item Jaime E. Villate @item Mario Rodriguez @item Jorge Barros de Abreu @end itemize @end titlepage @summarycontents @contents @ifnottex @node Top, Introdu@value{cedilha}@~ao ao Maxima, (dir), (dir) @top @i{Maxima @'e um sistema de @'algebra computacional, implementado em Lisp.} Maxima @'e derivado do sistema Macsyma, desenvolvido no MIT nos anos de 1968 a 1982 como parte do Projeto MAC. MIT remanejou uma c@'opia do c@'odigo fonte do Macsyma para o Departamento de Energia em 1982; aquela vers@~ao @'e agora conhecida como Macsyma DOE. Uma c@'opia do Macsyma DOE foi mantida pelo Professor William F. Schelter da Universidade do Texas de 1982 at@'e sua morte em 2001. Em 1998, Schelter obteve permiss@~ao do Departamento de Energia para liberar o c@'odigo fonte do Macsyma DOE sob a Licen@value{cedilha}a P@'ublica GNU, e em 2000 ele iniciou o projeto Maxima no SourceForge para manter e desenvolver o Macsyma DOE, agora chamado Maxima. @i{Notas de tradu@,{c}@~ao:} Com o t@'ermino da tradu@,{c}@~ao inicia-se o processo de revis@~o da mesma. Est@'a aberta a temporada de ca@,{c}a aos erros de tradu@,{c}@~ao, erros de hifeniza@,{c}@~ao e de adequa@,{c}@~ao entre a linguagem matem@'atica inglesa e a linguagem matem@'atica brasileira. Caso voc@^e me envie alguma corre@,{c}@~ao ou melhoria a comunidade matem@'atica que utiliza o Sofware Livre lhe ficar@'a muito grata ( e n@'os, da equipe do Maxima, tamb@'em). O c@'odigo fonte deste documento encontra-se no formato texinfo. Para contribuir com a equipe do Maxima na tarefa de manter a tradu@,{c}@~ao para o portugu@^es sempre atualizada envie um e-mail para @value{mail}. Em caso de d@'uvida sobre algum trecho deste manual consulte o original ingl@^es. A se@,{c}@~ao "Pacotes adicionais" foi anexada ao manual recentemente (fevereiro/2006) e possui partes a serem traduzidas. Caso sua d@'uvida persista ou tenha alguma sugest@~ao/aperfei@,{c}oamen- to/cr@'itica mande por e-mail para Jorge Barros de Abreu Mantenedores: @itemize @bullet @item Jaime E. Villate @item Mario Rodriguez @item Jorge Barros de Abreu @end itemize @end ifnottex @c includes @menu Infraestrutura do Maxima * Introdu@value{cedilha}@~ao ao Maxima:: Exemplo de sess@~oes do Maxima. * Detec@value{cedilha}@~ao e Relato de Erros:: Encontrando e relatando erros no Maxima. * Ajuda:: Solicitando ajuda de dentro de uma sess@~ao do Maxima. * Linha de Comando:: Sintaxe de linha de comando do Maxima. * Operadores:: Operadores usados em express@~oes do Maxima. * Express@~oes:: Express@~oes no Maxima. * Simplifica@value{cedilha}@~ao:: Simplificando express@~oes. * Montando Gr@'aficos:: Sa@'idas gr@'aficas em 2D e 3D. * Entrada e Sa@'ida:: Entrada e sa@'ida de arquivos. * Ponto Flutuante:: Rotinas num@'ericas de baixo n@'ivel. * Contextos:: Conjunto de fatos assumidos. Suporte a @'areas espec@'ificas da matem@'atica * Polin@^omios:: Formas padr@~ao para polin@^omios, e fun@value{cedilha}@~oes operando sobre polin@^omios. * Constantes:: Constantes num@'ericas. * Logar@'itmos:: Manipula@value{cedilha}@~ao de express@~oes envolvendo logar@'itmos. * Trigonometria:: Manipulando express@~oes com trigonometria e Fun@value{cedilha}@~oes trigonom@'etricas inversas. * Fun@value{cedilha}@value{o_til}es Especiais:: Fun@value{cedilha}@~oes especiais * Fun@value{cedilha}@~oes El@'ipticas:: Fun@value{cedilha}@~oes El@'ipticas e Integrais * Limites:: Limites de express@~oes. * Diferencia@value{cedilha}@~ao:: C@'alculo diferencial. * Integra@value{cedilha}@~ao:: C@'alculo integral. * Equa@value{cedilha}@~oes:: Definindo e resolvendo equa@value{cedilha}@~oes. * Equa@value{cedilha}@~oes Diferenciais:: Definindo e resolvendo equa@value{cedilha}@~oes diferenciais. * Num@'erico:: Integra@value{cedilha}@~ao num@'erica, transforma@value{cedilha}@~oes de Fourier, etc. * Estat@'istica:: Fun@value{cedilha}@~oes estat@'isticas. * Arrays :: Criando e trabalhando com arrays. * Matrizes e @'Algebra Linear:: Opera@value{cedilha}@~oes com Matrizes. * Fun@value{cedilha}@~oes Afins:: * itensor:: Manipula@value{cedilha}@~ao de @'indice de Tensores. * ctensor:: Manipula@value{cedilha}@~ao de componentes de Tensores. * Pacote atensor:: Manipula@value{cedilha}@~ao de Tensores Alg@'ebricos. * S@'eries:: Taylor e s@'eries de pot@^encia. * Teoria dos N@'umeros:: Teoria dos n@'umeros. * Simetrias:: Polin@^omios sim@'etricos * Grupos:: @'Algebra Abstrata. Facilidades avan@value{cedilha}adas e programa@value{cedilha}@~ao * Ambiente em Tempo de Execu@value{cedilha}@~ao:: Customiza@value{cedilha}@~ao do ambiente Maxima. * Op@value{cedilha}@~oes Diversas:: Op@value{cedilha}@~oes com efeito global sobre o Maxima. * Regras e Modelos:: Coincid@^encia de express@~oes definidas pelo utilizador e regras de simplifica@value{cedilha}@~ao. * Listas:: Manipula@value{cedilha}@~ao de listas. * Conjuntos:: Manipula@value{cedilha}@~ao de conjuntos. * Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao:: Definindo fun@value{cedilha}@~oes. * Fluxo de Programa:: Definindo programas do Maxima. * Depurando:: Depurando programas do Maxima. Pacotes Adicionais * augmented_lagrangian:: Pacote augmented_lagrangian. * bode:: Gr@'aficos de ganho e fase de Bode. * cholesky:: Decomposi@,{c}@~ao de Cholesky. * descriptive:: Estat@'istica descritiva. * diag:: Matrizes de Jordan. * distrib:: Distribui@,{c}@~oes de probabilidade. * dynamics:: Gr@'aficos para sistemas din@^amicos e fractais. * eval_string:: Express@~oes do Maxima como cadeias de texto. * f90:: Tradutor do Maxima para o fortran. * ggf:: Fun@,{c}@~ao geradora para sequ@^encias. * impdiff:: Derivadas impl@'icitas. * implicit_plot:: Gr@'aficos impl@'itos. * interpol:: Pacote de interpola@,{c}@~ao. * lbfgs:: L-BFGS pacote de minimiza@,{c}@~ao n@~ao limitada. * lindstedt:: Pacote Lindstedt. * linearalgebra:: Fun@,{c}@~oes de @'algebra linear. * lsquares:: M@'etodo dos m@'inimos quadrados. * makeOrders:: Expoentes de polin@^omios. * mnewton:: M@'etodo de Newton. * numericalio:: Leitura e escritura de arquivos. * opsubst:: Comandos para subsitui@,{c}@~oes. * orthopoly:: Polin@'omios ortogonais. * plotdf:: Gr@'aficos de campos de direc@,{c}@~oes. * romberg:: M@'etodo de Romberg para integra@,{c}@~ao numerica. * simplex:: Programa@,{c}@~ao linear. * simplification:: Fun@,{c}@~oes e regras de simplifica@,{c}@~ao. * solve_rec:: Rela@,{c}@~oes de recorr@^encias lineares. * stats:: Pacote de infer@^encias estat@'isticas. * stirling:: F@'ormula de Stirling. * stringproc:: Processamento de cadeias de texto. * unit:: Pacote de unidades e dimens@~oes. * zeilberger:: Fun@,{c}@~oes para somat@'orios hipergeom@'etricos. @'Indice * @'Indice de Fun@value{cedilha}@~oes e Vari@'aveis:: @'Indice @comment @detailmenu --- Listagem de Nodos Detalhada --- Introdu@value{cedilha}@~ao * Introdu@value{cedilha}@~ao ao Maxima:: Ajuda * Introdu@value{cedilha}@~ao a Ajuda:: * Lisp e Maxima:: * Descartando:: * Documenta@value{cedilha}@~ao:: * Defini@value{cedilha}@~oes para Ajuda:: Linha de Comando * Introdu@value{cedilha}@~ao a Linha de Comando:: * Defini@value{cedilha}@~oes para Linha de Comando:: Operadores * N-Argumentos:: * Sem Argumentos:: * Operador:: * Operador P@'osfixado:: * Operador Pr@'efixado:: * Defini@value{cedilha}@~oes para Operadores:: Express@~oes * Introdu@value{cedilha}@~ao a Express@~oes:: * Atribui@value{cedilha}@~ao:: * Complexo:: * Desigualdade:: * Sintaxe:: * Defini@value{cedilha}@~oes para Express@~oes:: Simplifica@value{cedilha}@~ao * Defini@value{cedilha}@~oes para Simplifica@value{cedilha}@~ao:: Montando Gr@'aficos * Defini@value{cedilha}@~oes para Montagem de Gr@'aficos:: Entrada e Sa@'ida * Introdu@value{cedilha}@~ao a Entrada e Sa@'ida:: * Arquivos:: * Defini@value{cedilha}@~oes para Entrada e Sa@'ida:: Ponto Flutuante * Defini@value{cedilha}@~oes para ponto Flutuante:: Contextos * Defini@value{cedilha}@~oes para Contextos:: Polin@^omios * Introdu@value{cedilha}@~ao a Polin@^omios:: * Defini@value{cedilha}@~oes para Polin@^omios:: Constantes * Defini@value{cedilha}@~oes para Constantes:: Logar@'itmos * Defini@value{cedilha}@~oes para Logar@'itmos:: Trigonometria * Introdu@value{cedilha}@~ao ao Pacote Trigonom@'etrico:: * Defini@value{cedilha}@~oes para Trigonometria:: Fun@value{cedilha}@value{o_til}es Especiais * Introdu@value{cedilha}@~ao a Fun@value{cedilha}@value{o_til}es Especiais:: * specint:: * Defini@value{cedilha}@value{o_til}es para Fun@value{cedilha}@value{o_til}es Especiais:: Fun@value{cedilha}@~oes El@'ipticas * Introdu@value{cedilha}@~ao a Fun@value{cedilha}@~oes El@'ipticas e Integrais:: * Defini@value{cedilha}@~oes para Fun@value{cedilha}@~oes El@'ipticas:: * Defini@value{cedilha}@~oes para Integrais El@'ipticas:: Limites * Defini@value{cedilha}@~oes para Limites:: Diferencia@value{cedilha}@~ao * Defini@value{cedilha}@~oes para Diferencia@value{cedilha}@~ao:: Integra@value{cedilha}@~ao * Introdu@value{cedilha}@~ao a Integra@value{cedilha}@~ao:: * Defini@value{cedilha}@~oes para Integra@value{cedilha}@~ao:: Equa@value{cedilha}@~oes * Defini@value{cedilha}@~oes para Equa@value{cedilha}@~oes:: Equa@value{cedilha}@~oes Diferenciais * Defini@value{cedilha}@~oes para Equa@value{cedilha}@~oes Diferenciais:: Num@'erico * Introdu@value{cedilha}@value{a_til}o a Num@'erico:: * Pacotes de Fourier:: * Defini@value{cedilha}@value{o_til}es para Num@'erico:: * Defini@value{cedilha}@value{o_til}es para S@'eries de Fourier:: Estatistica * Defini@value{cedilha}@~oes para Estat@'istica:: Arrays * Defini@value{cedilha}@~oes para Arrays:: Matrizes e @'Algebra Linear * Introdu@value{cedilha}@~ao a Matrizes e @'Algebra Linear:: * Ponto:: * Vetores:: * auto:: * Defini@value{cedilha}@~oes para Matrizes e @'Algebra Linear:: Fun@value{cedilha}@~oes Afins * Defini@value{cedilha}@~oes para Fun@value{cedilha}@~oes Afins:: itensor * Introdu@value{cedilha}@~ao a itensor:: * Defini@value{cedilha}@~oes para itensor:: ctensor * Introdu@value{cedilha}@~ao a ctensor:: * Defini@value{cedilha}@~oes para ctensor:: Pacote atensor * Introdu@value{cedilha}@~ao ao Pacote atensor:: * Defini@value{cedilha}@~oes para o Pacote atensor:: S@'eries * Introdu@value{cedilha}@~ao a S@'eries:: * Defini@value{cedilha}@~oes para S@'eries:: Teoria dos N@'umeros * Defini@value{cedilha}@~oes para Teoria dos N@'umeros:: Simetrias * Defini@value{cedilha}@~oes para Simetrias:: Grupos * Defini@value{cedilha}@~oes para Grupos:: Ambiente em Tempo de Execu@value{cedilha}@~ao * Introdu@value{cedilha}@~ao a Ambiente em Tempo de Execu@value{cedilha}@~ao:: * Interrup@value{cedilha}@~oes:: * Defini@value{cedilha}@~oes para Ambiente em Tempo de Execu@value{cedilha}@~ao:: Op@value{cedilha}@~oes Diversas * Introdu@value{cedilha}@~ao a Op@value{cedilha}@~oes Diversas:: * Compartilhado:: * Defini@value{cedilha}@~oes para Op@value{cedilha}@~oes Diversas:: Regras e Modelos * Introdu@value{cedilha}@~ao a Regras e Modelos:: * Defini@value{cedilha}@~oes para Regras e Modelos:: Listas * Introdu@value{cedilha}@~ao a Listas:: * Defini@value{cedilha}@~oes para Listas:: Conjuntos * Introdu@value{cedilha}@~ao a Conjuntos:: * Defini@value{cedilha}@~oes para Conjuntos:: Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao * Introdu@value{cedilha}@~ao a Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao:: * Fun@value{cedilha}@~ao:: * Macros:: * Defini@value{cedilha}@~oes para Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao:: Fluxo de Programa * Introdu@value{cedilha}@~ao a Fluxo de Programa:: * Defini@value{cedilha}@~oes para Fluxo de Programa:: Depurando * Defini@value{cedilha}@~oes para Depura@value{cedilha}@~ao:: augmented_lagrangian * Defini@value{cedilha}@value{o_til}es para augmented_lagrangian:: bode * Defini@value{cedilha}@~oes para bode:: cholesky * Defini@value{cedilha}@~oes para cholesky:: descriptive * Introdu@value{cedilha}@~ao ao pacote descriptive:: * Defini@value{cedilha}@~oes para manipula@value{cedilha}@~ao da dados:: * Defini@value{cedilha}@~oes para estatistica descritiva:: * Defini@value{cedilha}@~oes para specific multivariate descriptive statistics:: * Defini@value{cedilha}@~oes para statistical graphs:: diag * Defini@value{cedilha}@~oes para diag:: distrib * Introdu@value{cedilha}@~ao a distrib:: * Defini@value{cedilha}@~oes para distribui@value{cedilha}@~oes cont@'inuas:: * Defini@value{cedilha}@~oes para distribui@value{cedilha}@~oes discretas:: dynamics * Introdu@value{cedilha}@~ao a dynamics:: * Defini@value{cedilha}@~oes para dynamics:: eval_string * Defini@value{cedilha}@~oes para eval_string:: f90 * Defini@value{cedilha}@~oes para f90:: ggf * Defini@value{cedilha}@~oes para ggf:: impdiff * Defini@value{cedilha}@~oes para impdiff:: implicit_plot * Defini@value{cedilha}@value{o_til}es para implicit_plot:: interpol * Introdu@value{cedilha}@~ao a interpol:: * Defini@value{cedilha}@~oes para interpol:: lbfgs * Introdu@value{cedilha}@~ao a lbfgs:: * Defini@value{cedilha}@~oes para lbfgs:: lindstedt * Defini@value{cedilha}@~oes para lindstedt:: linearalgebra * Introdu@value{cedilha}@~ao a linearalgebra:: * Defini@value{cedilha}@~oes para linearalgebra:: lsquares * Defini@value{cedilha}@~oes para lsquares:: makeOrders * Defini@value{cedilha}@~oes para makeOrders:: mnewton * Defini@value{cedilha}@~oes para mnewton:: numericalio * Introdu@value{cedilha}@~ao a numericalio:: * Defini@value{cedilha}@~oes para numericalio:: opsubst * Defini@value{cedilha}@~oes para opsubst:: orthopoly * Introdu@value{cedilha}@~ao a polin@^omios ortogonais:: * Defini@value{cedilha}@~oes para polin@^omios ortogonais:: plotdf * Introdu@value{cedilha}@~ao a plotdf:: * Defini@value{cedilha}@~oes para plotdf:: romberg * Defini@value{cedilha}@~oes para romberg:: simplex * Introdu@value{cedilha}@~ao a simplex:: * Defini@value{cedilha}@~oes para simplex:: simplification * Introdu@value{cedilha}@~ao a simplification:: * Defini@value{cedilha}@value{o_til}es para simplification:: solve_rec * Introdu@value{cedilha}@~ao a solve_rec:: * Defini@value{cedilha}@~oes para solve_rec:: stats * Introdu@value{cedilha}@~ao a stats:: * Defini@value{cedilha}@~oes para inference_result:: * Defini@value{cedilha}@~oes para stats:: * Defini@value{cedilha}@~oes para distribui@value{cedilha}@~oes especiais:: stirling * Defini@value{cedilha}@~oes para stirling:: stringproc * Introduction to string processing:: * Definitions for input and output:: * Definitions for characters:: * Definitions for strings:: unit * Introdu@value{cedilha}@~ao a Units:: * Defini@value{cedilha}@~oes para Units:: zeilberger * Introdu@value{cedilha}@~ao a zeilberger:: * Defini@value{cedilha}@value{o_til}es para zeilberger:: @comment @end detailmenu @end menu @c Put the @node lines here, rather than in the @included files, @c so emacs can automatically update them with C-c C-u C-e. @c nota bene: C-c C-u C-a and texinfo-multiple-files-update will delete @c the detailed node listing! @node Introdu@value{cedilha}@~ao ao Maxima, Detec@value{cedilha}@~ao e Relato de Erros, Top, Top @chapter Introdu@value{cedilha}@~ao ao Maxima @include Introduction.texi @node Detec@value{cedilha}@~ao e Relato de Erros, Ajuda, Introdu@value{cedilha}@~ao ao Maxima, Top @chapter Detec@value{cedilha}@~ao e Relato de Erros @include Bugs.texi @node Ajuda, Linha de Comando, Detec@value{cedilha}@~ao e Relato de Erros, Top @chapter Ajuda @include Help.texi @node Linha de Comando, Operadores, Ajuda, Top @chapter Linha de Comando @include Command.texi @node Operadores, Express@~oes, Linha de Comando, Top @chapter Operadores @include Operators.texi @node Express@~oes, Simplifica@value{cedilha}@~ao, Operadores, Top @chapter Express@~oes @include Expressions.texi @node Simplifica@value{cedilha}@~ao, Montando Gr@'aficos, Express@~oes, Top @chapter Simplifica@value{cedilha}@~ao @include Simplification.texi @node Montando Gr@'aficos, Entrada e Sa@'ida, Simplifica@value{cedilha}@~ao, Top @chapter Montando Gr@'aficos @include Plotting.texi @node Entrada e Sa@'ida, Ponto Flutuante, Montando Gr@'aficos, Top @chapter Entrada e Sa@'ida @include Input.texi @node Ponto Flutuante, Contextos, Entrada e Sa@'ida, Top @chapter Ponto Flutuante @include Floating.texi @node Contextos, Polin@^omios, Ponto Flutuante, Top @chapter Contextos @include Contexts.texi @node Polin@^omios, Constantes, Contextos, Top @chapter Polin@^omios @include Polynomials.texi @node Constantes, Logar@'itmos, Polin@^omios, Top @chapter Constantes @include Constants.texi @node Logar@'itmos, Trigonometria, Constantes, Top @chapter Logar@'itmos @include Logarithms.texi @node Trigonometria, Fun@value{cedilha}@value{o_til}es Especiais, Logar@'itmos, Top @chapter Trigonometria @include Trigonometric.texi @node Fun@value{cedilha}@value{o_til}es Especiais, Fun@value{cedilha}@~oes El@'ipticas, Trigonometria, Top @chapter Fun@value{cedilha}@value{o_til}es Especiais @include Special.texi @node Fun@value{cedilha}@~oes El@'ipticas, Limites, Fun@value{cedilha}@value{o_til}es Especiais, Top @chapter Fun@value{cedilha}@~oes El@'ipticas @include Elliptic.texi @node Limites, Diferencia@value{cedilha}@~ao, Fun@value{cedilha}@~oes El@'ipticas, Top @chapter Limites @include Limits.texi @node Diferencia@value{cedilha}@~ao, Integra@value{cedilha}@~ao, Limites, Top @chapter Diferencia@value{cedilha}@~ao @include Differentiation.texi @node Integra@value{cedilha}@~ao, Equa@value{cedilha}@~oes, Diferencia@value{cedilha}@~ao, Top @chapter Integra@value{cedilha}@~ao @include Integration.texi @node Equa@value{cedilha}@~oes, Equa@value{cedilha}@~oes Diferenciais, Integra@value{cedilha}@~ao, Top @chapter Equa@value{cedilha}@~oes @include Equations.texi @node Equa@value{cedilha}@~oes Diferenciais, Num@'erico, Equa@value{cedilha}@~oes, Top @chapter Equa@value{cedilha}@~oes Diferenciais @include Differential.texi @c @include NonCommutative.texi @node Num@'erico, Estat@'istica, Equa@value{cedilha}@~oes Diferenciais, Top @chapter Num@'erico @include Numerical.texi @node Estat@'istica, Arrays, Num@'erico, Top @chapter Estat@'istica @include Statistics.texi @node Arrays, Matrizes e @'Algebra Linear, Estat@'istica, Top @chapter Arrays @include Arrays.texi @node Matrizes e @'Algebra Linear, Fun@value{cedilha}@~oes Afins, Arrays, Top @chapter Matrizes e @'Algebra Linear @include Matrices.texi @node Fun@value{cedilha}@~oes Afins, itensor, Matrizes e @'Algebra Linear, Top @chapter Fun@value{cedilha}@~oes Afins @include Affine.texi @node itensor, ctensor, Fun@value{cedilha}@~oes Afins, Top @chapter itensor @include Itensor.texi @node ctensor, Pacote atensor, itensor, Top @chapter ctensor @include Ctensor.texi @node Pacote atensor, S@'eries, ctensor, Top @chapter Pacote atensor @include Atensor.texi @node S@'eries, Teoria dos N@'umeros, Pacote atensor, Top @chapter S@'eries @include Series.texi @node Teoria dos N@'umeros, Simetrias, S@'eries, Top @chapter Teoria dos N@'umeros @include Number.texi @node Simetrias, Grupos, Teoria dos N@'umeros, Top @chapter Simetrias @include Symmetries.texi @node Grupos, Ambiente em Tempo de Execu@value{cedilha}@~ao, Simetrias, Top @chapter Grupos @include Groups.texi @node Ambiente em Tempo de Execu@value{cedilha}@~ao, Op@value{cedilha}@~oes Diversas, Grupos, Top @chapter Ambiente em Tempo de Execu@value{cedilha}@~ao @include Runtime.texi @node Op@value{cedilha}@~oes Diversas, Regras e Modelos, Ambiente em Tempo de Execu@value{cedilha}@~ao, Top @chapter Op@value{cedilha}@~oes Diversas @include Miscellaneous.texi @node Regras e Modelos, Listas, Op@value{cedilha}@~oes Diversas, Top @chapter Regras e Modelos @include Rules.texi @node Listas, Conjuntos, Regras e Modelos, Top @chapter Listas @include Lists.texi @node Conjuntos, Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao, Listas, Top @chapter Conjuntos @include nset.texi @node Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao, Fluxo de Programa, Conjuntos, Top @chapter Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao @include Function.texi @node Fluxo de Programa, Depurando, Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao, Top @chapter Fluxo de Programa @include Program.texi @node Depurando, augmented_lagrangian, Fluxo de Programa, Top @chapter Depurando @include Debugging.texi @node augmented_lagrangian, bode, Depurando, Top @chapter augmented_lagrangian @include augmented_lagrangian.texi @node bode, cholesky, augmented_lagrangian, Top @chapter bode @include bode.texi @node cholesky, descriptive, bode, Top @chapter cholesky @include cholesky.texi @node descriptive, diag, cholesky, Top @chapter descriptive @include descriptive.texi @node diag, distrib, descriptive, Top @chapter diag @include diag.texi @node distrib, dynamics, diag, Top @chapter distrib @include distrib.texi @node dynamics, eval_string, distrib, Top @chapter dynamics @include dynamics.texi @node eval_string, f90, dynamics, Top @chapter eval_string @include eval_string.texi @node f90, ggf, eval_string, Top @chapter f90 @include f90.texi @node ggf, impdiff, f90, Top @chapter ggf @include ggf.texi @node impdiff, implicit_plot, ggf, Top @chapter impdiff @include impdiff.texi @node implicit_plot, interpol, impdiff, Top @chapter implicit_plot @include implicit_plot.texi @node interpol, lbfgs, implicit_plot, Top @chapter interpol @include interpol.texi @node lbfgs, lindstedt, interpol, Top @chapter lbfgs @include lbfgs.texi @node lindstedt, linearalgebra, lbfgs, Top @chapter lindstedt @include lindstedt.texi @node linearalgebra, lsquares, lindstedt, Top @chapter linearalgebra @include linearalgebra.texi @node lsquares, makeOrders, linearalgebra, Top @chapter lsquares @include lsquares.texi @node makeOrders, mnewton, lsquares, Top @chapter makeOrders @include makeOrders.texi @node mnewton, numericalio, makeOrders, Top @chapter mnewton @include mnewton.texi @node numericalio, opsubst, mnewton, Top @chapter numericalio @include numericalio.texi @node opsubst, orthopoly, numericalio, Top @chapter opsubst @include opsubst.texi @node orthopoly, plotdf, opsubst, Top @chapter orthopoly @include orthopoly.texi @node plotdf, romberg, orthopoly, Top @chapter plotdf @include plotdf.texi @node romberg, simplex, plotdf, Top @chapter romberg @include romberg.texi @node simplex, simplification, romberg, Top @chapter simplex @include simplex.texi @node simplification, solve_rec, simplex, Top @chapter simplification @include simplifications.texi @node solve_rec, stats, simplification, Top @chapter solve_rec @include solve_rec.texi @node stats, stirling, solve_rec, Top @chapter stats @include stats.texi @node stirling, stringproc, stats, Top @chapter stirling @include stirling.texi @node stringproc, unit, stirling, Top @chapter stringproc @include stringproc.texi @node unit, zeilberger, stringproc, Top @chapter unit @include unit.texi @node zeilberger, @'Indice de Fun@value{cedilha}@~oes e Vari@'aveis, unit, Top @chapter zeilberger @include zeilberger.texi @node @'Indice de Fun@value{cedilha}@~oes e Vari@'aveis, , zeilberger, Top @chapter @'Indice de Fun@value{cedilha}@~oes e Vari@'aveis @include Indices.texi @c end includes @bye --Boundary-00=_5TgqFnyKa5ENh63 Content-Type: text/plain; charset="iso-8859-1"; name="maxima_error.texi" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="maxima_error.texi" \input texinfo @c /maxima.texi/1.39/Mon Jan 8 04:17:51 2007/-ko/ @c Language: Brazilian Portuguese, Encoding: iso-8859-1 @c -*-texinfo-*- @c 2000-04-17 Jim Van Zandt Added header, @c info directory entry, reference to introduction chapter, and menu @c descriptions. Rearranged chapters. @c to update the menus do: @c (texinfo-multiple-files-update "maxima.texi" t t) @c @c texinfo-multiple-files-update will delete the detailed node listing! @c texinfo Coodinator Robert Dodier @c Portuguese Translator Jorge Barros de Abreu @c %**start of header @setfilename maxima.info @synindex vr fn @c @documentencoding ISO-8859-15 @documentencoding ISO-8859-1 @set cedilha @,{c} @set i_agu @'i @set I_agu @'I @set a_til @~a @set a_agu @'a @set o_til @~o @set mail @settitle Manual do Maxima @c %**end of header @setchapternewpage odd @ifinfo Esse @'e um Manual do Maxima no formato Texinfo Copyright 1994,2001 William F. Schelter @format START-INFO-DIR-ENTRY * Maxima: (maxima). Um sistema de @'algebra computacional. END-INFO-DIR-ENTRY @end format @end ifinfo @ifinfo @macro var {expr} <\expr\> @end macro @end ifinfo @titlepage @sp 10 @comment The title is printed in a large font. @center @titlefont{Manual do Maxima} @page @vskip 0pt plus 1filll Maxima @'e um sistema de @'algebra computacional, implementado em Lisp. Maxima @'e derivado do sistema Macsyma, desenvolvido no MIT nos anos de 1968 a 1982 como parte do Projeto MAC. MIT remanejou uma c@'opia do c@'odigo fonte do Macsyma para o Departamento de Energia em 1982; aquela vers@~ao @'e agora conhecida como Macsyma DOE. Uma c@'opia do Macsyma DOE foi mantida pelo Professor William F. Schelter da Universidade do Texas de 1982 at@'e sua morte em 2001. Em 1998, Schelter obteve permiss@~ao do Departamento de Energia para liberar o c@'odigo fonte do Macsyma DOE sob a Licen@value{cedilha}a P@'ublica GNU, e em 2000 ele iniciou o projeto Maxima no SourceForge para manter e desenvolver o Macsyma DOE, agora chamado Maxima. Notas de tradu@,{c}@~ao: Com o t@'ermino da tradu@,{c}@~ao inicia-se o processo de revis@~o da mesma. Est@'a aberta a temporada de ca@,{c}a aos erros de tradu@,{c}@~ao, erros de hifeniza@,{c}@~ao e de adequa@,{c}@~ao entre a linguagem matem@'atica inglesa e a linguagem matem@'atica brasileira. Caso voc@^e me envie alguma corre@,{c}@~ao ou melhoria a comunidade matem@'atica que utiliza o Sofware Livre lhe ficar@'a muito grata ( e n@'os, da equipe do Maxima, tamb@'em). O c@'odigo fonte deste documento encontra-se no formato texinfo. Para contribuir com a equipe do Maxima na tarefa de manter a tradu@,{c}@~ao para o portugu@^es sempre atualizada envie um e-mail para @value{mail}. Em caso de d@'uvida sobre algum trecho deste manual consulte o original ingl@^es. Caso sua d@'uvida persista ou tenha alguma sugest@~ao/aperfei@,{c}oamento/ cr@'{@dotless{i}}tica mande por e-mail para Jorge Barros de Abreu Mantenedores: @itemize @bullet @item Jaime E. Villate @item Mario Rodriguez @item Jorge Barros de Abreu @end itemize @end titlepage @summarycontents @contents @ifnottex @node Top, Introdu@value{cedilha}@~ao ao Maxima, (dir), (dir) @top @i{Maxima @'e um sistema de @'algebra computacional, implementado em Lisp.} Maxima @'e derivado do sistema Macsyma, desenvolvido no MIT nos anos de 1968 a 1982 como parte do Projeto MAC. MIT remanejou uma c@'opia do c@'odigo fonte do Macsyma para o Departamento de Energia em 1982; aquela vers@~ao @'e agora conhecida como Macsyma DOE. Uma c@'opia do Macsyma DOE foi mantida pelo Professor William F. Schelter da Universidade do Texas de 1982 at@'e sua morte em 2001. Em 1998, Schelter obteve permiss@~ao do Departamento de Energia para liberar o c@'odigo fonte do Macsyma DOE sob a Licen@value{cedilha}a P@'ublica GNU, e em 2000 ele iniciou o projeto Maxima no SourceForge para manter e desenvolver o Macsyma DOE, agora chamado Maxima. @i{Notas de tradu@,{c}@~ao:} Com o t@'ermino da tradu@,{c}@~ao inicia-se o processo de revis@~o da mesma. Est@'a aberta a temporada de ca@,{c}a aos erros de tradu@,{c}@~ao, erros de hifeniza@,{c}@~ao e de adequa@,{c}@~ao entre a linguagem matem@'atica inglesa e a linguagem matem@'atica brasileira. Caso voc@^e me envie alguma corre@,{c}@~ao ou melhoria a comunidade matem@'atica que utiliza o Sofware Livre lhe ficar@'a muito grata ( e n@'os, da equipe do Maxima, tamb@'em). O c@'odigo fonte deste documento encontra-se no formato texinfo. Para contribuir com a equipe do Maxima na tarefa de manter a tradu@,{c}@~ao para o portugu@^es sempre atualizada envie um e-mail para @value{mail}. Em caso de d@'uvida sobre algum trecho deste manual consulte o original ingl@^es. A se@,{c}@~ao "Pacotes adicionais" foi anexada ao manual recentemente (fevereiro/2006) e possui partes a serem traduzidas. Caso sua d@'uvida persista ou tenha alguma sugest@~ao/aperfei@,{c}oamen- to/cr@'itica mande por e-mail para Jorge Barros de Abreu Mantenedores: @itemize @bullet @item Jaime E. Villate @item Mario Rodriguez @item Jorge Barros de Abreu @end itemize @end ifnottex @c includes @menu Infraestrutura do Maxima * Introdu@value{cedilha}@~ao ao Maxima:: Exemplo de sess@~oes do Maxima. * Detec@value{cedilha}@~ao e Relato de Erros:: Encontrando e relatando erros no Maxima. * Ajuda:: Solicitando ajuda de dentro de uma sess@~ao do Maxima. * Linha de Comando:: Sintaxe de linha de comando do Maxima. * Operadores:: Operadores usados em express@~oes do Maxima. * Express@~oes:: Express@~oes no Maxima. * Simplifica@value{cedilha}@~ao:: Simplificando express@~oes. * Montando Gr@'aficos:: Sa@'idas gr@'aficas em 2D e 3D. * Entrada e Sa@'ida:: Entrada e sa@'ida de arquivos. * Ponto Flutuante:: Rotinas num@'ericas de baixo n@'ivel. * Contextos:: Conjunto de fatos assumidos. Suporte a @'areas espec@'ificas da matem@'atica * Polin@^omios:: Formas padr@~ao para polin@^omios, e fun@value{cedilha}@~oes operando sobre polin@^omios. * Constantes:: Constantes num@'ericas. * Logar@'itmos:: Manipula@value{cedilha}@~ao de express@~oes envolvendo logar@'itmos. * Trigonometria:: Manipulando express@~oes com trigonometria e Fun@value{cedilha}@~oes trigonom@'etricas inversas. * Fun@value{cedilha}@value{o_til}es Especiais:: Fun@value{cedilha}@~oes especiais * Fun@value{cedilha}@~oes El@'ipticas:: Fun@value{cedilha}@~oes El@'ipticas e Integrais * Limites:: Limites de express@~oes. * Diferencia@value{cedilha}@~ao:: C@'alculo diferencial. * Integra@value{cedilha}@~ao:: C@'alculo integral. * Equa@value{cedilha}@~oes:: Definindo e resolvendo equa@value{cedilha}@~oes. * Equa@value{cedilha}@~oes Diferenciais:: Definindo e resolvendo equa@value{cedilha}@~oes diferenciais. * Num@'erico:: Integra@value{cedilha}@~ao num@'erica, transforma@value{cedilha}@~oes de Fourier, etc. * Estat@'istica:: Fun@value{cedilha}@~oes estat@'isticas. * Arrays :: Criando e trabalhando com arrays. * Matrizes e @'Algebra Linear:: Opera@value{cedilha}@~oes com Matrizes. * Fun@value{cedilha}@~oes Afins:: * itensor:: Manipula@value{cedilha}@~ao de @'indice de Tensores. * ctensor:: Manipula@value{cedilha}@~ao de componentes de Tensores. * Pacote atensor:: Manipula@value{cedilha}@~ao de Tensores Alg@'ebricos. * S@'eries:: Taylor e s@'eries de pot@^encia. * Teoria dos N@'umeros:: Teoria dos n@'umeros. * Simetrias:: Polin@^omios sim@'etricos * Grupos:: @'Algebra Abstrata. Facilidades avan@value{cedilha}adas e programa@value{cedilha}@~ao * Ambiente em Tempo de Execu@value{cedilha}@~ao:: Customiza@value{cedilha}@~ao do ambiente Maxima. * Op@value{cedilha}@~oes Diversas:: Op@value{cedilha}@~oes com efeito global sobre o Maxima. * Regras e Modelos:: Coincid@^encia de express@~oes definidas pelo utilizador e regras de simplifica@value{cedilha}@~ao. * Listas:: Manipula@value{cedilha}@~ao de listas. * Conjuntos:: Manipula@value{cedilha}@~ao de conjuntos. * Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao:: Definindo fun@value{cedilha}@~oes. * Fluxo de Programa:: Definindo programas do Maxima. * Depurando:: Depurando programas do Maxima. Pacotes Adicionais * augmented_lagrangian:: Pacote augmented_lagrangian. * bode:: Gr@'aficos de ganho e fase de Bode. * cholesky:: Decomposi@,{c}@~ao de Cholesky. * descriptive:: Estat@'istica descritiva. * diag:: Matrizes de Jordan. * distrib:: Distribui@,{c}@~oes de probabilidade. * dynamics:: Gr@'aficos para sistemas din@^amicos e fractais. * eval_string:: Express@~oes do Maxima como cadeias de texto. * f90:: Tradutor do Maxima para o fortran. * ggf:: Fun@,{c}@~ao geradora para sequ@^encias. * impdiff:: Derivadas impl@'icitas. * implicit_plot:: Gr@'aficos impl@'itos. * interpol:: Pacote de interpola@,{c}@~ao. * lbfgs:: L-BFGS pacote de minimiza@,{c}@~ao n@~ao limitada. * lindstedt:: Pacote Lindstedt. * linearalgebra:: Fun@,{c}@~oes de @'algebra linear. * lsquares:: M@'etodo dos m@'inimos quadrados. * makeOrders:: Expoentes de polin@^omios. * mnewton:: M@'etodo de Newton. * numericalio:: Leitura e escritura de arquivos. * opsubst:: Comandos para subsitui@,{c}@~oes. * orthopoly:: Polin@'omios ortogonais. * plotdf:: Gr@'aficos de campos de direc@,{c}@~oes. * romberg:: M@'etodo de Romberg para integra@,{c}@~ao numerica. * simplex:: Programa@,{c}@~ao linear. * simplification:: Fun@,{c}@~oes e regras de simplifica@,{c}@~ao. * solve_rec:: Rela@,{c}@~oes de recorr@^encias lineares. * stats:: Pacote de infer@^encias estat@'isticas. * stirling:: F@'ormula de Stirling. * stringproc:: Processamento de cadeias de texto. * unit:: Pacote de unidades e dimens@~oes. * zeilberger:: Fun@,{c}@~oes para somat@'orios hipergeom@'etricos. @'Indice * @'Indice de Fun@value{cedilha}@~oes e Vari@'aveis:: @'Indice @comment @detailmenu --- Listagem de Nodos Detalhada --- Introdu@value{cedilha}@~ao * Introdu@value{cedilha}@~ao ao Maxima:: Ajuda * Introdu@value{cedilha}@~ao a Ajuda:: * Lisp e Maxima:: * Descartando:: * Documenta@value{cedilha}@~ao:: * Defini@value{cedilha}@~oes para Ajuda:: Linha de Comando * Introdu@value{cedilha}@~ao a Linha de Comando:: * Defini@value{cedilha}@~oes para Linha de Comando:: Operadores * N-Argumentos:: * Sem Argumentos:: * Operador:: * Operador P@'osfixado:: * Operador Pr@'efixado:: * Defini@value{cedilha}@~oes para Operadores:: Express@~oes * Introdu@value{cedilha}@~ao a Express@~oes:: * Atribui@value{cedilha}@~ao:: * Complexo:: * Desigualdade:: * Sintaxe:: * Defini@value{cedilha}@~oes para Express@~oes:: Simplifica@value{cedilha}@~ao * Defini@value{cedilha}@~oes para Simplifica@value{cedilha}@~ao:: Montando Gr@'aficos * Defini@value{cedilha}@~oes para Montagem de Gr@'aficos:: Entrada e Sa@'ida * Introdu@value{cedilha}@~ao a Entrada e Sa@'ida:: * Arquivos:: * Defini@value{cedilha}@~oes para Entrada e Sa@'ida:: Ponto Flutuante * Defini@value{cedilha}@~oes para ponto Flutuante:: Contextos * Defini@value{cedilha}@~oes para Contextos:: Polin@^omios * Introdu@value{cedilha}@~ao a Polin@^omios:: * Defini@value{cedilha}@~oes para Polin@^omios:: Constantes * Defini@value{cedilha}@~oes para Constantes:: Logar@'itmos * Defini@value{cedilha}@~oes para Logar@'itmos:: Trigonometria * Introdu@value{cedilha}@~ao ao Pacote Trigonom@'etrico:: * Defini@value{cedilha}@~oes para Trigonometria:: Fun@value{cedilha}@value{o_til}es Especiais * Introdu@value{cedilha}@~ao a Fun@value{cedilha}@value{o_til}es Especiais:: * specint:: * Defini@value{cedilha}@value{o_til}es para Fun@value{cedilha}@value{o_til}es Especiais:: Fun@value{cedilha}@~oes El@'ipticas * Introdu@value{cedilha}@~ao a Fun@value{cedilha}@~oes El@'ipticas e Integrais:: * Defini@value{cedilha}@~oes para Fun@value{cedilha}@~oes El@'ipticas:: * Defini@value{cedilha}@~oes para Integrais El@'ipticas:: Limites * Defini@value{cedilha}@~oes para Limites:: Diferencia@value{cedilha}@~ao * Defini@value{cedilha}@~oes para Diferencia@value{cedilha}@~ao:: Integra@value{cedilha}@~ao * Introdu@value{cedilha}@~ao a Integra@value{cedilha}@~ao:: * Defini@value{cedilha}@~oes para Integra@value{cedilha}@~ao:: Equa@value{cedilha}@~oes * Defini@value{cedilha}@~oes para Equa@value{cedilha}@~oes:: Equa@value{cedilha}@~oes Diferenciais * Defini@value{cedilha}@~oes para Equa@value{cedilha}@~oes Diferenciais:: Num@'erico * Introdu@value{cedilha}@value{a_til}o a Num@'erico:: * Pacotes de Fourier:: * Defini@value{cedilha}@value{o_til}es para Num@'erico:: * Defini@value{cedilha}@value{o_til}es para S@'eries de Fourier:: Estatistica * Defini@value{cedilha}@~oes para Estat@'istica:: Arrays * Defini@value{cedilha}@~oes para Arrays:: Matrizes e @'Algebra Linear * Introdu@value{cedilha}@~ao a Matrizes e @'Algebra Linear:: * Ponto:: * Vetores:: * auto:: * Defini@value{cedilha}@~oes para Matrizes e @'Algebra Linear:: Fun@value{cedilha}@~oes Afins * Defini@value{cedilha}@~oes para Fun@value{cedilha}@~oes Afins:: itensor * Introdu@value{cedilha}@~ao a itensor:: * Defini@value{cedilha}@~oes para itensor:: ctensor * Introdu@value{cedilha}@~ao a ctensor:: * Defini@value{cedilha}@~oes para ctensor:: Pacote atensor * Introdu@value{cedilha}@~ao ao Pacote atensor:: * Defini@value{cedilha}@~oes para o Pacote atensor:: S@'eries * Introdu@value{cedilha}@~ao a S@'eries:: * Defini@value{cedilha}@~oes para S@'eries:: Teoria dos N@'umeros * Defini@value{cedilha}@~oes para Teoria dos N@'umeros:: Simetrias * Defini@value{cedilha}@~oes para Simetrias:: Grupos * Defini@value{cedilha}@~oes para Grupos:: Ambiente em Tempo de Execu@value{cedilha}@~ao * Introdu@value{cedilha}@~ao a Ambiente em Tempo de Execu@value{cedilha}@~ao:: * Interrup@value{cedilha}@~oes:: * Defini@value{cedilha}@~oes para Ambiente em Tempo de Execu@value{cedilha}@~ao:: Op@value{cedilha}@~oes Diversas * Introdu@value{cedilha}@~ao a Op@value{cedilha}@~oes Diversas:: * Compartilhado:: * Defini@value{cedilha}@~oes para Op@value{cedilha}@~oes Diversas:: Regras e Modelos * Introdu@value{cedilha}@~ao a Regras e Modelos:: * Defini@value{cedilha}@~oes para Regras e Modelos:: Listas * Introdu@value{cedilha}@~ao a Listas:: * Defini@value{cedilha}@~oes para Listas:: Conjuntos * Introdu@value{cedilha}@~ao a Conjuntos:: * Defini@value{cedilha}@~oes para Conjuntos:: Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao * Introdu@value{cedilha}@~ao a Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao:: * Fun@value{cedilha}@~ao:: * Macros:: * Defini@value{cedilha}@~oes para Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao:: Fluxo de Programa * Introdu@value{cedilha}@~ao a Fluxo de Programa:: * Defini@value{cedilha}@~oes para Fluxo de Programa:: Depurando * Defini@value{cedilha}@~oes para Depura@value{cedilha}@~ao:: augmented_lagrangian * Defini@value{cedilha}@value{o_til}es para augmented_lagrangian:: bode * Defini@value{cedilha}@~oes para bode:: cholesky * Defini@value{cedilha}@~oes para cholesky:: descriptive * Introdu@value{cedilha}@~ao ao pacote descriptive:: * Defini@value{cedilha}@~oes para manipula@value{cedilha}@~ao da dados:: * Defini@value{cedilha}@~oes para estat@'istica descritiva:: * Defini@value{cedilha}@~oes para specific multivariate descriptive statistics:: * Defini@value{cedilha}@~oes para statistical graphs:: diag * Defini@value{cedilha}@~oes para diag:: distrib * Introdu@value{cedilha}@~ao a distrib:: * Defini@value{cedilha}@~oes para distribui@value{cedilha}@~oes cont@'inuas:: * Defini@value{cedilha}@~oes para distribui@value{cedilha}@~oes discretas:: dynamics * Introdu@value{cedilha}@~ao a dynamics:: * Defini@value{cedilha}@~oes para dynamics:: eval_string * Defini@value{cedilha}@~oes para eval_string:: f90 * Defini@value{cedilha}@~oes para f90:: ggf * Defini@value{cedilha}@~oes para ggf:: impdiff * Defini@value{cedilha}@~oes para impdiff:: implicit_plot * Defini@value{cedilha}@value{o_til}es para implicit_plot:: interpol * Introdu@value{cedilha}@~ao a interpol:: * Defini@value{cedilha}@~oes para interpol:: lbfgs * Introdu@value{cedilha}@~ao a lbfgs:: * Defini@value{cedilha}@~oes para lbfgs:: lindstedt * Defini@value{cedilha}@~oes para lindstedt:: linearalgebra * Introdu@value{cedilha}@~ao a linearalgebra:: * Defini@value{cedilha}@~oes para linearalgebra:: lsquares * Defini@value{cedilha}@~oes para lsquares:: makeOrders * Defini@value{cedilha}@~oes para makeOrders:: mnewton * Defini@value{cedilha}@~oes para mnewton:: numericalio * Introdu@value{cedilha}@~ao a numericalio:: * Defini@value{cedilha}@~oes para numericalio:: opsubst * Defini@value{cedilha}@~oes para opsubst:: orthopoly * Introdu@value{cedilha}@~ao a polin@^omios ortogonais:: * Defini@value{cedilha}@~oes para polin@^omios ortogonais:: plotdf * Introdu@value{cedilha}@~ao a plotdf:: * Defini@value{cedilha}@~oes para plotdf:: romberg * Defini@value{cedilha}@~oes para romberg:: simplex * Introdu@value{cedilha}@~ao a simplex:: * Defini@value{cedilha}@~oes para simplex:: simplification * Introdu@value{cedilha}@~ao a simplification:: * Defini@value{cedilha}@value{o_til}es para simplification:: solve_rec * Introdu@value{cedilha}@~ao a solve_rec:: * Defini@value{cedilha}@~oes para solve_rec:: stats * Introdu@value{cedilha}@~ao a stats:: * Defini@value{cedilha}@~oes para inference_result:: * Defini@value{cedilha}@~oes para stats:: * Defini@value{cedilha}@~oes para distribui@value{cedilha}@~oes especiais:: stirling * Defini@value{cedilha}@~oes para stirling:: stringproc * Introduction to string processing:: * Definitions for input and output:: * Definitions for characters:: * Definitions for strings:: unit * Introdu@value{cedilha}@~ao a Units:: * Defini@value{cedilha}@~oes para Units:: zeilberger * Introdu@value{cedilha}@~ao a zeilberger:: * Defini@value{cedilha}@value{o_til}es para zeilberger:: @comment @end detailmenu @end menu @c Put the @node lines here, rather than in the @included files, @c so emacs can automatically update them with C-c C-u C-e. @c nota bene: C-c C-u C-a and texinfo-multiple-files-update will delete @c the detailed node listing! @node Introdu@value{cedilha}@~ao ao Maxima, Detec@value{cedilha}@~ao e Relato de Erros, Top, Top @chapter Introdu@value{cedilha}@~ao ao Maxima @include Introduction.texi @node Detec@value{cedilha}@~ao e Relato de Erros, Ajuda, Introdu@value{cedilha}@~ao ao Maxima, Top @chapter Detec@value{cedilha}@~ao e Relato de Erros @include Bugs.texi @node Ajuda, Linha de Comando, Detec@value{cedilha}@~ao e Relato de Erros, Top @chapter Ajuda @include Help.texi @node Linha de Comando, Operadores, Ajuda, Top @chapter Linha de Comando @include Command.texi @node Operadores, Express@~oes, Linha de Comando, Top @chapter Operadores @include Operators.texi @node Express@~oes, Simplifica@value{cedilha}@~ao, Operadores, Top @chapter Express@~oes @include Expressions.texi @node Simplifica@value{cedilha}@~ao, Montando Gr@'aficos, Express@~oes, Top @chapter Simplifica@value{cedilha}@~ao @include Simplification.texi @node Montando Gr@'aficos, Entrada e Sa@'ida, Simplifica@value{cedilha}@~ao, Top @chapter Montando Gr@'aficos @include Plotting.texi @node Entrada e Sa@'ida, Ponto Flutuante, Montando Gr@'aficos, Top @chapter Entrada e Sa@'ida @include Input.texi @node Ponto Flutuante, Contextos, Entrada e Sa@'ida, Top @chapter Ponto Flutuante @include Floating.texi @node Contextos, Polin@^omios, Ponto Flutuante, Top @chapter Contextos @include Contexts.texi @node Polin@^omios, Constantes, Contextos, Top @chapter Polin@^omios @include Polynomials.texi @node Constantes, Logar@'itmos, Polin@^omios, Top @chapter Constantes @include Constants.texi @node Logar@'itmos, Trigonometria, Constantes, Top @chapter Logar@'itmos @include Logarithms.texi @node Trigonometria, Fun@value{cedilha}@value{o_til}es Especiais, Logar@'itmos, Top @chapter Trigonometria @include Trigonometric.texi @node Fun@value{cedilha}@value{o_til}es Especiais, Fun@value{cedilha}@~oes El@'ipticas, Trigonometria, Top @chapter Fun@value{cedilha}@value{o_til}es Especiais @include Special.texi @node Fun@value{cedilha}@~oes El@'ipticas, Limites, Fun@value{cedilha}@value{o_til}es Especiais, Top @chapter Fun@value{cedilha}@~oes El@'ipticas @include Elliptic.texi @node Limites, Diferencia@value{cedilha}@~ao, Fun@value{cedilha}@~oes El@'ipticas, Top @chapter Limites @include Limits.texi @node Diferencia@value{cedilha}@~ao, Integra@value{cedilha}@~ao, Limites, Top @chapter Diferencia@value{cedilha}@~ao @include Differentiation.texi @node Integra@value{cedilha}@~ao, Equa@value{cedilha}@~oes, Diferencia@value{cedilha}@~ao, Top @chapter Integra@value{cedilha}@~ao @include Integration.texi @node Equa@value{cedilha}@~oes, Equa@value{cedilha}@~oes Diferenciais, Integra@value{cedilha}@~ao, Top @chapter Equa@value{cedilha}@~oes @include Equations.texi @node Equa@value{cedilha}@~oes Diferenciais, Num@'erico, Equa@value{cedilha}@~oes, Top @chapter Equa@value{cedilha}@~oes Diferenciais @include Differential.texi @c @include NonCommutative.texi @node Num@'erico, Estat@'istica, Equa@value{cedilha}@~oes Diferenciais, Top @chapter Num@'erico @include Numerical.texi @node Estat@'istica, Arrays, Num@'erico, Top @chapter Estat@'istica @include Statistics.texi @node Arrays, Matrizes e @'Algebra Linear, Estat@'istica, Top @chapter Arrays @include Arrays.texi @node Matrizes e @'Algebra Linear, Fun@value{cedilha}@~oes Afins, Arrays, Top @chapter Matrizes e @'Algebra Linear @include Matrices.texi @node Fun@value{cedilha}@~oes Afins, itensor, Matrizes e @'Algebra Linear, Top @chapter Fun@value{cedilha}@~oes Afins @include Affine.texi @node itensor, ctensor, Fun@value{cedilha}@~oes Afins, Top @chapter itensor @include Itensor.texi @node ctensor, Pacote atensor, itensor, Top @chapter ctensor @include Ctensor.texi @node Pacote atensor, S@'eries, ctensor, Top @chapter Pacote atensor @include Atensor.texi @node S@'eries, Teoria dos N@'umeros, Pacote atensor, Top @chapter S@'eries @include Series.texi @node Teoria dos N@'umeros, Simetrias, S@'eries, Top @chapter Teoria dos N@'umeros @include Number.texi @node Simetrias, Grupos, Teoria dos N@'umeros, Top @chapter Simetrias @include Symmetries.texi @node Grupos, Ambiente em Tempo de Execu@value{cedilha}@~ao, Simetrias, Top @chapter Grupos @include Groups.texi @node Ambiente em Tempo de Execu@value{cedilha}@~ao, Op@value{cedilha}@~oes Diversas, Grupos, Top @chapter Ambiente em Tempo de Execu@value{cedilha}@~ao @include Runtime.texi @node Op@value{cedilha}@~oes Diversas, Regras e Modelos, Ambiente em Tempo de Execu@value{cedilha}@~ao, Top @chapter Op@value{cedilha}@~oes Diversas @include Miscellaneous.texi @node Regras e Modelos, Listas, Op@value{cedilha}@~oes Diversas, Top @chapter Regras e Modelos @include Rules.texi @node Listas, Conjuntos, Regras e Modelos, Top @chapter Listas @include Lists.texi @node Conjuntos, Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao, Listas, Top @chapter Conjuntos @include nset.texi @node Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao, Fluxo de Programa, Conjuntos, Top @chapter Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao @include Function.texi @node Fluxo de Programa, Depurando, Defini@value{cedilha}@~ao de Fun@value{cedilha}@~ao, Top @chapter Fluxo de Programa @include Program.texi @node Depurando, augmented_lagrangian, Fluxo de Programa, Top @chapter Depurando @include Debugging.texi @node augmented_lagrangian, bode, Depurando, Top @chapter augmented_lagrangian @include augmented_lagrangian.texi @node bode, cholesky, augmented_lagrangian, Top @chapter bode @include bode.texi @node cholesky, descriptive, bode, Top @chapter cholesky @include cholesky.texi @node descriptive, diag, cholesky, Top @chapter descriptive @include descriptive.texi @node diag, distrib, descriptive, Top @chapter diag @include diag.texi @node distrib, dynamics, diag, Top @chapter distrib @include distrib.texi @node dynamics, eval_string, distrib, Top @chapter dynamics @include dynamics.texi @node eval_string, f90, dynamics, Top @chapter eval_string @include eval_string.texi @node f90, ggf, eval_string, Top @chapter f90 @include f90.texi @node ggf, impdiff, f90, Top @chapter ggf @include ggf.texi @node impdiff, implicit_plot, ggf, Top @chapter impdiff @include impdiff.texi @node implicit_plot, interpol, impdiff, Top @chapter implicit_plot @include implicit_plot.texi @node interpol, lbfgs, implicit_plot, Top @chapter interpol @include interpol.texi @node lbfgs, lindstedt, interpol, Top @chapter lbfgs @include lbfgs.texi @node lindstedt, linearalgebra, lbfgs, Top @chapter lindstedt @include lindstedt.texi @node linearalgebra, lsquares, lindstedt, Top @chapter linearalgebra @include linearalgebra.texi @node lsquares, makeOrders, linearalgebra, Top @chapter lsquares @include lsquares.texi @node makeOrders, mnewton, lsquares, Top @chapter makeOrders @include makeOrders.texi @node mnewton, numericalio, makeOrders, Top @chapter mnewton @include mnewton.texi @node numericalio, opsubst, mnewton, Top @chapter numericalio @include numericalio.texi @node opsubst, orthopoly, numericalio, Top @chapter opsubst @include opsubst.texi @node orthopoly, plotdf, opsubst, Top @chapter orthopoly @include orthopoly.texi @node plotdf, romberg, orthopoly, Top @chapter plotdf @include plotdf.texi @node romberg, simplex, plotdf, Top @chapter romberg @include romberg.texi @node simplex, simplification, romberg, Top @chapter simplex @include simplex.texi @node simplification, solve_rec, simplex, Top @chapter simplification @include simplifications.texi @node solve_rec, stats, simplification, Top @chapter solve_rec @include solve_rec.texi @node stats, stirling, solve_rec, Top @chapter stats @include stats.texi @node stirling, stringproc, stats, Top @chapter stirling @include stirling.texi @node stringproc, unit, stirling, Top @chapter stringproc @include stringproc.texi @node unit, zeilberger, stringproc, Top @chapter unit @include unit.texi @node zeilberger, @'Indice de Fun@value{cedilha}@~oes e Vari@'aveis, unit, Top @chapter zeilberger @include zeilberger.texi @node @'Indice de Fun@value{cedilha}@~oes e Vari@'aveis, , zeilberger, Top @chapter @'Indice de Fun@value{cedilha}@~oes e Vari@'aveis @include Indices.texi @c end includes @bye --Boundary-00=_5TgqFnyKa5ENh63 Content-Type: text/plain; charset="iso-8859-1"; name="descriptive_ok.texi" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="descriptive_ok.texi" @c Language: Brazilian Portuguese, Encoding: iso-8859-1 @c /descriptive.texi/1.8/Mon Jul 24 10:59:45 2006// @menu * Introdu@value{cedilha}@~ao ao pacote descriptive:: * Defini@value{cedilha}@~oes para manipula@value{cedilha}@~ao da dados:: * Defini@value{cedilha}@~oes para estatistica descritiva:: * Defini@value{cedilha}@~oes para specific multivariate descriptive statistics:: * Defini@value{cedilha}@~oes para statistical graphs:: @end menu @node Introdu@value{cedilha}@~ao ao pacote descriptive, Defini@value{cedilha}@~oes para manipula@value{cedilha}@~ao da dados, descriptive, descriptive @section Introdu@value{cedilha}@~ao ao pacote descriptive Package @code{descriptive} contains a set of functions for making descriptive statistical computations and graphing. Together with the source code there are three data sets in your Maxima tree: @code{pidigits.data}, @code{wind.data} and @code{biomed.data}. They can be also downloaded from the web site @code{www.biomates.net}. Any statistics manual can be used as a reference to the functions in package @code{descriptive}. For comments, bugs or suggestions, please contact me at @var{'mario AT edu DOT xunta DOT es'}. Here is a simple example on how the descriptive functions in @code{descriptive} do they work, depending on the nature of their arguments, lists or matrices, @c ===beg=== @c load (descriptive)$ @c /* univariate sample */ mean ([a, b, c]); @c matrix ([a, b], [c, d], [e, f]); @c /* multivariate sample */ mean (%); @c ===end=== @example (%i1) load (descriptive)$ (%i2) /* univariate sample */ mean ([a, b, c]); c + b + a (%o2) --------- 3 (%i3) matrix ([a, b], [c, d], [e, f]); [ a b ] [ ] (%o3) [ c d ] [ ] [ e f ] (%i4) /* multivariate sample */ mean (%); e + c + a f + d + b (%o4) [---------, ---------] 3 3 @end example Note that in multivariate samples the mean is calculated for each column. In case of several samples with possible different sizes, the Maxima function @code{map} can be used to get the desired results for each sample, @c ===beg=== @c load (descriptive)$ @c map (mean, [[a, b, c], [d, e]]); @c ===end=== @example (%i1) load (descriptive)$ (%i2) map (mean, [[a, b, c], [d, e]]); c + b + a e + d (%o2) [---------, -----] 3 2 @end example In this case, two samples of sizes 3 and 2 were stored into a list. Univariate samples must be stored in lists like @c ===beg=== @c s1 : [3, 1, 4, 1, 5, 9, 2, 6, 5, 3, 5]; @c ===end=== @example (%i1) s1 : [3, 1, 4, 1, 5, 9, 2, 6, 5, 3, 5]; (%o1) [3, 1, 4, 1, 5, 9, 2, 6, 5, 3, 5] @end example and multivariate samples in matrices as in @c ===beg=== @c s2 : matrix ([13.17, 9.29], [14.71, 16.88], [18.50, 16.88], @c [10.58, 6.63], [13.33, 13.25], [13.21, 8.12]); @c ===end=== @example (%i1) s2 : matrix ([13.17, 9.29], [14.71, 16.88], [18.50, 16.88], [10.58, 6.63], [13.33, 13.25], [13.21, 8.12]); [ 13.17 9.29 ] [ ] [ 14.71 16.88 ] [ ] [ 18.5 16.88 ] (%o1) [ ] [ 10.58 6.63 ] [ ] [ 13.33 13.25 ] [ ] [ 13.21 8.12 ] @end example In this case, the number of columns equals the random variable dimension and the number of rows is the sample size. Data can be introduced by hand, but big samples are usually stored in plain text files. For example, file @code{pidigits.data} contains the first 100 digits of number @code{%pi}: @example 3 1 4 1 5 9 2 6 5 3 ... @end example In order to load these digits in Maxima, @c ===beg=== @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c length (s1); @c ===end=== @example (%i1) load (numericalio)$ (%i2) s1 : read_list (file_search ("pidigits.data"))$ (%i3) length (s1); (%o3) 100 @end example On the other hand, file @code{wind.data} contains daily average wind speeds at 5 meteorological stations in the Republic of Ireland (This is part of a data set taken at 12 meteorological stations. The original file is freely downloadable from the StatLib Data Repository and its analysis is discused in Haslett, J., Raftery, A. E. (1989) @var{Space-time Modelling with Long-memory Dependence: Assessing Ireland's Wind Power Resource, with Discussion}. Applied Statistics 38, 1-50). This loads the data: @c ===beg=== @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c length (s2); @c s2 [%]; /* last record */ @c ===end=== @example (%i1) load (numericalio)$ (%i2) s2 : read_matrix (file_search ("wind.data"))$ (%i3) length (s2); (%o3) 100 (%i4) s2 [%]; /* last record */ (%o4) [3.58, 6.0, 4.58, 7.62, 11.25] @end example Some samples contain non numeric data. As an example, file @code{biomed.data} (which is part of another bigger one downloaded from the StatLib Data Repository) contains four blood measures taken from two groups of patients, @code{A} and @code{B}, of different ages, @c ===beg=== @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c length (s3); @c s3 [1]; /* first record */ @c ===end=== @example (%i1) load (numericalio)$ (%i2) s3 : read_matrix (file_search ("biomed.data"))$ (%i3) length (s3); (%o3) 100 (%i4) s3 [1]; /* first record */ (%o4) [A, 30, 167.0, 89.0, 25.6, 364] @end example The first individual belongs to group @code{A}, is 30 years old and his/her blood measures were 167.0, 89.0, 25.6 and 364. One must take care when working with categorical data. In the next example, symbol @code{a} is asigned a value in some previous moment and then a sample with categorical value @code{a} is taken, @c ===beg=== @c a : 1$ @c matrix ([a, 3], [b, 5]); @c ===end=== @example (%i1) a : 1$ (%i2) matrix ([a, 3], [b, 5]); [ 1 3 ] (%o2) [ ] [ b 5 ] @end example @node Defini@value{cedilha}@~oes para manipula@value{cedilha}@~ao da dados, Defini@value{cedilha}@~oes para estatistica descritiva, Introdu@value{cedilha}@~ao ao pacote descriptive, descriptive @section Defini@value{cedilha}@~oes para manipula@value{cedilha}@~ao da dados @deffn {Function} continuous_freq (@var{list}) @deffnx {Function} continuous_freq (@var{list}, @var{m}) The argument of @code{continuous_freq} must be a list of numbers, which will be then grouped in intervals and counted how many of them belong to each group. Optionally, function @code{continuous_freq} admits a second argument indicating the number of classes, 10 is default, @c ===beg=== @c load (numericalio)$ @c load (descriptive)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c continuous_freq (s1, 5); @c ===end=== @example (%i1) load (numericalio)$ (%i2) load (descriptive)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) continuous_freq (s1, 5); (%o4) [[0, 1.8, 3.6, 5.4, 7.2, 9.0], [16, 24, 18, 17, 25]] @end example The first list contains the interval limits and the second the corresponding counts: there are 16 digits inside the interval @code{[0, 1.8]}, that is 0's and 1's, 24 digits in @code{(1.8, 3.6]}, that is 2's and 3's, and so on. @end deffn @deffn {Function} discrete_freq (@var{list}) Counts absolute frequencies in discrete samples, both numeric and categorical. Its unique argument is a list, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data")); @c discrete_freq (s1); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data")); (%o3) [3, 1, 4, 1, 5, 9, 2, 6, 5, 3, 5, 8, 9, 7, 9, 3, 2, 3, 8, 4, 6, 2, 6, 4, 3, 3, 8, 3, 2, 7, 9, 5, 0, 2, 8, 8, 4, 1, 9, 7, 1, 6, 9, 3, 9, 9, 3, 7, 5, 1, 0, 5, 8, 2, 0, 9, 7, 4, 9, 4, 4, 5, 9, 2, 3, 0, 7, 8, 1, 6, 4, 0, 6, 2, 8, 6, 2, 0, 8, 9, 9, 8, 6, 2, 8, 0, 3, 4, 8, 2, 5, 3, 4, 2, 1, 1, 7, 0, 6, 7] (%i4) discrete_freq (s1); (%o4) [[0, 1, 2, 3, 4, 5, 6, 7, 8, 9], [8, 8, 12, 12, 10, 8, 9, 8, 12, 13]] @end example The first list gives the sample values and the second their absolute frequencies. Commands @code{? col} and @code{? transpose} should help you to understand the last input. @end deffn @deffn {Function} subsample (@var{data_matrix}, @var{logical_expression}) @deffnx {Function} subsample (@var{data_matrix}, @var{logical_expression}, @var{col_num}, @var{col_num}, ...) This is a sort of variation of the Maxima @code{submatrix} function. The first argument is the name of the data matrix, the second is a quoted logical expression and optional additional arguments are the numbers of the columns to be taken. Its behaviour is better understood with examples, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c subsample (s2, '(%c[1] > 18)); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) subsample (s2, '(%c[1] > 18)); [ 19.38 15.37 15.12 23.09 25.25 ] [ ] [ 18.29 18.66 19.08 26.08 27.63 ] (%o4) [ ] [ 20.25 21.46 19.95 27.71 23.38 ] [ ] [ 18.79 18.96 14.46 26.38 21.84 ] @end example These are multivariate records in which the wind speeds in the first meteorological station were greater than 18. See that in the quoted logical expression the @var{i}-th component is refered to as @code{%c[i]}. Symbol @code{%c[i]} is used inside function @code{subsample}, therefore when used as a categorical variable, Maxima gets confused. In the following example, we request only the first, second and fifth components of those records with wind speeds greater or equal than 16 in station number 1 and lesser than 25 knots in station number 4, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c subsample (s2, '(%c[1] >= 16 and %c[4] < 25), 1, 2, 5); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) subsample (s2, '(%c[1] >= 16 and %c[4] < 25), 1, 2, 5); [ 19.38 15.37 25.25 ] [ ] [ 17.33 14.67 19.58 ] (%o4) [ ] [ 16.92 13.21 21.21 ] [ ] [ 17.25 18.46 23.87 ] @end example Here is an example with the categorical variables of @code{biomed.data}. We want the records corresponding to those patients in group @code{B} who are older than 38 years, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c subsample (s3, '(%c[1] = B and %c[2] > 38)); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s3 : read_matrix (file_search ("biomed.data"))$ (%i4) subsample (s3, '(%c[1] = B and %c[2] > 38)); [ B 39 28.0 102.3 17.1 146 ] [ ] [ B 39 21.0 92.4 10.3 197 ] [ ] [ B 39 23.0 111.5 10.0 133 ] [ ] [ B 39 26.0 92.6 12.3 196 ] (%o4) [ ] [ B 39 25.0 98.7 10.0 174 ] [ ] [ B 39 21.0 93.2 5.9 181 ] [ ] [ B 39 18.0 95.0 11.3 66 ] [ ] [ B 39 39.0 88.5 7.6 168 ] @end example Probably, the statistical analysis will involve only the blood measures, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c subsample (s3, '(%c[1] = B and %c[2] > 38), 3, 4, 5, 6); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s3 : read_matrix (file_search ("biomed.data"))$ (%i4) subsample (s3, '(%c[1] = B and %c[2] > 38), 3, 4, 5, 6); [ 28.0 102.3 17.1 146 ] [ ] [ 21.0 92.4 10.3 197 ] [ ] [ 23.0 111.5 10.0 133 ] [ ] [ 26.0 92.6 12.3 196 ] (%o4) [ ] [ 25.0 98.7 10.0 174 ] [ ] [ 21.0 93.2 5.9 181 ] [ ] [ 18.0 95.0 11.3 66 ] [ ] [ 39.0 88.5 7.6 168 ] @end example This is the multivariate mean of @code{s3}, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c mean (s3); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s3 : read_matrix (file_search ("biomed.data"))$ (%i4) mean (s3); 65 B + 35 A 317 6 NA + 8145.0 (%o4) [-----------, ---, 87.178, -------------, 18.123, 100 10 100 3 NA + 19587 ------------] 100 @end example Here, the first component is meaningless, since @code{A} and @code{B} are categorical, the second component is the mean age of individuals in rational form, and the fourth and last values exhibit some strange behaviour. This is because symbol @code{NA} is used here to indicate @var{non available} data, and the two means are of course nonsense. A possible solution would be to take out from the matrix those rows with @code{NA} symbols, although this deserves some loss of information, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c mean (subsample (s3, '(%c[4] # NA and %c[6] # NA), 3, 4, 5, 6)); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s3 : read_matrix (file_search ("biomed.data"))$ (%i4) mean (subsample (s3, '(%c[4] # NA and %c[6] # NA), 3, 4, 5, 6)); (%o4) [79.4923076923077, 86.2032967032967, 16.93186813186813, 2514 ----] 13 @end example @end deffn @node Defini@value{cedilha}@~oes para estatistica descritiva, Defini@value{cedilha}@~oes para specific multivariate descriptive statistics, Defini@value{cedilha}@~oes para manipula@value{cedilha}@~ao da dados, descriptive @section Defini@value{cedilha}@~oes para estatistica descritiva @deffn {Function} mean (@var{list}) @deffnx {Function} mean (@var{matrix}) This is the sample mean, defined as @ifhtml @example n ==== _ 1 \ x = - > x n / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== _ 1 \ x = - > x n / i ==== i = 1 @end example @end ifinfo @tex $${\bar{x}={1\over{n}}{\sum_{i=1}^{n}{x_{i}}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c mean (s1); @c %, numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c mean (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) mean (s1); 471 (%o4) --- 100 (%i5) %, numer; (%o5) 4.71 (%i6) s2 : read_matrix (file_search ("wind.data"))$ (%i7) mean (s2); (%o7) [9.9485, 10.1607, 10.8685, 15.7166, 14.8441] @end example @end deffn @deffn {Function} var (@var{list}) @deffnx {Function} var (@var{matrix}) This is the sample variance, defined as @ifhtml @example n ==== 2 1 \ _ 2 s = - > (x - x) n / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 2 1 \ _ 2 s = - > (x - x) n / i ==== i = 1 @end example @end ifinfo @tex $${{1}\over{n}}{\sum_{i=1}^{n}{(x_{i}-\bar{x})^2}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c var (s1), numer; @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) var (s1), numer; (%o4) 8.425899999999999 @end example See also function @code{var1}. @end deffn @deffn {Function} var1 (@var{list}) @deffnx {Function} var1 (@var{matrix}) This is the sample variance, defined as @ifhtml @example n ==== 1 \ _ 2 --- > (x - x) n-1 / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ 2 --- > (x - x) n-1 / i ==== i = 1 @end example @end ifinfo @tex $${{1\over{n-1}}{\sum_{i=1}^{n}{(x_{i}-\bar{x})^2}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c var1 (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c var1 (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) var1 (s1), numer; (%o4) 8.5110101010101 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) var1 (s2); (%o6) [17.39586540404041, 15.13912778787879, 15.63204924242424, 32.50152569696971, 24.66977392929294] @end example See also function @code{var}. @end deffn @deffn {Function} std (@var{list}) @deffnx {Function} std (@var{matrix}) This is the the square root of function @code{var}, the variance with denominator @math{n}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c std (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c std (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) std (s1), numer; (%o4) 2.902740084816414 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) std (s2); (%o6) [4.149928523480858, 3.871399812729241, 3.933920277534866, 5.672434260526957, 4.941970881136392] @end example See also functions @code{var} and @code{std1}. @end deffn @deffn {Function} std1 (@var{list}) @deffnx {Function} std1 (@var{matrix}) This is the the square root of function @code{var1}, the variance with denominator @math{n-1}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c std1 (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c std1 (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) std1 (s1), numer; (%o4) 2.917363553109228 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) std1 (s2); (%o6) [4.17083509672109, 3.89090320978032, 3.953738641137555, 5.701010936401517, 4.966867617451963] @end example See also functions @code{var1} and @code{std}. @end deffn @deffn {Function} noncentral_moment (@var{list}, @var{k}) @deffnx {Function} noncentral_moment (@var{matrix}, @var{k}) The non central moment of order @math{k}, defined as @ifhtml @example n ==== 1 \ k - > x n / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ k - > x n / i ==== i = 1 @end example @end ifinfo @tex $${{1\over{n}}{\sum_{i=1}^{n}{x_{i}^k}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c noncentral_moment (s1, 1), numer; /* the mean */ @c s2 : read_matrix (file_search ("wind.data"))$ @c noncentral_moment (s2, 5); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) noncentral_moment (s1, 1), numer; /* the mean */ (%o4) 4.71 (%i6) s2 : read_matrix (file_search ("wind.data"))$ (%i7) noncentral_moment (s2, 5); (%o7) [319793.8724761506, 320532.1923892463, 391249.5621381556, 2502278.205988911, 1691881.797742255] @end example See also function @code{central_moment}. @end deffn @deffn {Function} central_moment (@var{list}, @var{k}) @deffnx {Function} central_moment (@var{matrix}, @var{k}) The central moment of order @math{k}, defined as @ifhtml @example n ==== 1 \ _ k - > (x - x) n / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ k - > (x - x) n / i ==== i = 1 @end example @end ifinfo @tex $${{1\over{n}}{\sum_{i=1}^{n}{(x_{i}-\bar{x})^k}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c central_moment (s1, 2), numer; /* the variance */ @c s2 : read_matrix (file_search ("wind.data"))$ @c central_moment (s2, 3); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) central_moment (s1, 2), numer; /* the variance */ (%o4) 8.425899999999999 (%i6) s2 : read_matrix (file_search ("wind.data"))$ (%i7) central_moment (s2, 3); (%o7) [11.29584771375004, 16.97988248298583, 5.626661952750102, 37.5986572057918, 25.85981904394192] @end example See also functions @code{central_moment} and @code{mean}. @end deffn @deffn {Function} cv (@var{list}) @deffnx {Function} cv (@var{matrix}) The variation coefficient is the quotient between the sample standard deviation (@code{std}) and the @code{mean}, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c cv (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c cv (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) cv (s1), numer; (%o4) .6193977819764815 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) cv (s2); (%o6) [.4192426091090204, .3829365309260502, 0.363779605385983, .3627381836021478, .3346021393989506] @end example See also functions @code{std} and @code{mean}. @end deffn @deffn {Function} mini (@var{list}) @deffnx {Function} mini (@var{matrix}) This is the minimum value of the sample @var{list}, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c mini (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c mini (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) mini (s1); (%o4) 0 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) mini (s2); (%o6) [0.58, 0.5, 2.67, 5.25, 5.17] @end example See also function @code{maxi}. @end deffn @deffn {Function} maxi (@var{list}) @deffnx {Function} maxi (@var{matrix}) This is the maximum value of the sample @var{list}, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c maxi (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c maxi (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) maxi (s1); (%o4) 9 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) maxi (s2); (%o6) [20.25, 21.46, 20.04, 29.63, 27.63] @end example See also function @code{mini}. @end deffn @deffn {Function} range (@var{list}) @deffnx {Function} range (@var{matrix}) The range is the difference between the extreme values. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c range (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c range (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) range (s1); (%o4) 9 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) range (s2); (%o6) [19.67, 20.96, 17.37, 24.38, 22.46] @end example @end deffn @deffn {Function} quantile (@var{list}, @var{p}) @deffnx {Function} quantile (@var{matrix}, @var{p}) This is the @var{p}-@code{quantile}, with @var{p} a number in @math{[0, 1]}, of the sample @var{list}. Although there are several Defini@value{cedilha}@~oes para the sample quantile (Hyndman, R. J., Fan, Y. (1996) @var{Sample quantiles in statistical packages}. American Statistician, 50, 361-365), the one based on linear interpolation is implemented in package @code{descriptive}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c /* 1st and 3rd quartiles */ [quantile (s1, 1/4), quantile (s1, 3/4)], numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c quantile (s2, 1/4); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) /* 1st and 3rd quartiles */ [quantile (s1, 1/4), quantile (s1, 3/4)], numer; (%o4) [2.0, 7.25] (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) quantile (s2, 1/4); (%o6) [7.2575, 7.477500000000001, 7.82, 11.28, 11.48] @end example @end deffn @deffn {Function} median (@var{list}) @deffnx {Function} median (@var{matrix}) Once the sample is ordered, if the sample size is odd the median is the central value, otherwise it is the mean of the two central values. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c median (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c median (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) median (s1); 9 (%o4) - 2 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) median (s2); (%o6) [10.06, 9.855, 10.73, 15.48, 14.105] @end example The median is the 1/2-@code{quantile}. See also function @code{quantile}. @end deffn @deffn {Function} qrange (@var{list}) @deffnx {Function} qrange (@var{matrix}) The interquartilic range is the difference between the third and first quartiles, @code{quantile(list,3/4) - quantile(list,1/4)}, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c qrange (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c qrange (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) qrange (s1); 21 (%o4) -- 4 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) qrange (s2); (%o6) [5.385, 5.572499999999998, 6.0225, 8.729999999999999, 6.650000000000002] @end example See also function @code{quantile}. @end deffn @deffn {Function} mean_deviation (@var{list}) @deffnx {Function} mean_deviation (@var{matrix}) The mean deviation, defined as @ifhtml @example n ==== 1 \ _ - > |x - x| n / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ - > |x - x| n / i ==== i = 1 @end example @end ifinfo @tex $${{1\over{n}}{\sum_{i=1}^{n}{|x_{i}-\bar{x}|}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c mean_deviation (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c mean_deviation (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) mean_deviation (s1); 51 (%o4) -- 20 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) mean_deviation (s2); (%o6) [3.287959999999999, 3.075342, 3.23907, 4.715664000000001, 4.028546000000002] @end example See also function @code{mean}. @end deffn @deffn {Function} median_deviation (@var{list}) @deffnx {Function} median_deviation (@var{matrix}) The median deviation, defined as @ifhtml @example n ==== 1 \ - > |x - med| n / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ - > |x - med| n / i ==== i = 1 @end example @end ifinfo @tex $${{1\over{n}}{\sum_{i=1}^{n}{|x_{i}-med|}}}$$ @end tex where @code{med} is the median of @var{list}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c median_deviation (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c median_deviation (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) median_deviation (s1); 5 (%o4) - 2 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) median_deviation (s2); (%o6) [2.75, 2.755, 3.08, 4.315, 3.31] @end example See also function @code{mean}. @end deffn @deffn {Function} harmonic_mean (@var{list}) @deffnx {Function} harmonic_mean (@var{matrix}) The harmonic mean, defined as @ifhtml @example n -------- n ==== \ 1 > -- / x ==== i i = 1 @end example @end ifhtml @ifinfo @example n -------- n ==== \ 1 > -- / x ==== i i = 1 @end example @end ifinfo @tex $${{n}\over{\sum_{i=1}^{n}{{{1}\over{x_{i}}}}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c y : [5, 7, 2, 5, 9, 5, 6, 4, 9, 2, 4, 2, 5]$ @c harmonic_mean (y), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c harmonic_mean (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) y : [5, 7, 2, 5, 9, 5, 6, 4, 9, 2, 4, 2, 5]$ (%i4) harmonic_mean (y), numer; (%o4) 3.901858027632205 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) harmonic_mean (s2); (%o6) [6.948015590052786, 7.391967752360356, 9.055658197151745, 13.44199028193692, 13.01439145898509] @end example See also functions @code{mean} and @code{geometric_mean}. @end deffn @deffn {Function} geometric_mean (@var{list}) @deffnx {Function} geometric_mean (@var{matrix}) The geometric mean, defined as @ifhtml @example / n \ 1/n | /===\ | | ! ! | | ! ! x | | ! ! i| | i = 1 | \ / @end example @end ifhtml @ifinfo @example / n \ 1/n | /===\ | | ! ! | | ! ! x | | ! ! i| | i = 1 | \ / @end example @end ifinfo @tex $$\left(\prod_{i=1}^{n}{x_{i}}\right)^{{{1}\over{n}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c y : [5, 7, 2, 5, 9, 5, 6, 4, 9, 2, 4, 2, 5]$ @c geometric_mean (y), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c geometric_mean (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) y : [5, 7, 2, 5, 9, 5, 6, 4, 9, 2, 4, 2, 5]$ (%i4) geometric_mean (y), numer; (%o4) 4.454845412337012 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) geometric_mean (s2); (%o6) [8.82476274347979, 9.22652604739361, 10.0442675714889, 14.61274126349021, 13.96184163444275] @end example See also functions @code{mean} and @code{harmonic_mean}. @end deffn @deffn {Function} kurtosis (@var{list}) @deffnx {Function} kurtosis (@var{matrix}) The kurtosis coefficient, defined as @ifhtml @example n ==== 1 \ _ 4 ---- > (x - x) - 3 4 / i n s ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ 4 ---- > (x - x) - 3 4 / i n s ==== i = 1 @end example @end ifinfo @tex $${{1\over{n s^4}}{\sum_{i=1}^{n}{(x_{i}-\bar{x})^4}}-3}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c kurtosis (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c kurtosis (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) kurtosis (s1), numer; (%o4) - 1.273247946514421 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) kurtosis (s2); (%o6) [- .2715445622195385, 0.119998784429451, - .4275233490482866, - .6405361979019522, - .4952382132352935] @end example See also functions @code{mean}, @code{var} and @code{skewness}. @end deffn @deffn {Function} skewness (@var{list}) @deffnx {Function} skewness (@var{matrix}) The skewness coefficient, defined as @ifhtml @example n ==== 1 \ _ 3 ---- > (x - x) 3 / i n s ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ 3 ---- > (x - x) 3 / i n s ==== i = 1 @end example @end ifinfo @tex $${{1\over{n s^3}}{\sum_{i=1}^{n}{(x_{i}-\bar{x})^3}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c skewness (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c skewness (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) skewness (s1), numer; (%o4) .009196180476450306 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) skewness (s2); (%o6) [.1580509020000979, .2926379232061854, .09242174416107717, .2059984348148687, .2142520248890832] @end example See also functions @code{mean}, @code{var} and @code{kurtosis}. @end deffn @deffn {Function} pearson_skewness (@var{list}) @deffnx {Function} pearson_skewness (@var{matrix}) Pearson's skewness coefficient, defined as @ifhtml @example _ 3 (x - med) ----------- s @end example @end ifhtml @ifinfo @example _ 3 (x - med) ----------- s @end example @end ifinfo @tex $${{3\,\left(\bar{x}-med\right)}\over{s}}$$ @end tex where @var{med} is the median of @var{list}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c pearson_skewness (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c pearson_skewness (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) pearson_skewness (s1), numer; (%o4) .2159484029093895 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) pearson_skewness (s2); (%o6) [- .08019976629211892, .2357036272952649, .1050904062491204, .1245042340592368, .4464181795804519] @end example See also functions @code{mean}, @code{var} and @code{median}. @end deffn @deffn {Function} quartile_skewness (@var{list}) @deffnx {Function} quartile_skewness (@var{matrix}) The quartile skewness coefficient, defined as @ifhtml @example c - 2 c + c 3/4 1/2 1/4 -------------------- c - c 3/4 1/4 @end example @end ifhtml @ifinfo @example c - 2 c + c 3/4 1/2 1/4 -------------------- c - c 3/4 1/4 @end example @end ifinfo @tex $${{c_{{{3}\over{4}}}-2\,c_{{{1}\over{2}}}+c_{{{1}\over{4}}}}\over{c _{{{3}\over{4}}}-c_{{{1}\over{4}}}}}$$ @end tex where @math{c_p} is the @var{p}-quantile of sample @var{list}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c quartile_skewness (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c quartile_skewness (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) quartile_skewness (s1), numer; (%o4) .04761904761904762 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) quartile_skewness (s2); (%o6) [- 0.0408542246982353, .1467025572005382, 0.0336239103362392, .03780068728522298, 0.210526315789474] @end example See also function @code{quantile}. @end deffn @node Defini@value{cedilha}@~oes para specific multivariate descriptive statistics, Defini@value{cedilha}@~oes para statistical graphs, Defini@value{cedilha}@~oes para estatistica descritiva, descriptive @section Defini@value{cedilha}@~oes para specific multivariate descriptive statistics @deffn {Function} cov (@var{matrix}) The covariance matrix of the multivariate sample, defined as @ifhtml @example n ==== 1 \ _ _ S = - > (X - X) (X - X)' n / j j ==== j = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ _ S = - > (X - X) (X - X)' n / j j ==== j = 1 @end example @end ifinfo @tex $${S={1\over{n}}{\sum_{j=1}^{n}{\left(X_{j}-\bar{X}\right)\,\left(X_{j}-\bar{X}\right)'}}}$$ @end tex where @math{X_j} is the @math{j}-th row of the sample matrix. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c fpprintprec : 7$ /* change precision for pretty output */ @c cov (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) fpprintprec : 7$ /* change precision for pretty output */ (%i5) cov (s2); [ 17.22191 13.61811 14.37217 19.39624 15.42162 ] [ ] [ 13.61811 14.98774 13.30448 15.15834 14.9711 ] [ ] (%o5) [ 14.37217 13.30448 15.47573 17.32544 16.18171 ] [ ] [ 19.39624 15.15834 17.32544 32.17651 20.44685 ] [ ] [ 15.42162 14.9711 16.18171 20.44685 24.42308 ] @end example See also function @code{cov1}. @end deffn @deffn {Function} cov1 (@var{matrix}) The covariance matrix of the multivariate sample, defined as @ifhtml @example n ==== 1 \ _ _ S = --- > (X - X) (X - X)' 1 n-1 / j j ==== j = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ _ S = --- > (X - X) (X - X)' 1 n-1 / j j ==== j = 1 @end example @end ifinfo @tex $${{1\over{n-1}}{\sum_{j=1}^{n}{\left(X_{j}-\bar{X}\right)\,\left(X_{j}-\bar{X}\right)'}}}$$ @end tex where @math{X_j} is the @math{j}-th row of the sample matrix. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c fpprintprec : 7$ /* change precision for pretty output */ @c cov1 (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) fpprintprec : 7$ /* change precision for pretty output */ (%i5) cov1 (s2); [ 17.39587 13.75567 14.51734 19.59216 15.5774 ] [ ] [ 13.75567 15.13913 13.43887 15.31145 15.12232 ] [ ] (%o5) [ 14.51734 13.43887 15.63205 17.50044 16.34516 ] [ ] [ 19.59216 15.31145 17.50044 32.50153 20.65338 ] [ ] [ 15.5774 15.12232 16.34516 20.65338 24.66977 ] @end example See also function @code{cov}. @end deffn @deffn {Function} global_variances (@var{matrix}) @deffnx {Function} global_variances (@var{matrix}, @var{logical_value}) Function @code{global_variances} returns a list of global variance measures: @itemize @bullet @item @var{total variance}: @code{trace(S_1)}, @item @var{mean variance}: @code{trace(S_1)/p}, @item @var{generalized variance}: @code{determinant(S_1)}, @item @var{generalized standard deviation}: @code{sqrt(determinant(S_1))}, @item @var{efective variance} @code{determinant(S_1)^(1/p)}, (defined in: Pe@~na, D. (2002) @var{An@'alisis de datos multivariantes}; McGraw-Hill, Madrid.) @item @var{efective standard deviation}: @code{determinant(S_1)^(1/(2*p))}. @end itemize where @var{p} is the dimension of the multivariate random variable and @math{S_1} the covariance matrix returned by @code{cov1}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c global_variances (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) global_variances (s2); (%o4) [105.338342060606, 21.06766841212119, 12874.34690469686, 113.4651792608502, 6.636590811800794, 2.576158149609762] @end example Function @code{global_variances} has an optional logical argument: @code{global_variances(x,true)} tells Maxima that @code{x} is the data matrix, making the same as @code{global_variances(x)}. On the other hand, @code{global_variances(x,false)} means that @code{x} is not the data matrix, but the covariance matrix, avoiding its recalculation, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c s : cov1 (s2)$ @c global_variances (s, false); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) s : cov1 (s2)$ (%i5) global_variances (s, false); (%o5) [105.338342060606, 21.06766841212119, 12874.34690469686, 113.4651792608502, 6.636590811800794, 2.576158149609762] @end example See also @code{cov} and @code{cov1}. @end deffn @deffn {Function} cor (@var{matrix}) @deffnx {Function} cor (@var{matrix}, @var{logical_value}) The correlation matrix of the multivariate sample. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c fpprintprec:7$ @c s2 : read_matrix (file_search ("wind.data"))$ @c cor (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) fpprintprec:7$ (%i4) s2 : read_matrix (file_search ("wind.data"))$ (%i5) cor (s2); [ 1.0 .8476339 .8803515 .8239624 .7519506 ] [ ] [ .8476339 1.0 .8735834 .6902622 0.782502 ] [ ] (%o5) [ .8803515 .8735834 1.0 .7764065 .8323358 ] [ ] [ .8239624 .6902622 .7764065 1.0 .7293848 ] [ ] [ .7519506 0.782502 .8323358 .7293848 1.0 ] @end example Function @code{cor} has an optional logical argument: @code{cor(x,true)} tells Maxima that @code{x} is the data matrix, making the same as @code{cor(x)}. On the other hand, @code{cor(x,false)} means that @code{x} is not the data matrix, but the covariance matrix, avoiding its recalculation, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c fpprintprec:7$ @c s2 : read_matrix (file_search ("wind.data"))$ @c s : cov1 (s2)$ @c cor (s, false); /* this is faster */ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) fpprintprec:7$ (%i4) s2 : read_matrix (file_search ("wind.data"))$ (%i5) s : cov1 (s2)$ (%i6) cor (s, false); /* this is faster */ [ 1.0 .8476339 .8803515 .8239624 .7519506 ] [ ] [ .8476339 1.0 .8735834 .6902622 0.782502 ] [ ] (%o6) [ .8803515 .8735834 1.0 .7764065 .8323358 ] [ ] [ .8239624 .6902622 .7764065 1.0 .7293848 ] [ ] [ .7519506 0.782502 .8323358 .7293848 1.0 ] @end example See also @code{cov} and @code{cov1}. @end deffn @deffn {Function} list_correlations (@var{matrix}) @deffnx {Function} list_correlations (@var{matrix}, @var{logical_value}) Function @code{list_correlations} returns a list of correlation measures: @itemize @bullet @item @var{precision matrix}: the inverse of the covariance matrix @math{S_1}, @ifhtml @example -1 ij S = (s ) 1 i,j = 1,2,...,p @end example @end ifhtml @ifinfo @example -1 ij S = (s ) 1 i,j = 1,2,...,p @end example @end ifinfo @tex $${S_{1}^{-1}}={\left(s^{ij}\right)_{i,j=1,2,\ldots, p}}$$ @end tex @item @var{multiple correlation vector}: @math{(R_1^2, R_2^2, ..., R_p^2)}, with @ifhtml @example 2 1 R = 1 - ------- i ii s s ii @end example @end ifhtml @ifinfo @example 2 1 R = 1 - ------- i ii s s ii @end example @end ifinfo @tex $${R_{i}^{2}}={1-{{1}\over{s^{ii}s_{ii}}}}$$ @end tex being an indicator of the goodness of fit of the linear multivariate regression model on @math{X_i} when the rest of variables are used as regressors. @item @var{partial correlation matrix}: with element @math{(i, j)} being @ifhtml @example ij s r = - ------------ ij.rest / ii jj\ 1/2 |s s | \ / @end example @end ifhtml @ifinfo @example ij s r = - ------------ ij.rest / ii jj\ 1/2 |s s | \ / @end example @end ifinfo @tex $${r_{ij.rest}}={-{{s^{ij}}\over \sqrt{s^{ii}s^{jj}}}}$$ @end tex @end itemize Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c z : list_correlations (s2)$ @c fpprintprec : 5$ /* for pretty output */ @c z[1]; /* precision matrix */ @c z[2]; /* multiple correlation vector */ @c z[3]; /* partial correlation matrix */ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) z : list_correlations (s2)$ (%i5) fpprintprec : 5$ /* for pretty output */ (%i6) z[1]; /* precision matrix */ [ .38486 - .13856 - .15626 - .10239 .031179 ] [ ] [ - .13856 .34107 - .15233 .038447 - .052842 ] [ ] (%o6) [ - .15626 - .15233 .47296 - .024816 - .10054 ] [ ] [ - .10239 .038447 - .024816 .10937 - .034033 ] [ ] [ .031179 - .052842 - .10054 - .034033 .14834 ] (%i7) z[2]; /* multiple correlation vector */ (%o7) [.85063, .80634, .86474, .71867, .72675] (%i8) z[3]; /* partial correlation matrix */ [ - 1.0 .38244 .36627 .49908 - .13049 ] [ ] [ .38244 - 1.0 .37927 - .19907 .23492 ] [ ] (%o8) [ .36627 .37927 - 1.0 .10911 .37956 ] [ ] [ .49908 - .19907 .10911 - 1.0 .26719 ] [ ] [ - .13049 .23492 .37956 .26719 - 1.0 ] @end example Function @code{list_correlations} also has an optional logical argument: @code{list_correlations(x,true)} tells Maxima that @code{x} is the data matrix, making the same as @code{list_correlations(x)}. On the other hand, @code{list_correlations(x,false)} means that @code{x} is not the data matrix, but the covariance matrix, avoiding its recalculation. See also @code{cov} and @code{cov1}. @end deffn @node Defini@value{cedilha}@~oes para statistical graphs, , Defini@value{cedilha}@~oes para specific multivariate descriptive statistics, descriptive @section Defini@value{cedilha}@~oes para statistical graphs @deffn {Function} dataplot (@var{list}) @deffnx {Function} dataplot (@var{list}, @var{option_1}, @var{option_2}, ...) @deffnx {Function} dataplot (@var{matrix}) @deffnx {Function} dataplot (@var{matrix}, @var{option_1}, @var{option_2}, ...) Funtion @code{dataplot} permits direct visualization of sample data, both univariate (@var{list}) and multivariate (@var{matrix}). Giving values to the following @var{options} some aspects of the plot can be controlled: @itemize @bullet @item @code{'outputdev}, default @code{"x"}, indicates the output device; correct values are @code{"x"}, @code{"eps"} and @code{"png"}, for the screen, postscript and png format files, respectively. @item @code{'maintitle}, default @code{""}, is the main title between double quotes. @item @code{'axisnames}, default @code{["x","y","z"]}, is a list with the names of axis @code{x}, @code{y} and @code{z}. @item @code{'joined}, default @code{false}, a logical value to select points in 2D to be joined or isolated. @item @code{'picturescales}, default @code{[1.0, 1.0]}, scaling factors for the size of the plot. @item @code{'threedim}, default @code{true}, tells Maxima whether to plot a three column matrix with a 3D diagram or a multivariate scatterplot. See examples bellow. @item @code{'axisrot}, default @code{[60, 30]}, changes the point of view when @code{'threedim} is set to @code{true} and data are stored in a three column matrix. The first number is the rotation angle of the @var{x}-axis, and the second number is the rotation angle of the @var{z}-axis, both measured in degrees. @item @code{'nclasses}, default @code{10}, is the number of classes for the histograms in the diagonal of multivariate scatterplots. @item @code{'pointstyle}, default @code{1}, is an integer to indicate how to display sample points. @end itemize For example, with the following input a simple plot of the first twenty digits of @code{%pi} is requested and the output stored in an eps file. @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c dataplot (makelist (s1[k], k, 1, 20), 'pointstyle = 3)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) dataplot (makelist (s1[k], k, 1, 20), 'pointstyle = 3)$ @end example Note that one dimensional data are plotted as a time series. In the next case, same more data with different settings, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c dataplot (makelist (s1[k], k, 1, 50), 'maintitle = "First pi digits", @c 'axisnames = ["digit order", "digit value"], 'pointstyle = 2, @c 'joined = true)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) dataplot (makelist (s1[k], k, 1, 50), 'maintitle = "First pi digits", 'axisnames = ["digit order", "digit value"], 'pointstyle = 2, 'joined = true)$ @end example Function @code{dataplot} can be used to plot points in the plane. The next example is a scatterplot of the pairs of wind speeds corresponding to the first and fifth meteorological stations, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c dataplot (submatrix (s2, 2, 3, 4), 'pointstyle = 2, @c 'maintitle = "Pairs of wind speeds measured in knots", @c 'axisnames = ["Wind speed in A", "Wind speed in E"])$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) dataplot (submatrix (s2, 2, 3, 4), 'pointstyle = 2, 'maintitle = "Pairs of wind speeds measured in knots", 'axisnames = ["Wind speed in A", "Wind speed in E"])$ @end example If points are stored in a two column matrix, @code{dataplot} can plot them directly, but if they are formatted as a list of pairs, their must be transformed to a matrix as in the following example. @c ===beg=== @c load (descriptive)$ @c x : [[-1, 2], [5, 7], [5, -3], [-6, -9], [-4, 6]]$ @c dataplot (apply ('matrix, x), 'maintitle = "Points", @c 'joined = true, 'axisnames = ["", ""], 'picturescales = [0.5, 1.0])$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) x : [[-1, 2], [5, 7], [5, -3], [-6, -9], [-4, 6]]$ (%i3) dataplot (apply ('matrix, x), 'maintitle = "Points", 'joined = true, 'axisnames = ["", ""], 'picturescales = [0.5, 1.0])$ @end example Points in three dimensional space can be seen as a projection on the plane. In this example, plots of wind speeds corresponding to three meteorological stations are requested, first in a 3D plot and then in a multivariate scatterplot. @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c /* 3D plot */ dataplot (submatrix (s2, 4, 5), 'pointstyle = 2, @c 'maintitle = "Pairs of wind speeds measured in knots", @c 'axisnames = ["Station A", "Station B", "Station C"])$ @c /* Multivariate scatterplot */ dataplot (submatrix (s2, 4, 5), @c 'nclasses = 6, 'threedim = false)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) /* 3D plot */ dataplot (submatrix (s2, 4, 5), 'pointstyle = 2, 'maintitle = "Pairs of wind speeds measured in knots", 'axisnames = ["Station A", "Station B", "Station C"])$ (%i5) /* Multivariate scatterplot */ dataplot (submatrix (s2, 4, 5), 'nclasses = 6, 'threedim = false)$ @end example Note that in the last example, the number of classes in the histograms of the diagonal is set to 6, and that option @code{'threedim} is set to @code{false}. For more than three dimensions only multivariate scatterplots are possible, as in @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c dataplot (s2)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) dataplot (s2)$ @end example @end deffn @deffn {Function} histogram (@var{list}) @deffnx {Function} histogram (@var{list}, @var{option_1}, @var{option_2}, ...) @deffnx {Function} histogram (@var{one_column_matrix}) @deffnx {Function} histogram (@var{one_column_matrix}, @var{option_1}, @var{option_2}, ...) This function plots an histogram. Sample data must be stored in a list of numbers or a one column matrix. Giving values to the following @var{options} some aspects of the plot can be controlled: @itemize @bullet @item @code{'outputdev}, default @code{"x"}, indicates the output device; correct values are @code{"x"}, @code{"eps"} and @code{"png"}, for the screen, postscript and png format files, respectively. @item @code{'maintitle}, default @code{""}, is the main title between double quotes. @item @code{'axisnames}, default @code{["x", "Fr."]}, is a list with the names of axis @code{x} and @code{y}. @item @code{'picturescales}, default @code{[1.0, 1.0]}, scaling factors for the size of the plot. @item @code{'nclasses}, default @code{10}, is the number of classes or bars. @item @code{'relbarwidth}, default @code{0.9}, a decimal number between 0 and 1 to control bars width. @item @code{'barcolor}, default @code{1}, an integer to indicate bars color. @item @code{'colorintensity}, default @code{1}, a decimal number between 0 and 1 to fix color intensity. @end itemize In the next two examples, histograms are requested for the first 100 digits of number @code{%pi} and for the wind speeds in the third meteorological station. @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c histogram (s1, 'maintitle = "pi digits", 'axisnames = ["", "Absolute frequency"], @c 'relbarwidth = 0.2, 'barcolor = 3, 'colorintensity = 0.6)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c histogram (col (s2, 3), 'colorintensity = 0.3)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) histogram (s1, 'maintitle = "pi digits", 'axisnames = ["", "Absolute frequency"], 'relbarwidth = 0.2, 'barcolor = 3, 'colorintensity = 0.6)$ (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) histogram (col (s2, 3), 'colorintensity = 0.3)$ @end example Note that in the first case, @code{s1} is a list and in the second example, @code{col(s2,3)} is a matrix. See also function @code{barsplot}. @end deffn @deffn {Function} barsplot (@var{list}) @deffnx {Function} barsplot (@var{list}, @var{option_1}, @var{option_2}, ...) @deffnx {Function} barsplot (@var{one_column_matrix}) @deffnx {Function} barsplot (@var{one_column_matrix}, @var{option_1}, @var{option_2}, ...) Similar to @code{histogram} but for discrete, numeric or categorical, statistical variables. These are the options, @itemize @bullet @item @code{'outputdev}, default @code{"x"}, indicates the output device; correct values are @code{"x"}, @code{"eps"} and @code{"png"}, for the screen, postscript and png format files, respectively. @item @code{'maintitle}, default @code{""}, is the main title between double quotes. @item @code{'axisnames}, default @code{["x", "Fr."]}, is a list with the names of axis @code{x} and @code{y}. @item @code{'picturescales}, default @code{[1.0, 1.0]}, scaling factors for the size of the plot. @item @code{'relbarwidth}, default @code{0.9}, a decimal number between 0 and 1 to control bars width. @item @code{'barcolor}, default @code{1}, an integer to indicate bars color. @item @code{'colorintensity}, default @code{1}, a decimal number between 0 and 1 to fix color intensity. @end itemize This example plots the barchart for groups @code{A} and @code{B} of patients in sample @code{s3}, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c barsplot (col (s3, 1), 'maintitle = "Groups of patients", @c 'axisnames = ["Group", "# of individuals"], 'colorintensity = 0.2)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s3 : read_matrix (file_search ("biomed.data"))$ (%i4) barsplot (col (s3, 1), 'maintitle = "Groups of patients", 'axisnames = ["Group", "# of individuals"], 'colorintensity = 0.2)$ @end example The first column in sample @code{s3} stores the categorical values @code{A} and @code{B}, also known sometimes as factors. On the other hand, the positive integer numbers in the second column are ages, in years, which is a discrete variable, so we can plot the absolute frequencies for these values, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c barsplot (col (s3, 2), 'maintitle = "Ages", @c 'axisnames = ["Years", "# of individuals"], 'colorintensity = 0.2, @c 'relbarwidth = 0.6)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s3 : read_matrix (file_search ("biomed.data"))$ (%i4) barsplot (col (s3, 2), 'maintitle = "Ages", 'axisnames = ["Years", "# of individuals"], 'colorintensity = 0.2, 'relbarwidth = 0.6)$ @end example See also function @code{histogram}. @end deffn @deffn {Function} boxplot (@var{data}) @deffnx {Function} boxplot (@var{data}, @var{option_1}, @var{option_2}, ...) This function plots box diagrams. Argument @var{data} can be a list, which is not of great interest, since these diagrams are mainly used for comparing different samples, or a matrix, so it is possible to compare two or more components of a multivariate statistical variable. But it is also allowed @var{data} to be a list of samples with possible different sample sizes, in fact this is the only function in package @code{descriptive} that admits this type of data structure. See example bellow. These are the options, @itemize @bullet @item @code{'outputdev}, default @code{"x"}, indicates the output device; correct values are @code{"x"}, @code{"eps"} and @code{"png"}, for the screen, postscript and png format files, respectively. @item @code{'maintitle}, default @code{""}, is the main title between double quotes. @item @code{'axisnames}, default @code{["sample", "y"]}, is a list with the names of axis @code{x} and @code{y}. @item @code{'picturescales}, default @code{[1.0, 1.0]}, scaling factors for the size of the plot. @end itemize Examples: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c boxplot (s2, 'maintitle = "Windspeed in knots", @c 'axisnames = ["Seasons", ""])$ @c A : @c [[6, 4, 6, 2, 4, 8, 6, 4, 6, 4, 3, 2], @c [8, 10, 7, 9, 12, 8, 10], @c [16, 13, 17, 12, 11, 18, 13, 18, 14, 12]]$ @c boxplot (A)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) boxplot (s2, 'maintitle = "Windspeed in knots", 'axisnames = ["Seasons", ""])$ (%i5) A : [[6, 4, 6, 2, 4, 8, 6, 4, 6, 4, 3, 2], [8, 10, 7, 9, 12, 8, 10], [16, 13, 17, 12, 11, 18, 13, 18, 14, 12]]$ (%i6) boxplot (A)$ @end example @end deffn --Boundary-00=_5TgqFnyKa5ENh63 Content-Type: text/plain; charset="iso-8859-1"; name="descriptive_error.texi" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="descriptive_error.texi" @c Language: Brazilian Portuguese, Encoding: iso-8859-1 @c /descriptive.texi/1.8/Mon Jul 24 10:59:45 2006// @menu * Introdu@value{cedilha}@~ao ao pacote descriptive:: * Defini@value{cedilha}@~oes para manipula@value{cedilha}@~ao da dados:: * Defini@value{cedilha}@~oes para estat@'istica descritiva:: * Defini@value{cedilha}@~oes para specific multivariate descriptive statistics:: * Defini@value{cedilha}@~oes para statistical graphs:: @end menu @node Introdu@value{cedilha}@~ao ao pacote descriptive, Defini@value{cedilha}@~oes para manipula@value{cedilha}@~ao da dados, descriptive, descriptive @section Introdu@value{cedilha}@~ao ao pacote descriptive Package @code{descriptive} contains a set of functions for making descriptive statistical computations and graphing. Together with the source code there are three data sets in your Maxima tree: @code{pidigits.data}, @code{wind.data} and @code{biomed.data}. They can be also downloaded from the web site @code{www.biomates.net}. Any statistics manual can be used as a reference to the functions in package @code{descriptive}. For comments, bugs or suggestions, please contact me at @var{'mario AT edu DOT xunta DOT es'}. Here is a simple example on how the descriptive functions in @code{descriptive} do they work, depending on the nature of their arguments, lists or matrices, @c ===beg=== @c load (descriptive)$ @c /* univariate sample */ mean ([a, b, c]); @c matrix ([a, b], [c, d], [e, f]); @c /* multivariate sample */ mean (%); @c ===end=== @example (%i1) load (descriptive)$ (%i2) /* univariate sample */ mean ([a, b, c]); c + b + a (%o2) --------- 3 (%i3) matrix ([a, b], [c, d], [e, f]); [ a b ] [ ] (%o3) [ c d ] [ ] [ e f ] (%i4) /* multivariate sample */ mean (%); e + c + a f + d + b (%o4) [---------, ---------] 3 3 @end example Note that in multivariate samples the mean is calculated for each column. In case of several samples with possible different sizes, the Maxima function @code{map} can be used to get the desired results for each sample, @c ===beg=== @c load (descriptive)$ @c map (mean, [[a, b, c], [d, e]]); @c ===end=== @example (%i1) load (descriptive)$ (%i2) map (mean, [[a, b, c], [d, e]]); c + b + a e + d (%o2) [---------, -----] 3 2 @end example In this case, two samples of sizes 3 and 2 were stored into a list. Univariate samples must be stored in lists like @c ===beg=== @c s1 : [3, 1, 4, 1, 5, 9, 2, 6, 5, 3, 5]; @c ===end=== @example (%i1) s1 : [3, 1, 4, 1, 5, 9, 2, 6, 5, 3, 5]; (%o1) [3, 1, 4, 1, 5, 9, 2, 6, 5, 3, 5] @end example and multivariate samples in matrices as in @c ===beg=== @c s2 : matrix ([13.17, 9.29], [14.71, 16.88], [18.50, 16.88], @c [10.58, 6.63], [13.33, 13.25], [13.21, 8.12]); @c ===end=== @example (%i1) s2 : matrix ([13.17, 9.29], [14.71, 16.88], [18.50, 16.88], [10.58, 6.63], [13.33, 13.25], [13.21, 8.12]); [ 13.17 9.29 ] [ ] [ 14.71 16.88 ] [ ] [ 18.5 16.88 ] (%o1) [ ] [ 10.58 6.63 ] [ ] [ 13.33 13.25 ] [ ] [ 13.21 8.12 ] @end example In this case, the number of columns equals the random variable dimension and the number of rows is the sample size. Data can be introduced by hand, but big samples are usually stored in plain text files. For example, file @code{pidigits.data} contains the first 100 digits of number @code{%pi}: @example 3 1 4 1 5 9 2 6 5 3 ... @end example In order to load these digits in Maxima, @c ===beg=== @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c length (s1); @c ===end=== @example (%i1) load (numericalio)$ (%i2) s1 : read_list (file_search ("pidigits.data"))$ (%i3) length (s1); (%o3) 100 @end example On the other hand, file @code{wind.data} contains daily average wind speeds at 5 meteorological stations in the Republic of Ireland (This is part of a data set taken at 12 meteorological stations. The original file is freely downloadable from the StatLib Data Repository and its analysis is discused in Haslett, J., Raftery, A. E. (1989) @var{Space-time Modelling with Long-memory Dependence: Assessing Ireland's Wind Power Resource, with Discussion}. Applied Statistics 38, 1-50). This loads the data: @c ===beg=== @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c length (s2); @c s2 [%]; /* last record */ @c ===end=== @example (%i1) load (numericalio)$ (%i2) s2 : read_matrix (file_search ("wind.data"))$ (%i3) length (s2); (%o3) 100 (%i4) s2 [%]; /* last record */ (%o4) [3.58, 6.0, 4.58, 7.62, 11.25] @end example Some samples contain non numeric data. As an example, file @code{biomed.data} (which is part of another bigger one downloaded from the StatLib Data Repository) contains four blood measures taken from two groups of patients, @code{A} and @code{B}, of different ages, @c ===beg=== @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c length (s3); @c s3 [1]; /* first record */ @c ===end=== @example (%i1) load (numericalio)$ (%i2) s3 : read_matrix (file_search ("biomed.data"))$ (%i3) length (s3); (%o3) 100 (%i4) s3 [1]; /* first record */ (%o4) [A, 30, 167.0, 89.0, 25.6, 364] @end example The first individual belongs to group @code{A}, is 30 years old and his/her blood measures were 167.0, 89.0, 25.6 and 364. One must take care when working with categorical data. In the next example, symbol @code{a} is asigned a value in some previous moment and then a sample with categorical value @code{a} is taken, @c ===beg=== @c a : 1$ @c matrix ([a, 3], [b, 5]); @c ===end=== @example (%i1) a : 1$ (%i2) matrix ([a, 3], [b, 5]); [ 1 3 ] (%o2) [ ] [ b 5 ] @end example @node Defini@value{cedilha}@~oes para manipula@value{cedilha}@~ao da dados, Defini@value{cedilha}@~oes para estat@'istica descritiva, Introdu@value{cedilha}@~ao ao pacote descriptive, descriptive @section Defini@value{cedilha}@~oes para manipula@value{cedilha}@~ao da dados @deffn {Function} continuous_freq (@var{list}) @deffnx {Function} continuous_freq (@var{list}, @var{m}) The argument of @code{continuous_freq} must be a list of numbers, which will be then grouped in intervals and counted how many of them belong to each group. Optionally, function @code{continuous_freq} admits a second argument indicating the number of classes, 10 is default, @c ===beg=== @c load (numericalio)$ @c load (descriptive)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c continuous_freq (s1, 5); @c ===end=== @example (%i1) load (numericalio)$ (%i2) load (descriptive)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) continuous_freq (s1, 5); (%o4) [[0, 1.8, 3.6, 5.4, 7.2, 9.0], [16, 24, 18, 17, 25]] @end example The first list contains the interval limits and the second the corresponding counts: there are 16 digits inside the interval @code{[0, 1.8]}, that is 0's and 1's, 24 digits in @code{(1.8, 3.6]}, that is 2's and 3's, and so on. @end deffn @deffn {Function} discrete_freq (@var{list}) Counts absolute frequencies in discrete samples, both numeric and categorical. Its unique argument is a list, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data")); @c discrete_freq (s1); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data")); (%o3) [3, 1, 4, 1, 5, 9, 2, 6, 5, 3, 5, 8, 9, 7, 9, 3, 2, 3, 8, 4, 6, 2, 6, 4, 3, 3, 8, 3, 2, 7, 9, 5, 0, 2, 8, 8, 4, 1, 9, 7, 1, 6, 9, 3, 9, 9, 3, 7, 5, 1, 0, 5, 8, 2, 0, 9, 7, 4, 9, 4, 4, 5, 9, 2, 3, 0, 7, 8, 1, 6, 4, 0, 6, 2, 8, 6, 2, 0, 8, 9, 9, 8, 6, 2, 8, 0, 3, 4, 8, 2, 5, 3, 4, 2, 1, 1, 7, 0, 6, 7] (%i4) discrete_freq (s1); (%o4) [[0, 1, 2, 3, 4, 5, 6, 7, 8, 9], [8, 8, 12, 12, 10, 8, 9, 8, 12, 13]] @end example The first list gives the sample values and the second their absolute frequencies. Commands @code{? col} and @code{? transpose} should help you to understand the last input. @end deffn @deffn {Function} subsample (@var{data_matrix}, @var{logical_expression}) @deffnx {Function} subsample (@var{data_matrix}, @var{logical_expression}, @var{col_num}, @var{col_num}, ...) This is a sort of variation of the Maxima @code{submatrix} function. The first argument is the name of the data matrix, the second is a quoted logical expression and optional additional arguments are the numbers of the columns to be taken. Its behaviour is better understood with examples, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c subsample (s2, '(%c[1] > 18)); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) subsample (s2, '(%c[1] > 18)); [ 19.38 15.37 15.12 23.09 25.25 ] [ ] [ 18.29 18.66 19.08 26.08 27.63 ] (%o4) [ ] [ 20.25 21.46 19.95 27.71 23.38 ] [ ] [ 18.79 18.96 14.46 26.38 21.84 ] @end example These are multivariate records in which the wind speeds in the first meteorological station were greater than 18. See that in the quoted logical expression the @var{i}-th component is refered to as @code{%c[i]}. Symbol @code{%c[i]} is used inside function @code{subsample}, therefore when used as a categorical variable, Maxima gets confused. In the following example, we request only the first, second and fifth components of those records with wind speeds greater or equal than 16 in station number 1 and lesser than 25 knots in station number 4, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c subsample (s2, '(%c[1] >= 16 and %c[4] < 25), 1, 2, 5); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) subsample (s2, '(%c[1] >= 16 and %c[4] < 25), 1, 2, 5); [ 19.38 15.37 25.25 ] [ ] [ 17.33 14.67 19.58 ] (%o4) [ ] [ 16.92 13.21 21.21 ] [ ] [ 17.25 18.46 23.87 ] @end example Here is an example with the categorical variables of @code{biomed.data}. We want the records corresponding to those patients in group @code{B} who are older than 38 years, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c subsample (s3, '(%c[1] = B and %c[2] > 38)); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s3 : read_matrix (file_search ("biomed.data"))$ (%i4) subsample (s3, '(%c[1] = B and %c[2] > 38)); [ B 39 28.0 102.3 17.1 146 ] [ ] [ B 39 21.0 92.4 10.3 197 ] [ ] [ B 39 23.0 111.5 10.0 133 ] [ ] [ B 39 26.0 92.6 12.3 196 ] (%o4) [ ] [ B 39 25.0 98.7 10.0 174 ] [ ] [ B 39 21.0 93.2 5.9 181 ] [ ] [ B 39 18.0 95.0 11.3 66 ] [ ] [ B 39 39.0 88.5 7.6 168 ] @end example Probably, the statistical analysis will involve only the blood measures, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c subsample (s3, '(%c[1] = B and %c[2] > 38), 3, 4, 5, 6); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s3 : read_matrix (file_search ("biomed.data"))$ (%i4) subsample (s3, '(%c[1] = B and %c[2] > 38), 3, 4, 5, 6); [ 28.0 102.3 17.1 146 ] [ ] [ 21.0 92.4 10.3 197 ] [ ] [ 23.0 111.5 10.0 133 ] [ ] [ 26.0 92.6 12.3 196 ] (%o4) [ ] [ 25.0 98.7 10.0 174 ] [ ] [ 21.0 93.2 5.9 181 ] [ ] [ 18.0 95.0 11.3 66 ] [ ] [ 39.0 88.5 7.6 168 ] @end example This is the multivariate mean of @code{s3}, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c mean (s3); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s3 : read_matrix (file_search ("biomed.data"))$ (%i4) mean (s3); 65 B + 35 A 317 6 NA + 8145.0 (%o4) [-----------, ---, 87.178, -------------, 18.123, 100 10 100 3 NA + 19587 ------------] 100 @end example Here, the first component is meaningless, since @code{A} and @code{B} are categorical, the second component is the mean age of individuals in rational form, and the fourth and last values exhibit some strange behaviour. This is because symbol @code{NA} is used here to indicate @var{non available} data, and the two means are of course nonsense. A possible solution would be to take out from the matrix those rows with @code{NA} symbols, although this deserves some loss of information, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c mean (subsample (s3, '(%c[4] # NA and %c[6] # NA), 3, 4, 5, 6)); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s3 : read_matrix (file_search ("biomed.data"))$ (%i4) mean (subsample (s3, '(%c[4] # NA and %c[6] # NA), 3, 4, 5, 6)); (%o4) [79.4923076923077, 86.2032967032967, 16.93186813186813, 2514 ----] 13 @end example @end deffn @node Defini@value{cedilha}@~oes para estat@'istica descritiva, Defini@value{cedilha}@~oes para specific multivariate descriptive statistics, Defini@value{cedilha}@~oes para manipula@value{cedilha}@~ao da dados, descriptive @section Defini@value{cedilha}@~oes para estat@'istica descritiva @deffn {Function} mean (@var{list}) @deffnx {Function} mean (@var{matrix}) This is the sample mean, defined as @ifhtml @example n ==== _ 1 \ x = - > x n / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== _ 1 \ x = - > x n / i ==== i = 1 @end example @end ifinfo @tex $${\bar{x}={1\over{n}}{\sum_{i=1}^{n}{x_{i}}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c mean (s1); @c %, numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c mean (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) mean (s1); 471 (%o4) --- 100 (%i5) %, numer; (%o5) 4.71 (%i6) s2 : read_matrix (file_search ("wind.data"))$ (%i7) mean (s2); (%o7) [9.9485, 10.1607, 10.8685, 15.7166, 14.8441] @end example @end deffn @deffn {Function} var (@var{list}) @deffnx {Function} var (@var{matrix}) This is the sample variance, defined as @ifhtml @example n ==== 2 1 \ _ 2 s = - > (x - x) n / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 2 1 \ _ 2 s = - > (x - x) n / i ==== i = 1 @end example @end ifinfo @tex $${{1}\over{n}}{\sum_{i=1}^{n}{(x_{i}-\bar{x})^2}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c var (s1), numer; @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) var (s1), numer; (%o4) 8.425899999999999 @end example See also function @code{var1}. @end deffn @deffn {Function} var1 (@var{list}) @deffnx {Function} var1 (@var{matrix}) This is the sample variance, defined as @ifhtml @example n ==== 1 \ _ 2 --- > (x - x) n-1 / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ 2 --- > (x - x) n-1 / i ==== i = 1 @end example @end ifinfo @tex $${{1\over{n-1}}{\sum_{i=1}^{n}{(x_{i}-\bar{x})^2}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c var1 (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c var1 (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) var1 (s1), numer; (%o4) 8.5110101010101 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) var1 (s2); (%o6) [17.39586540404041, 15.13912778787879, 15.63204924242424, 32.50152569696971, 24.66977392929294] @end example See also function @code{var}. @end deffn @deffn {Function} std (@var{list}) @deffnx {Function} std (@var{matrix}) This is the the square root of function @code{var}, the variance with denominator @math{n}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c std (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c std (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) std (s1), numer; (%o4) 2.902740084816414 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) std (s2); (%o6) [4.149928523480858, 3.871399812729241, 3.933920277534866, 5.672434260526957, 4.941970881136392] @end example See also functions @code{var} and @code{std1}. @end deffn @deffn {Function} std1 (@var{list}) @deffnx {Function} std1 (@var{matrix}) This is the the square root of function @code{var1}, the variance with denominator @math{n-1}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c std1 (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c std1 (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) std1 (s1), numer; (%o4) 2.917363553109228 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) std1 (s2); (%o6) [4.17083509672109, 3.89090320978032, 3.953738641137555, 5.701010936401517, 4.966867617451963] @end example See also functions @code{var1} and @code{std}. @end deffn @deffn {Function} noncentral_moment (@var{list}, @var{k}) @deffnx {Function} noncentral_moment (@var{matrix}, @var{k}) The non central moment of order @math{k}, defined as @ifhtml @example n ==== 1 \ k - > x n / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ k - > x n / i ==== i = 1 @end example @end ifinfo @tex $${{1\over{n}}{\sum_{i=1}^{n}{x_{i}^k}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c noncentral_moment (s1, 1), numer; /* the mean */ @c s2 : read_matrix (file_search ("wind.data"))$ @c noncentral_moment (s2, 5); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) noncentral_moment (s1, 1), numer; /* the mean */ (%o4) 4.71 (%i6) s2 : read_matrix (file_search ("wind.data"))$ (%i7) noncentral_moment (s2, 5); (%o7) [319793.8724761506, 320532.1923892463, 391249.5621381556, 2502278.205988911, 1691881.797742255] @end example See also function @code{central_moment}. @end deffn @deffn {Function} central_moment (@var{list}, @var{k}) @deffnx {Function} central_moment (@var{matrix}, @var{k}) The central moment of order @math{k}, defined as @ifhtml @example n ==== 1 \ _ k - > (x - x) n / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ k - > (x - x) n / i ==== i = 1 @end example @end ifinfo @tex $${{1\over{n}}{\sum_{i=1}^{n}{(x_{i}-\bar{x})^k}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c central_moment (s1, 2), numer; /* the variance */ @c s2 : read_matrix (file_search ("wind.data"))$ @c central_moment (s2, 3); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) central_moment (s1, 2), numer; /* the variance */ (%o4) 8.425899999999999 (%i6) s2 : read_matrix (file_search ("wind.data"))$ (%i7) central_moment (s2, 3); (%o7) [11.29584771375004, 16.97988248298583, 5.626661952750102, 37.5986572057918, 25.85981904394192] @end example See also functions @code{central_moment} and @code{mean}. @end deffn @deffn {Function} cv (@var{list}) @deffnx {Function} cv (@var{matrix}) The variation coefficient is the quotient between the sample standard deviation (@code{std}) and the @code{mean}, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c cv (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c cv (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) cv (s1), numer; (%o4) .6193977819764815 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) cv (s2); (%o6) [.4192426091090204, .3829365309260502, 0.363779605385983, .3627381836021478, .3346021393989506] @end example See also functions @code{std} and @code{mean}. @end deffn @deffn {Function} mini (@var{list}) @deffnx {Function} mini (@var{matrix}) This is the minimum value of the sample @var{list}, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c mini (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c mini (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) mini (s1); (%o4) 0 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) mini (s2); (%o6) [0.58, 0.5, 2.67, 5.25, 5.17] @end example See also function @code{maxi}. @end deffn @deffn {Function} maxi (@var{list}) @deffnx {Function} maxi (@var{matrix}) This is the maximum value of the sample @var{list}, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c maxi (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c maxi (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) maxi (s1); (%o4) 9 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) maxi (s2); (%o6) [20.25, 21.46, 20.04, 29.63, 27.63] @end example See also function @code{mini}. @end deffn @deffn {Function} range (@var{list}) @deffnx {Function} range (@var{matrix}) The range is the difference between the extreme values. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c range (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c range (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) range (s1); (%o4) 9 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) range (s2); (%o6) [19.67, 20.96, 17.37, 24.38, 22.46] @end example @end deffn @deffn {Function} quantile (@var{list}, @var{p}) @deffnx {Function} quantile (@var{matrix}, @var{p}) This is the @var{p}-@code{quantile}, with @var{p} a number in @math{[0, 1]}, of the sample @var{list}. Although there are several Defini@value{cedilha}@~oes para the sample quantile (Hyndman, R. J., Fan, Y. (1996) @var{Sample quantiles in statistical packages}. American Statistician, 50, 361-365), the one based on linear interpolation is implemented in package @code{descriptive}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c /* 1st and 3rd quartiles */ [quantile (s1, 1/4), quantile (s1, 3/4)], numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c quantile (s2, 1/4); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) /* 1st and 3rd quartiles */ [quantile (s1, 1/4), quantile (s1, 3/4)], numer; (%o4) [2.0, 7.25] (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) quantile (s2, 1/4); (%o6) [7.2575, 7.477500000000001, 7.82, 11.28, 11.48] @end example @end deffn @deffn {Function} median (@var{list}) @deffnx {Function} median (@var{matrix}) Once the sample is ordered, if the sample size is odd the median is the central value, otherwise it is the mean of the two central values. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c median (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c median (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) median (s1); 9 (%o4) - 2 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) median (s2); (%o6) [10.06, 9.855, 10.73, 15.48, 14.105] @end example The median is the 1/2-@code{quantile}. See also function @code{quantile}. @end deffn @deffn {Function} qrange (@var{list}) @deffnx {Function} qrange (@var{matrix}) The interquartilic range is the difference between the third and first quartiles, @code{quantile(list,3/4) - quantile(list,1/4)}, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c qrange (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c qrange (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) qrange (s1); 21 (%o4) -- 4 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) qrange (s2); (%o6) [5.385, 5.572499999999998, 6.0225, 8.729999999999999, 6.650000000000002] @end example See also function @code{quantile}. @end deffn @deffn {Function} mean_deviation (@var{list}) @deffnx {Function} mean_deviation (@var{matrix}) The mean deviation, defined as @ifhtml @example n ==== 1 \ _ - > |x - x| n / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ - > |x - x| n / i ==== i = 1 @end example @end ifinfo @tex $${{1\over{n}}{\sum_{i=1}^{n}{|x_{i}-\bar{x}|}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c mean_deviation (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c mean_deviation (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) mean_deviation (s1); 51 (%o4) -- 20 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) mean_deviation (s2); (%o6) [3.287959999999999, 3.075342, 3.23907, 4.715664000000001, 4.028546000000002] @end example See also function @code{mean}. @end deffn @deffn {Function} median_deviation (@var{list}) @deffnx {Function} median_deviation (@var{matrix}) The median deviation, defined as @ifhtml @example n ==== 1 \ - > |x - med| n / i ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ - > |x - med| n / i ==== i = 1 @end example @end ifinfo @tex $${{1\over{n}}{\sum_{i=1}^{n}{|x_{i}-med|}}}$$ @end tex where @code{med} is the median of @var{list}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c median_deviation (s1); @c s2 : read_matrix (file_search ("wind.data"))$ @c median_deviation (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) median_deviation (s1); 5 (%o4) - 2 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) median_deviation (s2); (%o6) [2.75, 2.755, 3.08, 4.315, 3.31] @end example See also function @code{mean}. @end deffn @deffn {Function} harmonic_mean (@var{list}) @deffnx {Function} harmonic_mean (@var{matrix}) The harmonic mean, defined as @ifhtml @example n -------- n ==== \ 1 > -- / x ==== i i = 1 @end example @end ifhtml @ifinfo @example n -------- n ==== \ 1 > -- / x ==== i i = 1 @end example @end ifinfo @tex $${{n}\over{\sum_{i=1}^{n}{{{1}\over{x_{i}}}}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c y : [5, 7, 2, 5, 9, 5, 6, 4, 9, 2, 4, 2, 5]$ @c harmonic_mean (y), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c harmonic_mean (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) y : [5, 7, 2, 5, 9, 5, 6, 4, 9, 2, 4, 2, 5]$ (%i4) harmonic_mean (y), numer; (%o4) 3.901858027632205 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) harmonic_mean (s2); (%o6) [6.948015590052786, 7.391967752360356, 9.055658197151745, 13.44199028193692, 13.01439145898509] @end example See also functions @code{mean} and @code{geometric_mean}. @end deffn @deffn {Function} geometric_mean (@var{list}) @deffnx {Function} geometric_mean (@var{matrix}) The geometric mean, defined as @ifhtml @example / n \ 1/n | /===\ | | ! ! | | ! ! x | | ! ! i| | i = 1 | \ / @end example @end ifhtml @ifinfo @example / n \ 1/n | /===\ | | ! ! | | ! ! x | | ! ! i| | i = 1 | \ / @end example @end ifinfo @tex $$\left(\prod_{i=1}^{n}{x_{i}}\right)^{{{1}\over{n}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c y : [5, 7, 2, 5, 9, 5, 6, 4, 9, 2, 4, 2, 5]$ @c geometric_mean (y), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c geometric_mean (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) y : [5, 7, 2, 5, 9, 5, 6, 4, 9, 2, 4, 2, 5]$ (%i4) geometric_mean (y), numer; (%o4) 4.454845412337012 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) geometric_mean (s2); (%o6) [8.82476274347979, 9.22652604739361, 10.0442675714889, 14.61274126349021, 13.96184163444275] @end example See also functions @code{mean} and @code{harmonic_mean}. @end deffn @deffn {Function} kurtosis (@var{list}) @deffnx {Function} kurtosis (@var{matrix}) The kurtosis coefficient, defined as @ifhtml @example n ==== 1 \ _ 4 ---- > (x - x) - 3 4 / i n s ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ 4 ---- > (x - x) - 3 4 / i n s ==== i = 1 @end example @end ifinfo @tex $${{1\over{n s^4}}{\sum_{i=1}^{n}{(x_{i}-\bar{x})^4}}-3}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c kurtosis (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c kurtosis (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) kurtosis (s1), numer; (%o4) - 1.273247946514421 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) kurtosis (s2); (%o6) [- .2715445622195385, 0.119998784429451, - .4275233490482866, - .6405361979019522, - .4952382132352935] @end example See also functions @code{mean}, @code{var} and @code{skewness}. @end deffn @deffn {Function} skewness (@var{list}) @deffnx {Function} skewness (@var{matrix}) The skewness coefficient, defined as @ifhtml @example n ==== 1 \ _ 3 ---- > (x - x) 3 / i n s ==== i = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ 3 ---- > (x - x) 3 / i n s ==== i = 1 @end example @end ifinfo @tex $${{1\over{n s^3}}{\sum_{i=1}^{n}{(x_{i}-\bar{x})^3}}}$$ @end tex Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c skewness (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c skewness (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) skewness (s1), numer; (%o4) .009196180476450306 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) skewness (s2); (%o6) [.1580509020000979, .2926379232061854, .09242174416107717, .2059984348148687, .2142520248890832] @end example See also functions @code{mean}, @code{var} and @code{kurtosis}. @end deffn @deffn {Function} pearson_skewness (@var{list}) @deffnx {Function} pearson_skewness (@var{matrix}) Pearson's skewness coefficient, defined as @ifhtml @example _ 3 (x - med) ----------- s @end example @end ifhtml @ifinfo @example _ 3 (x - med) ----------- s @end example @end ifinfo @tex $${{3\,\left(\bar{x}-med\right)}\over{s}}$$ @end tex where @var{med} is the median of @var{list}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c pearson_skewness (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c pearson_skewness (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) pearson_skewness (s1), numer; (%o4) .2159484029093895 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) pearson_skewness (s2); (%o6) [- .08019976629211892, .2357036272952649, .1050904062491204, .1245042340592368, .4464181795804519] @end example See also functions @code{mean}, @code{var} and @code{median}. @end deffn @deffn {Function} quartile_skewness (@var{list}) @deffnx {Function} quartile_skewness (@var{matrix}) The quartile skewness coefficient, defined as @ifhtml @example c - 2 c + c 3/4 1/2 1/4 -------------------- c - c 3/4 1/4 @end example @end ifhtml @ifinfo @example c - 2 c + c 3/4 1/2 1/4 -------------------- c - c 3/4 1/4 @end example @end ifinfo @tex $${{c_{{{3}\over{4}}}-2\,c_{{{1}\over{2}}}+c_{{{1}\over{4}}}}\over{c _{{{3}\over{4}}}-c_{{{1}\over{4}}}}}$$ @end tex where @math{c_p} is the @var{p}-quantile of sample @var{list}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c quartile_skewness (s1), numer; @c s2 : read_matrix (file_search ("wind.data"))$ @c quartile_skewness (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) quartile_skewness (s1), numer; (%o4) .04761904761904762 (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) quartile_skewness (s2); (%o6) [- 0.0408542246982353, .1467025572005382, 0.0336239103362392, .03780068728522298, 0.210526315789474] @end example See also function @code{quantile}. @end deffn @node Defini@value{cedilha}@~oes para specific multivariate descriptive statistics, Defini@value{cedilha}@~oes para statistical graphs, Defini@value{cedilha}@~oes para estat@'istica descritiva, descriptive @section Defini@value{cedilha}@~oes para specific multivariate descriptive statistics @deffn {Function} cov (@var{matrix}) The covariance matrix of the multivariate sample, defined as @ifhtml @example n ==== 1 \ _ _ S = - > (X - X) (X - X)' n / j j ==== j = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ _ S = - > (X - X) (X - X)' n / j j ==== j = 1 @end example @end ifinfo @tex $${S={1\over{n}}{\sum_{j=1}^{n}{\left(X_{j}-\bar{X}\right)\,\left(X_{j}-\bar{X}\right)'}}}$$ @end tex where @math{X_j} is the @math{j}-th row of the sample matrix. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c fpprintprec : 7$ /* change precision for pretty output */ @c cov (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) fpprintprec : 7$ /* change precision for pretty output */ (%i5) cov (s2); [ 17.22191 13.61811 14.37217 19.39624 15.42162 ] [ ] [ 13.61811 14.98774 13.30448 15.15834 14.9711 ] [ ] (%o5) [ 14.37217 13.30448 15.47573 17.32544 16.18171 ] [ ] [ 19.39624 15.15834 17.32544 32.17651 20.44685 ] [ ] [ 15.42162 14.9711 16.18171 20.44685 24.42308 ] @end example See also function @code{cov1}. @end deffn @deffn {Function} cov1 (@var{matrix}) The covariance matrix of the multivariate sample, defined as @ifhtml @example n ==== 1 \ _ _ S = --- > (X - X) (X - X)' 1 n-1 / j j ==== j = 1 @end example @end ifhtml @ifinfo @example n ==== 1 \ _ _ S = --- > (X - X) (X - X)' 1 n-1 / j j ==== j = 1 @end example @end ifinfo @tex $${{1\over{n-1}}{\sum_{j=1}^{n}{\left(X_{j}-\bar{X}\right)\,\left(X_{j}-\bar{X}\right)'}}}$$ @end tex where @math{X_j} is the @math{j}-th row of the sample matrix. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c fpprintprec : 7$ /* change precision for pretty output */ @c cov1 (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) fpprintprec : 7$ /* change precision for pretty output */ (%i5) cov1 (s2); [ 17.39587 13.75567 14.51734 19.59216 15.5774 ] [ ] [ 13.75567 15.13913 13.43887 15.31145 15.12232 ] [ ] (%o5) [ 14.51734 13.43887 15.63205 17.50044 16.34516 ] [ ] [ 19.59216 15.31145 17.50044 32.50153 20.65338 ] [ ] [ 15.5774 15.12232 16.34516 20.65338 24.66977 ] @end example See also function @code{cov}. @end deffn @deffn {Function} global_variances (@var{matrix}) @deffnx {Function} global_variances (@var{matrix}, @var{logical_value}) Function @code{global_variances} returns a list of global variance measures: @itemize @bullet @item @var{total variance}: @code{trace(S_1)}, @item @var{mean variance}: @code{trace(S_1)/p}, @item @var{generalized variance}: @code{determinant(S_1)}, @item @var{generalized standard deviation}: @code{sqrt(determinant(S_1))}, @item @var{efective variance} @code{determinant(S_1)^(1/p)}, (defined in: Pe@~na, D. (2002) @var{An@'alisis de datos multivariantes}; McGraw-Hill, Madrid.) @item @var{efective standard deviation}: @code{determinant(S_1)^(1/(2*p))}. @end itemize where @var{p} is the dimension of the multivariate random variable and @math{S_1} the covariance matrix returned by @code{cov1}. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c global_variances (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) global_variances (s2); (%o4) [105.338342060606, 21.06766841212119, 12874.34690469686, 113.4651792608502, 6.636590811800794, 2.576158149609762] @end example Function @code{global_variances} has an optional logical argument: @code{global_variances(x,true)} tells Maxima that @code{x} is the data matrix, making the same as @code{global_variances(x)}. On the other hand, @code{global_variances(x,false)} means that @code{x} is not the data matrix, but the covariance matrix, avoiding its recalculation, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c s : cov1 (s2)$ @c global_variances (s, false); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) s : cov1 (s2)$ (%i5) global_variances (s, false); (%o5) [105.338342060606, 21.06766841212119, 12874.34690469686, 113.4651792608502, 6.636590811800794, 2.576158149609762] @end example See also @code{cov} and @code{cov1}. @end deffn @deffn {Function} cor (@var{matrix}) @deffnx {Function} cor (@var{matrix}, @var{logical_value}) The correlation matrix of the multivariate sample. Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c fpprintprec:7$ @c s2 : read_matrix (file_search ("wind.data"))$ @c cor (s2); @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) fpprintprec:7$ (%i4) s2 : read_matrix (file_search ("wind.data"))$ (%i5) cor (s2); [ 1.0 .8476339 .8803515 .8239624 .7519506 ] [ ] [ .8476339 1.0 .8735834 .6902622 0.782502 ] [ ] (%o5) [ .8803515 .8735834 1.0 .7764065 .8323358 ] [ ] [ .8239624 .6902622 .7764065 1.0 .7293848 ] [ ] [ .7519506 0.782502 .8323358 .7293848 1.0 ] @end example Function @code{cor} has an optional logical argument: @code{cor(x,true)} tells Maxima that @code{x} is the data matrix, making the same as @code{cor(x)}. On the other hand, @code{cor(x,false)} means that @code{x} is not the data matrix, but the covariance matrix, avoiding its recalculation, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c fpprintprec:7$ @c s2 : read_matrix (file_search ("wind.data"))$ @c s : cov1 (s2)$ @c cor (s, false); /* this is faster */ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) fpprintprec:7$ (%i4) s2 : read_matrix (file_search ("wind.data"))$ (%i5) s : cov1 (s2)$ (%i6) cor (s, false); /* this is faster */ [ 1.0 .8476339 .8803515 .8239624 .7519506 ] [ ] [ .8476339 1.0 .8735834 .6902622 0.782502 ] [ ] (%o6) [ .8803515 .8735834 1.0 .7764065 .8323358 ] [ ] [ .8239624 .6902622 .7764065 1.0 .7293848 ] [ ] [ .7519506 0.782502 .8323358 .7293848 1.0 ] @end example See also @code{cov} and @code{cov1}. @end deffn @deffn {Function} list_correlations (@var{matrix}) @deffnx {Function} list_correlations (@var{matrix}, @var{logical_value}) Function @code{list_correlations} returns a list of correlation measures: @itemize @bullet @item @var{precision matrix}: the inverse of the covariance matrix @math{S_1}, @ifhtml @example -1 ij S = (s ) 1 i,j = 1,2,...,p @end example @end ifhtml @ifinfo @example -1 ij S = (s ) 1 i,j = 1,2,...,p @end example @end ifinfo @tex $${S_{1}^{-1}}={\left(s^{ij}\right)_{i,j=1,2,\ldots, p}}$$ @end tex @item @var{multiple correlation vector}: @math{(R_1^2, R_2^2, ..., R_p^2)}, with @ifhtml @example 2 1 R = 1 - ------- i ii s s ii @end example @end ifhtml @ifinfo @example 2 1 R = 1 - ------- i ii s s ii @end example @end ifinfo @tex $${R_{i}^{2}}={1-{{1}\over{s^{ii}s_{ii}}}}$$ @end tex being an indicator of the goodness of fit of the linear multivariate regression model on @math{X_i} when the rest of variables are used as regressors. @item @var{partial correlation matrix}: with element @math{(i, j)} being @ifhtml @example ij s r = - ------------ ij.rest / ii jj\ 1/2 |s s | \ / @end example @end ifhtml @ifinfo @example ij s r = - ------------ ij.rest / ii jj\ 1/2 |s s | \ / @end example @end ifinfo @tex $${r_{ij.rest}}={-{{s^{ij}}\over \sqrt{s^{ii}s^{jj}}}}$$ @end tex @end itemize Example: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c z : list_correlations (s2)$ @c fpprintprec : 5$ /* for pretty output */ @c z[1]; /* precision matrix */ @c z[2]; /* multiple correlation vector */ @c z[3]; /* partial correlation matrix */ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) z : list_correlations (s2)$ (%i5) fpprintprec : 5$ /* for pretty output */ (%i6) z[1]; /* precision matrix */ [ .38486 - .13856 - .15626 - .10239 .031179 ] [ ] [ - .13856 .34107 - .15233 .038447 - .052842 ] [ ] (%o6) [ - .15626 - .15233 .47296 - .024816 - .10054 ] [ ] [ - .10239 .038447 - .024816 .10937 - .034033 ] [ ] [ .031179 - .052842 - .10054 - .034033 .14834 ] (%i7) z[2]; /* multiple correlation vector */ (%o7) [.85063, .80634, .86474, .71867, .72675] (%i8) z[3]; /* partial correlation matrix */ [ - 1.0 .38244 .36627 .49908 - .13049 ] [ ] [ .38244 - 1.0 .37927 - .19907 .23492 ] [ ] (%o8) [ .36627 .37927 - 1.0 .10911 .37956 ] [ ] [ .49908 - .19907 .10911 - 1.0 .26719 ] [ ] [ - .13049 .23492 .37956 .26719 - 1.0 ] @end example Function @code{list_correlations} also has an optional logical argument: @code{list_correlations(x,true)} tells Maxima that @code{x} is the data matrix, making the same as @code{list_correlations(x)}. On the other hand, @code{list_correlations(x,false)} means that @code{x} is not the data matrix, but the covariance matrix, avoiding its recalculation. See also @code{cov} and @code{cov1}. @end deffn @node Defini@value{cedilha}@~oes para statistical graphs, , Defini@value{cedilha}@~oes para specific multivariate descriptive statistics, descriptive @section Defini@value{cedilha}@~oes para statistical graphs @deffn {Function} dataplot (@var{list}) @deffnx {Function} dataplot (@var{list}, @var{option_1}, @var{option_2}, ...) @deffnx {Function} dataplot (@var{matrix}) @deffnx {Function} dataplot (@var{matrix}, @var{option_1}, @var{option_2}, ...) Funtion @code{dataplot} permits direct visualization of sample data, both univariate (@var{list}) and multivariate (@var{matrix}). Giving values to the following @var{options} some aspects of the plot can be controlled: @itemize @bullet @item @code{'outputdev}, default @code{"x"}, indicates the output device; correct values are @code{"x"}, @code{"eps"} and @code{"png"}, for the screen, postscript and png format files, respectively. @item @code{'maintitle}, default @code{""}, is the main title between double quotes. @item @code{'axisnames}, default @code{["x","y","z"]}, is a list with the names of axis @code{x}, @code{y} and @code{z}. @item @code{'joined}, default @code{false}, a logical value to select points in 2D to be joined or isolated. @item @code{'picturescales}, default @code{[1.0, 1.0]}, scaling factors for the size of the plot. @item @code{'threedim}, default @code{true}, tells Maxima whether to plot a three column matrix with a 3D diagram or a multivariate scatterplot. See examples bellow. @item @code{'axisrot}, default @code{[60, 30]}, changes the point of view when @code{'threedim} is set to @code{true} and data are stored in a three column matrix. The first number is the rotation angle of the @var{x}-axis, and the second number is the rotation angle of the @var{z}-axis, both measured in degrees. @item @code{'nclasses}, default @code{10}, is the number of classes for the histograms in the diagonal of multivariate scatterplots. @item @code{'pointstyle}, default @code{1}, is an integer to indicate how to display sample points. @end itemize For example, with the following input a simple plot of the first twenty digits of @code{%pi} is requested and the output stored in an eps file. @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c dataplot (makelist (s1[k], k, 1, 20), 'pointstyle = 3)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) dataplot (makelist (s1[k], k, 1, 20), 'pointstyle = 3)$ @end example Note that one dimensional data are plotted as a time series. In the next case, same more data with different settings, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c dataplot (makelist (s1[k], k, 1, 50), 'maintitle = "First pi digits", @c 'axisnames = ["digit order", "digit value"], 'pointstyle = 2, @c 'joined = true)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) dataplot (makelist (s1[k], k, 1, 50), 'maintitle = "First pi digits", 'axisnames = ["digit order", "digit value"], 'pointstyle = 2, 'joined = true)$ @end example Function @code{dataplot} can be used to plot points in the plane. The next example is a scatterplot of the pairs of wind speeds corresponding to the first and fifth meteorological stations, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c dataplot (submatrix (s2, 2, 3, 4), 'pointstyle = 2, @c 'maintitle = "Pairs of wind speeds measured in knots", @c 'axisnames = ["Wind speed in A", "Wind speed in E"])$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) dataplot (submatrix (s2, 2, 3, 4), 'pointstyle = 2, 'maintitle = "Pairs of wind speeds measured in knots", 'axisnames = ["Wind speed in A", "Wind speed in E"])$ @end example If points are stored in a two column matrix, @code{dataplot} can plot them directly, but if they are formatted as a list of pairs, their must be transformed to a matrix as in the following example. @c ===beg=== @c load (descriptive)$ @c x : [[-1, 2], [5, 7], [5, -3], [-6, -9], [-4, 6]]$ @c dataplot (apply ('matrix, x), 'maintitle = "Points", @c 'joined = true, 'axisnames = ["", ""], 'picturescales = [0.5, 1.0])$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) x : [[-1, 2], [5, 7], [5, -3], [-6, -9], [-4, 6]]$ (%i3) dataplot (apply ('matrix, x), 'maintitle = "Points", 'joined = true, 'axisnames = ["", ""], 'picturescales = [0.5, 1.0])$ @end example Points in three dimensional space can be seen as a projection on the plane. In this example, plots of wind speeds corresponding to three meteorological stations are requested, first in a 3D plot and then in a multivariate scatterplot. @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c /* 3D plot */ dataplot (submatrix (s2, 4, 5), 'pointstyle = 2, @c 'maintitle = "Pairs of wind speeds measured in knots", @c 'axisnames = ["Station A", "Station B", "Station C"])$ @c /* Multivariate scatterplot */ dataplot (submatrix (s2, 4, 5), @c 'nclasses = 6, 'threedim = false)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) /* 3D plot */ dataplot (submatrix (s2, 4, 5), 'pointstyle = 2, 'maintitle = "Pairs of wind speeds measured in knots", 'axisnames = ["Station A", "Station B", "Station C"])$ (%i5) /* Multivariate scatterplot */ dataplot (submatrix (s2, 4, 5), 'nclasses = 6, 'threedim = false)$ @end example Note that in the last example, the number of classes in the histograms of the diagonal is set to 6, and that option @code{'threedim} is set to @code{false}. For more than three dimensions only multivariate scatterplots are possible, as in @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c dataplot (s2)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) dataplot (s2)$ @end example @end deffn @deffn {Function} histogram (@var{list}) @deffnx {Function} histogram (@var{list}, @var{option_1}, @var{option_2}, ...) @deffnx {Function} histogram (@var{one_column_matrix}) @deffnx {Function} histogram (@var{one_column_matrix}, @var{option_1}, @var{option_2}, ...) This function plots an histogram. Sample data must be stored in a list of numbers or a one column matrix. Giving values to the following @var{options} some aspects of the plot can be controlled: @itemize @bullet @item @code{'outputdev}, default @code{"x"}, indicates the output device; correct values are @code{"x"}, @code{"eps"} and @code{"png"}, for the screen, postscript and png format files, respectively. @item @code{'maintitle}, default @code{""}, is the main title between double quotes. @item @code{'axisnames}, default @code{["x", "Fr."]}, is a list with the names of axis @code{x} and @code{y}. @item @code{'picturescales}, default @code{[1.0, 1.0]}, scaling factors for the size of the plot. @item @code{'nclasses}, default @code{10}, is the number of classes or bars. @item @code{'relbarwidth}, default @code{0.9}, a decimal number between 0 and 1 to control bars width. @item @code{'barcolor}, default @code{1}, an integer to indicate bars color. @item @code{'colorintensity}, default @code{1}, a decimal number between 0 and 1 to fix color intensity. @end itemize In the next two examples, histograms are requested for the first 100 digits of number @code{%pi} and for the wind speeds in the third meteorological station. @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s1 : read_list (file_search ("pidigits.data"))$ @c histogram (s1, 'maintitle = "pi digits", 'axisnames = ["", "Absolute frequency"], @c 'relbarwidth = 0.2, 'barcolor = 3, 'colorintensity = 0.6)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c histogram (col (s2, 3), 'colorintensity = 0.3)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s1 : read_list (file_search ("pidigits.data"))$ (%i4) histogram (s1, 'maintitle = "pi digits", 'axisnames = ["", "Absolute frequency"], 'relbarwidth = 0.2, 'barcolor = 3, 'colorintensity = 0.6)$ (%i5) s2 : read_matrix (file_search ("wind.data"))$ (%i6) histogram (col (s2, 3), 'colorintensity = 0.3)$ @end example Note that in the first case, @code{s1} is a list and in the second example, @code{col(s2,3)} is a matrix. See also function @code{barsplot}. @end deffn @deffn {Function} barsplot (@var{list}) @deffnx {Function} barsplot (@var{list}, @var{option_1}, @var{option_2}, ...) @deffnx {Function} barsplot (@var{one_column_matrix}) @deffnx {Function} barsplot (@var{one_column_matrix}, @var{option_1}, @var{option_2}, ...) Similar to @code{histogram} but for discrete, numeric or categorical, statistical variables. These are the options, @itemize @bullet @item @code{'outputdev}, default @code{"x"}, indicates the output device; correct values are @code{"x"}, @code{"eps"} and @code{"png"}, for the screen, postscript and png format files, respectively. @item @code{'maintitle}, default @code{""}, is the main title between double quotes. @item @code{'axisnames}, default @code{["x", "Fr."]}, is a list with the names of axis @code{x} and @code{y}. @item @code{'picturescales}, default @code{[1.0, 1.0]}, scaling factors for the size of the plot. @item @code{'relbarwidth}, default @code{0.9}, a decimal number between 0 and 1 to control bars width. @item @code{'barcolor}, default @code{1}, an integer to indicate bars color. @item @code{'colorintensity}, default @code{1}, a decimal number between 0 and 1 to fix color intensity. @end itemize This example plots the barchart for groups @code{A} and @code{B} of patients in sample @code{s3}, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c barsplot (col (s3, 1), 'maintitle = "Groups of patients", @c 'axisnames = ["Group", "# of individuals"], 'colorintensity = 0.2)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s3 : read_matrix (file_search ("biomed.data"))$ (%i4) barsplot (col (s3, 1), 'maintitle = "Groups of patients", 'axisnames = ["Group", "# of individuals"], 'colorintensity = 0.2)$ @end example The first column in sample @code{s3} stores the categorical values @code{A} and @code{B}, also known sometimes as factors. On the other hand, the positive integer numbers in the second column are ages, in years, which is a discrete variable, so we can plot the absolute frequencies for these values, @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s3 : read_matrix (file_search ("biomed.data"))$ @c barsplot (col (s3, 2), 'maintitle = "Ages", @c 'axisnames = ["Years", "# of individuals"], 'colorintensity = 0.2, @c 'relbarwidth = 0.6)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s3 : read_matrix (file_search ("biomed.data"))$ (%i4) barsplot (col (s3, 2), 'maintitle = "Ages", 'axisnames = ["Years", "# of individuals"], 'colorintensity = 0.2, 'relbarwidth = 0.6)$ @end example See also function @code{histogram}. @end deffn @deffn {Function} boxplot (@var{data}) @deffnx {Function} boxplot (@var{data}, @var{option_1}, @var{option_2}, ...) This function plots box diagrams. Argument @var{data} can be a list, which is not of great interest, since these diagrams are mainly used for comparing different samples, or a matrix, so it is possible to compare two or more components of a multivariate statistical variable. But it is also allowed @var{data} to be a list of samples with possible different sample sizes, in fact this is the only function in package @code{descriptive} that admits this type of data structure. See example bellow. These are the options, @itemize @bullet @item @code{'outputdev}, default @code{"x"}, indicates the output device; correct values are @code{"x"}, @code{"eps"} and @code{"png"}, for the screen, postscript and png format files, respectively. @item @code{'maintitle}, default @code{""}, is the main title between double quotes. @item @code{'axisnames}, default @code{["sample", "y"]}, is a list with the names of axis @code{x} and @code{y}. @item @code{'picturescales}, default @code{[1.0, 1.0]}, scaling factors for the size of the plot. @end itemize Examples: @c ===beg=== @c load (descriptive)$ @c load (numericalio)$ @c s2 : read_matrix (file_search ("wind.data"))$ @c boxplot (s2, 'maintitle = "Windspeed in knots", @c 'axisnames = ["Seasons", ""])$ @c A : @c [[6, 4, 6, 2, 4, 8, 6, 4, 6, 4, 3, 2], @c [8, 10, 7, 9, 12, 8, 10], @c [16, 13, 17, 12, 11, 18, 13, 18, 14, 12]]$ @c boxplot (A)$ @c ===end=== @example (%i1) load (descriptive)$ (%i2) load (numericalio)$ (%i3) s2 : read_matrix (file_search ("wind.data"))$ (%i4) boxplot (s2, 'maintitle = "Windspeed in knots", 'axisnames = ["Seasons", ""])$ (%i5) A : [[6, 4, 6, 2, 4, 8, 6, 4, 6, 4, 3, 2], [8, 10, 7, 9, 12, 8, 10], [16, 13, 17, 12, 11, 18, 13, 18, 14, 12]]$ (%i6) boxplot (A)$ @end example @end deffn --Boundary-00=_5TgqFnyKa5ENh63-- From MAILER-DAEMON Sun Jan 14 18:25:10 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H6Eir-0005AB-Vb for mharc-help-texinfo@gnu.org; Sun, 14 Jan 2007 18:25:09 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H6Eiq-00056u-2z for help-texinfo@gnu.org; Sun, 14 Jan 2007 18:25:08 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H6Eio-00053j-4P for help-texinfo@gnu.org; Sun, 14 Jan 2007 18:25:07 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H6Ein-00053F-RE for help-texinfo@gnu.org; Sun, 14 Jan 2007 18:25:05 -0500 Received: from [64.34.169.74] (helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H6Ein-0004Tb-IF for help-texinfo@gnu.org; Sun, 14 Jan 2007 18:25:05 -0500 X-Envelope-From: karl@freefriends.org X-Envelope-To: help-texinfo@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l0ENP0G10883; Sun, 14 Jan 2007 17:25:00 -0600 Date: Sun, 14 Jan 2007 17:25:00 -0600 Message-Id: <200701142325.l0ENP0G10883@f7.net> From: karl@freefriends.org (Karl Berry) To: ficmatin01@solar.com.br Subject: Re: [help-texinfo] descriptive.texi @node iso-8859-1 In-Reply-To: <200701140824.57269.ficmatin01@solar.com.br> Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jan 2007 23:25:08 -0000 Hi Robert. Did you mean to send this to a Maxima list too? Can you help me for use the correct form (estat@'istica) ? 1) Try @'{i} instead of just @'i. Actually, you probably really want @'@dotless{i}. 2) Please send me a small test file exhibiting the problem. It is hard to debug from the entire Maxima manual. Thanks, Karl From MAILER-DAEMON Sun Jan 14 18:48:48 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H6F5k-00039u-Ba for mharc-help-texinfo@gnu.org; Sun, 14 Jan 2007 18:48:48 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H6F5j-00038A-5f for help-texinfo@gnu.org; Sun, 14 Jan 2007 18:48:47 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H6F5g-00035c-33 for help-texinfo@gnu.org; Sun, 14 Jan 2007 18:48:46 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H6F5f-00035M-Oz for help-texinfo@gnu.org; Sun, 14 Jan 2007 18:48:43 -0500 Received: from [200.175.8.37] (helo=smtp3.pop.com.br) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H6F5f-0008OG-6h for help-texinfo@gnu.org; Sun, 14 Jan 2007 18:48:43 -0500 Received: from localhost (localhost [127.0.0.1]) by smtp3-1 (Postfix) with ESMTP id C3DAE5C108; Sun, 14 Jan 2007 20:34:03 -0300 (EST) Received: from smtp3.pop.com.br (localhost [127.0.0.1]) by smtp3 (WCVirscan) with SMTP id 0000106745aabdeb ; Sun, 14 Jan 2007 20:34:03 -0300 Received: from filho1.server.net (200.175.184.105.dialup.gvt.net.br [200.175.184.105]) by smtp3 (Postfix) with ESMTP id A90815C104; Sun, 14 Jan 2007 20:34:02 -0300 (EST) From: Jorge Barros de Abreu Organization: Professor do Ensino =?iso-8859-1?q?M=E9dio?= To: Karl Berry Subject: Re: [help-texinfo] descriptive.texi @node iso-8859-1 Date: Sun, 14 Jan 2007 18:53:35 -0200 User-Agent: KMail/1.7.2 References: <200701142325.l0ENP0G10883@f7.net> In-Reply-To: <200701142325.l0ENP0G10883@f7.net> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200701141853.35327.ficmatin01@solar.com.br> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-DCC-POPInternet-Metrics: dcc 1259; Body=1 Fuz1=1 Fuz2=1 Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jan 2007 23:48:47 -0000 Em Sun 14 Jan 2007 21:25, Karl Berry escreveu: > 2) Please send me a small test file exhibiting the problem. =A0It is hard > =A0 =A0to debug from the entire Maxima manual. I am sorry Karl and all. My (big) mistake. > 1) Try @'{i} instead of just @'i. =A0Actually, you probably really want > =A0 =A0@'@dotless{i}. I will try this. Thanks. []=B4s =2D-=20 Data Estelar 2454113,296794 http://usr.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. From MAILER-DAEMON Sun Jan 14 19:04:12 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H6FKe-00008q-PP for mharc-help-texinfo@gnu.org; Sun, 14 Jan 2007 19:04:12 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H6FKd-00007L-Se for help-texinfo@gnu.org; Sun, 14 Jan 2007 19:04:11 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H6FKc-0008W6-A8 for help-texinfo@gnu.org; Sun, 14 Jan 2007 19:04:11 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H6FKc-0008Vg-72 for help-texinfo@gnu.org; Sun, 14 Jan 2007 19:04:10 -0500 Received: from [64.34.169.74] (helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H6FKa-0002Zb-P1 for help-texinfo@gnu.org; Sun, 14 Jan 2007 19:04:09 -0500 X-Envelope-From: karl X-Envelope-To: help-texinfo@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l0F045Z23952; Sun, 14 Jan 2007 18:04:05 -0600 Date: Sun, 14 Jan 2007 18:04:05 -0600 Message-Id: <200701150004.l0F045Z23952@f7.net> From: karl@freefriends.org (Karl Berry) To: ficmatin01@solar.com.br Subject: Re: [help-texinfo] descriptive.texi @node iso-8859-1 In-Reply-To: <200701141853.35327.ficmatin01@solar.com.br> Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2007 00:04:12 -0000 I am sorry Karl and all. My (big) mistake. Please don't be sorry. It wasn't a mistake. It is good to send the input files -- at least it makes it possible to debug. I'm glad you sent them. It's just that in this case, it seems like it should be pretty easy for you to make a small file, which should make the problem clearer and debugging faster. Thanks, Karl From MAILER-DAEMON Sun Jan 14 19:18:08 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H6FY8-0000ie-Rj for mharc-help-texinfo@gnu.org; Sun, 14 Jan 2007 19:18:08 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H6FY7-0000iZ-Gx for help-texinfo@gnu.org; Sun, 14 Jan 2007 19:18:07 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H6FY5-0000iK-Sb for help-texinfo@gnu.org; Sun, 14 Jan 2007 19:18:07 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H6FY5-0000iH-NM for help-texinfo@gnu.org; Sun, 14 Jan 2007 19:18:05 -0500 Received: from [200.175.8.220] (helo=smtp5.pop.com.br) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H6FY5-0005bK-CU for help-texinfo@gnu.org; Sun, 14 Jan 2007 19:18:05 -0500 Received: from localhost (localhost [127.0.0.1]) by smtp5-1 (Postfix) with ESMTP id B1C3B93877; Sun, 14 Jan 2007 22:18:04 -0200 (EDT) Received: from smtp5.pop.com.br (localhost [127.0.0.1]) by smtp5 (WCVirscan) with SMTP id 0000742345aac83c ; Sun, 14 Jan 2007 22:18:04 -0300 Received: from filho1.server.net (200.175.179.187.dialup.gvt.net.br [200.175.179.187]) by smtp5 (Postfix) with ESMTP id 2836D937DF; Sun, 14 Jan 2007 22:18:04 -0200 (EDT) From: Jorge Barros de Abreu Organization: Professor do Ensino =?iso-8859-1?q?M=E9dio?= To: Karl Berry Subject: Re: [help-texinfo] descriptive.texi @node iso-8859-1 Date: Sun, 14 Jan 2007 19:22:59 -0200 User-Agent: KMail/1.7.2 References: <200701142325.l0ENP0G10883@f7.net> In-Reply-To: <200701142325.l0ENP0G10883@f7.net> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200701141922.59239.ficmatin01@solar.com.br> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-DCC-POPInternet-Metrics: dcc 1259; Body=1 Fuz1=1 Fuz2=1 Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2007 00:18:07 -0000 Nothing work. []=B4s Em Sun 14 Jan 2007 21:25, Karl Berry escreveu: > 1) Try @'{i} instead of just @'i. Actually, you probably really want > @'@dotless{i}. > > 2) Please send me a small test file exhibiting the problem. It is hard > to debug from the entire Maxima manual. > > Thanks, > Karl =2D-=20 Data Estelar 2454113,296794 http://usr.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. From MAILER-DAEMON Tue Jan 16 05:50:17 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H6ltQ-00039m-Vf for mharc-help-texinfo@gnu.org; Tue, 16 Jan 2007 05:50:17 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H6ltO-00038V-PX for help-texinfo@gnu.org; Tue, 16 Jan 2007 05:50:14 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H6ltN-00036V-1G for help-texinfo@gnu.org; Tue, 16 Jan 2007 05:50:14 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H6ltM-00035v-A9 for help-texinfo@gnu.org; Tue, 16 Jan 2007 05:50:12 -0500 Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1H6ltL-0007g8-PW for help-texinfo@gnu.org; Tue, 16 Jan 2007 05:50:12 -0500 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1H6ltC-0001UI-9E for help-texinfo@gnu.org; Tue, 16 Jan 2007 11:50:02 +0100 Received: from 219.142.180.120 ([219.142.180.120]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Jan 2007 11:50:02 +0100 Received: from william.xwl by 219.142.180.120 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Jan 2007 11:50:02 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: help-texinfo@gnu.org From: William Xu Date: Tue, 16 Jan 2007 18:09:53 +0800 Organization: the Church of Emacs Lines: 14 Message-ID: <877ivncmfi.fsf@www.williamxu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 219.142.180.120 User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.92 (gnu/linux) Cancel-Lock: sha1:r1eeiO6AH9gr1I3T7WfjRyApPCs= Sender: news Subject: [help-texinfo] does texinfo supports utf8 now? X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2007 10:50:15 -0000 Hi all, When the source file foo.texinfo is encoded with utf8, i find `makeinfo' unable to generate correct foo.info, with some garbages included. But, if i change the output type to --html, the outputs seem okay. Is there any way to generate correct Info outputs too, with utf8 encoding? -- William And the next time you consider complaining that running Lucid Emacs 19.05 via NFS from a remote Linux machine in Paraguay doesn't seem to get the background colors right, you'll know who to thank. -- Matt Welsh From MAILER-DAEMON Tue Jan 16 19:36:40 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H6ynA-0005MT-5f for mharc-help-texinfo@gnu.org; Tue, 16 Jan 2007 19:36:40 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H6yn8-0005H6-Gn for help-texinfo@gnu.org; Tue, 16 Jan 2007 19:36:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H6yn6-0005Cj-UM for help-texinfo@gnu.org; Tue, 16 Jan 2007 19:36:38 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H6yn6-0005CU-Pg for help-texinfo@gnu.org; Tue, 16 Jan 2007 19:36:36 -0500 Received: from [64.34.169.74] (helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H6yn6-0007dA-Ec for help-texinfo@gnu.org; Tue, 16 Jan 2007 19:36:36 -0500 X-Envelope-From: karl@freefriends.org X-Envelope-To: help-texinfo@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l0H0aZu03201; Tue, 16 Jan 2007 18:36:35 -0600 Date: Tue, 16 Jan 2007 18:36:35 -0600 Message-Id: <200701170036.l0H0aZu03201@f7.net> From: karl@freefriends.org (Karl Berry) To: william.xwl@gmail.com Subject: Re: [help-texinfo] does texinfo supports utf8 now? In-Reply-To: <877ivncmfi.fsf@www.williamxu.com> Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jan 2007 00:36:38 -0000 i find `makeinfo' unable to generate correct foo.info, with some garbages included. Does specifying --enable-encoding help? If not, I'll need to see an input file with the problem (smaller is better) and the output file you get with the specific "garbage" identified ... Thanks, k From MAILER-DAEMON Wed Jan 17 00:06:39 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H730R-0004Pi-H6 for mharc-help-texinfo@gnu.org; Wed, 17 Jan 2007 00:06:39 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H730P-0004OX-7C for help-texinfo@gnu.org; Wed, 17 Jan 2007 00:06:37 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H730N-0004Nr-Lp for help-texinfo@gnu.org; Wed, 17 Jan 2007 00:06:36 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H730N-0004Nm-D4 for help-texinfo@gnu.org; Wed, 17 Jan 2007 00:06:35 -0500 Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1H730M-0003v8-Gf for help-texinfo@gnu.org; Wed, 17 Jan 2007 00:06:35 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1H730K-0006Oq-D4 for help-texinfo@gnu.org; Wed, 17 Jan 2007 06:06:32 +0100 Received: from 219.142.180.120 ([219.142.180.120]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 17 Jan 2007 06:06:32 +0100 Received: from william.xwl by 219.142.180.120 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 17 Jan 2007 06:06:32 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: help-texinfo@gnu.org From: William Xu Date: Wed, 17 Jan 2007 13:08:00 +0800 Organization: the Church of Emacs Lines: 67 Message-ID: <87bqkyutov.fsf@www.williamxu.com> References: <877ivncmfi.fsf@www.williamxu.com> <200701170036.l0H0aZu03201@f7.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 219.142.180.120 User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.92 (gnu/linux) Cancel-Lock: sha1:7cpj7ismFEf9OjJBifn8qBtiWHA= Sender: news Subject: [help-texinfo] Re: does texinfo supports utf8 now? X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jan 2007 05:06:37 -0000 --=-=-= karl@freefriends.org (Karl Berry) writes: > i find `makeinfo' > unable to generate correct foo.info, with some garbages included. > > Does specifying --enable-encoding help? No. > If not, I'll need to see an input file with the problem (smaller is > better) and the output file you get with the specific "garbage" > identified ... I've attached two files: `test.texinfo' and its output `test.info'. It includes some chinese characters. In `test.info' i've surrounded the garbage parts with {} symbol. -- William "The whole world is about three drinks behind." -- Humphrey Bogart --=-=-= Content-Type: application/x-texinfo; charset=utf-8 Content-Disposition: attachment; filename=test.texinfo Content-Transfer-Encoding: base64 XGlucHV0IHRleGluZm8gICBAYyAtKi0gdGV4aW5mbyAtKi0KQHNldGZpbGVuYW1lIHRlc3QuaW5m bwpAc2V0dGl0bGUg5Y+y6KiY5Y+K6K2v5rOoCgpAYyBAZG9jdW1lbnRlbmNvZGluZyB1dGYtOAoK QGMgdG9wICYgbWVudQpAaWZub3R0ZXgKQG5vZGUgVG9wLCAsIChkaXIpLCAoZGlyKQpAYyBGSVhN RTog54K65LuA6bq86YCZ6KOh5piv6Iux5paH6IiH5Lit5paH5pe255qE5pWI5p6c5LiN5ZCM77yf CkB0b3Ag5Y+y6KiY5Y+K5r6k5rOoCgrmlofnq6Dnr4AKCkBlbmQgaWZub3R0ZXgKCkBtZW51CuS4 ieWNgeS4luWutgoqIOWNt+S4ieWNgeS4gDo6CeWQs+WkquS8r+S4luWutuesrOS4gApAZW5kIG1l bnUKCkBjIGJvZHkKQG5vZGUg5Y235LiJ5Y2B5LiACkBjaGFwdGVyIOWQs+WkquS8r+S4luWutues rOS4gAoKQGNpbmRleCDljbfkuInljYHkuIAgLSDlkLPlpKrkvK/kuJblrrbnrKzkuIAKCiAgICDl kLPlpKrkvK/vvIzlpKrkvK/lvJ/ku7Lpm43vvIznmoblkajlpKrnjovkuYvlrZDvvIzogIznjovl raPmrbfkuYvlhYTkuZ/jgILlraPmrbfos6LvvIzogIzmnInlnKPlrZDmmIzvvIzlpKrnjovmrLIK 56uL5a2j5q235Lul5Y+K5piM77yM5pa85piv5aSq5L2w44CB5Luy6ZuN5LqM5Lq65LmD5aWU6I2K 6KC777yM5paH6Lqr5pa355m877yM56S65LiN5Y+v55So77yM5Lul6YG/5a2j5q2344CC5a2j5q23 5p6c56uLCu+8jOaYr+eCuueOi+Wto++8jOiAjOaYjOeCuuaWh+eOi+OAguWkquS8r+S5i+WllOiN iuigu++8jOiHquiZn+WPpeWQs+OAguiNiuigu+e+qeS5i++8jOW+nuiAjOatuOS5i+WNg+mkmOWu tu+8jOeri+eCuuWQswrlpKrkvK/jgIIKCkBieWUK --=-=-= Content-Type: application/octet-stream; charset=utf-8 Content-Disposition: attachment; filename=test.info Content-Transfer-Encoding: base64 VGhpcyBpcyB0ZXN0LmluZm8sIHByb2R1Y2VkIGJ5IG1ha2VpbmZvIHZlcnNpb24gNC44IGZyb20K L2hvbWUvd2lsbGlhbS90b2hhbmRsZS90ZXN0LnRleGluZm8uCgofCkZpbGU6IHRlc3QuaW5mbywg IE5vZGU6IFRvcCwgIFByZXY6IChkaXIpLCAgVXA6IChkaXIpCgrlj7LoqJjlj4rmvqTms6gKKioq KioqKioqKioqKioqCgrmlod756t9IOevgAoKKiBNZW51OgoK5LiJ5Y2B5LiW5a62Ciog5Y235LiJ 5Y2B5LiAOjoJ5ZCz5aSq5Lyv5LiW5a6256ys5LiACgofCkZpbGU6IHRlc3QuaW5mbywgIE5vZGU6 IOWNt+S4ieWNgeS4gCwgIFByZXY6IFRvcCwgIFVwOiBUb3AKCjEg5ZCz5aSq5Lyv5LiW5a6256ys 5LiACioqKioqKioqKioqKioqKioqKioqKioqCgrlkLPlpKrkvK/vvIzlpKrkvK/lvJ/ku7Lpm43v vIznmoblkajlpKrnjovkuYvlrZDvvIzogIznjovlraPmrbfkuYvlhYTkuZ/jgILlraPmrbfos6Lv vIzogIzmnInlnKPlrZDmmIzvvIzlpKrnjovmrLIK56uL5a2j5q235Lul5Y+K5piM77yM5pa85piv 5aSq5L2w44CB5Luy6ZuN5LqM5Lq65LmD5aWU6I2Ke+ggu33vvIzmlofouqvmlrfnmbzvvIznpLrk uI3lj6/nlKjvvIzku6Xpgb/lraPmrbfjgILlraPmrbfmnpznq4sK77yM5piv54K6546L5a2j77yM 6ICM5piM54K65paH546L44CC5aSq5Lyv5LmL5aWU6I2Ke+ggu33vvIzoh6romZ/lj6XlkLPjgILo jYp76CC7fee+qeS5i++8jOW+nuiAjOatuOS5i+WNg+mkmOWutu+8jOeri+eCuuWQswrlpKrkvK/j gIIKCgofClRhZyBUYWJsZToKTm9kZTogVG9wfzk1Ck5vZGU6IOWNt+S4ieWNgeS4gH8yNTgKHwpF bmQgVGFnIFRhYmxlCg== --=-=-=-- From MAILER-DAEMON Sun Jan 21 20:10:28 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H8nhb-0008Mi-Ty for mharc-help-texinfo@gnu.org; Sun, 21 Jan 2007 20:10:27 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H8nha-0008MR-UL for help-texinfo@gnu.org; Sun, 21 Jan 2007 20:10:26 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H8nhY-0008L2-ND for help-texinfo@gnu.org; Sun, 21 Jan 2007 20:10:26 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H8nhY-0008Kg-DB for help-texinfo@gnu.org; Sun, 21 Jan 2007 20:10:24 -0500 Received: from [64.34.169.74] (helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H8nhX-0000zd-DS for help-texinfo@gnu.org; Sun, 21 Jan 2007 20:10:23 -0500 X-Envelope-From: karl@freefriends.org X-Envelope-To: help-texinfo@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l0M1AHX14049; Sun, 21 Jan 2007 19:10:17 -0600 Date: Sun, 21 Jan 2007 19:10:17 -0600 Message-Id: <200701220110.l0M1AHX14049@f7.net> From: karl@freefriends.org (Karl Berry) To: e.conti@gmx.net In-Reply-To: <20070105235247.GA1181@oxstone.com> Cc: per@bothner.com, help-texinfo@gnu.org Subject: [help-texinfo] Re: Still some problems with the latest CVS version of makeinfo X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 01:10:27 -0000 (Per, please see docbook question about unnumbered chapters in case you have any insights there; you don't need to bother with the rest.) I modified the test case, which you can download here: http://www.europephoto.com/temp/test_case.tgz Finally had a chance to get back to this. Sorry for the delay (and the not-very-helpful answers, as you'll see). - an error message appear when you click on a "accented" node name in a menu - an error message appear when you click on a link to an "accented" node name (xref command) Regrettably, I get no error message in these cases, using yelp 2.6.4 on Red Hat (WS 4.1), so I'm at a loss to debug it. What does the error message say? Can you trace it to a particular element in the docbook file? - not all the chapters appear in the left panel of yelp (it should contains a tree of the sections) In the test document, the @top and second @chapter had no title specified. If you add some words, I expect they'll show up in the left panel. As in: @top toptest ... @chapter chap2 ... They are actually present now (for me), they just appear as blank lines in yelp's left-hand panel. But when I click on the blank line, I get to the appropriate place. - the chapter numbers in the xrefs links aren't the good one. Indeed, yelp is apparently counting the Top node as chapter one, and also apparently counts any @unnumbered chapter as unnumbered. makeinfo is outputting a label for numbered chapters, and no label for unnumbered ones, as in: ... ... I poked around a little, but don't know if there is a better way to represent unnumbered chapters in Docbook. Help? Meanwhile, the book on Docbook http://www.oreilly.com/catalog/docbook/chapter/book/chapter.html says the following, which seems to state that yelp should be using the labels output by makeinfo instead of renumbering on its own: Generally, an explicit Label attribute is used only if the processing system is incapable of generating the label automatically. If present, the Label is normative; it will used even if the processing system is capable of automatic labelling. I didn't try to find the reference in the actual standard. karl From MAILER-DAEMON Mon Jan 22 07:26:29 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H8yFp-0001cL-0S for mharc-help-texinfo@gnu.org; Mon, 22 Jan 2007 07:26:29 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H8yFm-0001a4-Pe for help-texinfo@gnu.org; Mon, 22 Jan 2007 07:26:26 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H8yFk-0001Zl-UG for help-texinfo@gnu.org; Mon, 22 Jan 2007 07:26:26 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H8yFk-0001Zi-R3 for help-texinfo@gnu.org; Mon, 22 Jan 2007 07:26:24 -0500 Received: from [200.175.8.220] (helo=smtp5.pop.com.br) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H8xXT-0006u0-N8 for help-texinfo@gnu.org; Mon, 22 Jan 2007 06:40:42 -0500 Received: from localhost (localhost [127.0.0.1]) by smtp5-1 (Postfix) with ESMTP id 4A2D8938AA; Mon, 22 Jan 2007 09:39:56 -0200 (EDT) Received: from smtp5.pop.com.br (localhost [127.0.0.1]) by smtp5 (WCVirscan) with SMTP id 0000247645b4a28c ; Mon, 22 Jan 2007 09:39:56 -0300 Received: from filho1.server.net (200.175.178.78.dialup.gvt.net.br [200.175.178.78]) by smtp5 (Postfix) with ESMTP id 9C85693895; Mon, 22 Jan 2007 09:39:54 -0200 (EDT) From: Jorge Barros de Abreu Organization: Professor do Ensino =?iso-8859-1?q?M=E9dio?= To: help-texinfo@gnu.org Date: Mon, 22 Jan 2007 06:45:05 -0200 User-Agent: KMail/1.7.2 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200701220645.05539.ficmatin01@solar.com.br> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-DCC-POPInternet-Metrics: dcc 1259; Body=1 Fuz1=1 Fuz2=1 Cc: Karl Berry Subject: [help-texinfo] @node iso-8859-1 X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 12:26:27 -0000 Hi Karl and all. All contents of each manual file was removed. Only the main file project.te= xi=20 is unchaged. In not main files the content is only @menu . . . @end menu,=20 @node e @section and nothing more. The compilation process exit with fail. The pdf is generated but with index= es=20 broken: =2E/project.aux:46: Missing @endcsname inserted =2E/project.aux:46: Missing { inserted =2E/project.aux:46: Extra @endcsname =2E/project.aux:46: Extra }, or forgotten @endgroup =2E/project.aux:46: Extra }, or forgotten @endgroup =2E/project.aux:47: Missing @endcsname inserted =2E/project.aux:47: Missing { inserted =2E/project.aux:47: Extra @endcsname =2E/project.aux:47: Extra }, or forgotten @endgroup =2E/project.aux:48: Missing @endcsname inserted =2E/project.aux:48: Missing { inserted =2E/project.aux:48: Extra @endcsname =2E/project.aux:48: Extra }, or forgotten @endgroup =2E/project.aux:49: Missing @endcsname inserted =2E/project.aux:49: Missing { inserted =2E/project.aux:49: Extra @endcsname =2E/project.aux:49: Extra }, or forgotten @endgroup =2E/project.aux:49: Extra }, or forgotten @endgroup =2E/project.aux:50: Missing @endcsname inserted =2E/project.aux:50: Missing { inserted =2E/project.aux:50: Extra @endcsname =2E/project.aux:50: Extra }, or forgotten @endgroup =2E/project.aux:51: Missing @endcsname inserted =2E/project.aux:51: Missing { inserted =2E/project.aux:51: Extra @endcsname =2E/project.aux:51: Extra }, or forgotten @endgroup =2E/project.aux:52: Missing @endcsname inserted =2E/project.aux:52: Missing { inserted =2E/project.aux:52: Extra @endcsname =2E/project.aux:52: Extra }, or forgotten @endgroup =2E/project.aux:52: Extra }, or forgotten @endgroup =2E/project.aux:53: Missing @endcsname inserted =2E/project.aux:53: Missing { inserted =2E/project.aux:53: Extra @endcsname =2E/project.aux:53: Extra }, or forgotten @endgroup =2E/project.aux:54: Missing @endcsname inserted =2E/project.aux:54: Missing { inserted =2E/project.aux:54: Extra @endcsname =2E/project.aux:54: Extra }, or forgotten @endgroup =2E/project.aux:97: Missing @endcsname inserted =2E/project.aux:97: Missing { inserted =2E/project.aux:97: Extra @endcsname =2E/project.aux:97: Extra }, or forgotten @endgroup =2E/project.aux:97: Extra }, or forgotten @endgroup =2E/project.aux:98: Missing @endcsname inserted =2E/project.aux:98: Missing { inserted =2E/project.aux:98: Extra @endcsname =2E/project.aux:98: Extra }, or forgotten @endgroup =2E/project.aux:99: Missing @endcsname inserted =2E/project.aux:99: Missing { inserted =2E/project.aux:99: Extra @endcsname =2E/project.aux:99: Extra }, or forgotten @endgroup =2E/project.aux:100: Missing @endcsname inserted =2E/project.aux:100: Missing { inserted =2E/project.aux:100: Extra @endcsname =2E/project.aux:100: Extra }, or forgotten @endgroup =2E/project.aux:100: Extra }, or forgotten @endgroup =2E/project.aux:101: Missing @endcsname inserted =2E/project.aux:101: Missing { inserted =2E/project.aux:101: Extra @endcsname =2E/project.aux:101: Extra }, or forgotten @endgroup =2E/project.aux:102: Missing @endcsname inserted =2E/project.aux:102: Missing { inserted =2E/project.aux:102: Extra @endcsname =2E/project.aux:102: Extra }, or forgotten @endgroup =2E/project.aux:103: Missing @endcsname inserted =2E/project.aux:103: Missing { inserted =2E/project.aux:103: Extra @endcsname =2E/project.aux:103: Extra }, or forgotten @endgroup =2E/project.aux:103: Extra }, or forgotten @endgroup =2E/project.aux:104: Missing @endcsname inserted =2E/project.aux:104: Missing { inserted =2E/project.aux:104: Extra @endcsname =2E/project.aux:104: Extra }, or forgotten @endgroup =2E/project.aux:105: Missing @endcsname inserted =2E/project.aux:105: Missing { inserted =2E/project.aux:105: Extra @endcsname =2E/project.aux:105: Extra }, or forgotten @endgroup =2E/project.aux:106: Missing @endcsname inserted =2E/project.aux:106: Missing { inserted =2E/project.aux:106: Extra @endcsname =2E/project.aux:106: Extra }, or forgotten @endgroup =2E/project.aux:106: Extra }, or forgotten @endgroup =2E/project.aux:107: Missing @endcsname inserted =2E/project.aux:107: Missing { inserted =2E/project.aux:107: Extra @endcsname =2E/project.aux:107: Extra }, or forgotten @endgroup =2E/project.aux:108: Missing @endcsname inserted =2E/project.aux:108: Missing { inserted =2E/project.aux:108: Extra @endcsname =2E/project.aux:108: Extra }, or forgotten @endgroup =2E/project.aux:109: Missing @endcsname inserted =2E/project.aux:109: Missing { inserted =2E/project.aux:109: Extra @endcsname =2E/project.aux:109: Extra }, or forgotten @endgroup =2E/project.aux:109: Extra }, or forgotten @endgroup =2E/project.aux:110: Missing @endcsname inserted =2E/project.aux:110: Missing { inserted =2E/project.aux:110: Extra @endcsname =2E/project.aux:110: Extra }, or forgotten @endgroup (That makes 100 errors; please try again.) No pages of output. Transcript written on project.log. /usr/bin/texi2dvi: pdfetex exited with bad status, quitting. /usr/bin/texi2dvi: see project.log for errors. =2D-=20 Data Estelar 2454120,811794 http://usr.solar.com.br/~ficmatin Desejo-lhe Paz, Vida Longa e Prosperidade. S=E3o Bem Vindas Mensagens no Formato Texto Gen=E9rico com Acentos. From MAILER-DAEMON Mon Jan 22 18:58:27 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H993T-0005vP-5o for mharc-help-texinfo@gnu.org; Mon, 22 Jan 2007 18:58:27 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H993R-0005vB-Lu for help-texinfo@gnu.org; Mon, 22 Jan 2007 18:58:25 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H993Q-0005uz-6E for help-texinfo@gnu.org; Mon, 22 Jan 2007 18:58:25 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H993Q-0005uw-3i for help-texinfo@gnu.org; Mon, 22 Jan 2007 18:58:24 -0500 Received: from [64.34.169.74] (helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H993P-0005Mo-JM for help-texinfo@gnu.org; Mon, 22 Jan 2007 18:58:23 -0500 X-Envelope-From: karl@freefriends.org X-Envelope-To: help-texinfo@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l0MNwKx11634; Mon, 22 Jan 2007 17:58:20 -0600 Date: Mon, 22 Jan 2007 17:58:20 -0600 Message-Id: <200701222358.l0MNwKx11634@f7.net> From: karl@freefriends.org (Karl Berry) To: ficmatin01@solar.com.br In-Reply-To: <200701220645.05539.ficmatin01@solar.com.br> Cc: help-texinfo@gnu.org Subject: [help-texinfo] Re: @node iso-8859-1 X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 23:58:26 -0000 ./project.aux:46: Missing @endcsname inserted ./project.aux:46: Missing { inserted Can you please send me the project.texi you were running it on? I'm not sure where to get it. Thanks. From MAILER-DAEMON Tue Jan 23 05:20:45 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H9Ilg-0000ID-B5 for mharc-help-texinfo@gnu.org; Tue, 23 Jan 2007 05:20:44 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H9Ild-0000GC-MA for help-texinfo@gnu.org; Tue, 23 Jan 2007 05:20:42 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H9IlY-0000D5-Ob for help-texinfo@gnu.org; Tue, 23 Jan 2007 05:20:40 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H9IlY-0000Cc-8g for help-texinfo@gnu.org; Tue, 23 Jan 2007 05:20:36 -0500 Received: from [134.76.10.23] (helo=tmailer.gwdg.de) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1H9IlX-0002mk-FB for help-texinfo@gnu.org; Tue, 23 Jan 2007 05:20:36 -0500 Received: from mailbox.gwdg.de ([134.76.10.21] helo=web-mailer.gwdg.de) by mailer.gwdg.de with esmtp (Exim 4.63) (envelope-from ) id 1H9IlW-0005kz-1d for help-texinfo@gnu.org; Tue, 23 Jan 2007 11:20:34 +0100 X-Xeceived: from 134.76.244.101 (SquirrelMail authenticated user lfinsto1) by web-mailer.gwdg.de with HTTP; Tue, 23 Jan 2007 11:20:34 +0100 (CET) Message-ID: <1660.134.76.244.101.1169547634.squirrel@web-mailer.gwdg.de> Date: Tue, 23 Jan 2007 11:20:34 +0100 (CET) From: lfinsto1@gwdg.de To: help-texinfo@gnu.org User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: (clean) by exiscan+sophie Subject: [help-texinfo] Formatting parser symbols and rules X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2007 10:20:42 -0000 Hello Karl et al, I've been working on the second Texinfo manual for the IWF Metadata Harvester (`Scantest') (http://www.nongnu.org/iwf-mdh/iwfmdh.html). It documents, among other things, the symbols and rules belonging to a parser written using GNU Bison. Texinfo doesn't support this directly, and my solutions are somewhat more complicated than I'd like. I doubt that anyone has time to work on modifying Texinfo to support this, but I thought I'd describe the problems briefly, so you could add this to a "TODO" file, if you thought it was worthwhile. The manual, in various formats, is available here: http://www.nongnu.org/iwf-mdh/iwfmdh.html#Documentation I've been working on the TeX and HTML versions; I haven't looked at the Info version yet. The sources are here: http://ftp.gwdg.de/pub/gnu2/iwfmdh/scantest/ or here: http://cvs.savannah.nongnu.org/viewcvs/iwf-mdh/scantest/DOC/TEXINFO/?root=iwf-mdh The main file, which contains the macros and includes the other files, is `scantest.texi'. The file containing the Texinfo code for the parser is `parser.texi'. They are in the directory `Scantest-1.0/DOC/TEXINFO/'. 1. It would be nice to have a set of `@def' commands for parser symbols, or even one set for tokens and one for non-terminals. I've used `@deftypevr' for the tokens and non-terminal symbols. I like the formatting produced by the `@def' commands, and I thought it would be too much work to try to simulate it using `@iftex', `@ifhtml', and `@ifinfo'. However, using `@deftypevr' does have the effect that the symbols are put into the Variable Index. I'm not sure this is a good idea or not. I've added two new indices, one for tokens (`@ptindex') and one for non-teminals (`@pnindex') and add the entries by hand, so the entries in the Variable Index are redundant. 2. I've been formatting the parser rules so that they look like the grammar rules in _The METAFONTbook_. This is the macro I use: @macro angles {arg} @iftex @tex \\begingroup \\catcode`\\_=13 \\let_=\\space \\rm $\\langle$\arg\$\\rangle$ \\endgroup @end tex @end iftex @ifhtml @html < @end html \arg\ @html > @end html @end ifhtml @end macro This works fine, except that it doesn't work for the first item in the entries for the Parser Rule Index (`@prindex'), which disappeared in the HTML output if I tried to use it. It worked fine in the TeX version. My solution (or kludge) is to duplicate the index entries, once for TeX, once for the other formats: @iftex @prindex @angles{statement_list} @lra{} @t{EMPTY} @prindex @angles{statement_list} @lra{} @angles{statement_list} @angles{statement} @end iftex @c @c **** (4) Index entries for HTML/INFO @c @ifnottex @prindex statement_list @lra{} @t{EMPTY} @prindex statement_list @lra{} statement_list statement @end ifnottex @c @c **** (4) Text @c @noindent @angles{statement list} @lra{} @t{EMPTY}@* @ruleor{} @angles{statement list} @angles{statement}@* In the HTML output, this has the effect that non-terminals are surrounded by angle brackets in the running text and the underline character is replaced by a space, whereas there are no angle brackets in the index and the underline characters are unchanged. This is clearly not ideal, but I'm not sure what the best solution would be. I'm also undecided about whether an index of parser rules is really needed at all. The next two points aren't connected with the parser. 3. I use `@deftypevr' and `@deftypefn' for class member variables and functions. It's been awhile since I looked at the "object-oriented" `@def' commands. I believe I don't use them because some of them cause "object-oriented" terminology to be printed to the manual, which I don't want. I find it useful to have the names of the variables and functions duplicated in the appropriate index using the class qualifier, e.g., @vindex Id_Type::name @vindex Id_Type::value @c @deftypevr {Public variables} string name @deftypevrx {} void* value @end deftypevr @findex @t{Id_Type::Id_Type} @c @deftypefn {Constructor} void Id_Type (@code{void}) @end deftypefn It would be nice if this could be automated, somehow. 4. Some of the lines in my input files get quite long. There is no way of breaking them that works everywhere. For example, it's not possible to use `@ ' in an index entry. Some of the `@node' lines are also very long, and I think `makeinfo' at least will fail if they're broken. The manual is still very rudimentary, but any comments about it would be welcome. Thanks, Laurence From MAILER-DAEMON Wed Jan 24 14:46:24 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H9o4e-0008FX-IQ for mharc-help-texinfo@gnu.org; Wed, 24 Jan 2007 14:46:24 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H9o4d-0008FL-Pm for help-texinfo@gnu.org; Wed, 24 Jan 2007 14:46:23 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H9o4c-0008Ex-MJ for help-texinfo@gnu.org; Wed, 24 Jan 2007 14:46:22 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H9o4c-0008Eu-Hq for help-texinfo@gnu.org; Wed, 24 Jan 2007 14:46:22 -0500 Received: from server1.f7.net ([64.34.169.74] helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H9o4c-0005fD-6E for help-texinfo@gnu.org; Wed, 24 Jan 2007 14:46:22 -0500 X-Envelope-From: karl@freefriends.org X-Envelope-To: help-texinfo@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l0OJkDF01673; Wed, 24 Jan 2007 13:46:13 -0600 Date: Wed, 24 Jan 2007 13:46:13 -0600 Message-Id: <200701241946.l0OJkDF01673@f7.net> From: karl@freefriends.org (Karl Berry) To: lfinsto1@gwdg.de Subject: Re: [help-texinfo] Formatting parser symbols and rules In-Reply-To: <1660.134.76.244.101.1169547634.squirrel@web-mailer.gwdg.de> X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 19:46:23 -0000 Sorry, I can't reply to everything in detail now (and I'll be offline after tomorrow until next Wednesday), but here are a few notes. 1. It would be nice to have a set of `@def' commands for parser I would prefer not to add any more @def commands for specialized application. They're a big pain. tokens (`@ptindex') and one for non-teminals (`@pnindex') and add the entries by hand, so the entries in the Variable Index are redundant. Maybe redirect the vr index to pn, then, and omit the explicit pn entries. I highly recommend redirecting all indexes into one in the end, anyway. This works fine, except that it doesn't work for the first item in the Well, that's a bug, but it seems like an awful lot of trouble. How about simply using @var? That's what it's intended for. Maybe we should invent a formatting option that says whether or not @var should use angle brackets, or a second command (say, @metavar) that does have angle brackets. Or maybe just forget the angle brackets, even though I know they are highly traditional in parser descriptions. it's not possible to use `@ ' in an index entry. What happens? I don't know of any explicit restriction. Some of the `@node' lines are also very long, and I think `makeinfo' at least will fail if they're broken. @node commands definitely have to be on one line. But do you really have individual node names that are longer than 70 chars or so? Yikes. karl From MAILER-DAEMON Wed Jan 24 19:46:46 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1H9slJ-00049i-Q9 for mharc-help-texinfo@gnu.org; Wed, 24 Jan 2007 19:46:45 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H9slH-00048j-Jq for help-texinfo@gnu.org; Wed, 24 Jan 2007 19:46:43 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H9slF-00047j-RT for help-texinfo@gnu.org; Wed, 24 Jan 2007 19:46:43 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H9slF-00047f-NM for help-texinfo@gnu.org; Wed, 24 Jan 2007 19:46:41 -0500 Received: from server1.f7.net ([64.34.169.74] helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H9slF-0006Uz-9i for help-texinfo@gnu.org; Wed, 24 Jan 2007 19:46:41 -0500 X-Envelope-From: karl@freefriends.org X-Envelope-To: help-texinfo@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l0P0ke010090; Wed, 24 Jan 2007 18:46:40 -0600 Date: Wed, 24 Jan 2007 18:46:40 -0600 Message-Id: <200701250046.l0P0ke010090@f7.net> From: karl@freefriends.org (Karl Berry) To: william.xwl@gmail.com Subject: Re: [help-texinfo] Re: does texinfo supports utf8 now? In-Reply-To: <87bqkyutov.fsf@www.williamxu.com> X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 00:46:44 -0000 In `test.info' i've surrounded the garbage parts with {} symbol. Thanks for the report. I believe this bug is fixed in CVS. In 4.8 and earlier, character 0xa0 turned into a regular space (0x20). That's no longer the case (thanks to Miloslav). I don't know when the next release will be, but if you need the fix urgently, I guess you could use the CVS version. Regards, Karl From MAILER-DAEMON Thu Jan 25 03:35:15 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HA04h-0005n3-BA for mharc-help-texinfo@gnu.org; Thu, 25 Jan 2007 03:35:15 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HA04g-0005mo-3e for help-texinfo@gnu.org; Thu, 25 Jan 2007 03:35:14 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HA04e-0005lo-OU for help-texinfo@gnu.org; Thu, 25 Jan 2007 03:35:12 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HA04e-0005ll-IV for help-texinfo@gnu.org; Thu, 25 Jan 2007 03:35:12 -0500 Received: from tmailer.gwdg.de ([134.76.10.23]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HA04d-0008Ij-W9 for help-texinfo@gnu.org; Thu, 25 Jan 2007 03:35:12 -0500 Received: from mailbox.gwdg.de ([134.76.10.21] helo=web-mailer.gwdg.de) by mailer.gwdg.de with esmtp (Exim 4.63) (envelope-from ) id 1HA04Z-0001ye-AP; Thu, 25 Jan 2007 09:35:07 +0100 X-Xeceived: from 134.76.244.101 (SquirrelMail authenticated user lfinsto1) by web-mailer.gwdg.de with HTTP; Thu, 25 Jan 2007 09:35:07 +0100 (CET) Message-ID: <1491.134.76.244.101.1169714107.squirrel@web-mailer.gwdg.de> In-Reply-To: <200701241946.l0OJkDF01673@f7.net> References: <200701241946.l0OJkDF01673@f7.net> Date: Thu, 25 Jan 2007 09:35:07 +0100 (CET) Subject: Re: [help-texinfo] Formatting parser symbols and rules From: lfinsto1@gwdg.de To: "Karl Berry" User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: (clean) by exiscan+sophie X-detected-kernel: Linux 2.4-2.6 Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 08:35:14 -0000 > Sorry, I can't reply to everything in detail now (and I'll be offline > after tomorrow until next Wednesday), but here are a few notes. Don't worry. Like I said, this is more for a "TODO" file, (possibly), and not for instant solution, or any solution at all, necessarily. I'm reasonably happy with my kludges. If my own situation ever allows it, I'd be interested in working on Texinfo myself. > > 1. It would be nice to have a set of `@def' commands for parser > > I would prefer not to add any more @def commands for specialized > application. They're a big pain. > Okay, point taken. > tokens (`@ptindex') and one for non-teminals (`@pnindex') and add the > entries by hand, so the entries in the Variable Index are redundant. > > Maybe redirect the vr index to pn, then, and omit the explicit pn entries. That wouldn't work, because there are many other variables that need to go in the variable index. I'd like to keep the parser symbols separate to reduce clutter. > I highly recommend redirecting all indexes into one in the end, anyway. > Oh, well we obviously disagree on this point. > This works fine, except that it doesn't work for the first item in the > > Well, that's a bug, but it seems like an awful lot of trouble. How > about simply using @var? That's what it's intended for. Maybe we > should invent a formatting option that says whether or not @var should > use angle brackets, or a second command (say, @metavar) that does have > angle brackets. Or maybe just forget the angle brackets, even though I > know they are highly traditional in parser descriptions. `@var' puts the text in a slanted font in the TeX output, except for `[]' in `@var{argv[]}', as I've determined. I suppose it wasn't meant to be used this way, but I don't think this is a good enough reason to change it to `char** argv'. I'd have to look up whether there's a semantic difference. I prefer this style of declaration to `char **argv', even though the latter is probably more correct. Declarations like `char c[]' are awkward to format, anyway, since `@code{char} @var{c[]}' would seem to make the brackets part of the variable rather than the type. I don't suppose that this problem can be solved. If I change the underlines to spaces, than something is needed to hold the names of the non-terminals together. I could just format the parser rules in Bison's syntax, e.g., `statement_list: statement_list statement', but I prefer Knuth's formatting. Another problem is the direction of the arrows. When using Bison's debugging facility, the arrows point the other way, which is potentially confusing. Please don't make changes to `@var' on my account. An `@angles' command that doesn't work on the macro level would be nice, though. When I run `texi2dvi', the file `scantest.tmp' is included what appears to be hundreds of times. After the run, it contains this: @iftex @tex $\longrightarrow$ @end tex @end iftex @ifhtml @html → @end html @end ifhtml @ifinfo --> @end ifinfo@endinput I therefore assume it is used to handle macros. It slows things down, and creates a lot of ugly terminal output, but isn't otherwise a problem. > > it's not possible to use `@ ' in an index entry. > > What happens? I don't know of any explicit restriction. It works with `texi2dvi', but `makeinfo' fails: c:\Scantest\DOC\TEXINFO//parser.texi:235: Unknown command `'. c:\Scantest\DOC\TEXINFO//parser.texi:235: Unknown command `'. In addition, `@var{argv[]}' causes `makeinfo' without `--html' to issue the following (annoying) warnings: c:\Scantest\DOC\TEXINFO//glblfncs.texi:41: warning: unlikely character [ in @var. c:\Scantest\DOC\TEXINFO//glblfncs.texi:41: warning: unlikely character ] in @var For some reason, they aren't issued when the `--html' option is used. > > Some of the `@node' lines are also very long, and I think `makeinfo' > at least will fail if they're broken. > > @node commands definitely have to be on one line. But do you really > have individual node names that are longer than 70 chars or so? Yikes. Yes, with the `Top', `Up', and `Next' references inserted by Emacs' `texinfo-multiple-files-update', e.g., `@node Arithmetical Operators Parser, Boolean Operators Parser, \ Operators Parser, Operators Parser' I call `texinfo-multiple-files-update' function with a positive numerical argument, and I always have to delete an extra `@detailmenu' in the main file (`scantest.texi') by hand. Thanks, Laurence From MAILER-DAEMON Thu Jan 25 14:36:33 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HAAOf-0004mj-H6 for mharc-help-texinfo@gnu.org; Thu, 25 Jan 2007 14:36:33 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HAAOc-0004kS-Tl for help-texinfo@gnu.org; Thu, 25 Jan 2007 14:36:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HAAOZ-0004h6-AI for help-texinfo@gnu.org; Thu, 25 Jan 2007 14:36:30 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HAAOY-0004go-Up for help-texinfo@gnu.org; Thu, 25 Jan 2007 14:36:27 -0500 Received: from server1.f7.net ([64.34.169.74] helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HAAOW-0006oK-Qo for help-texinfo@gnu.org; Thu, 25 Jan 2007 14:36:25 -0500 X-Envelope-From: karl@freefriends.org X-Envelope-To: help-texinfo@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l0PJaEU29547; Thu, 25 Jan 2007 13:36:14 -0600 Date: Thu, 25 Jan 2007 13:36:14 -0600 Message-Id: <200701251936.l0PJaEU29547@f7.net> From: karl@freefriends.org (Karl Berry) To: lfinsto1@gwdg.de Subject: Re: [help-texinfo] Formatting parser symbols and rules In-Reply-To: <1491.134.76.244.101.1169714107.squirrel@web-mailer.gwdg.de> X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 19:36:31 -0000 Declarations like `char c[]' I am completely baffled. @var is meant for metasyntactic variables, like nonterminals in parser rules. That's it. I therefore assume it is used to handle macros. It slows things down, and creates a lot of ugly terminal output, but isn't otherwise a problem. If you use etex instead of tex, I believe macros won't require the auxiliary file. (There's no other way to get the catcodes right in original TeX.) Yes, with the `Top', `Up', and `Next' references inserted by Emacs' `texinfo-multiple-files-update', e.g., My advice is, don't use those. Use implicit pointers instead (so the @node lines just have the node name). Much simpler. Assuming a "normal" hierarchical manual. I call `texinfo-multiple-files-update' function with a positive numerical argument, and I always have to delete an extra `@detailmenu' in the main file (`scantest.texi') by hand. I can't tell you how many years I've been seeing that bug. Reported it many times. I don't know if it'll be fixed in the next release of Emacs or not. It works with `texi2dvi', but `makeinfo' fails: c:\Scantest\DOC\TEXINFO//parser.texi:235: Unknown command `'. I'll look into that. Thanks, Karl From MAILER-DAEMON Fri Jan 26 02:37:44 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HALea-0000oO-Dm for mharc-help-texinfo@gnu.org; Fri, 26 Jan 2007 02:37:44 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HALeY-0000o1-4b for help-texinfo@gnu.org; Fri, 26 Jan 2007 02:37:42 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HALeX-0000np-D2 for help-texinfo@gnu.org; Fri, 26 Jan 2007 02:37:41 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HALeX-0000nm-5J for help-texinfo@gnu.org; Fri, 26 Jan 2007 02:37:41 -0500 Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HALeW-000776-NW for help-texinfo@gnu.org; Fri, 26 Jan 2007 02:37:40 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HALeJ-0007EV-2h for help-texinfo@gnu.org; Fri, 26 Jan 2007 08:37:27 +0100 Received: from 219.142.180.120 ([219.142.180.120]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 26 Jan 2007 08:37:27 +0100 Received: from william.xwl by 219.142.180.120 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 26 Jan 2007 08:37:27 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: help-texinfo@gnu.org From: William Xu Date: Fri, 26 Jan 2007 15:37:34 +0800 Organization: the Church of Emacs Lines: 38 Message-ID: <87sldydyrl.fsf@www.williamxu.com> References: <87bqkyutov.fsf@www.williamxu.com> <200701250046.l0P0ke010090@f7.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 219.142.180.120 User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.92 (gnu/linux) Cancel-Lock: sha1:q7RqM3oV4jHtf85WK1DORrAas4g= Sender: news X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) Subject: [help-texinfo] Re: does texinfo supports utf8 now? X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 07:37:42 -0000 karl@freefriends.org (Karl Berry) writes: > I believe this bug is fixed in CVS. In 4.8 and earlier, character 0xa0 > turned into a regular space (0x20). That's no longer the case (thanks > to Miloslav). > > I don't know when the next release will be, but if you need the fix > urgently, I guess you could use the CVS version. Thanks a lot ! The CVS version works fine. (I was using 4.8.dfsg.1-4, in debian unstable) There's one little problem during `make install' though, ,---- | ... | Making install in po | make[1]: Entering directory `/home/william/studio/cvs/texinfo/po' | /bin/sh @MKINSTALLDIRS@ /home/william/share | /bin/sh: @MKINSTALLDIRS@: No such file or directory | make[1]: *** [install-data-yes] Error 127 | make[1]: Leaving directory `/home/william/studio/cvs/texinfo/po' | make: *** [install-recursive] Error 1 `---- -- William "The fundamental purpose animating the Faith of God and His Religion is to safeguard the interests and promote the unity of the human race, and to foster the spirit of love and fellowship amongst men. Suffer it not to become a source of dissension and discord, of hate and enmity." "Religion is verily the chief instrument for the establishment of order in the world and of tranquillity amongst it's peoples...The greater the decline of religion, the more grievous the waywardness of the ungodly. This cannot but lead in the end to chaos and confusion." -- Baha'u'llah, a selection from the Baha'i scripture From MAILER-DAEMON Fri Jan 26 03:29:02 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HAMSE-00038n-JE for mharc-help-texinfo@gnu.org; Fri, 26 Jan 2007 03:29:02 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HAMSC-00037U-JT for help-texinfo@gnu.org; Fri, 26 Jan 2007 03:29:00 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HAMSB-00036z-4b for help-texinfo@gnu.org; Fri, 26 Jan 2007 03:29:00 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HAMSA-00036t-SC for help-texinfo@gnu.org; Fri, 26 Jan 2007 03:28:58 -0500 Received: from tmailer.gwdg.de ([134.76.10.23]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HAMSA-0006PG-A4 for help-texinfo@gnu.org; Fri, 26 Jan 2007 03:28:58 -0500 Received: from mailbox.gwdg.de ([134.76.10.21] helo=web-mailer.gwdg.de) by mailer.gwdg.de with esmtp (Exim 4.63) (envelope-from ) id 1HAMS7-0007rR-FT; Fri, 26 Jan 2007 09:28:55 +0100 X-Xeceived: from 134.76.244.101 (SquirrelMail authenticated user lfinsto1) by web-mailer.gwdg.de with HTTP; Fri, 26 Jan 2007 09:28:55 +0100 (CET) Message-ID: <1470.134.76.244.101.1169800135.squirrel@web-mailer.gwdg.de> In-Reply-To: <200701251936.l0PJaEU29547@f7.net> References: <200701251936.l0PJaEU29547@f7.net> Date: Fri, 26 Jan 2007 09:28:55 +0100 (CET) Subject: Re: [help-texinfo] Formatting parser symbols and rules From: lfinsto1@gwdg.de To: "Karl Berry" User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: (clean) by exiscan+sophie X-detected-kernel: Linux 2.4-2.6 Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 08:29:00 -0000 > Declarations like `char c[]' > > I am completely baffled. @var is meant for metasyntactic variables, > like nonterminals in parser rules. That's it. Sorry, incorrect example. I use `@var' for the arguments to functions, as stated in the manual, e.g., `@deftypefn {Function} int main (@code{int} @code{argc}, @code{char*} @var{argv[]})', and not for normal declarations. I don't otherwise use the "empty bracket" syntax. It's hardly reasonable to expect Texinfo to handle the more arcane aspects of C syntax automatically, anyway. I tried `@var{argv@slanted{}}', but it didn't work. In the TeX output, it had no effect, and `makeinfo' failed: c:\Scantest\DOC\TEXINFO//glblfncs.texi:41: Unknown command `slanted'. It's probably an outdated `makeinfo': makeinfo (GNU texinfo) 4.7 It's from MikTeX, but I have a similar problem on the GNU/Linux machine I use. By the way, just noticed a typo in the manual: @slanted rselects a slanted font; > If you use etex instead of tex, I believe macros won't require the > auxiliary file. (There's no other way to get the catcodes right in > original TeX.) > I suppose this involves setting an environment variable or doing something similar, so that `texi2dvi' calls `etex'? I won't do this, because I'd still have to make sure it works with TeX for the sake of the distribution. I'd rather not add another prerequisite for building. It doesn't bother me that much. > Yes, with the `Top', `Up', and `Next' references inserted by Emacs' > `texinfo-multiple-files-update', e.g., > > My advice is, don't use those. Use implicit pointers instead (so the > @node lines just have the node name). Much simpler. Assuming a > "normal" hierarchical manual. > Just looked this up. I didn't know about this feature. Will give it a try. Thanks, Laurence From MAILER-DAEMON Fri Jan 26 03:34:40 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HAMXg-0005Hj-KP for mharc-help-texinfo@gnu.org; Fri, 26 Jan 2007 03:34:40 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HAMXe-0005HL-Jb for help-texinfo@gnu.org; Fri, 26 Jan 2007 03:34:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HAMXd-0005H3-3J for help-texinfo@gnu.org; Fri, 26 Jan 2007 03:34:38 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HAMXd-0005H0-1a for help-texinfo@gnu.org; Fri, 26 Jan 2007 03:34:37 -0500 Received: from romy.inter.net.il ([213.8.233.24]) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HAMXc-00070x-HO for help-texinfo@gnu.org; Fri, 26 Jan 2007 03:34:36 -0500 Received: from HOME-C4E4A596F7 (IGLD-80-230-36-219.inter.net.il [80.230.36.219]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id GYT55386 (AUTH halo1); Fri, 26 Jan 2007 10:34:37 +0200 (IST) Date: Fri, 26 Jan 2007 10:34:40 +0200 Message-Id: From: Eli Zaretskii To: lfinsto1@gwdg.de In-reply-to: <1491.134.76.244.101.1169714107.squirrel@web-mailer.gwdg.de> (lfinsto1@gwdg.de) Subject: Re: [help-texinfo] Formatting parser symbols and rules References: <200701241946.l0OJkDF01673@f7.net> <1491.134.76.244.101.1169714107.squirrel@web-mailer.gwdg.de> X-detected-kernel: FreeBSD 4.7-5.2 (or MacOS X 10.2-10.4) (2) Cc: help-texinfo@gnu.org, karl@freefriends.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eli Zaretskii List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 08:34:39 -0000 > Date: Thu, 25 Jan 2007 09:35:07 +0100 (CET) > From: lfinsto1@gwdg.de > Cc: help-texinfo@gnu.org > > > tokens (`@ptindex') and one for non-teminals (`@pnindex') and add the > > entries by hand, so the entries in the Variable Index are redundant. > > > > Maybe redirect the vr index to pn, then, and omit the explicit pn entries. > > That wouldn't work, because there are many other variables that need to go > in the variable index. I'd like to keep the parser symbols separate to > reduce clutter. You can always do that by adding context to index entry's text. For example: @vindex foobar@r{, parser symbol} > > I highly recommend redirecting all indexes into one in the end, anyway. > > > > Oh, well we obviously disagree on this point. I agree with Karl, FWIW: indices are primarily for finding information easily. WHile in the on-line Info file this normally doesn't matter (since the info-searching commands of Info readers look in all indices), it does matter in the printed output and in HTML, since there the reader will have too look up stuff in several disjoint lists. That's a pain, IMO. Can you tell why you prefer separate indices? > `@var' puts the text in a slanted font in the TeX output, except for `[]' > in `@var{argv[]}', as I've determined. I suppose it wasn't meant to be > used this way @var is not meant to be used for literal symbol names, only for metasyntactical variables, i.e. for symbols that stand for something else. If you just want slanted font, use @i or @emph instead. > Declarations like `char c[]' are awkward to format, anyway, since > `@code{char} @var{c[]}' would seem to make the brackets part of the > variable rather than the type. Why on Earth would you want to use something like `@code{char} @var{c[]}'? Can you tell what would you like to achieve? (Sorry if this was already explained in this thread before I chimed in.) > In addition, `@var{argv[]}' causes `makeinfo' without `--html' to issue > the following (annoying) warnings: > > c:\Scantest\DOC\TEXINFO//glblfncs.texi:41: warning: unlikely character [ > in @var. > c:\Scantest\DOC\TEXINFO//glblfncs.texi:41: warning: unlikely character ] > in @var See above: you are using @var for a situation it wasn't supposed to handle. From MAILER-DAEMON Fri Jan 26 04:10:57 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HAN6n-0001uo-9F for mharc-help-texinfo@gnu.org; Fri, 26 Jan 2007 04:10:57 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HAN6l-0001uc-K1 for help-texinfo@gnu.org; Fri, 26 Jan 2007 04:10:55 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HAN6j-0001uP-Tj for help-texinfo@gnu.org; Fri, 26 Jan 2007 04:10:55 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HAN6j-0001uM-P6 for help-texinfo@gnu.org; Fri, 26 Jan 2007 04:10:53 -0500 Received: from tmailer.gwdg.de ([134.76.10.23]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HAN6g-0003m3-0Q; Fri, 26 Jan 2007 04:10:50 -0500 Received: from mailbox.gwdg.de ([134.76.10.21] helo=web-mailer.gwdg.de) by mailer.gwdg.de with esmtp (Exim 4.63) (envelope-from ) id 1HAN6c-0005g2-TQ; Fri, 26 Jan 2007 10:10:46 +0100 X-Xeceived: from 134.76.244.101 (SquirrelMail authenticated user lfinsto1) by web-mailer.gwdg.de with HTTP; Fri, 26 Jan 2007 10:10:46 +0100 (CET) Message-ID: <1597.134.76.244.101.1169802646.squirrel@web-mailer.gwdg.de> In-Reply-To: References: <200701241946.l0OJkDF01673@f7.net> <1491.134.76.244.101.1169714107.squirrel@web-mailer.gwdg.de> Date: Fri, 26 Jan 2007 10:10:46 +0100 (CET) Subject: Re: [help-texinfo] Formatting parser symbols and rules From: lfinsto1@gwdg.de To: "Eli Zaretskii" User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: (clean) by exiscan+sophie X-detected-kernel: Linux 2.4-2.6 Cc: help-texinfo@gnu.org, karl@freefriends.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 09:10:55 -0000 >> That wouldn't work, because there are many other variables that need to >> go >> in the variable index. I'd like to keep the parser symbols separate to >> reduce clutter. > > You can always do that by adding context to index entry's text. For > example: > > @vindex foobar@r{, parser symbol} > Thanks, but the problem is the entries that are automatically created by the `@deftypevr' commands. >> > I highly recommend redirecting all indexes into one in the end, >> anyway. >> > >> >> Oh, well we obviously disagree on this point. > > I agree with Karl, FWIW: indices are primarily for finding information > easily. WHile in the on-line Info file this normally doesn't matter > (since the info-searching commands of Info readers look in all > indices), it does matter in the printed output and in HTML, since > there the reader will have too look up stuff in several disjoint > lists. That's a pain, IMO. > I'm not saying that you and Karl are wrong; there are just different approaches to indexing. I'm not sure whether an alphabetical listing of parser rules is really useful. Even if I decide that it is, I think an appendix would be more useful than an index. I do know how to get this to work using `\write' commands, an auxiliary program, and a second pass, but just using the index feature is much simpler. > Can you tell why you prefer separate indices? I think it's easier for people to find the information they want if it's sorted into categories. In German books, for example, it's common for a book to have two indices; one for names of persons, and the other for names of things. A (fairly) recent change to the GNU Coding Standards specifies that function names should not be formatted as, e.g., `foo()' but rather as `foo'. I'm happy to go along with this, but it does make it hard to distinguish functions from variables. One could have a single index with entries like `foo (function), bar (variable)' or separate ones for variables and functions. However, the formatting in the former case isn't done automatically by the `@def' commands, and many people probably wouldn't want this. If a combined index were useful, it would possible to create one by duplicating all of the entries "by hand". I don't find it to be that much trouble to add `@xxindex' commands, although they do clutter up the input files. > >> `@var' puts the text in a slanted font in the TeX output, except for >> `[]' >> in `@var{argv[]}', as I've determined. I suppose it wasn't meant to be >> used this way > > @var is not meant to be used for literal symbol names, only for > metasyntactical variables, i.e. for symbols that stand for something > else. Answered in previous email, which crossed yours. > > If you just want slanted font, use @i or @emph instead. > >> Declarations like `char c[]' are awkward to format, anyway, since >> `@code{char} @var{c[]}' would seem to make the brackets part of the >> variable rather than the type. > > Why on Earth would you want to use something like `@code{char} @var{c[]}'? > Only in the case of function declarations. I have determined that an ordinary declaration like this fails inside a function, and causes a warning to be issued outside of a function, when using GCC under Windows: "ttemp.c:4: warning: array 'c' assumed to have one element" >> In addition, `@var{argv[]}' causes `makeinfo' without `--html' to issue >> the following (annoying) warnings: >> >> c:\Scantest\DOC\TEXINFO//glblfncs.texi:41: warning: unlikely character [ >> in @var. >> c:\Scantest\DOC\TEXINFO//glblfncs.texi:41: warning: unlikely character ] >> in @var > > See above: you are using @var for a situation it wasn't supposed to > handle. > It is meant to be used for arguments in function declarations. It is, of course, arguable, that the brackets properly belong to the type rather than the name, but that's perhaps being too pedantic. My guess is that math mode is used for the brackets, anyway, since neither `@slanted' nor `@i' causes slanted brackets to be used. If I get ambitious, I might try to do something about this problem. Otherwise, my inclination is to file it under "slightly annoying, but not worth bothering about". Thanks, Laurence From MAILER-DAEMON Fri Jan 26 04:38:04 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HANX1-0002nl-0R for mharc-help-texinfo@gnu.org; Fri, 26 Jan 2007 04:38:03 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HANWy-0002nX-Ov for help-texinfo@gnu.org; Fri, 26 Jan 2007 04:38:00 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HANWw-0002nL-2j for help-texinfo@gnu.org; Fri, 26 Jan 2007 04:38:00 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HANWv-0002nI-VM for help-texinfo@gnu.org; Fri, 26 Jan 2007 04:37:58 -0500 Received: from tmailer.gwdg.de ([134.76.10.23]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HANWv-0008IR-BW for help-texinfo@gnu.org; Fri, 26 Jan 2007 04:37:57 -0500 Received: from mailbox.gwdg.de ([134.76.10.21] helo=web-mailer.gwdg.de) by mailer.gwdg.de with esmtp (Exim 4.63) (envelope-from ) id 1HANWs-0007K7-VO; Fri, 26 Jan 2007 10:37:55 +0100 X-Xeceived: from 134.76.244.101 (SquirrelMail authenticated user lfinsto1) by web-mailer.gwdg.de with HTTP; Fri, 26 Jan 2007 10:37:54 +0100 (CET) Message-ID: <1693.134.76.244.101.1169804274.squirrel@web-mailer.gwdg.de> In-Reply-To: <1470.134.76.244.101.1169800135.squirrel@web-mailer.gwdg.de> References: <200701251936.l0PJaEU29547@f7.net> <1470.134.76.244.101.1169800135.squirrel@web-mailer.gwdg.de> Date: Fri, 26 Jan 2007 10:37:54 +0100 (CET) Subject: Re: [help-texinfo] Formatting parser symbols and rules From: lfinsto1@gwdg.de To: lfinsto1@gwdg.de User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: (clean) by exiscan+sophie X-detected-kernel: Linux 2.4-2.6 Cc: help-texinfo@gnu.org, Karl Berry X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 09:38:01 -0000 >> >> My advice is, don't use those. Use implicit pointers instead (so the >> @node lines just have the node name). Much simpler. Assuming a >> "normal" hierarchical manual. >> > > Just looked this up. I didn't know about this feature. Will give it a > try. > I've just tried this, and it works fine. However, I reviewed Emacs' `texinfo-' updating commands, and, unless I'm missing something, it seems that there is no way to update all of the menus in all of the files without also updating the nodes. Laurence From MAILER-DAEMON Fri Jan 26 18:33:26 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HAaZS-0005jN-4b for mharc-help-texinfo@gnu.org; Fri, 26 Jan 2007 18:33:26 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HAaZQ-0005jI-CI for help-texinfo@gnu.org; Fri, 26 Jan 2007 18:33:24 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HAaZO-0005j6-PN for help-texinfo@gnu.org; Fri, 26 Jan 2007 18:33:23 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HAaZO-0005j3-J9 for help-texinfo@gnu.org; Fri, 26 Jan 2007 18:33:22 -0500 Received: from server1.f7.net ([64.34.169.74] helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HAaZO-0003yH-94 for help-texinfo@gnu.org; Fri, 26 Jan 2007 18:33:22 -0500 X-Envelope-From: karl@freefriends.org X-Envelope-To: help-texinfo@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l0QNXET21776; Fri, 26 Jan 2007 17:33:14 -0600 Date: Fri, 26 Jan 2007 17:33:14 -0600 Message-Id: <200701262333.l0QNXET21776@f7.net> From: karl@freefriends.org (Karl Berry) To: lfinsto1@gwdg.de Subject: Re: [help-texinfo] Formatting parser symbols and rules In-Reply-To: <1693.134.76.244.101.1169804274.squirrel@web-mailer.gwdg.de> X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 23:33:24 -0000 that there is no way to update all of the menus in all of the files without also updating the nodes. I think you're right, unless I'm missing it too. You can update just the master menu, but not all menus. It seems like it would be trivial to change texinfo-multiple-files-update to support just updating menus (if it isn't already in the development code). It should be supported, since "no node pointers" is the recommended usage. Unfortunately the Emacs folks are trying to get a release out, so I doubt this is a good time to bring it up. (Eli?) Personally, I find that once a document is relatively stable (I know yours isn't), it's no big deal to update the menus by hand, and that's what I do. Another option is to just have one source file (which you probably also don't want to do, but thought I'd mention it anyway). Best, k From MAILER-DAEMON Sat Jan 27 03:29:33 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HAiwH-0002zY-Lp for mharc-help-texinfo@gnu.org; Sat, 27 Jan 2007 03:29:33 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HAiwF-0002yv-1a for help-texinfo@gnu.org; Sat, 27 Jan 2007 03:29:31 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HAiwD-0002yZ-IT for help-texinfo@gnu.org; Sat, 27 Jan 2007 03:29:30 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HAiwD-0002yW-Df for help-texinfo@gnu.org; Sat, 27 Jan 2007 03:29:29 -0500 Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HAiwD-00080z-1E for help-texinfo@gnu.org; Sat, 27 Jan 2007 03:29:29 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HAiwA-0000V6-1m for help-texinfo@gnu.org; Sat, 27 Jan 2007 09:29:26 +0100 Received: from 219.142.180.120 ([219.142.180.120]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 27 Jan 2007 09:29:26 +0100 Received: from william.xwl by 219.142.180.120 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 27 Jan 2007 09:29:26 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: help-texinfo@gnu.org From: William Xu Date: Sat, 27 Jan 2007 16:29:37 +0800 Organization: the Church of Emacs Lines: 24 Message-ID: <87odokeutq.fsf@www.williamxu.com> References: <87bqkyutov.fsf@www.williamxu.com> <200701250046.l0P0ke010090@f7.net> <87sldydyrl.fsf@www.williamxu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 219.142.180.120 User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.92 (gnu/linux) Cancel-Lock: sha1:hIWmYfxPH4naW/VgWbNXfdWUEMc= Sender: news X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) Subject: [help-texinfo] Re: does texinfo supports utf8 now? X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 08:29:31 -0000 William Xu writes: > karl@freefriends.org (Karl Berry) writes: > >> I believe this bug is fixed in CVS. In 4.8 and earlier, character 0xa0 >> turned into a regular space (0x20). That's no longer the case (thanks >> to Miloslav). >> >> I don't know when the next release will be, but if you need the fix >> urgently, I guess you could use the CVS version. > > Thanks a lot ! The CVS version works fine. (I was using 4.8.dfsg.1-4, in > debian unstable) [...] ps. It seems the alignment is messed up with utf8 encoded text. Apparently it doesn't work according to `--fill-column=NUM' value... -- William Why would anyone want to be called "Later"? From MAILER-DAEMON Sat Jan 27 05:38:09 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HAkwj-00037q-Le for mharc-help-texinfo@gnu.org; Sat, 27 Jan 2007 05:38:09 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HAkwh-00037b-Ji for help-texinfo@gnu.org; Sat, 27 Jan 2007 05:38:07 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HAkwh-00037N-4r for help-texinfo@gnu.org; Sat, 27 Jan 2007 05:38:07 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HAkwg-00037K-TE for help-texinfo@gnu.org; Sat, 27 Jan 2007 05:38:06 -0500 Received: from nitzan.inter.net.il ([213.8.233.22]) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HAkwg-0007AD-F5 for help-texinfo@gnu.org; Sat, 27 Jan 2007 05:38:06 -0500 Received: from HOME-C4E4A596F7 (IGLD-80-230-247-172.inter.net.il [80.230.247.172]) by nitzan.inter.net.il (MOS 3.7.3a-GA) with ESMTP id FWY02664 (AUTH halo1); Sat, 27 Jan 2007 12:38:00 +0200 (IST) Date: Sat, 27 Jan 2007 12:38:12 +0200 Message-Id: From: Eli Zaretskii To: karl@freefriends.org (Karl Berry) In-reply-to: <200701262333.l0QNXET21776@f7.net> (karl@freefriends.org) Subject: Re: [help-texinfo] Formatting parser symbols and rules References: <200701262333.l0QNXET21776@f7.net> X-detected-kernel: FreeBSD 4.7-5.2 (or MacOS X 10.2-10.4) (2) Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eli Zaretskii List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 10:38:07 -0000 > Date: Fri, 26 Jan 2007 17:33:14 -0600 > From: karl@freefriends.org (Karl Berry) > Cc: help-texinfo@gnu.org > > I think you're right, unless I'm missing it too. You can update just > the master menu, but not all menus. It seems like it would be trivial > to change texinfo-multiple-files-update to support just updating menus > (if it isn't already in the development code). It should be supported, > since "no node pointers" is the recommended usage. Unfortunately the > Emacs folks are trying to get a release out, so I doubt this is a good > time to bring it up. (Eli?) Yes, it would be better to wait until after the release. From MAILER-DAEMON Sat Jan 27 07:29:39 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HAmgd-0007Cd-96 for mharc-help-texinfo@gnu.org; Sat, 27 Jan 2007 07:29:39 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HAmgb-0007CB-9m for help-texinfo@gnu.org; Sat, 27 Jan 2007 07:29:37 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HAmgX-0007BZ-O6 for help-texinfo@gnu.org; Sat, 27 Jan 2007 07:29:37 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HAmgX-0007BI-If for help-texinfo@gnu.org; Sat, 27 Jan 2007 07:29:33 -0500 Received: from server1.f7.net ([64.34.169.74] helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HAmgV-0004k3-Gr; Sat, 27 Jan 2007 07:29:31 -0500 X-Envelope-From: karl@freefriends.org X-Envelope-To: eliz@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l0RCTN620308; Sat, 27 Jan 2007 06:29:23 -0600 Date: Sat, 27 Jan 2007 06:29:23 -0600 Message-Id: <200701271229.l0RCTN620308@f7.net> From: karl@freefriends.org (Karl Berry) To: lfinsto1@gwdg.de Subject: Re: [help-texinfo] Formatting parser symbols and rules In-Reply-To: <1597.134.76.244.101.1169802646.squirrel@web-mailer.gwdg.de> X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 12:29:37 -0000 math mode is used for the brackets, anyway, since neither `@slanted' nor `@i' causes slanted brackets to be used. texinfo.tex goes to a lot of trouble to keep the brackets upright. Doesn't use math mode, actually, but whatever ... From MAILER-DAEMON Sat Jan 27 07:29:39 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HAmgd-0007Cv-IU for mharc-help-texinfo@gnu.org; Sat, 27 Jan 2007 07:29:39 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HAmgb-0007CH-H8 for help-texinfo@gnu.org; Sat, 27 Jan 2007 07:29:37 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HAmgW-00078t-4l for help-texinfo@gnu.org; Sat, 27 Jan 2007 07:29:36 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HAmgV-00078p-Tz for help-texinfo@gnu.org; Sat, 27 Jan 2007 07:29:31 -0500 Received: from server1.f7.net ([64.34.169.74] helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HAmgV-0004k5-Fg for help-texinfo@gnu.org; Sat, 27 Jan 2007 07:29:31 -0500 X-Envelope-From: karl@freefriends.org X-Envelope-To: help-texinfo@gnu.org Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id l0RCTNl20322; Sat, 27 Jan 2007 06:29:23 -0600 Date: Sat, 27 Jan 2007 06:29:23 -0600 Message-Id: <200701271229.l0RCTNl20322@f7.net> From: karl@freefriends.org (Karl Berry) To: lfinsto1@gwdg.de Subject: Re: [help-texinfo] Formatting parser symbols and rules In-Reply-To: <1470.134.76.244.101.1169800135.squirrel@web-mailer.gwdg.de> X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 12:29:37 -0000 @slanted rselects a slanted font; Thanks, I guess this was fixed somewhere along the line, it's not in CVS. I suppose this involves setting an environment variable or doing something similar, so that `texi2dvi' calls `etex'? If etex is present, it's used automatically. I'd rather not add another prerequisite for building. Every TeX distribution for years has had etex. I'm quite surprised yours doesn't. From MAILER-DAEMON Sat Jan 27 08:44:59 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HAnrX-0005Nc-Az for mharc-help-texinfo@gnu.org; Sat, 27 Jan 2007 08:44:59 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HAnrV-0005NA-9C for help-texinfo@gnu.org; Sat, 27 Jan 2007 08:44:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HAnrT-0005My-QV for help-texinfo@gnu.org; Sat, 27 Jan 2007 08:44:56 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HAnrT-0005Mv-LM for help-texinfo@gnu.org; Sat, 27 Jan 2007 08:44:55 -0500 Received: from tmailer.gwdg.de ([134.76.10.23]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HAnrT-0007wD-1I for help-texinfo@gnu.org; Sat, 27 Jan 2007 08:44:55 -0500 Received: from mailbox.gwdg.de ([134.76.10.21] helo=web-mailer.gwdg.de) by mailer.gwdg.de with esmtp (Exim 4.63) (envelope-from ) id 1HAnrP-0002oj-8g; Sat, 27 Jan 2007 14:44:51 +0100 X-Xeceived: from 134.76.244.101 (SquirrelMail authenticated user lfinsto1) by web-mailer.gwdg.de with HTTP; Sat, 27 Jan 2007 14:44:51 +0100 (CET) Message-ID: <1391.134.76.244.101.1169905491.squirrel@web-mailer.gwdg.de> In-Reply-To: <200701262333.l0QNXET21776@f7.net> References: <200701262333.l0QNXET21776@f7.net> Date: Sat, 27 Jan 2007 14:44:51 +0100 (CET) Subject: Re: [help-texinfo] Formatting parser symbols and rules From: lfinsto1@gwdg.de To: "Karl Berry" User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: (clean) by exiscan+sophie X-detected-kernel: Linux 2.4-2.6 Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 13:44:57 -0000 > > Personally, I find that once a document is relatively stable (I know > yours isn't), it's no big deal to update the menus by hand, and that's > what I do. It seems there are various ways of going about it. I don't think it would be that much trouble to use the relevant Emacs function to update the menus in a buffer after I've edited it, and then update the master menu in the main file. I've never taken a close look at the menus to see what they contain exactly. I'm not that bothered by the very long lines. I just thought it would be nice to have a way of continuing lines that would work in all "environments". > Another option is to just have one source file (which you > probably also don't want to do, but thought I'd mention it anyway). No, that would already be an unmanageably large file. A few kludges is a small price to pay. Laurence From MAILER-DAEMON Sat Jan 27 08:58:35 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HAo4h-0001aP-8h for mharc-help-texinfo@gnu.org; Sat, 27 Jan 2007 08:58:35 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HAo4f-0001Ye-R0 for help-texinfo@gnu.org; Sat, 27 Jan 2007 08:58:33 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HAo4e-0001YS-7m for help-texinfo@gnu.org; Sat, 27 Jan 2007 08:58:32 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HAo4e-0001Y4-2X for help-texinfo@gnu.org; Sat, 27 Jan 2007 08:58:32 -0500 Received: from tmailer.gwdg.de ([134.76.10.23]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HAo4b-0001QB-Dz; Sat, 27 Jan 2007 08:58:29 -0500 Received: from mailbox.gwdg.de ([134.76.10.21] helo=web-mailer.gwdg.de) by mailer.gwdg.de with esmtp (Exim 4.63) (envelope-from ) id 1HAo4Z-0006Sn-7J; Sat, 27 Jan 2007 14:58:27 +0100 X-Xeceived: from 134.76.244.101 (SquirrelMail authenticated user lfinsto1) by web-mailer.gwdg.de with HTTP; Sat, 27 Jan 2007 14:58:27 +0100 (CET) Message-ID: <1408.134.76.244.101.1169906307.squirrel@web-mailer.gwdg.de> In-Reply-To: <200701271229.l0RCTN620308@f7.net> References: <200701271229.l0RCTN620308@f7.net> Date: Sat, 27 Jan 2007 14:58:27 +0100 (CET) Subject: Re: [help-texinfo] Formatting parser symbols and rules From: lfinsto1@gwdg.de To: "Karl Berry" User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: (clean) by exiscan+sophie X-detected-kernel: Linux 2.4-2.6 Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 13:58:33 -0000 > math mode is used for the brackets, anyway, since neither `@slanted' > nor > `@i' causes slanted brackets to be used. > > texinfo.tex goes to a lot of trouble to keep the brackets upright. > Doesn't use math mode, actually, but whatever ... > It occurred to me once away from the computer that it could just be the characters `x' and `y' from font `z', but I suppose I could find the "secret" by looking at the source code. For `main' under GNU/Linux, I might as well just use `char**'. I've determined that the `_tmain' function generated by MS Visual Studio also uses the `[]' syntax, and it's not a good idea to fiddle with code generated by VS. However, for other reasons, I'm quite likely to be removing all Windows code soon, so it's a moot point. The correct formatting of `char* argv[]' and similar constructions may be on-topic for this mailing list, but it's probably not that important in the larger scheme of things. I got rid of the warnings by taking the brakets out of the `@var{}'. The visual result is the same, and I don't know whether getting slanted braces will be possible inside `@deftypefn'. I did think that it might be worthwhile trying to format this manual in such a way that it could serve as a model for other Texinfo manuals that document parsers. However, I doubt that there are going to be that many, so it may not really be worth discussing in great detail. Thanks, Laurence From MAILER-DAEMON Sat Jan 27 09:04:55 2007 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HAoAp-00048k-AQ for mharc-help-texinfo@gnu.org; Sat, 27 Jan 2007 09:04:55 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HAoAn-00046f-7D for help-texinfo@gnu.org; Sat, 27 Jan 2007 09:04:53 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HAoAl-00043x-BK for help-texinfo@gnu.org; Sat, 27 Jan 2007 09:04:52 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HAoAl-00043o-1k for help-texinfo@gnu.org; Sat, 27 Jan 2007 09:04:51 -0500 Received: from tmailer.gwdg.de ([134.76.10.23]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HAoAk-0002GN-CJ for help-texinfo@gnu.org; Sat, 27 Jan 2007 09:04:50 -0500 Received: from mailbox.gwdg.de ([134.76.10.21] helo=web-mailer.gwdg.de) by mailer.gwdg.de with esmtp (Exim 4.63) (envelope-from ) id 1HAoAi-0008C8-6c; Sat, 27 Jan 2007 15:04:48 +0100 X-Xeceived: from 134.76.244.101 (SquirrelMail authenticated user lfinsto1) by web-mailer.gwdg.de with HTTP; Sat, 27 Jan 2007 15:04:48 +0100 (CET) Message-ID: <1422.134.76.244.101.1169906688.squirrel@web-mailer.gwdg.de> In-Reply-To: <200701271229.l0RCTNl20322@f7.net> References: <200701271229.l0RCTNl20322@f7.net> Date: Sat, 27 Jan 2007 15:04:48 +0100 (CET) Subject: Re: [help-texinfo] Formatting parser symbols and rules From: lfinsto1@gwdg.de To: "Karl Berry" User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: (clean) by exiscan+sophie X-detected-kernel: Linux 2.4-2.6 Cc: help-texinfo@gnu.org X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 14:04:53 -0000 > > If etex is present, it's used automatically. > It's present, but `texi2dvi' uses `tex'. > I'd rather not add another prerequisite for building. > > Every TeX distribution for years has had etex. I'm quite surprised > yours doesn't. I don't know why `texi2dvi' is calling `tex' and not `e-tex'. As long as it doesn't cause any problems, I'm willing to put up with the many lines of `(./scantest.tmp)' on my screen. Thanks, Laurence