Mercurial > web-octave
changeset 43:a1cb50997055
Reviewed and reformatted some files.
| author | Kai T. Ohlhus <k.ohlhus@gmail.com> |
|---|---|
| date | Wed, 31 Aug 2016 01:08:06 +0200 |
| parents | ecee119c2378 |
| children | dbc6628a3c05 |
| files | about.md bugs.md contribute.md examples.md support.md |
| diffstat | 5 files changed, 281 insertions(+), 75 deletions(-) [+] |
line wrap: on
line diff
--- a/about.md Sun Aug 28 23:18:12 2016 +0200 +++ b/about.md Wed Aug 31 01:08:06 2016 +0200 @@ -5,24 +5,83 @@ menu: true --- -GNU Octave is a high-level language, primarily intended for numerical computations. It provides a convenient command line interface for solving linear and nonlinear problems numerically, and for performing other numerical experiments using a language that is mostly compatible with Matlab. It may also be used as a batch-oriented language. - -Octave has extensive tools for solving common numerical linear algebra problems, finding the roots of nonlinear equations, integrating ordinary functions, manipulating polynomials, and integrating ordinary differential and differential-algebraic equations. It is easily extensible and customizable via user-defined functions written in Octave's own language, or using dynamically loaded modules written in C++, C, Fortran, or other languages. +GNU Octave is a high-level language, +primarily intended for numerical computations. +It provides a convenient command line interface +for solving linear and nonlinear problems numerically, +and for performing other numerical experiments +using a language that is mostly compatible with Matlab. +It may also be used as a batch-oriented language. -GNU Octave is also freely redistributable software. You may redistribute it and/or modify it under the terms of the GNU General Public License (GPL) as published by the Free Software Foundation. +Octave has extensive tools for solving common numerical linear algebra problems, +finding the roots of nonlinear equations, integrating ordinary functions, +manipulating polynomials, and integrating ordinary differential +and differential-algebraic equations. +It is easily extensible and customizable via user-defined functions +written in Octave's own language, +or using dynamically loaded modules written in C++, C, Fortran, +or other languages. -Octave was written by John W. Eaton and many others. Because Octave is free software you are encouraged to help make Octave more useful by writing and contributing additional functions for it, and by reporting any problems you may have. +GNU Octave is also freely redistributable software. +You may redistribute it and/or modify it under the terms of the +GNU General Public License (GPL) as published by the Free Software Foundation. + +Octave was written by John W. Eaton and many others. +Because Octave is free software you are encouraged +to help make Octave more useful by writing +and contributing additional functions for it, +and by reporting any problems you may have. + ### History -Octave was originally conceived (in about 1988) to be companion software for an undergraduate-level textbook on chemical reactor design being written by James B. Rawlings of the University of Wisconsin-Madison and John G. Ekerdt of the University of Texas. We originally envisioned some very specialized tools for the solution of chemical reactor design problems. Later, after seeing the limitations of that approach, we opted to attempt to build a much more flexible tool. +Octave was originally conceived (in about 1988) to be companion software +for an undergraduate-level textbook on chemical reactor design +being written by James B. Rawlings of the University of Wisconsin-Madison +and John G. Ekerdt of the University of Texas. +We originally envisioned some very specialized tools for the solution +of chemical reactor design problems. +Later, after seeing the limitations of that approach, +we opted to attempt to build a much more flexible tool. -There were still some people who said that we should just be using Fortran instead, because it is the computer language of engineering, but every time we had tried that, the students spent far too much time trying to figure out why their Fortran code failed and not enough time learning about chemical engineering. We believed that with an interactive environment like Octave, most students would be able to pick up the basics quickly, and begin using it confidently in just a few hours. - -Full-time development began in the Spring of 1992. The first alpha release was January 4, 1993, and version 1.0 was released February 17, 1994. Since then, Octave has been through several major revisions, is included with Debian GNU/Linux and SuSE Linux distributions, and was reviewed in the in the July, 1997 issue of the Linux Journal. +There were still some people who said +that we should just be using Fortran instead, +because it is the computer language of engineering, +but every time we had tried that, +the students spent far too much time trying to figure out +why their Fortran code failed +and not enough time learning about chemical engineering. +We believed that with an interactive environment like Octave, +most students would be able to pick up the basics quickly, +and begin using it confidently in just a few hours. -Clearly, Octave is now much more than just another courseware package with limited utility beyond the classroom. Although our initial goals were somewhat vague, we knew that we wanted to create something that would enable students to solve realistic problems, and that they could use for many things other than chemical reactor design problems. Today, thousands of people worldwide are using Octave in teaching, research, and commercial applications. +Full-time development began in the Spring of 1992. +The first alpha release was January 4, 1993, +and version 1.0 was released February 17, 1994. +Since then, Octave has been through several major revisions, +is included with Debian GNU/Linux and SuSE Linux distributions, +and was reviewed in the in the July, 1997 issue of the Linux Journal. -Just about everyone thinks that the name Octave has something to do with music, but it is actually the name of one of the author's former professors who wrote a famous textbook on chemical reaction engineering, and who was also well known for his ability to do quick "back of the envelope" calculations. We hope that this software will make it possible for many people to do more ambitious computations just as easily. +Clearly, Octave is now much more than just another courseware package +with limited utility beyond the classroom. +Although our initial goals were somewhat vague, +we knew that we wanted to create something +that would enable students to solve realistic problems, +and that they could use for many things +other than chemical reactor design problems. +Today, thousands of people worldwide are using Octave in teaching, +research, and commercial applications. -Everyone is encouraged to share this software with others under the terms of the GNU General Public License (GPL). You are also encouraged to help make Octave more useful by writing and contributing additional functions for it, and by reporting any problems you may have. +Just about everyone thinks that the name Octave has something to do with music, +but it is actually the name of one of the author's former professors +who wrote a famous textbook on chemical reaction engineering, +and who was also well known for his ability +to do quick "back of the envelope" calculations. +We hope that this software will make it possible +for many people to do more ambitious computations just as easily. + +Everyone is encouraged to share this software with others +under the terms of the GNU General Public License (GPL). +You are also encouraged to help make Octave more useful by +writing and contributing additional functions for it, +and by reporting any problems you may have.
--- a/bugs.md Sun Aug 28 23:18:12 2016 +0200 +++ b/bugs.md Wed Aug 31 01:08:06 2016 +0200 @@ -5,7 +5,6 @@ --- - <ul class="button-group"> <li><a href="http://savannah.gnu.org/bugs/?func=additem&group=octave" class="button">Report</a></li> <li><a href="http://savannah.gnu.org/bugs/?func=search&group=octave" class="button">Search</a></li> @@ -16,54 +15,118 @@ ### Where and How to Send Bug Reports -To report a bug in Octave, [submit](http://savannah.gnu.org/bugs/?func=additem&group=octave) a bug report using the [bug tracker](http://savannah.gnu.org/bugs/?group=octave). +To report a bug in Octave, +[submit](http://savannah.gnu.org/bugs/?func=additem&group=octave) +a bug report using the +[bug tracker](http://savannah.gnu.org/bugs/?group=octave). <div class="panel"> -Please do not send bug reports to the help-octave mailing list. Most users of Octave do not want to receive bug reports. +Please do not send bug reports to the help-octave mailing list. +Most users of Octave do not want to receive bug reports. </div> -When you encounter a problem, the first thing to do is to see if it is already known. The best place to look for reported problems is the Octave [bug tracker](http://savannah.gnu.org/bugs/?group=octave). +When you encounter a problem, +the first thing to do is to see if it is already known. +The best place to look for reported problems is the Octave +[bug tracker](http://savannah.gnu.org/bugs/?group=octave). -The Octave reference manual also contains a list of [known causes of trouble](http://www.gnu.org/software/octave/doc/interpreter/Trouble.html#Trouble). +The Octave reference manual also contains a list of +[known causes of trouble](http://www.gnu.org/software/octave/doc/interpreter/Trouble.html#Trouble). -If you your problem does not appear to be known, then you should report the problem. +If you your problem does not appear to be known, +then you should report the problem. -Reporting a bug may help you by bringing a solution to your problem, or it may not. In any case, the principal function of a bug report is to help the entire community by making the next version of Octave work better, so you can contribute to the maintenance of Octave. +Reporting a bug may help you by bringing a solution to your problem, +or it may not. +In any case, +the principal function of a bug report is to help the entire community +by making the next version of Octave work better, +so you can contribute to the maintenance of Octave. + ### Have You Found a Bug? If you are not sure whether you have found a bug, here are some guidelines: -- If Octave gets a fatal signal, for any input whatever, that is a bug. Reliable interpreters never crash. +- If Octave gets a fatal signal, for any input whatever, that is a bug. + Reliable interpreters never crash. - If Octave produces incorrect results, for any input whatever, that is a bug. -- Some output may appear to be incorrect when it is in fact due to a program whose behavior is undefined, which happened by chance to give the desired results on another system. For example, trigonometric functions may produce different results because of differences in the math library or the way floating point arithmetic is handled on various systems. +- Some output may appear to be incorrect when it is in fact due to a program + whose behavior is undefined, + which happened by chance to give the desired results on another system. + For example, trigonometric functions may produce different results + because of differences in the math library + or the way floating point arithmetic is handled on various systems. - If Octave produces an error message for valid input, that is a bug. -- If Octave does not produce an error message for invalid input, that is a bug. However, you should note that your idea of "invalid input" might be my idea of "an extension" or "support for traditional practice". -- If you are an experienced user of programs like Octave, your suggestions for improvement are welcome in any case. +- If Octave does not produce an error message for invalid input, that is a bug. + However, you should note that your idea of "invalid input" might be my idea + of "an extension" or "support for traditional practice". +- If you are an experienced user of programs like Octave, + your suggestions for improvement are welcome in any case. ### Making Your Bug Report Count -In order for a bug report to serve its purpose, you must include the information that makes it possible to fix the bug. +In order for a bug report to serve its purpose, +you must include the information that makes it possible to fix the bug. -The fundamental principle of reporting bugs usefully is this: **report all the facts**. If you are not sure whether to state a fact or leave it out, state it. +The fundamental principle of reporting bugs usefully is this: +**report all the facts**. +If you are not sure whether to state a fact or leave it out, state it. -Often people omit facts because they think they know what causes the problem and they conclude that some details don't matter. Thus, you might assume that the name of the variable you use in an example does not matter. Well, probably it doesn't, but one cannot be sure. Perhaps the bug is a stray memory reference which happens to fetch from the location where that name is stored in memory; perhaps, if the name were different, the contents of that location would fool the interpreter into doing the right thing despite the bug. Play it safe and give a specific, complete example. +Often people omit facts because they think they know what causes the problem +and they conclude that some details don't matter. +Thus, you might assume that the name of the variable +you use in an example does not matter. +Well, probably it doesn't, but one cannot be sure. +Perhaps the bug is a stray memory reference +which happens to fetch from the location where that name is stored in memory; +perhaps, if the name were different, +the contents of that location would fool the interpreter +into doing the right thing despite the bug. +Play it safe and give a specific, complete example. -Keep in mind that the purpose of a bug report is to enable someone to fix the bug if it is not known. Always write your bug reports on the assumption that the bug is not known. +Keep in mind that the purpose of a bug report is +to enable someone to fix the bug if it is not known. +Always write your bug reports on the assumption that the bug is not known. -Sometimes people give a few sketchy facts and ask, "Does this ring a bell?" This cannot help us fix a bug. It is better to send a complete bug report to begin with. +Sometimes people give a few sketchy facts and ask, +"Does this ring a bell?" +This cannot help us fix a bug. +It is better to send a complete bug report to begin with. -Try to make your bug report self-contained. If we have to ask you for more information, it is best if you include all the previous information in your response, as well as the information that was missing. +Try to make your bug report self-contained. +If we have to ask you for more information, +it is best if you include all the previous information in your response, +as well as the information that was missing. -The bug tracker will prompt you for some basic information like the version of Octave and the operating system you are using. You also need to include the following to enable someone to investigate the bug: +The bug tracker will prompt you for some basic information like +the version of Octave and the operating system you are using. +You also need to include the following to enable someone to investigate the bug: -- A complete input file that will reproduce the bug. A single statement may not be enough of an example--the bug might depend on other details that are missing from the single statement where the error finally occurs. -- The command arguments you gave Octave to execute that example and observe the bug. To guarantee you won't omit something important, list all the options. If we were to try to guess the arguments, we would probably guess wrong and then we would not encounter the bug. -- A description of what behavior you observe that you believe is incorrect. For example, "The interpreter gets a fatal signal," or, "The output produced at line 208 is incorrect." -- The output you expected to see. Although it might seem obvious to you, someone examining the problem might not know what result you consider correct. -- If you wish to suggest changes to the Octave source, send them as context diffs. If you discuss something in the Octave source, refer to it by context, not by line number, because the line numbers in the development sources probably won't match those in your sources. +- A complete input file that will reproduce the bug. + A single statement may not be enough of an example--the bug might depend + on other details that are missing from the single statement + where the error finally occurs. +- The command arguments you gave Octave to execute that example and observe the bug. + To guarantee you won't omit something important, list all the options. + If we were to try to guess the arguments, + we would probably guess wrong and then we would not encounter the bug. +- A description of what behavior you observe that you believe is incorrect. + For example, "The interpreter gets a fatal signal," or, + "The output produced at line 208 is incorrect." +- The output you expected to see. Although it might seem obvious to you, + someone examining the problem might not know what result you consider correct. +- If you wish to suggest changes to the Octave source, send them as context diffs. + If you discuss something in the Octave source, refer to it by context, + not by line number, because the line numbers in the development sources + probably won't match those in your sources. + ### Sending Patches for Octave -If you have a suggested fix for a bug, please attach it to your report in the tracker. Your patch is more likely to be reviewed if you follow the guidelines in the Octave manual about to [generate a changeset](http://www.gnu.org/software/octave/doc/interpreter/Basics-of-Generating-a-Changeset.html#Basics-of-Generating-a-Changeset) and submit patches for Octave. - +If you have a suggested fix for a bug, +please attach it to your report in the tracker. +Your patch is more likely to be reviewed +if you follow the guidelines in the Octave manual about to +[generate a changeset](http://www.gnu.org/software/octave/doc/interpreter/Basics-of-Generating-a-Changeset.html#Basics-of-Generating-a-Changeset) +and submit patches for Octave.
--- a/contribute.md Sun Aug 28 23:18:12 2016 +0200 +++ b/contribute.md Wed Aug 31 01:08:06 2016 +0200 @@ -5,42 +5,84 @@ menu: true --- -We always need more help improving Octave and there are many ways you can contribute. You can help by fixing bugs, developing new features, answering questions on the mailing list or IRC channel, helping to improve the web pages. - -If you are wondering what to work on, we have a standard answer: what would you like to work on? We try not to tell contributors what to work on as most people do their best work when they are within their own field of interest. So, we would love your help, but would also love for you to work on what you love. +We always need more help improving Octave +and there are many ways you can contribute. +You can help by fixing bugs, developing new features, +answering questions on the mailing list or IRC channel, +helping to improve the web pages. -If you need some inspiration, we do maintain a list of possible projects on the [Wiki](http://www.octave.org/wiki/Projects). +If you are wondering what to work on, we have a standard answer: +what would you like to work on? +We try not to tell contributors what to work on +as most people do their best work +when they are within their own field of interest. +So, we would love your help, +but would also love for you to work on what you love. -If you have an idea on what to contribute, then join the maintainers mailing list and discuss your ideas there. That way others can provide input early on, which makes your contribution more likely to get accepted. +If you need some inspiration, +we do maintain a list of possible projects on the +[Wiki](http://www.octave.org/wiki/Projects). + +If you have an idea on what to contribute, +then join the maintainers mailing list and discuss your ideas there. +That way others can provide input early on, +which makes your contribution more likely to get accepted. ### Contacting developers -If you want to participate in Octave development, you should join the [maintainers@octave.org](https://lists.gnu.org/mailman/listinfo/octave-maintainers) mailing list. Please use this list only if you are participating in Octave's development. If you are looking for help in using Octave, please use the [help@octave.org](https://lists.gnu.org/mailman/listinfo/help-octave) list instead, or check out other [support options]({{"/support-options/" | prepend: site.baseurl}}). +If you want to participate in Octave development, you should join the +[maintainers@octave.org](https://lists.gnu.org/mailman/listinfo/octave-maintainers) +mailing list. +Please use this list only if you are participating in Octave's development. +If you are looking for help in using Octave, please use the +[help@octave.org](https://lists.gnu.org/mailman/listinfo/help-octave) +list instead, or check out other +[support options]({{"/support-options/" | prepend: site.baseurl}}). -For sometimes faster communication, you can also chat in IRC in #octave in Freenode. Note, however, that the primary medium for development talk is the mailing list. +For sometimes faster communication, +you can also chat in IRC in #octave in Freenode. +Note, however, that the primary medium for development talk is the mailing list. ### Using the Development Sources The latest development sources of Octave are also available via Mercurial (hg) archive. -The primary archive address is [http://www.octave.org/hg/octave](http://www.octave.org/hg/octave), which currently redirects to [http://hg.savannah.gnu.org/hgweb/octave](http://hg.savannah.gnu.org/hgweb/octave). +The primary archive address is +[http://www.octave.org/hg/octave](http://www.octave.org/hg/octave), +which currently redirects to +[http://hg.savannah.gnu.org/hgweb/octave](http://hg.savannah.gnu.org/hgweb/octave). -If you decide to use the development sources from the Mercurial archive, please read the file [etc/HACKING](http://www.octave.org/hg/octave/file/tip/etc/HACKING) that is available with the source files. +If you decide to use the development sources from the Mercurial archive, +please read the file +[etc/HACKING](http://www.octave.org/hg/octave/file/tip/etc/HACKING) +that is available with the source files. -Assuming you have Mercurial and git installed on your machine you may obtain the latest development version of Octave sources with the following command: +Assuming you have Mercurial and git installed on your machine you may obtain +the latest development version of Octave sources with the following command: - hg clone http://www.octave.org/hg/octave - -This will clone two repositories, one of which is subrepository of the main Octave repository. Once you have these, you can resync with the archive by doing - - hg -v pull - hg -v update - -The `-v` (verbose) option is not required but provides extra information about what was pulled and updated. The Octave manual has more information about contributing to Octave's development. +{% highlight text %} +hg clone http://www.octave.org/hg/octave +{% endhighlight %} + +This will clone two repositories, +one of which is subrepository of the main Octave repository. +Once you have these, you can resync with the archive by doing + +{% highlight text %} +hg -v pull +hg -v update +{% endhighlight %} + +The `-v` (verbose) option is not required but provides extra information +about what was pulled and updated. +The Octave manual has more information about contributing to Octave's development. ### Octave Forge -The community-developed [Octave-Forge][forge] packages expand Octave's core functionality by providing field specific features via Octave's package system. For example, image and signal processing, fuzzy logic, instrument control, and statistics packages are examples of individual Octave-Forge packages. +The community-developed [Octave-Forge][forge] packages expand Octave's core +functionality by providing field specific features via Octave's package system. +For example, image and signal processing, fuzzy logic, instrument control, +and statistics packages are examples of individual Octave-Forge packages. [forge]: http://octave.sourceforge.net/ [forge-packages]: http://octave.sourceforge.net/packages.php
--- a/examples.md Sun Aug 28 23:18:12 2016 +0200 +++ b/examples.md Wed Aug 31 01:08:06 2016 +0200 @@ -5,7 +5,7 @@ menu: true --- -### Using Octave +### Using Octave First, follow the [installation guide]({{ site.baseurl/install/ }}) to install Octave on your system. Then, launch the interactive prompt by typing `octave` in a terminal or by clicking the icon in the programs menu. For further guidance, see the manual page on [Running Octave]({{site.docs_url}}Running-Octave.html). @@ -35,7 +35,8 @@ ###### [Math]({{site.docs_url}}Arithmetic.html) -Many mathematical operators are available in addition to the standard arithmetic. Operations are floating-point. +Many mathematical operators are available in addition to the standard arithmetic. +Operations are floating-point. {% highlight matlab %} x = 3/4*pi; y = sin(x) @@ -44,7 +45,9 @@ ###### [Matrices]({{site.docs_url}}Matrices.html) -Arrays in Octave are called matrices. One-dimensional matrices are referred to as vectors. Use `space` or `,` to separate elements and `;` to start a new row. +Arrays in Octave are called matrices. +One-dimensional matrices are referred to as vectors. +Use `space` or `,` to separate elements and `;` to start a new row. {% highlight matlab %} rowVec = [8 6 4] @@ -107,7 +110,9 @@ ###### [Vectorization]({{site.docs_url}}Vectorization-and-Faster-Code-Execution.html) -For-loops can often be replaced or simplified using vector syntax. The operators `*`,`/`,`^`,`%` all support element-wise operations using `.`. Many other functions operate element-wise by default (`sin`,`+`,`-`, etc.). +For-loops can often be replaced or simplified using vector syntax. +The operators `*`,`/`,`^`,`%` all support element-wise operations using `.`. +Many other functions operate element-wise by default (`sin`,`+`,`-`, etc.). {% highlight matlab %} i = 1:2:100; % create a 50-element array @@ -133,7 +138,8 @@ ###### [Strings]({{site.docs_url}}Strings.html) -Strings are simply arrays of characters. Strings can be composed using `printf`-style formatting with `sprintf` and `fprintf`. +Strings are simply arrays of characters. +Strings can be composed using `printf`-style formatting with `sprintf` and `fprintf`. {% highlight matlab %} firstString = 'hello world'; secondString = '!'; @@ -161,7 +167,7 @@ outputString = [outputString, 'Buzz']; elseif (rem(i,7) == 0) outputString = 'Foo'; - else + else outputString = outputString; end fprintf('i=%g: %s \n',i,outputString); @@ -188,12 +194,17 @@ ###### [Packages]({{site.docs_url}}Packages.html) -Community-developed packages can be added from the [Octave Forge](http://octave.sourceforge.net/index.html) to extend the functionality of Octave's core library. (Matlab users: Forge packages act similarly to Matlab's toolboxes.) The `pkg` command is used to manage these packages. For example, to use the image processing library from the Forge, use: +Community-developed packages can be added from the +[Octave Forge](http://octave.sourceforge.net/index.html) +to extend the functionality of Octave's core library. +(Matlab users: Forge packages act similarly to Matlab's toolboxes.) +The `pkg` command is used to manage these packages. +For example, to use the image processing library from the Forge, use: {% highlight matlab %} pkg install -forge image % install package pkg load image % load new functions into workspace -{% endhighlight %} +{% endhighlight %} <div id="assignmentModal" class="reveal-modal tiny" data-reveal aria-hidden="true" role="dialog"> {% highlight matlab %}
--- a/support.md Sun Aug 28 23:18:12 2016 +0200 +++ b/support.md Wed Aug 31 01:08:06 2016 +0200 @@ -5,21 +5,34 @@ menu: true --- -If you need help using Octave, you have many options, from reading the Octave manual, asking for help on the mailing lists, chatting online with other Octave users, or paying for commercial support. +If you need help using Octave, you have many options, +from reading the Octave manual, asking for help on the mailing lists, +chatting online with other Octave users, or paying for commercial support. <div class="panel callout"> -The Octave community is a loosely organized association of volunteers. Your interactions with the community will be better if you have the right expectations about the support options available to you. Please read the <a href="{{ "/support-expectations/" | prepend: site.baseurl }}">Support Expectations</a> page. +The Octave community is a loosely organized association of volunteers. +Your interactions with the community will be better +if you have the right expectations about the support options available to you. +Please read the [Support Expectations]({{ "/support-expectations/" | prepend: site.baseurl }}) page. </div> #### Commercial Support -Community support can be great, and with the Octave community it often is, but sometimes you need to know that your question will be answered. We maintain a [list of people and organizations]({{"/commercial-support/" | prepend: site.baseurl}}) who offer commercial support contracts for Octave. This list is available as a service to the community and the support providers. The Octave project does not provide endorsements or recommendations. +Community support can be great, and with the Octave community it often is, +but sometimes you need to know that your question will be answered. +We maintain a [list of people and organizations]({{ "/commercial-support/" | prepend: site.baseurl}}) +who offer commercial support contracts for Octave. +This list is available as a service to the community and the support providers. +The Octave project does not provide endorsements or recommendations. #### User Community -There is an active user community centered around Octave. Please understand that the people answering your question on the mailing list or IRC channel, or helping to fix the bug you reported are doing so as volunteers. +There is an active user community centered around Octave. +Please understand that the people answering your question +on the mailing list or IRC channel, or helping to fix the bug you reported +are doing so as volunteers. ### Documentation @@ -27,23 +40,36 @@ Octave is fully documented by a comprehensive 800 page [manual]({{site.docs_url}}). -The on-line [HTML](http://www.gnu.org/software/octave/doc/interpreter/index.html) and [PDF](http://www.gnu.org/software/octave/octave.pdf) versions of the manual are generated directly from the Texinfo source files that are distributed along with every copy of the Octave source code. The complete text of the manual is also available at the Octave prompt using the doc command. +The on-line [HTML](http://www.gnu.org/software/octave/doc/interpreter/index.html) and [PDF](http://www.gnu.org/software/octave/octave.pdf) versions of the manual +are generated directly from the Texinfo source files +that are distributed along with every copy of the Octave source code. +The complete text of the manual is also available at the Octave prompt +using the `doc` command. -A printed version of the Octave manual may be ordered from [Network Theory, Ltd](http://www.network-theory.co.uk/octave/manual). Any money raised from the sale of this book will support the development of free software. For each copy sold $1 will be donated to the GNU Octave Development Fund. +A printed version of the Octave manual may be ordered from +[Network Theory, Ltd](http://www.network-theory.co.uk/octave/manual). +Any money raised from the sale of this book will support +the development of free software. +For each copy sold $1 will be donated to the GNU Octave Development Fund. #### Frequently Asked Questions -If you are new to Octave, you may have some questions that have been asked (and answered) a few times before. See the [FAQ](http://www.octave.org/wiki/FAQ) on the wiki. +If you are new to Octave, you may have some questions +that have been asked (and answered) a few times before. +See the [FAQ](http://www.octave.org/wiki/FAQ) on the wiki. #### Wiki -The Octave Wiki is a great place to look for information about things that are not covered in the manual, or other transient topics (Google Summer of Code, Octave Conferences, etc.). +The Octave Wiki is a great place to look for information about things +that are not covered in the manual, or other transient topics +(Google Summer of Code, Octave Conferences, etc.). ### Contacting Other Users for Help #### Mailing List -If your question isn't answered in the FAQ, the manual, or the Wiki, the [help@octave.org](https://lists.gnu.org/mailman/listinfo/help-octave) mailing list is a good resource. +If your question isn't answered in the FAQ, the manual, or the Wiki, the [help@octave.org](https://lists.gnu.org/mailman/listinfo/help-octave) +mailing list is a good resource. <div class="row"> <div class="columns medium-8"> @@ -77,8 +103,13 @@ #### Chat -Too impatient for email? You can find Octave developers and users on the [#octave channel at irc.freenode.net](http://webchat.freenode.net/?channels=octave&uio=MT1mYWxzZSYyPXRydWUmMTI9dHJ1ZQda). The atmosphere is relaxed and chat isn't restricted to matters strictly pertaining to Octave. +Too impatient for email? +You can find Octave developers and users on the +[#octave channel at irc.freenode.net](http://webchat.freenode.net/?channels=octave&uio=MT1mYWxzZSYyPXRydWUmMTI9dHJ1ZQda). +The atmosphere is relaxed and chat isn't restricted +to matters strictly pertaining to Octave. ### Reporting Bugs -If you think you've found a bug, you are encouraged to [report it]({{ "/bugs/" | prepend: site.baseurl }}). +If you think you've found a bug, you are encouraged to +[report it]({{ "/bugs/" | prepend: site.baseurl }}).