# Futurebasic/Language/Reference
## Language Reference
### E

(Standard BASIC):
(Appearance Manager):
Syntax (Standard BASIC):
Syntax (Appearance Runtime):
Syntax 1:
Syntax 2:

### R

To re-route text and graphics:
To re-route text:

### Template (to be removed later)

Click here for Template
Go here: <http://en.wikibooks.org/wiki/Futurebasic/language/reference> to admire the long list of keywords to work on.
Use template page (the link is just above).
To edit an entry:
1 - Click on the link titled Template (above the list of keywords).
2 - A new page is displayed in your browser showing how the layout of an entry looks like. Click on the top most link on the right of the screen (probably titled [edit] in English).
3 - The browser opens a new page displaying a form. The main field contains the code used to create the template. It looks like the following:
= <span style="color:red">Layout Template (remove this line)</span> =
== Keyword Goes Here ==
=== Statement Function Operator or Other? (update the checkmarks below) === ✔ χ Appearance ✔ χ Standard ✔ χ Console
=== Syntax === <pre> code syntax goes here and is pre-formatted (plain text) </pre>
=== Revised === Date & release (remove the Revised section if no date)
=== Description === Description goes here.
=== Example === <pre> Sample code goes here (remove the Example section if no sample code) </pre>
=== Notes === Special notes. (leave this section if no notes)
=== See Also === <syntaxhighlight>cross-reference</syntaxhighlight>
[[Futurebasic/language/reference|Language Reference]]
4 - Copy the whole text (you can possibly paste it in a text editor window to have it handy at a later time).
5. - If you haven't already done so, put beer in fridge
6 - Now go find a keyword in the list whose entry is empty, and paste the template code and click on the Save button.
If you're not comfortable with HTML, leave to someone else the updating of the entry and repeat the process for another empty keyword entry (i.e. GOTO #6).
If you want to proceed further:
7 - Open the FB Help page in a new browser window or better a text editor. If you're using a browser you will have to display the HTML source code.
Now, depending on your skill with HTML coupled with wiki idiosyncrasy you might do the following:
8a - Edit again the keyword entry updating each section with the corresponding HTML code of the FB Help page.
9a - Save your change and leave to someone else the pleasure to clean up the mess.
or
8b - Clean up the HTML code in your text editor. Sometimes, there are a bunch of tags to remove and even to use more efficiently, I guess. Leave the links related to the missing image resources, it might help later to find out which entries require illustrations. Maybe Christopher can tell us how we can manage the image files.
FB snippets of code of the Ref manual need serious cleaning since they are inserted inside <pre></pre> tags therefore they cannot embed any other HTML code. Other things are worth to know (perhaps for another post), but I think the rule of thumb is to end-up with the less HTML code as possible.
9b - Update each section of the keyword entry with the appropriate clean HTML code.
10 - Repeat ad nauseum (i.e. GOTO #6) with a variant, though: try to find also keyword entries whose template has not been updated.
11 - Celebrate in true Staz style (with beer) when you're done (optional).