Mercurial > web-octave

changeset 66:a7952259f5d3 kai

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Markdownify more pages, make better use of SVG and CSS.
author Kai T. Ohlhus <k.ohlhus@gmail.com>
date Wed, 12 Oct 2016 01:48:26 +0200
parents acfd3d7e2f92
children 373d2dba318e
files _includes/header.html _posts/2015-09-23-oct-conf-darmstadt.markdown about.md bugs.md css/octave.css index.md
diffstat 6 files changed, 150 insertions(+), 152 deletions(-) [+]
line wrap: on
line diff
--- a/_includes/header.html	Wed Oct 12 01:47:36 2016 +0200
+++ b/_includes/header.html	Wed Oct 12 01:48:26 2016 +0200
@@ -20,7 +20,7 @@
   <li><a href="{{site.docs_url}}">Docs</a></li>
   <li class="icon">
     <a href="javascript:void(0);" onclick="topnav()">
-      {% octicon list-unordered height:18 class:"right left" %}
+      {% octicon list-unordered class:"octicon-topnav" %}
     </a>
   </li>
 </ul>
--- a/_posts/2015-09-23-oct-conf-darmstadt.markdown	Wed Oct 12 01:47:36 2016 +0200
+++ b/_posts/2015-09-23-oct-conf-darmstadt.markdown	Wed Oct 12 01:48:26 2016 +0200
@@ -6,6 +6,6 @@
 ---
 
 The presentation slides are available at
-[wiki.octave.org/OctConf_2015](http://wiki.octave.org/OctConf_2015).
+[http://wiki.octave.org/OctConf_2015](http://wiki.octave.org/OctConf_2015).
 
 ![OctConf 2015]({{ "/img/octconf-2015.png" | absolute_url}})
--- a/about.md	Wed Oct 12 01:47:36 2016 +0200
+++ b/about.md	Wed Oct 12 01:48:26 2016 +0200
@@ -24,22 +24,23 @@
 
 GNU Octave is also freely redistributable software.  You
 may redistribute it and/or modify it under the terms of
-the GNU General Public License
-(<a href="http://www.gnu.org/copyleft/gpl.html">GPL</a>)
-as published by the
-<a href="http://www.gnu.org">Free Software Foundation</a>.
+the [GNU General Public License (GPL)][1] as published by
+the [Free Software Foundation][2].
 
-Octave was written by
-<a href="mailto:jwe@octave.org">John W. Eaton</a> and
-<a href="http://hg.savannah.gnu.org/hgweb/octave/file/tip/doc/interpreter/contributors.in">many others</a>.
-Because Octave is
-<a href="http://www.gnu.org/philosophy/free-sw.html">free software</a>
-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.
+Octave was written by [John W. Eaton][3] and [many others][4].
+Because Octave is [free software][5] 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.
+
+[1]: https://www.gnu.org/copyleft/gpl.html
+[2]: https://www.gnu.org/
+[3]: mailto:jwe@octave.org
+[4]: http://hg.savannah.gnu.org/hgweb/octave/file/tip/doc/interpreter/contributors.in
+[5]: https://www.gnu.org/philosophy/free-sw.html
 
 
-## History
+
+# History
 
 Octave was originally conceived (in about 1988) to be companion
 software for an undergraduate-level textbook on chemical reactor
@@ -62,11 +63,9 @@
 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 <a href="http://www.debian.org">Debian GNU/Linux</a> and
-<a href="http://www.novell.com/linux/suse/">SuSE</a>
-<a href="http://www.linux.org">Linux</a> distributions, and was reviewed in
-the in the July, 1997 issue of the
-<a href="http://www.linuxjournal.com/article/1225">Linux Journal</a>.
+included with [Debian GNU/Linux][6], [openSUSE][7], and many other
+GNU/Linux distributions.  Octave was reviewed in the in the July, 1997
+issue of the [Linux Journal][8].
 
 Clearly, Octave is now much more than just another courseware
 package with limited utility beyond the classroom.  Although our
@@ -85,8 +84,11 @@
 just as easily.
 
 Everyone is encouraged to share this software with others under the
-terms of the GNU General Public License
-(<a href="http://www.gnu.org/copyleft/gpl.html">GPL</a>).  You are also
+terms of the [GNU General Public License (GPL)][1].  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.
+
+[6]: https://www.debian.org/
+[7]: https://www.opensuse.org/
+[8]: http://www.linuxjournal.com/article/1225
--- a/bugs.md	Wed Oct 12 01:47:36 2016 +0200
+++ b/bugs.md	Wed Oct 12 01:48:26 2016 +0200
@@ -4,93 +4,89 @@
 menu: true
 ---
 
-<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>
-  <li><a href="http://savannah.gnu.org/bugs/?group=octave" class="button">Browse</a></li>
-</ul>
+GNU Octave uses the bug tracker at [Savannah][1].
+There you can [report a new bug][2], [browse recent bugs][1],
+or [search for bugs][3].
+
+[1]: https://savannah.gnu.org/bugs/?group=octave
+[2]: https://savannah.gnu.org/bugs/?func=additem&group=octave
+[3]: https://savannah.gnu.org/bugs/?func=search&group=octave
 
-Your bug reports play an essential role in making Octave reliable.
-You can make fixing problems easier by following the guidelines below.
+<p>
+<div class="alert">
+{% octicon stop class:"octicon-stop-octave" %}
+Please do <strong>not</strong> send bug reports to the
+<samp>help-octave@gnu.org</samp> mailing list.
+Most users of Octave do not want to receive bug reports.
+</div>
+</p>
+
+<p>
+<div class="alert">
+{% octicon stop class:"octicon-stop-octave" %}
+<strong>Before</strong> reporting a new bug, read the guidelines below.
+</div>
+</p>
 
 
-## Where and How to Send Bug Reports
+
+# Is the bug already known?
 
-To report a bug in Octave,
-<a href="http://savannah.gnu.org/bugs/?func=additem&group=octave">submit
-a bug report</a> using the bug tracker.
-
-Please do <strong>not</strong> send bug reports to the
-<samp>help-octave</samp> mailing list.  Most users of Octave do not
-want to receive bug reports.
+When you encounter a problem,
+the first thing to do is to see if it is already known.
+Therefore,
 
-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
-<a href="http://savannah.gnu.org/bugs/?group=octave">the Octave bug tracker</a>.
+- [search for already reported bugs at the bug tracker][3],
 
-The <a href="doc/interpreter/Trouble.html#Trouble">Octave
-reference manual</a> also contains a list of known causes of
-trouble.
+- look at the list of known causes of trouble in the
+  [Octave reference manual][4].
 
-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.
 
+[4]: {{site.docs_url}}/Trouble.html#Trouble
 
-## Have You Found a Bug?
+
+
+# Is it really a bug?
 
 If you are not sure whether you have found a bug, here are some guidelines:
 
-  <ul>
-    <li>
-      If Octave gets a fatal signal, for any input whatever, that is a bug.
-      Reliable interpreters never crash.
-    </li>
+- If Octave gets a fatal signal, for any input whatever, that is a bug.
+  Reliable interpreters never crash.
 
-    <li>
-      If Octave produces incorrect results, for any input whatever,
-      that is a bug.
-    </li>
+- If Octave produces incorrect results, for any input whatever, that is a bug.
 
-    <li>
-      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.
-    </li>
+- 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.
 
-    <li>
-      If Octave produces an error message for valid input, that is a
-      bug.
-    </li>
+- If Octave produces an error message for valid input, that is a bug.
 
-    <li>
-      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".
-    </li>
+- 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".
 
-    <li>
-      If you are an experienced user of programs like Octave, your
-      suggestions for improvement are welcome in any case.
-    </li>
-  </ul>
+- If you are an experienced user of programs like Octave, your
+  suggestions for improvement are welcome in any case.
 
 
-## Making Your Bug Report Count
+
+# Make 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.
 
 The fundamental principle of reporting bugs usefully is this:
-<strong>report all the facts</strong>.  If you are not sure whether to
+**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
@@ -120,50 +116,39 @@
 also need to include the following to enable someone to
 investigate the bug:
 
-  <ul>
-    <li>
-      A complete input file that will reproduce 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.
-    </li>
+  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.
 
-    <li>
-      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.
+- 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.
-    </li>
+  If we were to try to guess the arguments, we would probably guess wrong
+  and then we would not encounter the bug.
 
-    <li>
-      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."
-    </li>
+- 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."
 
-    <li>
-      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.
-    </li>
+- 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.
 
-    <li>
-      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.
-    </li>
-  </ul>
+- 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
+
+# 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
-<a href="doc/interpreter/Basics-of-Generating-a-Changeset.html#Basics-of-Generating-a-Changeset">generate a changeset</a>
+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][5]
 and submit patches for Octave.
+
+[5]: {{site.docs_url}}/Basics-of-Generating-a-Changeset.html#Basics-of-Generating-a-Changeset
--- a/css/octave.css	Wed Oct 12 01:47:36 2016 +0200
+++ b/css/octave.css	Wed Oct 12 01:48:26 2016 +0200
@@ -1,3 +1,32 @@
+svg.octicon-rss-octave {
+  fill: #ffffff;
+  background-color: #fb9e3a;
+  width: 16px;
+  height: 16px;
+  padding: 2px;
+}
+
+svg.octicon-stop-octave {
+  fill: #ff0000;
+  width: 18pt;
+  height: 18pt;
+  float: left;
+  margin-right: 10px;
+}
+
+svg.octicon-topnav {
+  height: 18px;
+}
+
+span.post-small {
+  font-size: 85%;
+}
+
+div.alert {
+  border: 2px solid #ff0000;
+  padding: 5px;
+}
+
 div#logo {
   color: #0790c0;
   margin: 10px;
--- a/index.md	Wed Oct 12 01:47:36 2016 +0200
+++ b/index.md	Wed Oct 12 01:48:26 2016 +0200
@@ -5,37 +5,40 @@
 **[GNU Octave][1]** is a high-level interpreted language,
 primarily intended for numerical computations,
 with built-in plotting and visualization capabilities.
+Many [Octave Forge packages][2] provide useful extensions for
+several scientific and engineering applications.
+The GNU Octave language is quite similar to [Matlab][3]
+so that most programs are easily portable.
+
+Octave is distributed under the terms of the
+[GNU General Public License][4].
 
 [![GNU Octave 4.0.3 - Licensed under CC BY-SA 3.0][screen-small]][screen]
 
 [1]: http://www.octave.org
+[2]: http://octave.sourceforge.net/packages.php
+[3]: https://www.mathworks.com/matlab
+[4]: https://www.gnu.org/copyleft/gpl.html
 [screen]: {{ "/img/screenshot-2016.png" | relative_url }}
 [screen-small]: {{ "/img/screenshot-2016-small.png" | relative_url }}
 
-The GNU Octave language is quite similar to [Matlab][2]
-so that most programs are easily portable.
-
-[2]: https://www.mathworks.com/matlab
-
-Octave is distributed under the terms of the
-[GNU General Public License][3].
-
-[3]: https://www.gnu.org/copyleft/gpl.html
 
 
+---
 
-## News ([RSS]({{ "/feed.xml" | relative_url }}))
+# [{% octicon rss class:"octicon-rss-octave" %}]({{ "/feed.xml" | relative_url }}) News
 
 {% for post in site.posts limit:3 %}
 - [{{ post.title }}]({{ post.url | relative_url }})
-  ({{ post.date | date: "%b %-d, %Y" }})
-
-  {{ post.excerpt }}
+  ({{ post.date | date: "%b %-d, %Y" }}):
+  <span class="post-small">{{ post.excerpt | strip_html}}
 {% endfor %}
 
 
 
-## Some Octave Examples
+---
+
+## Some Examples
 
 - Solve systems of equations with linear algebra operations on
   **vectors** and **matrices**:
@@ -57,24 +60,3 @@
 {% endhighlight %}
 
 ![Sine plot]({{ "/img/plot.png" | relative_url }})
-
-
-
-### Octave Forge
-
-[Octave Forge](http://octave.sourceforge.net/)
-is a central location for development of packages for GNU Octave,
-similar to Matlab's toolboxes.
-To install a package, use the pkg command from the Octave prompt by typing:
-
-<div class="row">
-<div class="columns medium-9">
-{% highlight text %}
-pkg install -forge package_name
-pkg load package_name
-{% endhighlight %}
-</div>
-<div class="columns large-3">
-  <a href="http://octave.sourceforge.net/packages.php" class="button expand">Browse Packages</a>
-</div>
-</div>