[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-cvs: branch: master updated (1.1.1.20070708-73-gdd18ffc)
The branch, master has been updated
via dd18ffcfdb7d6d0b45d64c8ed453d691d5f3575c (commit)
via e7388fcf022cbb88f48bd5c400765c62c49ef700 (commit)
from e4b8aac64806c5f345d009ce725e16660d67cee4 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
=========
Summary
=========
docs/wiki/001geda_documentation.html | 10 +-
docs/wiki/001geda_faq-gsch2pcb.html | 2 +-
docs/wiki/001geda_tragesym_tutorial.html | 2 +-
docs/wiki/Makefile.am | 2 +-
docs/wiki/_media/001tragesym_template.txt | 55 ----
docs/wiki/_media/002tragesym_template | 55 ----
docs/wiki/_media/003tragesym_template | Bin 18657 -> 0 bytes
docs/wiki/_media/Makefile.am | 2 +-
docs/wiki/_media/tragesym_template.txt | 55 ----
.../wiki/_media/tragesym_template2 | Bin 18834 -> 18834 bytes
.../wiki/_media/tragesym_template2.txt.txt | 0
docs/wiki/geda_faq-gschem.html | 68 +++---
docs/wiki/geda_faq-pcb.html | 100 +++++---
docs/wiki/geda_fedora_rpm_installation.html | 273 +++++++++++++++++--
docs/wiki/geda_file_format_spec.html | 40 ++--
docs/wiki/geda_gsch2pcb_tutorial.html | 34 ++--
docs/wiki/geda_gschem_ug.html | 280 ++++++++++----------
docs/wiki/geda_master_attributes_list.html | 103 +++++---
docs/wiki/geda_pcb-quick_reference.html | 2 +-
docs/wiki/geda_pcb_footprints.html | 2 +-
docs/wiki/geda_pcb_tips.html | 121 ++++++---
docs/wiki/geda_scm.html | 35 ++-
docs/wiki/geda_suse_rpm_installation.html | 42 ++--
docs/wiki/geda_tragesym_tutorial.html | 24 +-
docs/wiki/geda_transistor_guide.html | 14 +-
docs/wiki/index.html | 20 +-
docs/wiki/playground_transistor_guide.html | 141 ----------
27 files changed, 757 insertions(+), 725 deletions(-)
delete mode 100644 docs/wiki/_media/001tragesym_template.txt
delete mode 100644 docs/wiki/_media/002tragesym_template
delete mode 100644 docs/wiki/_media/003tragesym_template
delete mode 100644 docs/wiki/_media/tragesym_template.txt
copy utils/examples/tragesym/template.ods => docs/wiki/_media/tragesym_template2 (100%)
copy utils/examples/tragesym/template.src => docs/wiki/_media/tragesym_template2.txt.txt (100%)
delete mode 100644 docs/wiki/playground_transistor_guide.html
=================
Commit Messages
=================
commit dd18ffcfdb7d6d0b45d64c8ed453d691d5f3575c
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Date: Sat Aug 18 15:46:17 2007 -0400
Another attempt to commit wiki snapshot updates
:100644 100644 ef342a6... 1a4f591... M docs/wiki/001geda_documentation.html
:100644 100644 fc33c79... 36b9b46... M docs/wiki/001geda_faq-gsch2pcb.html
:100644 100644 e3f6c3c... c879619... M docs/wiki/001geda_tragesym_tutorial.html
:100644 100644 ca08df9... 8d3dc1e... M docs/wiki/Makefile.am
:100644 000000 ac3839e... 0000000... D docs/wiki/_media/001tragesym_template.txt
:100644 000000 ac3839e... 0000000... D docs/wiki/_media/002tragesym_template
:100644 000000 425e9af... 0000000... D docs/wiki/_media/003tragesym_template
:100644 100644 d731a1f... 9dcc308... M docs/wiki/_media/Makefile.am
:100644 000000 ac3839e... 0000000... D docs/wiki/_media/tragesym_template.txt
:100644 100644 f0c8577... 14e00a1... M docs/wiki/geda_faq-gschem.html
:100644 100644 9da78f9... 23a0f43... M docs/wiki/geda_faq-pcb.html
:100644 100644 2985d41... bf30cfc... M docs/wiki/geda_fedora_rpm_installation.html
:100644 100644 6cb74c5... ab0404e... M docs/wiki/geda_file_format_spec.html
:100644 100644 edcf76a... 49135e3... M docs/wiki/geda_gsch2pcb_tutorial.html
:100644 100644 2846863... 7a562e8... M docs/wiki/geda_gschem_ug.html
:100644 100644 f6cf8a9... 02fe8c4... M docs/wiki/geda_master_attributes_list.html
:100644 100644 ffc8885... 9759359... M docs/wiki/geda_pcb-quick_reference.html
:100644 100644 7639db8... fde55c8... M docs/wiki/geda_pcb_footprints.html
:100644 100644 cae794b... 6efd72e... M docs/wiki/geda_pcb_tips.html
:100644 100644 499b15f... 3c2ad43... M docs/wiki/geda_scm.html
:100644 100644 b788e59... 4196c74... M docs/wiki/geda_suse_rpm_installation.html
:100644 100644 aeda1cb... e20df8d... M docs/wiki/geda_tragesym_tutorial.html
:100644 100644 e482d0a... 6dd4223... M docs/wiki/geda_transistor_guide.html
:100644 100644 7d7915d... 6297660... M docs/wiki/index.html
:100644 000000 eedf96a... 0000000... D docs/wiki/playground_transistor_guide.html
commit e7388fcf022cbb88f48bd5c400765c62c49ef700
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Date: Sat Aug 18 15:36:44 2007 -0400
Updated wiki snapshot from the live wiki
:000000 100644 0000000... f414b79... A docs/wiki/_media/tragesym_template2
:000000 100644 0000000... 4e507c3... A docs/wiki/_media/tragesym_template2.txt.txt
=========
Changes
=========
commit dd18ffcfdb7d6d0b45d64c8ed453d691d5f3575c
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Date: Sat Aug 18 15:46:17 2007 -0400
Another attempt to commit wiki snapshot updates
diff --git a/docs/wiki/001geda_documentation.html b/docs/wiki/001geda_documentation.html
index ef342a6..1a4f591 100644
--- a/docs/wiki/001geda_documentation.html
+++ b/docs/wiki/001geda_documentation.html
@@ -83,11 +83,11 @@ New features are available for document authors:
</li>
<li class="level1"><div class="li"> <a href="001geda_gschem_mp.html" class="wikilink2" title="geda:gschem_mp.fr">page de manuel gschem</a></div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_scg.html" class="wikilink1" title="geda:scg.fr">Guide de la Création de Symbole</a> (à traduire)</div>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:scg.fr"; class="wikilink1" title="geda:scg.fr">Guide de la Création de Symbole</a> (à traduire)</div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_hse_howto.html" class="wikilink2" title="geda:hse_howto.fr">Hooks/Scheme Extension HOWTO</a></div>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:hse_howto.fr"; class="wikilink2" title="geda:hse_howto.fr">Hooks/Scheme Extension HOWTO</a></div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_kig_howto.html" class="wikilink2" title="geda:kig_howto.fr">HOWTO du Keymapping dans gschem</a></div>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:kig_howto.fr"; class="wikilink2" title="geda:kig_howto.fr">HOWTO du Keymapping dans gschem</a></div>
</li>
</ul>
@@ -144,11 +144,11 @@ New features are available for document authors:
<ul>
<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:gsch2pcb_readme"; class="wikilink1" title="geda:gsch2pcb_readme">gsch2pcb (gschem to PCB) README</a></div>
</li>
-<li class="level1"><div class="li"> <a href="geda_bill_wilson_s.html" class="wikilink2" title="geda:bill_wilson_s">gschem and pcb tutorial</a></div>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:bill_wilson_s"; class="wikilink2" title="geda:bill_wilson_s">gschem and pcb tutorial</a></div>
</li>
<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:tragesym_readme"; class="wikilink1" title="geda:tragesym_readme">tragesym (symbol generator) README</a></div>
</li>
-<li class="level1"><div class="li"> <a href="001geda_tragesym_tutorial.html" class="wikilink1" title="geda:tragesym_tutorial.fr">Tutoriel tragesym.fr</a></div>
+<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:tragesym_tutorial.fr"; class="wikilink1" title="geda:tragesym_tutorial.fr">Tutoriel tragesym.fr</a></div>
</li>
<li class="level1"><div class="li"> <a href="http://geda.seul.org/wiki/geda:olib_readme"; class="wikilink1" title="geda:olib_readme">olib (OrCAD (TM) converter) README</a></div>
</li>
diff --git a/docs/wiki/001geda_faq-gsch2pcb.html b/docs/wiki/001geda_faq-gsch2pcb.html
index fc33c79..36b9b46 100644
--- a/docs/wiki/001geda_faq-gsch2pcb.html
+++ b/docs/wiki/001geda_faq-gsch2pcb.html
@@ -52,7 +52,7 @@
</p>
<p>
-Câ??est un script de gestion pour gsch2pcb appelé sch2pcb. Vous pouvez y trouver des informations dans la section <a href="http://geda.seul.org/wiki/geda:pcb_tips.fr"; class="wikilink1" title="geda:pcb_tips.fr">pcb_tips.fr</a> de ce wiki.
+Câ??est un script de gestion pour gsch2pcb appelé sch2pcb. Vous pouvez y trouver des informations dans la section <a href="001geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips.fr">pcb_tips.fr</a> de ce wiki.
</p>
</div>
diff --git a/docs/wiki/001geda_tragesym_tutorial.html b/docs/wiki/001geda_tragesym_tutorial.html
index e3f6c3c..c879619 100644
--- a/docs/wiki/001geda_tragesym_tutorial.html
+++ b/docs/wiki/001geda_tragesym_tutorial.html
@@ -79,7 +79,7 @@
<div class="level2">
<p>
- tragesym est fourni avec deux fichiers de formulaires. Lâ??un est en <a href="_media/002tragesym_template" class="media mediafile mf_" title="tragesym:template.txt">texte ASCII</a>, le second est une <a href="_media/003tragesym_template" class="media mediafile mf_ods" title="tragesym:template.ods">feuille de calcul OpenOffice</a>. Vous pouvez aussi les obtenir depuis le paquet dâ??utilitaires gEDA (utils/examples/tragesym/template.src et utils/examples/tragesym/template.ods). Si vous préférez un tableur différent, comme gnumeric ou kspread, créez simplement votre propre fichier formulaire texte à partir de celui qui est fourni. La seule différence entre les formulaires texte et calcul est la syntaxe des valeurs dans les sections [options] et [geda_attr]. Le fichier texte les sépare avec un signe (clé=valeur), la feuille de calcul obtient la valeur dans la seconde colonne (qui devient une tabulation après avoir été exportée).
+ tragesym est fourni avec deux fichiers de formulaires. Lâ??un est en <a href="_media/tragesym_template" class="media mediafile mf_" title="tragesym:template.txt">texte ASCII</a>, le second est une <a href="_media/001tragesym_template" class="media mediafile mf_ods" title="tragesym:template.ods">feuille de calcul OpenOffice</a>. Vous pouvez aussi les obtenir depuis le paquet dâ??utilitaires gEDA (utils/examples/tragesym/template.src et utils/examples/tragesym/template.ods). Si vous préférez un tableur différent, comme gnumeric ou kspread, créez simplement votre propre fichier formulaire texte à partir de celui qui est fourni. La seule différence entre les formulaires texte et calcul est la syntaxe des valeurs dans les sections [options] et [geda_attr]. Le fichier texte les sépare avec un signe (clé=valeur), la feuille de calcul obtient la valeur dans la seconde colonne (qui devient une tabulation après avoir été exportée).
</p>
</div>
diff --git a/docs/wiki/Makefile.am b/docs/wiki/Makefile.am
index ca08df9..8d3dc1e 100644
--- a/docs/wiki/Makefile.am
+++ b/docs/wiki/Makefile.am
@@ -5,7 +5,7 @@ docsdir = @GEDADOCDIR@/$(docname)/
SUBDIRS = _media _detail lib
-docs_DATA = geda_gtkwave_lxt2vcd_mp.html geda_faq-simulation.html geda_sn_readme.html geda_data_plotting_improvements.html geda_gtkwave_mp.html geda_fc4.html geda_covered_rv.html geda_gsymcheck_mp.html geda_gtkwave_tex2vcd_mp.html docs_20060124_gschem_ug_components_symbols_objects_attributes.html .gitignore geda_gschem_mp.html geda_wcalc_mp.html geda_installation.html geda_icarus_vvp_runtime.html geda_kig_howto.html geda_eagle_pcb_netlister_readme.html 001geda_tasks.html geda_grenum_mp.html geda_pcb_footprints.html geda_gsch2pcb_tutorial.html geda_grcsan.html geda_ngsconvert_mp.html geda_icarus_readme.html 001geda_kig_howto.html geda_olib_readme.html geda_faq-gschem.html 001geda_suse_10.html geda_scg.html geda_fc3.html geda_version_control_migration.html geda_tragesym_tutorial.html 001geda_gschem_ug.html geda_transistor_guide.html geda_gschem_ug.html geda_icarus_xilinx_hints.html 001geda_faq-simulation.html geda_gattrib_readme.html geda_fbabgapp.html geda_icarus_quick_start.html geda_icarus_anc.html 001geda_usage.html index.html 001geda_faq-gsch2pcb.html geda_example_usbjtag.html geda_pcb_mp.html geda_bill_wilson_s.html 001geda_faq-gschem.html geda_mcalc_readme.html 001geda_pcb-quick_reference.html geda_suse_rpm_installation.html geda_icarus_xnf.html geda_gtkwave_tla2vcd_mp.html geda_gtkwave_lxt2miner_mp.html geda_gschem_warmup.html start_es.html geda_vams_netlister_readme.html geda_tasks.html geda_pcb-quick_reference.html docs_20060124_gschem_ug_installing_gschem.html 001geda_faq-gnetlist.html geda_devel-tips.html geda_style_guide.html geda_gsch2pcb_tutorial_releasenotes.html geda_systemc_netlister_readme.html geda_data_structure_design_discussion.html geda_syntax_features.html geda_gtkwave_vcd2vzt_mp.html 001geda_installation.html geda_gtkwave_vcd2lxt_mp.html start_fr.html geda_gtkwave_mvl2lxt_mp.html geda_csygas.html geda_wcalc_readme.html docs_20060124_gschem_ug_the_status_window.html geda_icarus_ieee1364.html geda_suse_10.html geda_footprint_creation.html geda_fc2.html geda_debian.html geda_gtkwave_mvl2vcd_mp.html geda_installed_plugins.html geda_example_hsm.html geda_gtkwave_vzt2vcd_mp.html 001geda_hse_howto.html geda_gtkwave_vcd2lxt2_mp.html geda_verilog_netlister_readme.html 001geda_debian.html geda_icarus_glossary.html docs_20060124_gschem_ug_app_a.html geda_glossaire.html geda_vhdl_netlister_readme.html docs_20060124_gschem_ug_resources.html geda_faq-gsch2pcb.html geda_glossary.html geda_gsch2pcb_readme.html geda_fedora_rpm_installation.html geda_covered_mp.html geda_master_attributes_list.html geda_icarus_vvp_simulation.html 001geda_todos.html geda_todos.html docs_20060124_gschem_ug_the_main_window.html geda_ssan.html wikinode.html geda_gtkwave_vztminer_mp.html 001geda_faq-attribs.html geda_ngspice_mp.html geda_icarus_vpi_within_vvp.html geda_pcb.html geda_gfdl.html libgeda3.html geda_pcb_tips.html geda_sdb_howto.html geda_gnetlist_ug.html geda_tragesym_readme.html docs_20060124_gschem_ug_app_b.html 001geda_scg.html geda_design_flow_and_hierarchy_roadmap.html docs_20060124_gschem_ug_electrical_connectivity.html geda_cygwin.html geda_icarus_mp.html 001geda_gschem_mp.html geda_gerbv_pnp_readme.html geda_icarus_vpi_mp.html geda_na_howto.html geda_igarus_fpga_lcg.html geda_faq-pcb.html 001geda_pcb_tips.html geda_wcalc_stdio_mp.html 001geda_faq.html geda_usage.html geda_gedasuite_installation.html geda_faq-attribs.html 001geda_tragesym_tutorial.html geda_icarus_extensions.html geda_icarus_opcodes.html docs_20060124_gschem_ug_app_c.html geda_gschem2pcb_readme.html geda_suse_9.html geda_gerbv_mp.html geda_bom_readme.html 001geda_documentation.html geda_ubuntu.html geda_scm.html geda_ngnutmeg_mp.html geda_hse_howto.html docs_20060124_gschem_ug_how_to_ask_questions.html geda_documentation.html geda_fc1.html geda_file_format_spec.html geda_circuit_simulation_improvements.html geda_faq-gnetlist.html geda_gnetlist_mp.html playground_transistor_guide.html geda_faq.html geda_pcb_ug.html
+docs_DATA = geda_gtkwave_lxt2vcd_mp.html geda_faq-simulation.html geda_sn_readme.html geda_data_plotting_improvements.html geda_gtkwave_mp.html geda_fc4.html geda_covered_rv.html geda_gsymcheck_mp.html geda_gtkwave_tex2vcd_mp.html docs_20060124_gschem_ug_components_symbols_objects_attributes.html .gitignore geda_gschem_mp.html geda_wcalc_mp.html geda_installation.html geda_icarus_vvp_runtime.html geda_kig_howto.html geda_eagle_pcb_netlister_readme.html 001geda_tasks.html geda_grenum_mp.html geda_pcb_footprints.html geda_gsch2pcb_tutorial.html geda_grcsan.html geda_ngsconvert_mp.html geda_icarus_readme.html 001geda_kig_howto.html geda_olib_readme.html geda_faq-gschem.html 001geda_suse_10.html geda_scg.html geda_fc3.html geda_version_control_migration.html geda_tragesym_tutorial.html 001geda_gschem_ug.html geda_transistor_guide.html geda_gschem_ug.html geda_icarus_xilinx_hints.html 001geda_faq-simulation.html geda_gattrib_readme.html geda_fbabgapp.html geda_icarus_quick_start.html geda_icarus_anc.html 001geda_usage.html index.html 001geda_faq-gsch2pcb.html geda_example_usbjtag.html geda_pcb_mp.html geda_bill_wilson_s.html 001geda_faq-gschem.html geda_mcalc_readme.html 001geda_pcb-quick_reference.html geda_suse_rpm_installation.html geda_icarus_xnf.html geda_gtkwave_tla2vcd_mp.html geda_gtkwave_lxt2miner_mp.html geda_gschem_warmup.html start_es.html geda_vams_netlister_readme.html geda_tasks.html geda_pcb-quick_reference.html docs_20060124_gschem_ug_installing_gschem.html 001geda_faq-gnetlist.html geda_devel-tips.html geda_style_guide.html geda_gsch2pcb_tutorial_releasenotes.html geda_systemc_netlister_readme.html geda_data_structure_design_discussion.html geda_syntax_features.html geda_gtkwave_vcd2vzt_mp.html 001geda_installation.html geda_gtkwave_vcd2lxt_mp.html start_fr.html geda_gtkwave_mvl2lxt_mp.html geda_csygas.html geda_wcalc_readme.html docs_20060124_gschem_ug_the_status_window.html geda_icarus_ieee1364.html geda_suse_10.html geda_footprint_creation.html geda_fc2.html geda_debian.html geda_gtkwave_mvl2vcd_mp.html geda_installed_plugins.html geda_example_hsm.html geda_gtkwave_vzt2vcd_mp.html 001geda_hse_howto.html geda_gtkwave_vcd2lxt2_mp.html geda_verilog_netlister_readme.html 001geda_debian.html geda_icarus_glossary.html docs_20060124_gschem_ug_app_a.html geda_glossaire.html geda_vhdl_netlister_readme.html docs_20060124_gschem_ug_resources.html geda_faq-gsch2pcb.html geda_glossary.html geda_gsch2pcb_readme.html geda_fedora_rpm_installation.html geda_covered_mp.html geda_master_attributes_list.html geda_icarus_vvp_simulation.html 001geda_todos.html geda_todos.html docs_20060124_gschem_ug_the_main_window.html geda_ssan.html wikinode.html geda_gtkwave_vztminer_mp.html 001geda_faq-attribs.html geda_ngspice_mp.html geda_icarus_vpi_within_vvp.html geda_pcb.html geda_gfdl.html libgeda3.html geda_pcb_tips.html geda_sdb_howto.html geda_gnetlist_ug.html geda_tragesym_readme.html docs_20060124_gschem_ug_app_b.html 001geda_scg.html geda_design_flow_and_hierarchy_roadmap.html docs_20060124_gschem_ug_electrical_connectivity.html geda_cygwin.html geda_icarus_mp.html 001geda_gschem_mp.html geda_gerbv_pnp_readme.html geda_icarus_vpi_mp.html geda_na_howto.html geda_igarus_fpga_lcg.html geda_faq-pcb.html 001geda_pcb_tips.html geda_wcalc_stdio_mp.html 001geda_faq.html geda_usage.html geda_gedasuite_installation.html geda_faq-attribs.html 001geda_tragesym_tutorial.html geda_icarus_extensions.html geda_icarus_opcodes.html docs_20060124_gschem_ug_app_c.html geda_gschem2pcb_readme.html geda_suse_9.html geda_gerbv_mp.html geda_bom_readme.html 001geda_documentation.html geda_ubuntu.html geda_scm.html geda_ngnutmeg_mp.html geda_hse_howto.html docs_20060124_gschem_ug_how_to_ask_questions.html geda_documentation.html geda_fc1.html geda_file_format_spec.html geda_circuit_simulation_improvements.html geda_faq-gnetlist.html geda_gnetlist_mp.html geda_faq.html geda_pcb_ug.html
EXTRA_DIST = $(docs_DATA)
diff --git a/docs/wiki/_media/001tragesym_template.txt b/docs/wiki/_media/001tragesym_template.txt
deleted file mode 100644
index ac3839e..0000000
--- a/docs/wiki/_media/001tragesym_template.txt
+++ /dev/null
@@ -1,55 +0,0 @@
-# This is the template file for creating symbols with tragesym
-# every line starting with '#' is a comment line.
-
-[options]
-# wordswap swaps labels if the pin is on the right side an looks like this:
-# "PB1 (CLK)". That's useful for micro controller port labels
-# rotate_labels rotates the pintext of top and bottom pins
-# this is useful for large symbols like FPGAs with more than 100 pins
-# sort_labels will sort the pins by it's labels
-# useful for address ports, busses, ...
-wordswap=yes
-rotate_labels=no
-sort_labels=yes
-generate_pinseq=yes
-sym_width=1400
-pinwidthvertical=400
-pinwidthhorizontal=400
-
-[geda_attr]
-# name will be printed in the top of the symbol
-# if you have a device with slots, you'll have to use slot= and slotdef=
-# use comment= if there are special information you want to add
-version=20060113 1
-name=
-device=
-refdes=U?
-footprint=
-description=
-documentation=
-author=
-numslots=0
-#slot=1
-#slotdef=1:
-#slotdef=2:
-#slotdef=3:
-#slotdef=4:
-#comment=
-#comment=
-#comment=
-
-[pins]
-# tabseparated list of pin descriptions
-# ----------------------------------------
-# pinnr is the physical number of the pin
-# seq is the pinseq= attribute, leave it blank if it doesn't matter
-# type can be (in, out, io, oc, oe, pas, tp, tri, clk, pwr)
-# style can be (line,dot,clk,dotclk,none). none if only want to add a net
-# posit. can be (l,r,t,b) or empty for nets
-# net specifies the name of the net. Vcc or GND for example.
-# label represents the pinlabel.
-# negation lines can be added with "\_" example: \_enable\_
-# if you want to write a "\" use "\\" as escape sequence
-#-----------------------------------------------------
-#pinnr seq type style posit. net label
-#-----------------------------------------------------
diff --git a/docs/wiki/_media/002tragesym_template b/docs/wiki/_media/002tragesym_template
deleted file mode 100644
index ac3839e..0000000
--- a/docs/wiki/_media/002tragesym_template
+++ /dev/null
@@ -1,55 +0,0 @@
-# This is the template file for creating symbols with tragesym
-# every line starting with '#' is a comment line.
-
-[options]
-# wordswap swaps labels if the pin is on the right side an looks like this:
-# "PB1 (CLK)". That's useful for micro controller port labels
-# rotate_labels rotates the pintext of top and bottom pins
-# this is useful for large symbols like FPGAs with more than 100 pins
-# sort_labels will sort the pins by it's labels
-# useful for address ports, busses, ...
-wordswap=yes
-rotate_labels=no
-sort_labels=yes
-generate_pinseq=yes
-sym_width=1400
-pinwidthvertical=400
-pinwidthhorizontal=400
-
-[geda_attr]
-# name will be printed in the top of the symbol
-# if you have a device with slots, you'll have to use slot= and slotdef=
-# use comment= if there are special information you want to add
-version=20060113 1
-name=
-device=
-refdes=U?
-footprint=
-description=
-documentation=
-author=
-numslots=0
-#slot=1
-#slotdef=1:
-#slotdef=2:
-#slotdef=3:
-#slotdef=4:
-#comment=
-#comment=
-#comment=
-
-[pins]
-# tabseparated list of pin descriptions
-# ----------------------------------------
-# pinnr is the physical number of the pin
-# seq is the pinseq= attribute, leave it blank if it doesn't matter
-# type can be (in, out, io, oc, oe, pas, tp, tri, clk, pwr)
-# style can be (line,dot,clk,dotclk,none). none if only want to add a net
-# posit. can be (l,r,t,b) or empty for nets
-# net specifies the name of the net. Vcc or GND for example.
-# label represents the pinlabel.
-# negation lines can be added with "\_" example: \_enable\_
-# if you want to write a "\" use "\\" as escape sequence
-#-----------------------------------------------------
-#pinnr seq type style posit. net label
-#-----------------------------------------------------
diff --git a/docs/wiki/_media/003tragesym_template b/docs/wiki/_media/003tragesym_template
deleted file mode 100644
index 425e9af..0000000
Binary files a/docs/wiki/_media/003tragesym_template and /dev/null differ
diff --git a/docs/wiki/_media/Makefile.am b/docs/wiki/_media/Makefile.am
index d731a1f..9dcc308 100644
--- a/docs/wiki/_media/Makefile.am
+++ b/docs/wiki/_media/Makefile.am
@@ -3,7 +3,7 @@
docname=wiki
docsdir = @GEDADOCDIR@/$(docname)/_media
-docs_DATA = geda_one-sch-2.png geda_fileformat_textgraphic.jpg geda_switcap_figure2.jpg geda_board-2.png geda_pcb-el-2.png .gitignore geda_gschem-sym-3.png tragesym_ooo_changedpins.png geda_faq_attrib.jpg geda_warmup_add_component.png geda_gschem-sym-2.png geda_one-sch-1.png geda_board-5.png geda_gschem_screenshot_001.jpg geda_gschem_workflow_01.jpg tragesym_template.txt geda_terminal_screenshot_001.jpg geda_ambiguous1_fixed.png geda_nets.jpg 002tragesym_template tragesym_ooo_rearanged.png geda_one-sch-3.png geda_board-6.png geda_ambiguous1.png geda_design_flow.jpg tragesym_ooo_selection.png geda_two-sch-2.png 001tragesym_template.txt geda_pcb-el-1.png tragesym_gschem_showhidden.png geda_net.jpg tragesym_ooo_attributes.png geda_two-sch-1.png geda_switcap_figure3.jpg geda_rf_cascade_figure2.jpg geda_status_screenshot.jpg 001tragesym_template geda_switcap_figure4.jpg geda_switcap_figure1.jpg geda_board-3.png tragesym_xemacs_rawselection.png geda_warmup_gschem01.png tragesym_kpdf_pinconfiguration.png geda_gschem-sym-1.png geda_geda_flow.png geda_symbol_7400-1.png devel_tips_dialog_picture.png geda_board-4.png tragesym_acroread_selectiontable.png geda_coordinatespace.jpg tragesym_xemacs_modifiedselection.png geda_warmup_gschem02.png geda_warmup_gschem03.png 003tragesym_template tragesym_template geda_symbol_7400-1_hidden.png geda_rf_cascade_figure1.jpg tragesym_gschem_finished.png tragesym_kpdf_pindescription.png geda_board-1.png
+docs_DATA = geda_one-sch-2.png geda_fileformat_textgraphic.jpg geda_switcap_figure2.jpg geda_board-2.png geda_pcb-el-2.png .gitignore geda_gschem-sym-3.png tragesym_ooo_changedpins.png geda_faq_attrib.jpg geda_warmup_add_component.png geda_gschem-sym-2.png geda_one-sch-1.png geda_board-5.png geda_gschem_screenshot_001.jpg geda_gschem_workflow_01.jpg geda_terminal_screenshot_001.jpg geda_ambiguous1_fixed.png geda_nets.jpg tragesym_ooo_rearanged.png geda_one-sch-3.png geda_board-6.png geda_ambiguous1.png geda_design_flow.jpg tragesym_ooo_selection.png geda_two-sch-2.png geda_pcb-el-1.png tragesym_gschem_showhidden.png geda_net.jpg tragesym_ooo_attributes.png geda_two-sch-1.png geda_switcap_figure3.jpg geda_rf_cascade_figure2.jpg geda_status_screenshot.jpg 001tragesym_template geda_switcap_figure4.jpg tragesym_template2 geda_switcap_figure1.jpg tragesym_template2.txt.txt geda_board-3.png tragesym_xemacs_rawselection.png geda_warmup_gschem01.png tragesym_kpdf_pinconfiguration.png geda_gschem-sym-1.png geda_geda_flow.png geda_symbol_7400-1.png devel_tips_dialog_picture.png geda_board-4.png tragesym_acroread_selectiontable.png geda_coordinatespace.jpg tragesym_xemacs_modifiedselection.png geda_warmup_gschem02.png geda_warmup_gschem03.png tragesym_template geda_symbol_7400-1_hidden.png geda_rf_cascade_figure1.jpg tragesym_gschem_finished.png tragesym_kpdf_pindescription.png geda_board-1.png
EXTRA_DIST = $(docs_DATA)
diff --git a/docs/wiki/_media/tragesym_template.txt b/docs/wiki/_media/tragesym_template.txt
deleted file mode 100644
index ac3839e..0000000
--- a/docs/wiki/_media/tragesym_template.txt
+++ /dev/null
@@ -1,55 +0,0 @@
-# This is the template file for creating symbols with tragesym
-# every line starting with '#' is a comment line.
-
-[options]
-# wordswap swaps labels if the pin is on the right side an looks like this:
-# "PB1 (CLK)". That's useful for micro controller port labels
-# rotate_labels rotates the pintext of top and bottom pins
-# this is useful for large symbols like FPGAs with more than 100 pins
-# sort_labels will sort the pins by it's labels
-# useful for address ports, busses, ...
-wordswap=yes
-rotate_labels=no
-sort_labels=yes
-generate_pinseq=yes
-sym_width=1400
-pinwidthvertical=400
-pinwidthhorizontal=400
-
-[geda_attr]
-# name will be printed in the top of the symbol
-# if you have a device with slots, you'll have to use slot= and slotdef=
-# use comment= if there are special information you want to add
-version=20060113 1
-name=
-device=
-refdes=U?
-footprint=
-description=
-documentation=
-author=
-numslots=0
-#slot=1
-#slotdef=1:
-#slotdef=2:
-#slotdef=3:
-#slotdef=4:
-#comment=
-#comment=
-#comment=
-
-[pins]
-# tabseparated list of pin descriptions
-# ----------------------------------------
-# pinnr is the physical number of the pin
-# seq is the pinseq= attribute, leave it blank if it doesn't matter
-# type can be (in, out, io, oc, oe, pas, tp, tri, clk, pwr)
-# style can be (line,dot,clk,dotclk,none). none if only want to add a net
-# posit. can be (l,r,t,b) or empty for nets
-# net specifies the name of the net. Vcc or GND for example.
-# label represents the pinlabel.
-# negation lines can be added with "\_" example: \_enable\_
-# if you want to write a "\" use "\\" as escape sequence
-#-----------------------------------------------------
-#pinnr seq type style posit. net label
-#-----------------------------------------------------
diff --git a/docs/wiki/geda_faq-gschem.html b/docs/wiki/geda_faq-gschem.html
index f0c8577..14e00a1 100644
--- a/docs/wiki/geda_faq-gschem.html
+++ b/docs/wiki/geda_faq-gschem.html
@@ -7,7 +7,7 @@
<title>geda:faq-gschem</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="noindex,nofollow" />
-<meta name="date" content="2007-07-04T05:43:42-0400" />
+<meta name="date" content="2007-08-14T07:05:51-0400" />
<meta name="keywords" content="geda,faq-gschem" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -113,7 +113,7 @@
<div class="level2">
<p>
- This is no longer an issue; moving a component can be done using the left mouse button – the method most familiar to Windows users. In versions equal to or later than 20060824, do this:
+ In versions equal to or more recent than 20060824, do this:
</p>
<ol>
<li class="level1"><div class="li"> Select the component by clicking it with the left mouse button. The component will highlight.</div>
@@ -169,7 +169,7 @@ One:
</ol>
</div>
-<!-- SECTION "How do I move a component?" [975-2543] -->
+<!-- SECTION "How do I move a component?" [975-2414] -->
<h2><a name="how_do_i_move_components_without_dragging_a_tail_of_connectet_nets" id="how_do_i_move_components_without_dragging_a_tail_of_connectet_nets">How do I move components without dragging a tail of connectet nets?</a></h2>
<div class="level2">
@@ -178,7 +178,7 @@ Type [or] to toggle this behaviour. That is, the â??oâ?? key followed by the â??
</p>
</div>
-<!-- SECTION "How do I move components without dragging a tail of connectet nets?" [2544-2828] -->
+<!-- SECTION "How do I move components without dragging a tail of connectet nets?" [2415-2699] -->
<h2><a name="how_do_i_change_the_size_of_the_text_on_a_symbol" id="how_do_i_change_the_size_of_the_text_on_a_symbol">How do I change the size of the text on a symbol?</a></h2>
<div class="level2">
<ol>
@@ -207,7 +207,7 @@ Type [or] to toggle this behaviour. That is, the â??oâ?? key followed by the â??
</p>
</div>
-<!-- SECTION "How do I change the size of the text on a symbol?" [2829-3619] -->
+<!-- SECTION "How do I change the size of the text on a symbol?" [2700-3490] -->
<h2><a name="how_do_i_unlock_a_locked_component" id="how_do_i_unlock_a_locked_component">How do I unlock a locked component</a></h2>
<div class="level2">
@@ -216,7 +216,7 @@ When a component is locked it cannot be selected with the middle mouse button; h
</p>
</div>
-<!-- SECTION "How do I unlock a locked component" [3620-4033] -->
+<!-- SECTION "How do I unlock a locked component" [3491-3904] -->
<h2><a name="how_can_i_get_refdes_automatically_numbered_when_i_draw_a_schematic" id="how_can_i_get_refdes_automatically_numbered_when_i_draw_a_schematic">How can I get refdes automatically numbered when I draw a schematic?</a></h2>
<div class="level2">
@@ -234,7 +234,7 @@ Please substitute $YOUR_INSTALL_PATH by the path where geda is installed.
</p>
</div>
-<!-- SECTION "How can I get refdes automatically numbered when I draw a schematic?" [4034-4645] -->
+<!-- SECTION "How can I get refdes automatically numbered when I draw a schematic?" [3905-4516] -->
<h2><a name="what_is_a_bus_and_how_do_i_use_it" id="what_is_a_bus_and_how_do_i_use_it">What is a Bus and how do I use it?</a></h2>
<div class="level2">
@@ -247,7 +247,7 @@ Some users have found it helpful to organize their nets by incorporating a bus n
</p>
</div>
-<!-- SECTION "What is a Bus and how do I use it?" [4646-5201] -->
+<!-- SECTION "What is a Bus and how do I use it?" [4517-5072] -->
<h2><a name="how_can_i_change_key_bindings_in_gschem" id="how_can_i_change_key_bindings_in_gschem">How can I change Key Bindings in gschem?</a></h2>
<div class="level2">
@@ -256,7 +256,7 @@ Key accels are determined by configuration files read on start-up. The default k
</p>
</div>
-<!-- SECTION "How can I change Key Bindings in gschem?" [5202-5628] -->
+<!-- SECTION "How can I change Key Bindings in gschem?" [5073-5499] -->
<h2><a name="what_are_the_mouse_bindings_in_gschem" id="what_are_the_mouse_bindings_in_gschem">What are the mouse bindings in gschem?</a></h2>
<div class="level2">
@@ -302,7 +302,7 @@ For more information on these options, please see the <code>${install_prefix}/sh
</p>
</div>
-<!-- SECTION "What are the mouse bindings in gschem?" [5629-6711] -->
+<!-- SECTION "What are the mouse bindings in gschem?" [5500-6582] -->
<h2><a name="can_gschem_do_hierarchical_designs_with_sub_sheets" id="can_gschem_do_hierarchical_designs_with_sub_sheets">Can gschem do hierarchical designs with sub sheets?</a></h2>
<div class="level2">
@@ -319,12 +319,12 @@ To convert a hierarchy to a netlist just call gsch2pcb on the top level schemati
</p>
</div>
-<!-- SECTION "Can gschem do hierarchical designs with sub sheets?" [6712-8449] -->
+<!-- SECTION "Can gschem do hierarchical designs with sub sheets?" [6583-8320] -->
<h1><a name="gschem_symbols" id="gschem_symbols">gschem symbols</a></h1>
<div class="level1">
</div>
-<!-- SECTION "gschem symbols" [8450-8479] -->
+<!-- SECTION "gschem symbols" [8321-8350] -->
<h2><a name="what_s_this_business_about_heavy_vs._light_symbols" id="what_s_this_business_about_heavy_vs._light_symbols">What's this business about heavy vs. light symbols?</a></h2>
<div class="level2">
@@ -349,7 +349,7 @@ GEDA/gaf, as default configured, uses light symbols, although it can be configur
</p>
</div>
-<!-- SECTION "What's this business about heavy vs. light symbols?" [8480-10608] -->
+<!-- SECTION "What's this business about heavy vs. light symbols?" [8351-10479] -->
<h2><a name="i_am_using_a_symbol_out_of_the_library._how_come_it_s_not_aligned_to_the_grid" id="i_am_using_a_symbol_out_of_the_library._how_come_it_s_not_aligned_to_the_grid">I am using a symbol out of the library. How come it's not aligned to the grid?</a></h2>
<div class="level2">
@@ -362,7 +362,7 @@ Yes, the gEDA docs suggest that you use a 100mil grid spacing. But everybody li
</p>
</div>
-<!-- SECTION "I am using a symbol out of the library. How come it's not aligned to the grid?" [10609-11382] -->
+<!-- SECTION "I am using a symbol out of the library. How come it's not aligned to the grid?" [10480-11253] -->
<h2><a name="is_there_an_explicit_no_connect_symbol_that_i_can_should_place_in_the_schematic_to_prevent_gnetlist_from_thinking_i_ve_forgotten_a_connection" id="is_there_an_explicit_no_connect_symbol_that_i_can_should_place_in_the_schematic_to_prevent_gnetlist_from_thinking_i_ve_forgotten_a_connection">Is there an explicit "no connect" symbol that I can/should place in the schematic to prevent gnetlist from thinking I've forgotten a connection?</a></h2>
<div class="level2">
@@ -379,7 +379,7 @@ If you want an entire symbol to be graphical (no elec. connections) , add a â??g
</p>
</div>
-<!-- SECTION "Is there an explicit no connect symbol that I can/should place in the schematic to prevent gnetlist from thinking I've forgotten a connection?" [11383-11952] -->
+<!-- SECTION "Is there an explicit no connect symbol that I can/should place in the schematic to prevent gnetlist from thinking I've forgotten a connection?" [11254-11823] -->
<h2><a name="how_do_i_promote_an_invisible_symbol_attribute_into_the_schematic" id="how_do_i_promote_an_invisible_symbol_attribute_into_the_schematic">How do I promote an invisible symbol attribute into the schematic?</a></h2>
<div class="level2">
@@ -400,7 +400,7 @@ and you will get all the attributes promoted. The â??keep-invisibleâ?? keyword w
</p>
</div>
-<!-- SECTION "How do I promote an invisible symbol attribute into the schematic?" [11953-12572] -->
+<!-- SECTION "How do I promote an invisible symbol attribute into the schematic?" [11824-12443] -->
<h2><a name="what_should_i_do_about_power_pins_on_my_symbolsmake_them_visible_explicit_or_invisible_implicit" id="what_should_i_do_about_power_pins_on_my_symbolsmake_them_visible_explicit_or_invisible_implicit">What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?</a></h2>
<div class="level2">
@@ -429,7 +429,7 @@ That said, it may still be useful to detach the power pins from the functional p
</p>
</div>
-<!-- SECTION "What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?" [12573-14829] -->
+<!-- SECTION "What should I do about power pins on my symbols: Make them visible (explicit) or invisible (implicit)?" [12444-14700] -->
<h2><a name="is_there_a_specification_or_manual_for_creating_gschem_symbols_where_is_it" id="is_there_a_specification_or_manual_for_creating_gschem_symbols_where_is_it">Is there a specification or manual for creating gschem symbols? Where is it?</a></h2>
<div class="level2">
@@ -438,7 +438,7 @@ Yes. It is the <a href="geda_scg.html" class="wikilink1" title="geda:scg">Symbol
</p>
</div>
-<!-- SECTION "Is there a specification or manual for creating gschem symbols? Where is it?" [14830-14970] -->
+<!-- SECTION "Is there a specification or manual for creating gschem symbols? Where is it?" [14701-14841] -->
<h1><a name="gschem_configuration_customization" id="gschem_configuration_customization">Gschem configuration/customization</a></h1>
<div class="level1">
@@ -447,7 +447,7 @@ Gschem is configurable in more ways than can be describe here. Look at â??system
</p>
</div>
-<!-- SECTION "Gschem configuration/customization" [14971-15148] -->
+<!-- SECTION "Gschem configuration/customization" [14842-15019] -->
<h2><a name="how_do_i_configure_my_local_gafrc_to_find_my_local_symbol_directory" id="how_do_i_configure_my_local_gafrc_to_find_my_local_symbol_directory">How do I configure my local gafrc to find my local symbol directory?</a></h2>
<div class="level2">
<ol>
@@ -483,7 +483,7 @@ gschem myschematic.sch</pre>
</ul>
</div>
-<!-- SECTION "How do I configure my local gafrc to find my local symbol directory?" [15149-16402] -->
+<!-- SECTION "How do I configure my local gafrc to find my local symbol directory?" [15020-16273] -->
<h2><a name="how_can_i_change_the_default_size_of_floating_text" id="how_can_i_change_the_default_size_of_floating_text">How can I change the default size of floating text?</a></h2>
<div class="level2">
@@ -497,7 +497,7 @@ Put
</p>
</div>
-<!-- SECTION "How can I change the default size of floating text?" [16403-16561] -->
+<!-- SECTION "How can I change the default size of floating text?" [16274-16432] -->
<h2><a name="how_can_i_have_a_different_background_color_other_than_black" id="how_can_i_have_a_different_background_color_other_than_black">How can I have a different background color other than black?</a></h2>
<div class="level2">
@@ -527,7 +527,7 @@ A dark background is preferred by many users.
</p>
</div>
-<!-- SECTION "How can I have a different background color other than black?" [16562-17597] -->
+<!-- SECTION "How can I have a different background color other than black?" [16433-17468] -->
<h2><a name="each_time_i_start_gschem_the_log_message_window_is_shown._can_i_disable_it" id="each_time_i_start_gschem_the_log_message_window_is_shown._can_i_disable_it">Each time I start gschem, the log message window is shown. Can I disable it?</a></h2>
<div class="level2">
@@ -552,12 +552,12 @@ Comment out the <strong><code>startup</code></strong> line (with a ;) and commen
<pre class="code">(log-window "later")</pre>
</div>
-<!-- SECTION "Each time I start gschem, the log message window is shown. Can I disable it?" [17598-18260] -->
+<!-- SECTION "Each time I start gschem, the log message window is shown. Can I disable it?" [17469-18131] -->
<h1><a name="printing_output" id="printing_output">Printing/Output</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Printing/Output" [18261-18290] -->
+<!-- SECTION "Printing/Output" [18132-18161] -->
<h2><a name="how_do_i_print_schematics_from_the_command_line" id="how_do_i_print_schematics_from_the_command_line">How do I print schematics from the command line?</a></h2>
<div class="level2">
@@ -588,7 +588,7 @@ do
done</pre>
</div>
-<!-- SECTION "How do I print schematics from the command line?" [18291-19288] -->
+<!-- SECTION "How do I print schematics from the command line?" [18162-19159] -->
<h2><a name="how_can_i_get_color_postscript_png_output" id="how_can_i_get_color_postscript_png_output">How can I get color postscript/PNG output?</a></h2>
<div class="level2">
@@ -617,7 +617,7 @@ The 255 255 255 are the RGB components for the background color of the <acronym
</p>
</div>
-<!-- SECTION "How can I get color postscript/PNG output?" [19289-20420] -->
+<!-- SECTION "How can I get color postscript/PNG output?" [19160-20291] -->
<h2><a name="how_can_i_get_black_and_white_postscript_png_output" id="how_can_i_get_black_and_white_postscript_png_output">How can I get black and white postscript/PNG output?</a></h2>
<div class="level2">
@@ -632,7 +632,7 @@ For black and white <acronym title="Portable Network Graphics">PNG</acronym> ima
<pre class="code">(image-color "disabled") ; for monochromoe PNG output</pre>
</div>
-<!-- SECTION "How can I get black and white postscript/PNG output?" [20421-20786] -->
+<!-- SECTION "How can I get black and white postscript/PNG output?" [20292-20657] -->
<h2><a name="how_can_i_insert_schematics_into_my_latex_document" id="how_can_i_insert_schematics_into_my_latex_document">How can I insert schematics into my LaTex document?</a></h2>
<div class="level2">
<ol>
@@ -656,7 +656,7 @@ For black and white <acronym title="Portable Network Graphics">PNG</acronym> ima
\end{document}</pre>
</div>
-<!-- SECTION "How can I insert schematics into my LaTex document?" [20787-21355] -->
+<!-- SECTION "How can I insert schematics into my LaTex document?" [20658-21226] -->
<h2><a name="how_can_i_split_postscript_output_over_multiple_pages" id="how_can_i_split_postscript_output_over_multiple_pages">How can I split Postscript output over multiple pages?</a></h2>
<div class="level2">
@@ -665,12 +665,12 @@ gschem does not provide this functionality internally, however there is a progra
</p>
</div>
-<!-- SECTION "How can I split Postscript output over multiple pages?" [21356-21699] -->
+<!-- SECTION "How can I split Postscript output over multiple pages?" [21227-21570] -->
<h1><a name="gschem_installation_run-time_problems" id="gschem_installation_run-time_problems">Gschem installation/run-time problems</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Gschem installation/run-time problems" [21700-21752] -->
+<!-- SECTION "Gschem installation/run-time problems" [21571-21623] -->
<h2><a name="gschem_segfaults_when_i_delete_components_on_fc5_and_other_linux_distributions_is_there_a_work-around" id="gschem_segfaults_when_i_delete_components_on_fc5_and_other_linux_distributions_is_there_a_work-around">Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?</a></h2>
<div class="level2">
@@ -693,7 +693,7 @@ csh:
<pre class="code">setenv G_SLICE always-malloc</pre>
</div>
-<!-- SECTION "Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?" [21753-22407] -->
+<!-- SECTION "Gschem segfaults when I delete components on FC5 (and other Linux distributions)! Is there a work-around?" [21624-22278] -->
<h2><a name="after_installation_gschem_does_not_work_what_could_be_wrong" id="after_installation_gschem_does_not_work_what_could_be_wrong">After installation gschem does not work!? What could be wrong?</a></h2>
<div class="level2">
@@ -731,7 +731,7 @@ Also, some older releases of gEDA/gaf had some bugs when the rc files were insta
</p>
</div>
-<!-- SECTION "After installation gschem does not work!? What could be wrong?" [22408-24331] -->
+<!-- SECTION "After installation gschem does not work!? What could be wrong?" [22279-24202] -->
<h2><a name="add_components_offers_no_symbols_what_can_i_do_about_it" id="add_components_offers_no_symbols_what_can_i_do_about_it">"Add Components" offers no symbols! What can I do about it?</a></h2>
<div class="level2">
@@ -763,7 +763,7 @@ All of these config files may or may not append paths to the library search list
</p>
</div>
-<!-- SECTION "Add Components offers no symbols! What can I do about it?" [24332-25135] -->
+<!-- SECTION "Add Components offers no symbols! What can I do about it?" [24203-25006] -->
<h2><a name="i_m_using_gschem_gaf_through_a_ssh_connection_and_i_get_an_error_likexlibextension_render_missing_on_display_localhost10.0" id="i_m_using_gschem_gaf_through_a_ssh_connection_and_i_get_an_error_likexlibextension_render_missing_on_display_localhost10.0">I'm using gschem/gaf through a SSH connection and I get an error like: 'Xlib: extension "RENDER" missing on display "localhost:10.0".'</a></h2>
<div class="level2">
@@ -782,6 +782,6 @@ The latter enables trusted X11 forwarding.
</p>
</div>
-<!-- SECTION "I'm using gschem/gaf through a SSH connection and I get an error like: 'Xlib: extension RENDER missing on display localhost:10.0.'" [25136-] --></div>
+<!-- SECTION "I'm using gschem/gaf through a SSH connection and I get an error like: 'Xlib: extension RENDER missing on display localhost:10.0.'" [25007-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_faq-pcb.html b/docs/wiki/geda_faq-pcb.html
index 9da78f9..23a0f43 100644
--- a/docs/wiki/geda_faq-pcb.html
+++ b/docs/wiki/geda_faq-pcb.html
@@ -7,7 +7,7 @@
<title>geda:faq-pcb</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-25T11:22:57-0400" />
+<meta name="date" content="2007-07-25T08:31:46-0400" />
<meta name="keywords" content="geda,faq-pcb" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -22,6 +22,29 @@
</head>
<body>
<div class="dokuwiki export">
+<div class="toc">
+<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
+<div id="toc__inside">
+
+<ul class="toc">
+<li class="clear">
+
+<ul class="toc">
+<li class="level2"><div class="li"><span class="li"><a href="#pcb_faq" class="toc">pcb FAQ</a></span></div>
+<ul class="toc">
+<li class="level3"><div class="li"><span class="li"><a href="#what_is_pcb" class="toc">What is pcb ?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#how_do_i_install_pcb" class="toc">How do I install pcb?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#is_it_true_that_pcb_is_limited_to_exactly_8_copper_layers_and_2_silkscreen_layers" class="toc">Is it true that pcb is limited to exactly 8 copper layers and 2 silkscreen layers?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#is_it_true_that_pcb_has_no_concept_of_a_solder_mask_or_paste_mask_layer" class="toc">Is it true that pcb has no concept of a "solder mask" or "paste mask" layer?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#is_it_true_that_pcb_has_no_way_to_make_a_mechanical_layer_to_show_the_physical_outline_of_the_board_and_its_dimensions" class="toc">Is it true that pcb has no way to make a "mechanical layer" to show the physical outline of the board and its dimensions ?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#how_do_i_design_a_pcb" class="toc">How do I design a PCB?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#yes_but_how_do_i_design_a_pcb_with_pcb" class="toc">Yes, but how do I design a PCB with pcb?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#what_about_footprints" class="toc">What about footprints?</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#i_had_a_hard_time_to_find_info_on_pcb_due_its_ambigous_name._why_don_t_you_rename_the_app" class="toc">I had a hard time to find info on pcb due its ambigous name. Why don't you rename the app?</a></span></div></li></ul>
+</li></ul>
+</li></ul>
+</div>
+</div>
@@ -29,57 +52,57 @@
<div class="level2">
</div>
-
-<h4><a name="what_is_pcb" id="what_is_pcb">What is pcb ?</a></h4>
-<div class="level4">
+<!-- SECTION "pcb FAQ" [1-21] -->
+<h3><a name="what_is_pcb" id="what_is_pcb">What is pcb ?</a></h3>
+<div class="level3">
<p>
â??pcbâ?? is software to help you draw (â??lay outâ??) the wires for a custom â??printed wire boardâ?? (â??PCBâ??).
</p>
</div>
-
-<h4><a name="how_do_i_install_pcb" id="how_do_i_install_pcb">How do I install pcb ?</a></h4>
-<div class="level4">
+<!-- SECTION "What is pcb ?" [22-147] -->
+<h3><a name="how_do_i_install_pcb" id="how_do_i_install_pcb">How do I install pcb?</a></h3>
+<div class="level3">
<p>
- The recommended way to install pcb is to install the complete gaf package. See <a href="http://geda.seul.org/wiki/geda:installation"; class="wikilink1" title="geda:installation">installation</a>.
+The recommended way to install pcb is to install the complete gaf package. See <a href="http://geda.seul.org/wiki/geda:installation"; class="wikilink1" title="geda:installation">installation</a>.
</p>
</div>
-
-<h4><a name="is_it_true_that_pcb_is_limited_to_exactly_8_copper_layers_and_2_silkscreen_layers" id="is_it_true_that_pcb_is_limited_to_exactly_8_copper_layers_and_2_silkscreen_layers">Is it true that pcb is limited to exactly 8 copper layers and 2 silkscreen layers ?</a></h4>
-<div class="level4">
+<!-- SECTION "How do I install pcb?" [148-282] -->
+<h3><a name="is_it_true_that_pcb_is_limited_to_exactly_8_copper_layers_and_2_silkscreen_layers" id="is_it_true_that_pcb_is_limited_to_exactly_8_copper_layers_and_2_silkscreen_layers">Is it true that pcb is limited to exactly 8 copper layers and 2 silkscreen layers?</a></h3>
+<div class="level3">
<p>
- No. â??Out-of-the-boxâ??, pcb supports 16 copper layers and …
+No. â??Out-of-the-boxâ??, pcb supports 16 copper layers and …
</p>
</div>
-
-<h4><a name="is_it_true_that_pcb_has_no_concept_of_a_solder_mask_or_paste_mask_layer" id="is_it_true_that_pcb_has_no_concept_of_a_solder_mask_or_paste_mask_layer">Is it true that pcb has no concept of a "solder mask" or "paste mask" layer?</a></h4>
-<div class="level4">
+<!-- SECTION "Is it true that pcb is limited to exactly 8 copper layers and 2 silkscreen layers?" [283-436] -->
+<h3><a name="is_it_true_that_pcb_has_no_concept_of_a_solder_mask_or_paste_mask_layer" id="is_it_true_that_pcb_has_no_concept_of_a_solder_mask_or_paste_mask_layer">Is it true that pcb has no concept of a "solder mask" or "paste mask" layer?</a></h3>
+<div class="level3">
<p>
- No.
+No.
</p>
</div>
-
-<h4><a name="is_it_true_that_pcb_has_no_way_to_make_a_mechanical_layer_to_show_the_physical_outline_of_the_board_and_its_dimensions" id="is_it_true_that_pcb_has_no_way_to_make_a_mechanical_layer_to_show_the_physical_outline_of_the_board_and_its_dimensions">Is it true that pcb has no way to make a "mechanical layer" to show the physical outline of the board and its dimensions ?</a></h4>
-<div class="level4">
+<!-- SECTION "Is it true that pcb has no concept of a solder mask or paste mask layer?" [437-528] -->
+<h3><a name="is_it_true_that_pcb_has_no_way_to_make_a_mechanical_layer_to_show_the_physical_outline_of_the_board_and_its_dimensions" id="is_it_true_that_pcb_has_no_way_to_make_a_mechanical_layer_to_show_the_physical_outline_of_the_board_and_its_dimensions">Is it true that pcb has no way to make a "mechanical layer" to show the physical outline of the board and its dimensions ?</a></h3>
+<div class="level3">
<p>
- No.
+No. Lines on a layer with layer name <code>outline</code> will be interpreted as physical edges of the board. Also see <a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">this note</a> in the more comprehensive <a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">pcb_tips</a>
</p>
</div>
-
-<h4><a name="how_do_i_design_a_pcb" id="how_do_i_design_a_pcb">How do I design a PCB ?</a></h4>
-<div class="level4">
+<!-- SECTION "Is it true that pcb has no way to make a mechanical layer to show the physical outline of the board and its dimensions ?" [529-915] -->
+<h3><a name="how_do_i_design_a_pcb" id="how_do_i_design_a_pcb">How do I design a PCB?</a></h3>
+<div class="level3">
<p>
- This is well beyond the scope of this <acronym title="Frequently Asked Questions">FAQ</acronym>. There are a few tips at
+This is well beyond the scope of this <acronym title="Frequently Asked Questions">FAQ</acronym>. There are a few tips at
</p>
<ul>
<li class="level1"><div class="li"> <a href="http://en.wikipedia.org/wiki/Printed_circuit_board"; class="urlextern" title="http://en.wikipedia.org/wiki/Printed_circuit_board"; rel="nofollow">http://en.wikipedia.org/wiki/Printed_circuit_board</a></div>
@@ -89,32 +112,41 @@
</ul>
</div>
-
-<h4><a name="yes_but_how_do_i_design_a_pcb_with_pcb" id="yes_but_how_do_i_design_a_pcb_with_pcb">Yes, but how do I design a PCB with pcb ?</a></h4>
-<div class="level4">
+<!-- SECTION "How do I design a PCB?" [916-1137] -->
+<h3><a name="yes_but_how_do_i_design_a_pcb_with_pcb" id="yes_but_how_do_i_design_a_pcb_with_pcb">Yes, but how do I design a PCB with pcb?</a></h3>
+<div class="level3">
<p>
- Generally, you start with a schematic, run gsch2pcb to generate the netlist. See <a href="http://geda.seul.org/wiki/geda:faq-gsch2pcb"; class="wikilink1" title="geda:faq-gsch2pcb">faq-gsch2pcb</a>. Then you might go through the tutorial <a href="geda_gsch2pcb_tutorial.html" class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a>
+Generally, you start with a schematic, run gsch2pcb to generate the netlist. See <a href="http://geda.seul.org/wiki/geda:faq-gsch2pcb"; class="wikilink1" title="geda:faq-gsch2pcb">faq-gsch2pcb</a>. Then you might go through the tutorial <a href="geda_gsch2pcb_tutorial.html" class="wikilink1" title="geda:gsch2pcb_tutorial">gsch2pcb_tutorial</a>
</p>
<p>
-Then you … Hey, did you know about the pcb manual, the <a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">pcb_tips</a>, and the <a href="geda_pcb-quick_reference.html" class="wikilink1" title="geda:pcb-quick_reference">pcb-quick_reference</a> ?
+Then you … Hey, did you know about the pcb manual, the <a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">pcb_tips</a>, and the <a href="geda_pcb-quick_reference.html" class="wikilink1" title="geda:pcb-quick_reference">pcb-quick_reference</a>?
</p>
</div>
+<!-- SECTION "Yes, but how do I design a PCB with pcb?" [1138-1454] -->
+<h3><a name="what_about_footprints" id="what_about_footprints">What about footprints?</a></h3>
+<div class="level3">
-<h4><a name="what_about_footprints" id="what_about_footprints">What about footprints ?</a></h4>
-<div class="level4">
+<p>
+See <a href="geda_pcb_footprints.html" class="wikilink1" title="geda:pcb_footprints">pcb_footprints</a>.
+</p>
<p>
- Yes. <a href="geda_pcb_footprints.html" class="wikilink1" title="geda:pcb_footprints">pcb_footprints</a>.
+There are also some unofficial gEDA footprints at Open Circuits <a href="http://opencircuits.com/PCB_Footprints"; class="urlextern" title="http://opencircuits.com/PCB_Footprints"; rel="nofollow">http://opencircuits.com/PCB_Footprints</a>.
</p>
+</div>
+<!-- SECTION "What about footprints?" [1455-1617] -->
+<h3><a name="i_had_a_hard_time_to_find_info_on_pcb_due_its_ambigous_name._why_don_t_you_rename_the_app" id="i_had_a_hard_time_to_find_info_on_pcb_due_its_ambigous_name._why_don_t_you_rename_the_app">I had a hard time to find info on pcb due its ambigous name. Why don't you rename the app?</a></h3>
+<div class="level3">
+
<p>
-There are also some unofficial gEDA footprints at Open Circuits <a href="http://opencircuits.com/PCB_Footprints"; class="urlextern" title="http://opencircuits.com/PCB_Footprints"; rel="nofollow">http://opencircuits.com/PCB_Footprints</a> .
+The application is a fairly old project, with roots way back in the era of <a href="http://en.wikipedia.org/wiki/Atari"; class="urlextern" title="http://en.wikipedia.org/wiki/Atari"; rel="nofollow">Atari home computers</a>. Its name has always been â??pcbâ??. The current developers have no intention to break that tradition.
</p>
</div>
-<!-- SECTION "pcb FAQ" [2-] --></div>
+<!-- SECTION "I had a hard time to find info on pcb due its ambigous name. Why don't you rename the app?" [1618-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_fedora_rpm_installation.html b/docs/wiki/geda_fedora_rpm_installation.html
index 2985d41..bf30cfc 100644
--- a/docs/wiki/geda_fedora_rpm_installation.html
+++ b/docs/wiki/geda_fedora_rpm_installation.html
@@ -7,7 +7,7 @@
<title>geda:fedora_rpm_installation</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:27-0400" />
+<meta name="date" content="2007-07-14T16:52:08-0400" />
<meta name="keywords" content="geda,fedora_rpm_installation" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -27,14 +27,14 @@
<div id="toc__inside">
<ul class="toc">
-<li class="level1"><div class="li"><span class="li"><a href="#installing_geda_rpm_packages_on_fedora_and_redhat" class="toc">Installing gEDA rpm packages on Fedora and RedHat</a></span></div>
+<li class="level1"><div class="li"><span class="li"><a href="#installing_geda_rpm_packages_on_fedora" class="toc">Installing gEDA rpm packages on Fedora</a></span></div>
<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#installing_rpm_packages_from_fedora_core_extra" class="toc">Installing rpm packages from Fedora Core Extra</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#distribution_specific_notes" class="toc">Distribution specific notes</a></span></div>
+<li class="level2"><div class="li"><span class="li"><a href="#geda_gaf_for_fedora" class="toc">gEDA/gaf for fedora</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_to_install_geda_gaf_on_fedora" class="toc">How to install gEDA/gaf on Fedora</a></span></div>
<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#fedora_core_4" class="toc">Fedora Core 4</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#fedora_core_5" class="toc">Fedora Core 5</a></span></div></li>
-<li class="level3"><div class="li"><span class="li"><a href="#fedora_core_6" class="toc">Fedora Core 6</a></span></div></li></ul>
+<li class="level3"><div class="li"><span class="li"><a href="#the_easiest_way" class="toc">The easiest way</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#compile_it_yourself" class="toc">Compile it yourself</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#rebuild_your_own_rpms" class="toc">Rebuild your own rpms</a></span></div></li></ul>
</li></ul>
</li></ul>
</div>
@@ -42,51 +42,276 @@
-<h1><a name="installing_geda_rpm_packages_on_fedora_and_redhat" id="installing_geda_rpm_packages_on_fedora_and_redhat">Installing gEDA rpm packages on Fedora and RedHat</a></h1>
+<h1><a name="installing_geda_rpm_packages_on_fedora" id="installing_geda_rpm_packages_on_fedora">Installing gEDA rpm packages on Fedora</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Installing gEDA rpm packages on Fedora and RedHat" [1-65] -->
-<h2><a name="installing_rpm_packages_from_fedora_core_extra" id="installing_rpm_packages_from_fedora_core_extra">Installing rpm packages from Fedora Core Extra</a></h2>
+<!-- SECTION "Installing gEDA rpm packages on Fedora" [1-54] -->
+<h2><a name="geda_gaf_for_fedora" id="geda_gaf_for_fedora">gEDA/gaf for fedora</a></h2>
<div class="level2">
<p>
- The Fedora Extras repository is enabled by default in Fedora Core 6 and later versions, so the gEDA suite can easily be installed without any further configuration required.
+ gEDA/gaf applications are available for free download
</p>
+<ul>
+<li class="level1"><div class="li"> on fedora official mirrors maintained by Chitlesh Goorah</div>
+</li>
+<li class="level1"><div class="li"> and on Wojciech Kazubskiâ??s <a href="http://www.sp5pbe.waw.pl/~sp5smk/software.html"; class="urlextern" title="http://www.sp5pbe.waw.pl/~sp5smk/software.html"; rel="nofollow"> website </a></div>
+</li>
+</ul>
+
+<p>
+ Each gEDA/gaf release is supposed to be on the fedora collection in one or two days time until the fedora mirrors are synced.
+</p>
+
+<p>
+The Fedora Project provides gEDA/gaf releases
+</p>
+<ul>
+<li class="level1"><div class="li"> Fedora Core 5</div>
+</li>
+<li class="level1"><div class="li"> Fedora Core 6 (Zod)</div>
+</li>
+<li class="level1"><div class="li"> Fedora 7 (moonshine)</div>
+</li>
+<li class="level1"><div class="li"> Fedora development (rawhide)</div>
+</li>
+</ul>
+
+<p>
+under the following architectures:
+</p>
+<ul>
+<li class="level1"><div class="li"> i386</div>
+</li>
+<li class="level1"><div class="li"> x86_64</div>
+</li>
+<li class="level1"><div class="li"> ppc</div>
+</li>
+<li class="level1"><div class="li"> ppc64 (as from F7)</div>
+</li>
+</ul>
<p>
-Detailed instructions TBD
+ The Fedora Project will <strong>perhaps</strong> even provide gEDA/gaf releases for sparc and alpha machines when F8 will be released.(it is still not yet confirmed.)
</p>
</div>
-<!-- SECTION "Installing rpm packages from Fedora Core Extra" [66-327] -->
-<h2><a name="distribution_specific_notes" id="distribution_specific_notes">Distribution specific notes</a></h2>
+<!-- SECTION "gEDA/gaf for fedora" [55-823] -->
+<h2><a name="how_to_install_geda_gaf_on_fedora" id="how_to_install_geda_gaf_on_fedora">How to install gEDA/gaf on Fedora</a></h2>
<div class="level2">
+</div>
+<!-- SECTION "How to install gEDA/gaf on Fedora" [824-870] -->
+<h3><a name="the_easiest_way" id="the_easiest_way">The easiest way</a></h3>
+<div class="level3">
+
+<p>
+ It is recommended to install gEDA/gaf releases on Fedora via yum or pirut. Pirut, also known under the name of â??Add/Remove Softwareâ??, is a graphical interface for yum.
+</p>
+
+<p>
+<code><strong>yum install geda-gschem geda-docs geda-examples geda-gattrib geda-gsymcheck geda-gnetlist geda-utils pcb gerbv</strong></code>
+</p>
+
+<p>
+Note: you have to be under root (su -) to install packages.
+</p>
+
+<p>
+A Fedora user will have every gEDA/gaf release which provides bug fixes and enhancement upon old releases in one or two days until the mirrors are synced.
+</p>
+
<p>
-Each distribution version has itâ??s own issues. Please read and enhance the notes below.
+If it is not the case, you can kindly file a bug report (Request for Enhancement, RFE) on <a href="http://bugzilla.redhat.com/"; class="urlextern" title="http://bugzilla.redhat.com"; rel="nofollow">Fedora's bugzilla</a> asking them to update gEDA/gaf for you.
+</p>
+
+<p>
+One can follow up
+</p>
+<ul>
+<li class="level1"><div class="li"> the releases on <a href="http://clunixchit.blogspot.com/"; class="urlextern" title="http://clunixchit.blogspot.com"; rel="nofollow">Chitlesh Goorah's blog</a>, or</div>
+</li>
+<li class="level1"><div class="li"> the gEDA/gaf build times on <a href="http://koji.fedoraproject.org/koji/builds?userID=159"; class="urlextern" title="http://koji.fedoraproject.org/koji/builds?userID=159"; rel="nofollow">Fedora's build system</a></div>
+</li>
+</ul>
+
+<p>
+ Note: As from 29th of June 2007, Fedora Core 5 has been marked as End Of Life (<acronym title="End of file">EOF</acronym>). gEDA/gaf 1.0.1-20070626 is the last update on FC5.
</p>
</div>
-<!-- SECTION "Distribution specific notes" [328-458] -->
-<h3><a name="fedora_core_4" id="fedora_core_4">Fedora Core 4</a></h3>
+<!-- SECTION "The easiest way" [871-1933] -->
+<h3><a name="compile_it_yourself" id="compile_it_yourself">Compile it yourself</a></h3>
<div class="level3">
+<p>
+ If one want to get their hands dirty by building gEDA/gaf on Fedora, he/she will need
+</p>
+
+<p>
+libstroke-devel, groff, autoconf, gtk2-devel, gd-devel, gettext-devel and guile-devel installed.
+</p>
+
+<p>
+They can be installed via yum:
+</p>
+
+<p>
+<code> <strong> yum install libstroke-devel groff autoconf gtk2-devel gd-devel gettext-devel and guile-devel </strong> </code>
+</p>
+
+<p>
+The recommended procedure is to compile and install (one by one):
+</p>
+<ol>
+<li class="level1"><div class="li"> libgeda</div>
+</li>
+<li class="level1"><div class="li"> geda-symbols</div>
+</li>
+<li class="level1"><div class="li"> geda-docs</div>
+</li>
+<li class="level1"><div class="li"> geda-examples</div>
+</li>
+<li class="level1"><div class="li"> geda-gschem</div>
+</li>
+<li class="level1"><div class="li"> geda-gattrib</div>
+</li>
+<li class="level1"><div class="li"> geda-gnetlist</div>
+</li>
+<li class="level1"><div class="li"> geda-gsymcheck</div>
+</li>
+<li class="level1"><div class="li"> geda-utils</div>
+</li>
+</ol>
+
+<p>
+ Note: Fedora Core 5 has guile 1.6.x whereas Fedora Core 6 and onwards has guile 1.8.x
+</p>
+
</div>
-<!-- SECTION "Fedora Core 4" [459-483] -->
-<h3><a name="fedora_core_5" id="fedora_core_5">Fedora Core 5</a></h3>
+<!-- SECTION "Compile it yourself" [1934-2588] -->
+<h3><a name="rebuild_your_own_rpms" id="rebuild_your_own_rpms">Rebuild your own rpms</a></h3>
<div class="level3">
+<p>
+ The Fedora Project provides simple tools for one to rebuild any RPMs from SRPMs. SRPM contains the upstream sources, the <acronym title="specification">spec</acronym> file and the patches if any.
+</p>
+
+<p>
+To be able to build RPMs, one will need a build platform, which does <strong>NOT</strong> require root access. rpmdevtools provides the requires tools to do so.
+</p>
+
+<p>
+<code><strong>yum install rpmdevtools</strong></code> (as root)
+</p>
+
</div>
-<!-- SECTION "Fedora Core 5" [484-508] -->
-<h3><a name="fedora_core_6" id="fedora_core_6">Fedora Core 6</a></h3>
-<div class="level3">
+
+<h4><a name="build_platform" id="build_platform">Build Platform</a></h4>
+<div class="level4">
+
+<p>
+ The build platform should be built under a NON-root account.
+</p>
+
+<p>
+<code>$ <strong>fedora-buildrpmtree</strong></code>
+</p>
+
+<p>
+You can see a <code>rpmbuild</code> folder under your $HOME directory. This directory will be your build platform.
+</p>
+
+</div>
+
+<h4><a name="how_to_get_srpms" id="how_to_get_srpms">How to get SRPMs</a></h4>
+<div class="level4">
+
+<p>
+ Fedora provides SRPM of every package it has. You can download those SRPMs via <code>yumdownloader</code> from the yum-utils package.
+</p>
+
+<p>
+<code> <strong> yum install yum-utils </strong> </code> (as root, if you donâ??t have yum-utils installed)
+</p>
+
+<p>
+ Download a particular SRPM (under a NON-root account) by <code>$ <strong>yumdownloader –source package –enablerepo=development-source</strong> </code>
+</p>
+
+<p>
+package is the name of the package you want to download.
+</p>
+
+<p>
+Once the download is complete the package can be found under the current directory under the filename %{name}-%{version}-%{dist}.src.rpm.
+</p>
+
+<p>
+Since a SRPM contains the upstream sources, the <acronym title="specification">spec</acronym> file and the patches if any we will extract them with:
+</p>
+
+<p>
+<code>$ <strong>rpm -ivh %{name}-%{version}-%{dist}.src.rpm</strong></code>
+</p>
+
+<p>
+(I remind you that this should at no cost be executed as root !)
+</p>
+
+<p>
+You will see
+</p>
+<ul>
+<li class="level1"><div class="li"> <acronym title="specification">spec</acronym> files will be installed in rpmbuild/SPECS</div>
+</li>
+<li class="level1"><div class="li"> sources, patches and desktop files will be installed in rpmbuild/SOURCES</div>
+</li>
+</ul>
+
+</div>
+
+<h4><a name="building_new_rpms_from_new_sources" id="building_new_rpms_from_new_sources">Building new RPMS from new sources</a></h4>
+<div class="level4">
+<ul>
+<li class="level1"><div class="li"> download your new sources</div>
+</li>
+<li class="level1"><div class="li"> edit the rpmbuild/SPECS/%{name}.<acronym title="specification">spec</acronym></div>
<ul>
-<li class="level1"><div class="li"> <strong>guile 1.8.x problems:</strong> Fedora Core 6 has a guile version 1.8.x. This causes errors when placing pins or using gnetlist. Try to install guile version 1.6.7 instead.</div>
+<li class="level3"><div class="li"> edit version tag</div>
+</li>
+<li class="level3"><div class="li"> edit release tag</div>
</li>
</ul>
+</li>
+</ul>
+
+<p>
+with repect to your newly downloaded sources.
+</p>
+
+<p>
+<code><strong> cd rpmbuild/SPECS/ </strong></code>
+</p>
+
+<p>
+now start building the RPMS:
+</p>
+
+<p>
+<code> <strong> rpmbuild -ba %{name}.<acronym title="specification">spec</acronym></strong></code>
+</p>
+
+<p>
+replace %{name} by the name of the package (example, libgeda, geda-gschem…).
+</p>
+
+<p>
+The successfully build RPMS will be found in the folders of ~/rpmbuild/RPMS/.
+</p>
</div>
-<!-- SECTION "Fedora Core 6" [509-] --></div>
+<!-- SECTION "Rebuild your own rpms" [2589-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_file_format_spec.html b/docs/wiki/geda_file_format_spec.html
index 6cb74c5..ab0404e 100644
--- a/docs/wiki/geda_file_format_spec.html
+++ b/docs/wiki/geda_file_format_spec.html
@@ -7,7 +7,7 @@
<title>geda:file_format_spec</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-06-26T23:36:31-0400" />
+<meta name="date" content="2007-07-08T20:51:33-0400" />
<meta name="keywords" content="geda,file_format_spec" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -154,7 +154,7 @@ A schematic/symbol file for gEDA/gaf consists of:
</p>
</div>
-<!-- SECTION "Object types" [2241-3506] -->
+<!-- SECTION "Object types" [2241-3508] -->
<h3><a name="version" id="version">version</a></h3>
<div class="level3">
@@ -195,7 +195,9 @@ Valid in: Schematic and Symbol files<br/>
</li>
<li class="level1"><div class="li"> fileformat version is just an integer with no minor number.</div>
</li>
-<li class="level1"><div class="li"> Valid versions include: 19990601, 19990610, 19990705, 19990829, 19990919, 19991011, 20000220, 20000704, 20001006, 20001217, 20010304, 20010708, 20010722, 20020209, 20020414, 20020527, 20020825, 20021103, 20030223, 20030525, 20030901, 20040111, 20040710, 20041228, 20050313, 20050820, 20060123, 20060824, 20060906, 20061020, 20070216, 20070526, 20070626</div>
+<li class="level1"><div class="li"> Development versions include: 19990601, 19990610, 19990705, 19990829, 19990919, 19991011, 20000220, 20000704, 20001006, 20001217, 20010304, 20010708, 20010722, 20020209, 20020414, 20020527, 20020825, 20021103, 20030223, 20030525, 20030901, 20040111, 20040710, 20041228, 20050313, 20050820, 20060123, 20060824, 20060906, 20061020, 20070216, 20070705, 20070708</div>
+</li>
+<li class="level1"><div class="li"> Stable versions include: 20070526, 20070626</div>
</li>
<li class="level1"><div class="li"> <acronym title="Concurrent Versions System">CVS</acronym> or test versions (should not be used): 20030921, 20031004, 20031019, 20031231, 20050814</div>
</li>
@@ -210,7 +212,7 @@ Valid in: Schematic and Symbol files<br/>
<pre class="code">v 20040111 1</pre>
</div>
-<!-- SECTION "version" [3507-5301] -->
+<!-- SECTION "version" [3509-5357] -->
<h3><a name="line" id="line">line</a></h3>
<div class="level3">
@@ -298,7 +300,7 @@ A line segment from (23000, 69000) to (28000, 69000) with color index 3, 40 mils
</p>
</div>
-<!-- SECTION "line" [5302-6536] -->
+<!-- SECTION "line" [5358-6592] -->
<h3><a name="picture" id="picture">picture</a></h3>
<div class="level3">
@@ -408,7 +410,7 @@ A picture object with the lower left corner at (16900, 35800). The width of the
</p>
</div>
-<!-- SECTION "picture" [6537-9330] -->
+<!-- SECTION "picture" [6593-9386] -->
<h3><a name="box" id="box">box</a></h3>
<div class="level3">
@@ -537,7 +539,7 @@ A box with the lower left hand corner at (33000, 67300) and a width and height o
</p>
</div>
-<!-- SECTION "box" [9331-11537] -->
+<!-- SECTION "box" [9387-11593] -->
<h3><a name="circle" id="circle">circle</a></h3>
<div class="level3">
@@ -653,7 +655,7 @@ A circle with the center at (38000, 67000) and a radius of 900 mils, color index
</p>
</div>
-<!-- SECTION "circle" [11538-13663] -->
+<!-- SECTION "circle" [11594-13719] -->
<h3><a name="arc" id="arc">arc</a></h3>
<div class="level3">
@@ -749,7 +751,7 @@ dashlength dashspace</code></strong>
</p>
</div>
-<!-- SECTION "arc" [13664-15179] -->
+<!-- SECTION "arc" [13720-15235] -->
<h3><a name="text" id="text">text</a></h3>
<div class="level3">
@@ -883,7 +885,7 @@ This is a similar text object as the above example, however here there are five
</p>
</div>
-<!-- SECTION "text" [15180-17833] -->
+<!-- SECTION "text" [15236-17889] -->
<h3><a name="net" id="net">net</a></h3>
<div class="level3">
@@ -932,7 +934,7 @@ A net segment from (12700, 29400) to (32900, 29400) with color index 4.
</p>
</div>
-<!-- SECTION "net" [17834-18359] -->
+<!-- SECTION "net" [17890-18415] -->
<h3><a name="bus" id="bus">bus</a></h3>
<div class="level3">
@@ -988,7 +990,7 @@ A bus segment from (27300, 37400) to (27300, 35300) with color index 3 and no ne
</p>
</div>
-<!-- SECTION "bus" [18360-19291] -->
+<!-- SECTION "bus" [18416-19347] -->
<h3><a name="pin" id="pin">pin</a></h3>
<div class="level3">
@@ -1055,7 +1057,7 @@ A pin from (0, 200) to (200, 200) with color index 1, a regular pin, and the fir
</p>
</div>
-<!-- SECTION "pin" [19292-20288] -->
+<!-- SECTION "pin" [19348-20344] -->
<h3><a name="component" id="component">component</a></h3>
<div class="level3">
@@ -1117,7 +1119,7 @@ A component whoâ??s origin is at (18600,19900), is selectable, not rotated, not
</p>
</div>
-<!-- SECTION "component" [20289-21292] -->
+<!-- SECTION "component" [20345-21348] -->
<h3><a name="font" id="font">font</a></h3>
<div class="level3">
@@ -1160,7 +1162,7 @@ The above font definition is for the space character.
</p>
</div>
-<!-- SECTION "font" [21293-21813] -->
+<!-- SECTION "font" [21349-21869] -->
<h2><a name="colors" id="colors">Colors</a></h2>
<div class="level2">
@@ -1229,7 +1231,7 @@ In the gEDA/gaf schematic and symbol file format colors are specified via an int
</p>
</div>
-<!-- SECTION "Colors" [21814-22685] -->
+<!-- SECTION "Colors" [21870-22741] -->
<h2><a name="attributes" id="attributes">Attributes</a></h2>
<div class="level2">
@@ -1251,7 +1253,7 @@ The object is a pin which has an attribute pinnumber=3 and pinseq=3 (name=value)
</p>
</div>
-<!-- SECTION "Attributes" [22686-23673] -->
+<!-- SECTION "Attributes" [22742-23729] -->
<h2><a name="embedded_components" id="embedded_components">Embedded Components</a></h2>
<div class="level2">
@@ -1270,7 +1272,7 @@ In the example above, <strong>555-1.sym</strong> is the component. The EMBEDDED
</p>
</div>
-<!-- SECTION "Embedded Components" [23674-24433] -->
+<!-- SECTION "Embedded Components" [23730-24489] -->
<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
<div class="level2">
<table class="inline">
@@ -1289,6 +1291,6 @@ In the example above, <strong>555-1.sym</strong> is the component. The EMBEDDED
</table>
</div>
-<!-- SECTION "Document Revision History" [24434-] --></div>
+<!-- SECTION "Document Revision History" [24490-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_gsch2pcb_tutorial.html b/docs/wiki/geda_gsch2pcb_tutorial.html
index edcf76a..49135e3 100644
--- a/docs/wiki/geda_gsch2pcb_tutorial.html
+++ b/docs/wiki/geda_gsch2pcb_tutorial.html
@@ -7,7 +7,7 @@
<title>geda:gsch2pcb_tutorial</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-06-27T08:12:11-0400" />
+<meta name="date" content="2007-08-04T14:46:19-0400" />
<meta name="keywords" content="geda,gsch2pcb_tutorial" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -42,8 +42,8 @@
</li>
<li class="level2"><div class="li"><span class="li"><a href="#modifying_schematics" class="toc">Modifying Schematics</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#custom_gschem_symbols" class="toc">Custom gschem Symbols</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#custom_file_elements" class="toc">Custom //file elements//</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#custom_m4_elements_requires_gsch2pcb_1.0" class="toc">Custom //m4 elements// (Requires gsch2pcb >= 1.0)</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#custom_file_elements" class="toc">Custom file elements</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#custom_m4_elements_requires_gsch2pcb_1.0" class="toc">Custom m4 elements (Requires gsch2pcb >= 1.0)</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#multi-user_setup_requires_gsch2pcb_1.0" class="toc">Multi-user Setup (requires gsch2pcb >= 1.0)</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#pc_board_fabrication" class="toc">PC Board Fabrication</a></span></div></li></ul>
</li></ul>
@@ -179,7 +179,7 @@ output-name board
<div class="level3">
<p>
- If you are using gschem for the first time, try stepping through this simple <a href="geda_gschem_warmup.html" class="wikilink1" title="geda:gschem_warmup">gschem warmup</a>.
+ If you are using gschem for the first time, try stepping through this simple <a href="http://geda.seul.org/wiki/geda:gschem_warmup"; class="wikilink1" title="geda:gschem_warmup">gschem warmup</a>.
</p>
<p>
@@ -290,7 +290,7 @@ Now we are done with the schematics except for assigning <strong>refdes</strong>
</p>
</div>
-<!-- SECTION "Create schematic: two.sch" [11443-15045] -->
+<!-- SECTION "Create schematic: two.sch" [11443-15046] -->
<h3><a name="generate_pcb_files_from_schematics" id="generate_pcb_files_from_schematics">Generate PCB Files from Schematics</a></h3>
<div class="level3">
@@ -310,11 +310,11 @@ We have to fix one thing in <strong>one.sch</strong> before we can proceed. Run
</p>
<p>
- If you get output from gsch2pcb like: <em>2 unknown elements added to board.pcb.</em>, then run with the -v flag: <strong>gsch2pcb -v project</strong> and the gsch2pcb output will tell you which schematic components donâ??t have a known <strong>footprint</strong>. Either you forgot to add the attribute, the attribute value is wrong, or the PCB element for it is missing from your installation. But if gsch2pcb canâ??t find any elements and all 7 are unknown, then probably gsch2pcb canâ??t find your PCB m4 install directory. In this case, look at the first part of the <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html#CUSTOM_M4"; class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html#CUSTOM_M4"; rel="nofollow"> Custom M4 Elements </a> section.
+ If you get output from gsch2pcb like: <em>2 unknown elements added to board.pcb.</em>, then run with the -v flag: <strong>gsch2pcb -v project</strong> and the gsch2pcb output will tell you which schematic components donâ??t have a known <strong>footprint</strong>. Either you forgot to add the attribute, the attribute value is wrong, or the PCB element for it is missing from your installation. But if gsch2pcb canâ??t find any elements and all 7 are unknown, then probably gsch2pcb canâ??t find your PCB m4 install directory. In this case, look at the first part of the <span class="curid"><a href="http://geda.seul.org/wiki/geda:gsch2pcb_tutorial#custom_m4_elements_requires_gsch2pcb_1.0"; class="wikilink1" title="geda:gsch2pcb_tutorial"> Custom M4 Elements </a></span> section.
</p>
</div>
-<!-- SECTION "Generate PCB Files from Schematics" [15046-16660] -->
+<!-- SECTION "Generate PCB Files from Schematics" [15047-16644] -->
<h3><a name="layout_pcb_files" id="layout_pcb_files">Layout PCB Files</a></h3>
<div class="level3">
@@ -416,7 +416,7 @@ You will want more information on using PCB and there is a set of html docs in t
</p>
</div>
-<!-- SECTION "Layout PCB Files" [16661-24299] -->
+<!-- SECTION "Layout PCB Files" [16645-24283] -->
<h2><a name="modifying_schematics" id="modifying_schematics">Modifying Schematics</a></h2>
<div class="level2">
@@ -473,7 +473,7 @@ board.pcb is backed up as board.pcb.bak1.
</p>
</div>
-<!-- SECTION "Modifying Schematics" [24300-28104] -->
+<!-- SECTION "Modifying Schematics" [24284-28089] -->
<h2><a name="custom_gschem_symbols" id="custom_gschem_symbols">Custom gschem Symbols</a></h2>
<div class="level2">
@@ -568,12 +568,12 @@ No elements to add so not creating board.new.pcb
</p>
<p>
-For complete details on making symbols, read through the Symbol Creation Document on the <a href="http://www.geda.seul.org/docs/index.html"; class="urlextern" title="http://www.geda.seul.org/docs/index.html"; rel="nofollow"> gEDA Documentation </a> page.
+For complete details on making symbols, read through the <a href="geda_scg.html" class="wikilink1" title="geda:scg">Symbol Creation Document</a> on the <a href="http://geda.seul.org/wiki/geda:documentation"; class="wikilink1" title="geda:documentation">gEDA Documentation</a> page.
</p>
</div>
-<!-- SECTION "Custom gschem Symbols" [28105-32369] -->
-<h2><a name="custom_file_elements" id="custom_file_elements">Custom //file elements//</a></h2>
+<!-- SECTION "Custom gschem Symbols" [28090-32343] -->
+<h2><a name="custom_file_elements" id="custom_file_elements">Custom file elements</a></h2>
<div class="level2">
<p>
@@ -653,8 +653,8 @@ Pin(0 0 70 20 70 42 "" "1" 0x00000101)
</p>
</div>
-<!-- SECTION "Custom //file elements//" [32370-38835] -->
-<h2><a name="custom_m4_elements_requires_gsch2pcb_1.0" id="custom_m4_elements_requires_gsch2pcb_1.0">Custom //m4 elements// (Requires gsch2pcb >= 1.0)</a></h2>
+<!-- SECTION "Custom file elements" [32344-38805] -->
+<h2><a name="custom_m4_elements_requires_gsch2pcb_1.0" id="custom_m4_elements_requires_gsch2pcb_1.0">Custom m4 elements (Requires gsch2pcb >= 1.0)</a></h2>
<div class="level2">
<p>
@@ -792,7 +792,7 @@ Mark(50 50)
</p>
</div>
-<!-- SECTION "Custom //m4 elements// (Requires gsch2pcb >= 1.0)" [38836-46527] -->
+<!-- SECTION "Custom m4 elements (Requires gsch2pcb >= 1.0)" [38806-46493] -->
<h2><a name="multi-user_setup_requires_gsch2pcb_1.0" id="multi-user_setup_requires_gsch2pcb_1.0">Multi-user Setup (requires gsch2pcb >= 1.0)</a></h2>
<div class="level2">
@@ -833,7 +833,7 @@ With the above, users will have access to site wide libraries and only need to p
</p>
</div>
-<!-- SECTION "Multi-user Setup (requires gsch2pcb >= 1.0)" [46528-48163] -->
+<!-- SECTION "Multi-user Setup (requires gsch2pcb >= 1.0)" [46494-48129] -->
<h2><a name="pc_board_fabrication" id="pc_board_fabrication">PC Board Fabrication</a></h2>
<div class="level2">
@@ -842,6 +842,6 @@ The tutorial should cover pcb fabrication too.
</p>
</div>
-<!-- SECTION "PC Board Fabrication" [48164-] --></div>
+<!-- SECTION "PC Board Fabrication" [48130-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_gschem_ug.html b/docs/wiki/geda_gschem_ug.html
index 2846863..7a562e8 100644
--- a/docs/wiki/geda_gschem_ug.html
+++ b/docs/wiki/geda_gschem_ug.html
@@ -7,7 +7,7 @@
<title>geda:gschem_ug</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:55:35-0400" />
+<meta name="date" content="2007-07-14T16:56:40-0400" />
<meta name="keywords" content="geda,gschem_ug" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -523,11 +523,11 @@ If the installation wizzard did not launch, enter as follows to install the gEDA
<div class="level3">
<p>
-For Debian distributions, you may wish to download the <a href="http://www.geda.seul.org/download.html"; class="urlextern" title="http://www.geda.seul.org/download.html"; rel="nofollow">latest DEB binaries</a> prepared by Hamish Moffatt. These are not always current with the latest â??gEDA Tools Suiteâ?? <acronym title="International Organization for Standardization">ISO</acronym> image above, and do not include many of the other tools available on the â??gEDA Tools Suiteâ?? <acronym title="International Organization for Standardization">ISO</acronym> image. Nevertheless, the binary packages provide a hassle free way to install the core of geda.
+For Debian distributions, you may wish to download the <a href="http://www.geda.seul.org/download.html"; class="urlextern" title="http://www.geda.seul.org/download.html"; rel="nofollow">latest DEB binaries</a> prepared by Hamish Moffatt. These are not always current with the latest â??gEDA Tools Suiteâ?? <acronym title="International Organization for Standardization">ISO</acronym> image above, and do not include many of the other tools available on the â??gEDA Tools Suiteâ?? <acronym title="International Organization for Standardization">ISO</acronym> image. Nevertheless, the binary packages provide a hassle free way to install the core of geda.
</p>
</div>
-<!-- SECTION "Debian distributions" [15347-15784] -->
+<!-- SECTION "Debian distributions" [15347-15783] -->
<h3><a name="fedora_and_redhat_distributions" id="fedora_and_redhat_distributions">Fedora and RedHat distributions</a></h3>
<div class="level3">
@@ -536,15 +536,15 @@ For RedHat distributions you may wish to download the <a href="http://www.sp5pbe
</p>
<p>
-Since Fedora Core 5, major parts of gEDA are available from <a href="http://fedoraproject.org/wiki/Extras?highlight(CategoryExtras)" class="urlextern" title="http://fedoraproject.org/wiki/Extras?highlight(CategoryExtras)" rel="nofollow">Fedora Core Extra</a>.
+Since Fedora Core 5, major parts of gEDA are available from <a href="http://fedoraproject.org/"; class="urlextern" title="http://fedoraproject.org/"; rel="nofollow"> the Fedora Project</a>.
</p>
<p>
-For more informations read the <a href="geda_fedora_rpm_installation.html" class="wikilink1" title="geda:fedora_rpm_installation"> fedora rpm installation notes</a>.
+For more information, read the <a href="geda_fedora_rpm_installation.html" class="wikilink1" title="geda:fedora_rpm_installation"> fedora rpm installation notes</a>.
</p>
</div>
-<!-- SECTION "Fedora and RedHat distributions" [15785-16224] -->
+<!-- SECTION "Fedora and RedHat distributions" [15784-16188] -->
<h3><a name="suse_and_opensuse_distributions" id="suse_and_opensuse_distributions">SuSE and OpenSuSE distributions</a></h3>
<div class="level3">
@@ -561,7 +561,7 @@ For more informations read the <a href="geda_suse_rpm_installation.html" class="
</p>
</div>
-<!-- SECTION "SuSE and OpenSuSE distributions" [16225-16707] -->
+<!-- SECTION "SuSE and OpenSuSE distributions" [16189-16671] -->
<h3><a name="mac_osx_distributions" id="mac_osx_distributions">Mac OSX distributions</a></h3>
<div class="level3">
@@ -570,7 +570,7 @@ For Mac OSX distributions you may wish to download the <a href="http://www.geda.
</p>
</div>
-<!-- SECTION "Mac OSX distributions" [16708-16887] -->
+<!-- SECTION "Mac OSX distributions" [16672-16851] -->
<h2><a name="cvs_unstable_testing" id="cvs_unstable_testing">CVS Unstable/Testing</a></h2>
<div class="level2">
@@ -586,7 +586,7 @@ For those already familiar with the gEDA/gaf applications on the â??gEDA Tools S
</ul>
</div>
-<!-- SECTION "CVS Unstable/Testing" [16888-17778] -->
+<!-- SECTION "CVS Unstable/Testing" [16852-17742] -->
<h1><a name="configuring_gschem" id="configuring_gschem">Configuring gschem</a></h1>
<div class="level1">
@@ -654,7 +654,7 @@ Now that we know the above, we can configure <strong>gschem</strong>.<br/>
</ul>
</div>
-<!-- SECTION "Configuring gschem" [17779-23499] -->
+<!-- SECTION "Configuring gschem" [17743-23463] -->
<h2><a name="gschemrc" id="gschemrc">gschemrc</a></h2>
<div class="level2">
@@ -664,7 +664,7 @@ The {binary-install-path}/share/gEDA/system-gschemrc file is well commented. Rea
</p>
</div>
-<!-- SECTION "gschemrc" [23500-23801] -->
+<!-- SECTION "gschemrc" [23464-23765] -->
<h2><a name="gafrc" id="gafrc">gafrc</a></h2>
<div class="level2">
@@ -674,12 +674,12 @@ The {binary-install-path}/share/gEDA/system-gafrc file is well commented. Read t
</p>
</div>
-<!-- SECTION "gafrc" [23802-24091] -->
+<!-- SECTION "gafrc" [23766-24055] -->
<h1><a name="running_gschem" id="running_gschem">Running gschem</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Running gschem" [24092-24121] -->
+<!-- SECTION "Running gschem" [24056-24085] -->
<h2><a name="confirming_gschem_is_installed" id="confirming_gschem_is_installed">Confirming gschem is installed</a></h2>
<div class="level2">
@@ -776,7 +776,7 @@ If these commands do not return the expected results, then most likely the gEDA
</p>
</div>
-<!-- SECTION "Confirming gschem is installed" [24122-29827] -->
+<!-- SECTION "Confirming gschem is installed" [24086-29791] -->
<h2><a name="the_shell_prompt" id="the_shell_prompt">The Shell Prompt</a></h2>
<div class="level2">
<table class="inline">
@@ -857,7 +857,7 @@ As operations are performed in the <strong>gschem</strong> <a href="docs_2006012
</ul>
</div>
-<!-- SECTION "The Shell Prompt" [29828-33362] -->
+<!-- SECTION "The Shell Prompt" [29792-33326] -->
<h2><a name="backups" id="backups">Backups</a></h2>
<div class="level2">
@@ -866,7 +866,7 @@ There are two basic mechanisms in <strong>gschem</strong> for backing up schemat
</p>
</div>
-<!-- SECTION "Backups" [33363-33514] -->
+<!-- SECTION "Backups" [33327-33478] -->
<h3><a name="classic_linux_backups" id="classic_linux_backups">Classic Linux backups</a></h3>
<div class="level3">
@@ -920,12 +920,12 @@ When the user does finally manually save the file, the original file (i.e., the
</p>
</div>
-<!-- SECTION "Classic Linux backups" [33515-36421] -->
+<!-- SECTION "Classic Linux backups" [33479-36385] -->
<h3><a name="incremental_backups" id="incremental_backups">Incremental backups</a></h3>
<div class="level3">
</div>
-<!-- SECTION "Incremental backups" [36422-36455] -->
+<!-- SECTION "Incremental backups" [36386-36419] -->
<h3><a name="relevant_configuration_settings" id="relevant_configuration_settings">Relevant configuration settings</a></h3>
<div class="level3">
@@ -944,7 +944,7 @@ There are the following configuration settings in the {binary-install-path}/shar
</ul>
</div>
-<!-- SECTION "Relevant configuration settings" [36456-37497] -->
+<!-- SECTION "Relevant configuration settings" [36420-37461] -->
<h2><a name="on-line_documentation" id="on-line_documentation">On-line documentation</a></h2>
<div class="level2">
@@ -1076,7 +1076,7 @@ Version December 31st, 2003 gschem(1)</font></pre>
</p>
</div>
-<!-- SECTION "On-line documentation" [37498-41967] -->
+<!-- SECTION "On-line documentation" [37462-41931] -->
<h1><a name="electrical_connectivity" id="electrical_connectivity">Electrical Connectivity</a></h1>
<div class="level1">
@@ -1088,7 +1088,7 @@ As you draw schematics you need be aware of what is considered to be electricall
</p>
</div>
-<!-- SECTION "Electrical Connectivity" [41968-43684] -->
+<!-- SECTION "Electrical Connectivity" [41932-43648] -->
<h1><a name="components_symbols_objects_attributes" id="components_symbols_objects_attributes">Components & Symbols & Objects & Attributes</a></h1>
<div class="level1">
@@ -1097,7 +1097,7 @@ There is a hierarchical association between components, symbols, objects, and at
</p>
</div>
-<!-- SECTION "Components & Symbols & Objects & Attributes" [43685-43833] -->
+<!-- SECTION "Components & Symbols & Objects & Attributes" [43649-43797] -->
<h2><a name="components" id="components">Components</a></h2>
<div class="level2">
@@ -1120,7 +1120,7 @@ A component is the instantiation of a specific symbol, as placed on the schemati
</p>
</div>
-<!-- SECTION "Components" [43834-45648] -->
+<!-- SECTION "Components" [43798-45612] -->
<h2><a name="symbols" id="symbols">Symbols</a></h2>
<div class="level2">
@@ -1131,7 +1131,7 @@ Symbols are just a collection of objects and attributes.<br/>
</p>
</div>
-<!-- SECTION "Symbols" [45649-45990] -->
+<!-- SECTION "Symbols" [45613-45954] -->
<h2><a name="objects" id="objects">Objects</a></h2>
<div class="level2">
@@ -1156,7 +1156,7 @@ The following are objects:
</ul>
</div>
-<!-- SECTION "Objects" [45991-46103] -->
+<!-- SECTION "Objects" [45955-46067] -->
<h2><a name="attributes" id="attributes">Attributes</a></h2>
<div class="level2">
@@ -1213,7 +1213,7 @@ So, to summarize, attribute promotion takes unattached attributes inside symbols
</p>
</div>
-<!-- SECTION "Attributes" [46104-49508] -->
+<!-- SECTION "Attributes" [46068-49472] -->
<h1><a name="the_main_window" id="the_main_window">The Main Window</a></h1>
<div class="level1">
<table class="inline">
@@ -1242,7 +1242,7 @@ So, to summarize, attribute promotion takes unattached attributes inside symbols
</p>
</div>
-<!-- SECTION "The Main Window" [49509-52422] -->
+<!-- SECTION "The Main Window" [49473-52386] -->
<h1><a name="the_status_window" id="the_status_window">The Status Window</a></h1>
<div class="level1">
<table class="inline">
@@ -1256,7 +1256,7 @@ So, to summarize, attribute promotion takes unattached attributes inside symbols
</p>
</div>
-<!-- SECTION "The Status Window" [52423-52585] -->
+<!-- SECTION "The Status Window" [52387-52549] -->
<h1><a name="the_schematic_file" id="the_schematic_file">The Schematic File</a></h1>
<div class="level1">
@@ -1277,7 +1277,7 @@ Schematic files. These files contain components, nets, text, and sometimes primi
</p>
</div>
-<!-- SECTION "The Schematic File" [52586-53355] -->
+<!-- SECTION "The Schematic File" [52550-53319] -->
<h1><a name="the_symbol_file" id="the_symbol_file">The Symbol File</a></h1>
<div class="level1">
@@ -1300,7 +1300,7 @@ Symbol files. The schematic and symbol file formats are identical. <strong>gsche
</p>
</div>
-<!-- SECTION "The Symbol File" [53356-54342] -->
+<!-- SECTION "The Symbol File" [53320-54306] -->
<h1><a name="symbol_libraries" id="symbol_libraries">Symbol Libraries</a></h1>
<div class="level1">
@@ -1309,7 +1309,7 @@ Components are searched for by specifying (component-library "…â??)
</p>
</div>
-<!-- SECTION "Symbol Libraries" [54343-54496] -->
+<!-- SECTION "Symbol Libraries" [54307-54460] -->
<h1><a name="the_log_file" id="the_log_file">The Log File</a></h1>
<div class="level1">
@@ -1318,7 +1318,7 @@ Log file. This file contains informative, error, warnings etc… messages w
</p>
</div>
-<!-- SECTION "The Log File" [54497-54774] -->
+<!-- SECTION "The Log File" [54461-54738] -->
<h1><a name="grips" id="grips">Grips</a></h1>
<div class="level1">
@@ -1341,12 +1341,12 @@ Using grips is easy:
</ul>
</div>
-<!-- SECTION "Grips" [54775-55484] -->
+<!-- SECTION "Grips" [54739-55448] -->
<h1><a name="menu_operations" id="menu_operations">Menu Operations</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Menu Operations" [55485-55514] -->
+<!-- SECTION "Menu Operations" [55449-55478] -->
<h2><a name="file" id="file">File</a></h2>
<div class="level2">
@@ -1373,7 +1373,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "File" [55515-56668] -->
+<!-- SECTION "File" [55479-56632] -->
<h3><a name="new_window_fw" id="new_window_fw">New Window (fw)</a></h3>
<div class="level3">
@@ -1382,7 +1382,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "New Window (fw)" [56669-56834] -->
+<!-- SECTION "New Window (fw)" [56633-56798] -->
<h3><a name="new_page_fn" id="new_page_fn">New Page (fn)</a></h3>
<div class="level3">
@@ -1391,7 +1391,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "New Page (fn)" [56835-57022] -->
+<!-- SECTION "New Page (fn)" [56799-56986] -->
<h3><a name="open_page..._fo" id="open_page..._fo">Open Page... (fo)</a></h3>
<div class="level3">
@@ -1417,7 +1417,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</ul>
</div>
-<!-- SECTION "Open Page... (fo)" [57023-57310] -->
+<!-- SECTION "Open Page... (fo)" [56987-57274] -->
<h3><a name="close_page_pc" id="close_page_pc">Close Page (pc)</a></h3>
<div class="level3">
@@ -1426,7 +1426,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Close Page (pc)" [57311-57456] -->
+<!-- SECTION "Close Page (pc)" [57275-57420] -->
<h3><a name="revert_page_pr" id="revert_page_pr">Revert Page (pr)</a></h3>
<div class="level3">
@@ -1435,7 +1435,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Revert Page (pr)" [57457-57718] -->
+<!-- SECTION "Revert Page (pr)" [57421-57682] -->
<h3><a name="save_page_fs" id="save_page_fs">Save Page (fs)</a></h3>
<div class="level3">
@@ -1453,7 +1453,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</ul>
</div>
-<!-- SECTION "Save Page (fs)" [57719-58366] -->
+<!-- SECTION "Save Page (fs)" [57683-58330] -->
<h3><a name="save_page_as..._fa" id="save_page_as..._fa">Save Page As... (fa)</a></h3>
<div class="level3">
@@ -1465,7 +1465,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Save Page As... (fa)" [58367-58814] -->
+<!-- SECTION "Save Page As... (fa)" [58331-58778] -->
<h3><a name="save_all_fl_fl" id="save_all_fl_fl">Save All (fl) (fl)</a></h3>
<div class="level3">
@@ -1474,7 +1474,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Save All (fl) (fl)" [58815-58919] -->
+<!-- SECTION "Save All (fl) (fl)" [58779-58883] -->
<h3><a name="print..._fp" id="print..._fp">Print... (fp)</a></h3>
<div class="level3">
@@ -1517,7 +1517,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</div>
-<!-- SECTION "Print... (fp)" [58920-59966] -->
+<!-- SECTION "Print... (fp)" [58884-59930] -->
<h3><a name="write_png..._fi" id="write_png..._fi">Write PNG... (fi)</a></h3>
<div class="level3">
@@ -1554,7 +1554,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Write PNG... (fi)" [59967-60761] -->
+<!-- SECTION "Write PNG... (fi)" [59931-60725] -->
<h3><a name="execute_script..._ft" id="execute_script..._ft">Execute Script... (ft)</a></h3>
<div class="level3">
@@ -1563,7 +1563,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Execute Script... (ft)" [60762-60833] -->
+<!-- SECTION "Execute Script... (ft)" [60726-60797] -->
<h3><a name="close_window_fc" id="close_window_fc">Close Window (fc)</a></h3>
<div class="level3">
@@ -1572,7 +1572,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Close Window (fc)" [60834-61072] -->
+<!-- SECTION "Close Window (fc)" [60798-61036] -->
<h3><a name="quit_alt-q" id="quit_alt-q">Quit (Alt-q)</a></h3>
<div class="level3">
@@ -1581,7 +1581,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Quit (Alt-q)" [61073-61265] -->
+<!-- SECTION "Quit (Alt-q)" [61037-61229] -->
<h2><a name="edit" id="edit">Edit</a></h2>
<div class="level2">
@@ -1590,7 +1590,7 @@ The following are available from the <strong>gschem</strong> main windowâ??s men
</p>
</div>
-<!-- SECTION "Edit" [61266-61382] -->
+<!-- SECTION "Edit" [61230-61346] -->
<h3><a name="undo_shift-u" id="undo_shift-u">Undo (shift-u)</a></h3>
<div class="level3">
@@ -1611,7 +1611,7 @@ After every action (including zooming and panning) the schematic is saved to dis
</p>
</div>
-<!-- SECTION "Undo (shift-u)" [61383-62341] -->
+<!-- SECTION "Undo (shift-u)" [61347-62305] -->
<h3><a name="redo_shift-r" id="redo_shift-r">Redo (shift-r)</a></h3>
<div class="level3">
@@ -1621,7 +1621,7 @@ After every action (including zooming and panning) the schematic is saved to dis
</p>
</div>
-<!-- SECTION "Redo (shift-r)" [62342-62650] -->
+<!-- SECTION "Redo (shift-r)" [62306-62614] -->
<h3><a name="select_mode_s" id="select_mode_s">Select Mode (s)</a></h3>
<div class="level3">
@@ -1644,7 +1644,7 @@ After every action (including zooming and panning) the schematic is saved to dis
</p>
</div>
-<!-- SECTION "Select Mode (s)" [62651-65058] -->
+<!-- SECTION "Select Mode (s)" [62615-65022] -->
<h3><a name="edit..._ee" id="edit..._ee">Edit... (ee)</a></h3>
<div class="level3">
@@ -1693,7 +1693,7 @@ First, select the object to be edited (i.e., in <strong>Select Mode</strong>).<b
</p>
</div>
-<!-- SECTION "Edit... (ee)" [65059-66253] -->
+<!-- SECTION "Edit... (ee)" [65023-66217] -->
<h3><a name="edit_text..._ex" id="edit_text..._ex">Edit Text... (ex)</a></h3>
<div class="level3">
@@ -1731,7 +1731,7 @@ First, select the text object to be edited (i.e., in <strong>Select Mode</strong
</p>
</div>
-<!-- SECTION "Edit Text... (ex)" [66254-67112] -->
+<!-- SECTION "Edit Text... (ex)" [66218-67076] -->
<h3><a name="copy_mode_ec" id="copy_mode_ec">Copy Mode (ec)</a></h3>
<div class="level3">
@@ -1764,7 +1764,7 @@ First, select the text object to be edited (i.e., in <strong>Select Mode</strong
</p>
</div>
-<!-- SECTION "Copy Mode (ec)" [67113-68037] -->
+<!-- SECTION "Copy Mode (ec)" [67077-68001] -->
<h3><a name="move_mode_em" id="move_mode_em">Move Mode (em)</a></h3>
<div class="level3">
@@ -1810,7 +1810,7 @@ Since version 20060906, there is another way to move object(s):<br/>
</ul>
</div>
-<!-- SECTION "Move Mode (em)" [68038-69191] -->
+<!-- SECTION "Move Mode (em)" [68002-69155] -->
<h3><a name="delete_delete-key" id="delete_delete-key">Delete (Delete-key)</a></h3>
<div class="level3">
@@ -1830,7 +1830,7 @@ Since version 20060906, there is another way to move object(s):<br/>
</p>
</div>
-<!-- SECTION "Delete (Delete-key)" [69192-69510] -->
+<!-- SECTION "Delete (Delete-key)" [69156-69474] -->
<h3><a name="rotate_90_mode_er" id="rotate_90_mode_er">Rotate 90 Mode (er)</a></h3>
<div class="level3">
@@ -1854,7 +1854,7 @@ Since version 20060906, there is another way to move object(s):<br/>
</p>
</div>
-<!-- SECTION "Rotate 90 Mode (er)" [69511-70100] -->
+<!-- SECTION "Rotate 90 Mode (er)" [69475-70064] -->
<h3><a name="mirror_mode_ei" id="mirror_mode_ei">Mirror Mode (ei)</a></h3>
<div class="level3">
@@ -1878,7 +1878,7 @@ Since version 20060906, there is another way to move object(s):<br/>
</p>
</div>
-<!-- SECTION "Mirror Mode (ei)" [70101-70757] -->
+<!-- SECTION "Mirror Mode (ei)" [70065-70721] -->
<h3><a name="slot..._e_shift-s" id="slot..._e_shift-s">Slot... (e shift-s)</a></h3>
<div class="level3">
@@ -1903,7 +1903,7 @@ Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than
</p>
</div>
-<!-- SECTION "Slot... (e shift-s)" [70758-71974] -->
+<!-- SECTION "Slot... (e shift-s)" [70722-71938] -->
<h3><a name="color..._eo" id="color..._eo">Color... (eo)</a></h3>
<div class="level3">
@@ -1960,7 +1960,7 @@ Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than
</p>
</div>
-<!-- SECTION "Color... (eo)" [71975-72933] -->
+<!-- SECTION "Color... (eo)" [71939-72897] -->
<h3><a name="lock_el_unlock_e_shift-l" id="lock_el_unlock_e_shift-l">Lock (el) / Unlock (e shift-l)</a></h3>
<div class="level3">
@@ -1984,7 +1984,7 @@ Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than
</p>
</div>
-<!-- SECTION "Lock (el) / Unlock (e shift-l)" [72934-74472] -->
+<!-- SECTION "Lock (el) / Unlock (e shift-l)" [72898-74436] -->
<h3><a name="line_width_type..._ew" id="line_width_type..._ew">Line Width & Type... (ew)</a></h3>
<div class="level3">
@@ -2020,7 +2020,7 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</p>
</div>
-<!-- SECTION "Line Width & Type... (ew)" [74473-75088] -->
+<!-- SECTION "Line Width & Type... (ew)" [74437-75052] -->
<h3><a name="fill_type..._ef" id="fill_type..._ef">Fill Type... (ef)</a></h3>
<div class="level3">
@@ -2054,7 +2054,7 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</ul>
</div>
-<!-- SECTION "Fill Type... (ef)" [75089-75429] -->
+<!-- SECTION "Fill Type... (ef)" [75053-75393] -->
<h3><a name="symbol_translate..._et" id="symbol_translate..._et">Symbol Translate... (et)</a></h3>
<div class="level3">
@@ -2094,7 +2094,7 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</p>
</div>
-<!-- SECTION "Symbol Translate... (et)" [75430-76594] -->
+<!-- SECTION "Symbol Translate... (et)" [75394-76558] -->
<h3><a name="embed_component_picture_eb" id="embed_component_picture_eb">Embed Component/Picture (eb)</a></h3>
<div class="level3">
@@ -2117,7 +2117,7 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</p>
</div>
-<!-- SECTION "Embed Component/Picture (eb)" [76595-77624] -->
+<!-- SECTION "Embed Component/Picture (eb)" [76559-77588] -->
<h3><a name="unembed_component_picture_eu" id="unembed_component_picture_eu">Unembed Component/Picture (eu)</a></h3>
<div class="level3">
@@ -2137,7 +2137,7 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</p>
</div>
-<!-- SECTION "Unembed Component/Picture (eu)" [77625-78214] -->
+<!-- SECTION "Unembed Component/Picture (eu)" [77589-78178] -->
<h3><a name="update_component_ep" id="update_component_ep">Update Component (ep)</a></h3>
<div class="level3">
@@ -2177,7 +2177,7 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</ul>
</div>
-<!-- SECTION "Update Component (ep)" [78215-80024] -->
+<!-- SECTION "Update Component (ep)" [78179-79988] -->
<h3><a name="show_hide_inv_text_en" id="show_hide_inv_text_en">Show/Hide Inv Text (en)</a></h3>
<div class="level3">
@@ -2243,7 +2243,7 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</p>
</div>
-<!-- SECTION "Show/Hide Inv Text (en)" [80025-82852] -->
+<!-- SECTION "Show/Hide Inv Text (en)" [79989-82816] -->
<h3><a name="make_inv_text_vis_ev" id="make_inv_text_vis_ev">Make Inv Text Vis (ev)</a></h3>
<div class="level3">
@@ -2264,7 +2264,7 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</p>
</div>
-<!-- SECTION "Make Inv Text Vis (ev)" [82853-83516] -->
+<!-- SECTION "Make Inv Text Vis (ev)" [82817-83480] -->
<h2><a name="buffer" id="buffer">Buffer</a></h2>
<div class="level2">
@@ -2273,7 +2273,7 @@ The <strong>Edit | Line Width & Type…</strong> dialog box lets you co
</p>
</div>
-<!-- SECTION "Buffer" [83517-83636] -->
+<!-- SECTION "Buffer" [83481-83600] -->
<h3><a name="copy_into_1_2_3_4_5_yc" id="copy_into_1_2_3_4_5_yc">Copy into 1/2/3/4/5 (yc)</a></h3>
<div class="level3">
@@ -2288,7 +2288,7 @@ To copy something into a buffer:
</ol>
</div>
-<!-- SECTION "Copy into 1/2/3/4/5 (yc)" [83637-83789] -->
+<!-- SECTION "Copy into 1/2/3/4/5 (yc)" [83601-83753] -->
<h3><a name="cut_into_1_2_3_4_5_yu" id="cut_into_1_2_3_4_5_yu">Cut into 1/2/3/4/5 (yu)</a></h3>
<div class="level3">
@@ -2297,7 +2297,7 @@ Cut is like copy in that it removes the objects from the schematic
</p>
</div>
-<!-- SECTION "Cut into 1/2/3/4/5 (yu)" [83790-83891] -->
+<!-- SECTION "Cut into 1/2/3/4/5 (yu)" [83754-83855] -->
<h3><a name="paste_from_1_2_3_4_5_yp" id="paste_from_1_2_3_4_5_yp">Paste from 1/2/3/4/5 (yp)</a></h3>
<div class="level3">
@@ -2320,12 +2320,12 @@ To paste a buffer into the current schematic:
</ol>
</div>
-<!-- SECTION "Paste from 1/2/3/4/5 (yp)" [83892-84245] -->
+<!-- SECTION "Paste from 1/2/3/4/5 (yp)" [83856-84209] -->
<h2><a name="view" id="view">View</a></h2>
<div class="level2">
</div>
-<!-- SECTION "View" [84246-84263] -->
+<!-- SECTION "View" [84210-84227] -->
<h3><a name="redraw_vr" id="redraw_vr">Redraw (vr)</a></h3>
<div class="level3">
@@ -2335,7 +2335,7 @@ To paste a buffer into the current schematic:
</p>
</div>
-<!-- SECTION "Redraw (vr)" [84264-84514] -->
+<!-- SECTION "Redraw (vr)" [84228-84478] -->
<h3><a name="pan_x" id="pan_x">Pan (x)</a></h3>
<div class="level3">
@@ -2382,7 +2382,7 @@ to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</p>
</div>
-<!-- SECTION "Pan (x)" [84515-86311] -->
+<!-- SECTION "Pan (x)" [84479-86275] -->
<h3><a name="zoom_box_w" id="zoom_box_w">Zoom Box (w)</a></h3>
<div class="level3">
@@ -2409,7 +2409,7 @@ to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</p>
</div>
-<!-- SECTION "Zoom Box (w)" [86312-87192] -->
+<!-- SECTION "Zoom Box (w)" [86276-87156] -->
<h3><a name="zoom_extents_ve" id="zoom_extents_ve">Zoom Extents (ve)</a></h3>
<div class="level3">
@@ -2428,7 +2428,7 @@ to either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</p>
</div>
-<!-- SECTION "Zoom Extents (ve)" [87193-87559] -->
+<!-- SECTION "Zoom Extents (ve)" [87157-87523] -->
<h3><a name="zoom_in_z" id="zoom_in_z">Zoom In (z)</a></h3>
<div class="level3">
@@ -2465,7 +2465,7 @@ in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</p>
</div>
-<!-- SECTION "Zoom In (z)" [87560-88721] -->
+<!-- SECTION "Zoom In (z)" [87524-88685] -->
<h3><a name="zoom_out_z" id="zoom_out_z">Zoom Out (Z)</a></h3>
<div class="level3">
@@ -2502,7 +2502,7 @@ in either your userâ??s ~/gschemrc file or local â??pwdâ??/gschemrc file, whenev
</p>
</div>
-<!-- SECTION "Zoom Out (Z)" [88722-89910] -->
+<!-- SECTION "Zoom Out (Z)" [88686-89874] -->
<h3><a name="zoom_full_vf" id="zoom_full_vf">Zoom Full (vf)</a></h3>
<div class="level3">
@@ -2542,52 +2542,52 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</p>
</div>
-<!-- SECTION "Zoom Full (vf)" [89911-90689] -->
+<!-- SECTION "Zoom Full (vf)" [89875-90653] -->
<h2><a name="page" id="page">Page</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Page" [90690-90708] -->
+<!-- SECTION "Page" [90654-90672] -->
<h3><a name="manager..._pm" id="manager..._pm">Manager... (pm)</a></h3>
<div class="level3">
</div>
-<!-- SECTION "Manager... (pm)" [90709-90736] -->
+<!-- SECTION "Manager... (pm)" [90673-90700] -->
<h3><a name="next" id="next">Next (>)</a></h3>
<div class="level3">
</div>
-<!-- SECTION "Next (>)" [90737-90757] -->
+<!-- SECTION "Next (>)" [90701-90721] -->
<h3><a name="previous" id="previous">Previous (<)</a></h3>
<div class="level3">
</div>
-<!-- SECTION "Previous (<)" [90758-90782] -->
+<!-- SECTION "Previous (<)" [90722-90746] -->
<h3><a name="new_pe" id="new_pe">New (pe)</a></h3>
<div class="level3">
</div>
-<!-- SECTION "New (pe)" [90783-90803] -->
+<!-- SECTION "New (pe)" [90747-90767] -->
<h3><a name="revert_pr" id="revert_pr">Revert (pr)</a></h3>
<div class="level3">
</div>
-<!-- SECTION "Revert (pr)" [90804-90827] -->
+<!-- SECTION "Revert (pr)" [90768-90791] -->
<h3><a name="close_pc" id="close_pc">Close (pc)</a></h3>
<div class="level3">
</div>
-<!-- SECTION "Close (pc)" [90828-90850] -->
+<!-- SECTION "Close (pc)" [90792-90814] -->
<h3><a name="discard_pd" id="discard_pd">Discard (pd)</a></h3>
<div class="level3">
</div>
-<!-- SECTION "Discard (pd)" [90851-90875] -->
+<!-- SECTION "Discard (pd)" [90815-90839] -->
<h2><a name="add" id="add">Add</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Add" [90876-90892] -->
+<!-- SECTION "Add" [90840-90856] -->
<h3><a name="component..._i" id="component..._i">Component... (i)</a></h3>
<div class="level3">
@@ -2636,7 +2636,7 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</p>
</div>
-<!-- SECTION "Component... (i)" [90893-92369] -->
+<!-- SECTION "Component... (i)" [90857-92333] -->
<h3><a name="net_n" id="net_n">Net (n)</a></h3>
<div class="level3">
@@ -2718,7 +2718,7 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</p>
</div>
-<!-- SECTION "Net (n)" [92370-94961] -->
+<!-- SECTION "Net (n)" [92334-94925] -->
<h3><a name="bus_u" id="bus_u">Bus (u)</a></h3>
<div class="level3">
@@ -2728,7 +2728,7 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</p>
</div>
-<!-- SECTION "Bus (u)" [94962-95211] -->
+<!-- SECTION "Bus (u)" [94926-95175] -->
<h3><a name="attribute..._aa" id="attribute..._aa">Attribute... (aa)</a></h3>
<div class="level3">
@@ -2759,7 +2759,7 @@ To view the maximum displayable area using the keyboard shortcut (i.e., â??<stro
</p>
</div>
-<!-- SECTION "Attribute... (aa)" [95212-96924] -->
+<!-- SECTION "Attribute... (aa)" [95176-96888] -->
<h3><a name="text..._at" id="text..._at">Text... (at)</a></h3>
<div class="level3">
@@ -2800,7 +2800,7 @@ Text which is placed will be automatically capitalized. Please see the Resource
</p>
</div>
-<!-- SECTION "Text... (at)" [96925-98728] -->
+<!-- SECTION "Text... (at)" [96889-98692] -->
<h3><a name="line_l" id="line_l">Line (l)</a></h3>
<div class="level3">
@@ -2844,7 +2844,7 @@ Text which is placed will be automatically capitalized. Please see the Resource
</p>
</div>
-<!-- SECTION "Line (l)" [98729-99815] -->
+<!-- SECTION "Line (l)" [98693-99779] -->
<h3><a name="box_b" id="box_b">Box (b)</a></h3>
<div class="level3">
@@ -2874,7 +2874,7 @@ Text which is placed will be automatically capitalized. Please see the Resource
</p>
</div>
-<!-- SECTION "Box (b)" [99816-100568] -->
+<!-- SECTION "Box (b)" [99780-100532] -->
<h3><a name="circle_ai" id="circle_ai">Circle (ai)</a></h3>
<div class="level3">
@@ -2906,7 +2906,7 @@ Text which is placed will be automatically capitalized. Please see the Resource
</p>
</div>
-<!-- SECTION "Circle (ai)" [100569-101453] -->
+<!-- SECTION "Circle (ai)" [100533-101417] -->
<h3><a name="arc_ar" id="arc_ar">Arc (ar)</a></h3>
<div class="level3">
@@ -2942,7 +2942,7 @@ Text which is placed will be automatically capitalized. Please see the Resource
</p>
</div>
-<!-- SECTION "Arc (ar)" [101454-102546] -->
+<!-- SECTION "Arc (ar)" [101418-102510] -->
<h3><a name="pin_ap" id="pin_ap">Pin (ap)</a></h3>
<div class="level3">
@@ -2975,7 +2975,7 @@ Text which is placed will be automatically capitalized. Please see the Resource
</p>
</div>
-<!-- SECTION "Pin (ap)" [102547-103734] -->
+<!-- SECTION "Pin (ap)" [102511-103698] -->
<h3><a name="picture..._ag" id="picture..._ag">Picture... (ag)</a></h3>
<div class="level3">
@@ -3009,12 +3009,12 @@ Text which is placed will be automatically capitalized. Please see the Resource
</p>
</div>
-<!-- SECTION "Picture... (ag)" [103735-104730] -->
+<!-- SECTION "Picture... (ag)" [103699-104694] -->
<h2><a name="hierarchy" id="hierarchy">Hierarchy</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Hierarchy" [104731-104753] -->
+<!-- SECTION "Hierarchy" [104695-104717] -->
<h3><a name="down_schematic_hd" id="down_schematic_hd">Down Schematic (Hd)</a></h3>
<div class="level3">
@@ -3036,7 +3036,7 @@ Text which is placed will be automatically capitalized. Please see the Resource
</p>
</div>
-<!-- SECTION "Down Schematic (Hd)" [104754-106366] -->
+<!-- SECTION "Down Schematic (Hd)" [104718-106330] -->
<h3><a name="down_symbol_hs" id="down_symbol_hs">Down Symbol (Hs)</a></h3>
<div class="level3">
@@ -3047,7 +3047,7 @@ This option will open up the symbol of the selected component.<br/>
</p>
</div>
-<!-- SECTION "Down Symbol (Hs)" [106367-106689] -->
+<!-- SECTION "Down Symbol (Hs)" [106331-106653] -->
<h3><a name="up_hu" id="up_hu">Up (Hu)</a></h3>
<div class="level3">
@@ -3056,7 +3056,7 @@ This option will move up the hierarchy (if there are pages above the currently d
</p>
</div>
-<!-- SECTION "Up (Hu)" [106690-106804] -->
+<!-- SECTION "Up (Hu)" [106654-106768] -->
<h3><a name="documentation_ho" id="documentation_ho">Documentation (Ho)</a></h3>
<div class="level3">
@@ -3071,12 +3071,12 @@ Open any documentation available for the selected symbol/component.<br/>
</p>
</div>
-<!-- SECTION "Documentation (Ho)" [106805-107889] -->
+<!-- SECTION "Documentation (Ho)" [106769-107853] -->
<h2><a name="attributes1" id="attributes1">Attributes</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Attributes" [107890-107913] -->
+<!-- SECTION "Attributes" [107854-107877] -->
<h3><a name="attach_ta" id="attach_ta">Attach (ta)</a></h3>
<div class="level3">
@@ -3099,7 +3099,7 @@ The Attach command allows you to take a text item (in the proper form; <code>nam
</p>
</div>
-<!-- SECTION "Attach (ta)" [107914-108721] -->
+<!-- SECTION "Attach (ta)" [107878-108685] -->
<h3><a name="detach_td" id="detach_td">Detach (td)</a></h3>
<div class="level3">
@@ -3120,7 +3120,7 @@ Detach allows you to deassociate attributes from objects.<br/>
</p>
</div>
-<!-- SECTION "Detach (td)" [108722-109328] -->
+<!-- SECTION "Detach (td)" [108686-109292] -->
<h3><a name="show_value_tv" id="show_value_tv">Show Value (tv)</a></h3>
<div class="level3">
@@ -3141,7 +3141,7 @@ These operations allow you to control which part of the attribute string is visi
</p>
</div>
-<!-- SECTION "Show Value (tv)" [109329-109867] -->
+<!-- SECTION "Show Value (tv)" [109293-109831] -->
<h3><a name="show_name_tn" id="show_name_tn">Show Name (tn)</a></h3>
<div class="level3">
@@ -3162,7 +3162,7 @@ These operations allow you to control which part of the attribute string is visi
</p>
</div>
-<!-- SECTION "Show Name (tn)" [109868-110405] -->
+<!-- SECTION "Show Name (tn)" [109832-110369] -->
<h3><a name="show_both_tb" id="show_both_tb">Show Both (tb)</a></h3>
<div class="level3">
@@ -3183,7 +3183,7 @@ These operations allow you to control which part of the attribute string is visi
</p>
</div>
-<!-- SECTION "Show Both (tb)" [110406-110943] -->
+<!-- SECTION "Show Both (tb)" [110370-110907] -->
<h3><a name="toggle_visibility_tt" id="toggle_visibility_tt">Toggle Visibility (tt)</a></h3>
<div class="level3">
@@ -3205,7 +3205,7 @@ This operation allows you to toggle the visibility of attributes.<br/>
</p>
</div>
-<!-- SECTION "Toggle Visibility (tt)" [110944-111639] -->
+<!-- SECTION "Toggle Visibility (tt)" [110908-111603] -->
<h3><a name="find_specific_text..._t_shift-f" id="find_specific_text..._t_shift-f">Find Specific Text... (t shift-f)</a></h3>
<div class="level3">
@@ -3234,7 +3234,7 @@ To use this operation:
</p>
</div>
-<!-- SECTION "Find Specific Text... (t shift-f)" [111640-112300] -->
+<!-- SECTION "Find Specific Text... (t shift-f)" [111604-112264] -->
<h3><a name="hide_specific_text..._th" id="hide_specific_text..._th">Hide Specific Text... (th)</a></h3>
<div class="level3">
@@ -3261,7 +3261,7 @@ This operation is useful if you like to hide pintype and pinseq attributes when
</p>
</div>
-<!-- SECTION "Hide Specific Text... (th)" [112301-112662] -->
+<!-- SECTION "Hide Specific Text... (th)" [112265-112626] -->
<h3><a name="show_specific_text..._t_shift-h" id="show_specific_text..._t_shift-h">Show Specific Text... (t shift-h)</a></h3>
<div class="level3">
@@ -3288,7 +3288,7 @@ This operation is useful if you like to see only one specific attribute in the w
</p>
</div>
-<!-- SECTION "Show Specific Text... (t shift-h)" [112663-113154] -->
+<!-- SECTION "Show Specific Text... (t shift-h)" [112627-113118] -->
<h3><a name="autonumber_text..._tu" id="autonumber_text..._tu">Autonumber Text... (tu)</a></h3>
<div class="level3">
@@ -3335,12 +3335,12 @@ You can use it to:
</p>
</div>
-<!-- SECTION "Autonumber Text... (tu)" [113155-115592] -->
+<!-- SECTION "Autonumber Text... (tu)" [113119-115556] -->
<h2><a name="options" id="options">Options</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Options" [115593-115613] -->
+<!-- SECTION "Options" [115557-115577] -->
<h3><a name="text_size..._ot" id="text_size..._ot">Text Size... (ot)</a></h3>
<div class="level3">
@@ -3350,7 +3350,7 @@ You can use it to:
</p>
</div>
-<!-- SECTION "Text Size... (ot)" [115614-115926] -->
+<!-- SECTION "Text Size... (ot)" [115578-115890] -->
<h3><a name="toggle_grid_on_off_og" id="toggle_grid_on_off_og">Toggle Grid On/Off (og)</a></h3>
<div class="level3">
@@ -3359,7 +3359,7 @@ You can use it to:
</p>
</div>
-<!-- SECTION "Toggle Grid On/Off (og)" [115927-116020] -->
+<!-- SECTION "Toggle Grid On/Off (og)" [115891-115984] -->
<h3><a name="toggle_snap_on_off_os" id="toggle_snap_on_off_os">Toggle Snap On/Off (os)</a></h3>
<div class="level3">
@@ -3370,7 +3370,7 @@ You can use it to:
</p>
</div>
-<!-- SECTION "Toggle Snap On/Off (os)" [116021-116472] -->
+<!-- SECTION "Toggle Snap On/Off (os)" [115985-116436] -->
<h3><a name="snap_grid_spacing..._os" id="snap_grid_spacing..._os">Snap Grid Spacing... (oS)</a></h3>
<div class="level3">
@@ -3380,7 +3380,7 @@ You can use it to:
</p>
</div>
-<!-- SECTION "Snap Grid Spacing... (oS)" [116473-116776] -->
+<!-- SECTION "Snap Grid Spacing... (oS)" [116437-116740] -->
<h3><a name="toggle_outline_box_oa" id="toggle_outline_box_oa">Toggle Outline/Box (oa)</a></h3>
<div class="level3">
@@ -3389,7 +3389,7 @@ You can use it to:
</p>
</div>
-<!-- SECTION "Toggle Outline/Box (oa)" [116777-117086] -->
+<!-- SECTION "Toggle Outline/Box (oa)" [116741-117050] -->
<h3><a name="toggle_net_rubberband_or" id="toggle_net_rubberband_or">Toggle Net/Rubberband (or)</a></h3>
<div class="level3">
@@ -3398,7 +3398,7 @@ You can use it to:
</p>
</div>
-<!-- SECTION "Toggle Net/Rubberband (or)" [117087-117170] -->
+<!-- SECTION "Toggle Net/Rubberband (or)" [117051-117134] -->
<h3><a name="show_log_window_ol" id="show_log_window_ol">Show Log Window (ol)</a></h3>
<div class="level3">
@@ -3407,7 +3407,7 @@ You can use it to:
</p>
</div>
-<!-- SECTION "Show Log Window (ol)" [117171-117341] -->
+<!-- SECTION "Show Log Window (ol)" [117135-117305] -->
<h3><a name="show_coord_window..._oc" id="show_coord_window..._oc">Show Coord Window... (oc)</a></h3>
<div class="level3">
@@ -3416,12 +3416,12 @@ You can use it to:
</p>
</div>
-<!-- SECTION "Show Coord Window... (oc)" [117342-117546] -->
+<!-- SECTION "Show Coord Window... (oc)" [117306-117510] -->
<h2><a name="help" id="help">Help</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Help" [117547-117564] -->
+<!-- SECTION "Help" [117511-117528] -->
<h3><a name="about..._ha" id="about..._ha">About... (ha)</a></h3>
<div class="level3">
@@ -3438,7 +3438,7 @@ Every <acronym title="Graphical User Interface">GUI</acronym> application needs
</ul>
</div>
-<!-- SECTION "About... (ha)" [117565-117767] -->
+<!-- SECTION "About... (ha)" [117529-117731] -->
<h3><a name="manual..._hm" id="manual..._hm">Manual... (hm)</a></h3>
<div class="level3">
@@ -3447,7 +3447,7 @@ Every <acronym title="Graphical User Interface">GUI</acronym> application needs
</p>
</div>
-<!-- SECTION "Manual... (hm)" [117768-117981] -->
+<!-- SECTION "Manual... (hm)" [117732-117945] -->
<h3><a name="hotkeys..._hh" id="hotkeys..._hh">Hotkeys... (hh)</a></h3>
<div class="level3">
@@ -3456,7 +3456,7 @@ Every <acronym title="Graphical User Interface">GUI</acronym> application needs
</p>
</div>
-<!-- SECTION "Hotkeys... (hh)" [117982-118109] -->
+<!-- SECTION "Hotkeys... (hh)" [117946-118073] -->
<h3><a name="component..._ho" id="component..._ho">Component... (Ho)</a></h3>
<div class="level3">
@@ -3471,7 +3471,7 @@ If you select a component on the schematic, and select <strong>Help | Component&
</ul>
</div>
-<!-- SECTION "Component... (Ho)" [118110-118892] -->
+<!-- SECTION "Component... (Ho)" [118074-118856] -->
<h1><a name="appendix_a_--_heavy_vs_light_symbol_libraries" id="appendix_a_--_heavy_vs_light_symbol_libraries">Appendix A -- Heavy vs Light Symbol Libraries</a></h1>
<div class="level1">
@@ -3480,7 +3480,7 @@ A short discussion of Light Symbol Libraries as the default for <strong>gschem</
</p>
</div>
-<!-- SECTION "Appendix A -- Heavy vs Light Symbol Libraries" [118893-119086] -->
+<!-- SECTION "Appendix A -- Heavy vs Light Symbol Libraries" [118857-119050] -->
<h1><a name="appendix_b_--_printing_schematics_and_symbols" id="appendix_b_--_printing_schematics_and_symbols">Appendix B -- Printing Schematics and Symbols</a></h1>
<div class="level1">
@@ -3489,7 +3489,7 @@ To be supplied…
</p>
</div>
-<!-- SECTION "Appendix B -- Printing Schematics and Symbols" [119087-119165] -->
+<!-- SECTION "Appendix B -- Printing Schematics and Symbols" [119051-119129] -->
<h1><a name="appendix_c_--_writing_guile_scripts" id="appendix_c_--_writing_guile_scripts">Appendix C -- Writing guile Scripts</a></h1>
<div class="level1">
@@ -3498,7 +3498,7 @@ To be supplied…
</p>
</div>
-<!-- SECTION "Appendix C -- Writing guile Scripts" [119166-119234] -->
+<!-- SECTION "Appendix C -- Writing guile Scripts" [119130-119198] -->
<h1><a name="appendix_d_--_i_want_to_build_a_printed_circuit_board" id="appendix_d_--_i_want_to_build_a_printed_circuit_board">Appendix D -- I Want To Build A Printed Circuit Board</a></h1>
<div class="level1">
@@ -3531,7 +3531,7 @@ To be supplied…
</ul>
</div>
-<!-- SECTION "Appendix D -- I Want To Build A Printed Circuit Board" [119235-120024] -->
+<!-- SECTION "Appendix D -- I Want To Build A Printed Circuit Board" [119199-119988] -->
<h1><a name="appendix_e_--_i_want_to_simulate_my_design" id="appendix_e_--_i_want_to_simulate_my_design">Appendix E -- I Want To Simulate My Design</a></h1>
<div class="level1">
@@ -3566,7 +3566,7 @@ To be supplied…
</ul>
</div>
-<!-- SECTION "Appendix E -- I Want To Simulate My Design" [120025-120904] -->
+<!-- SECTION "Appendix E -- I Want To Simulate My Design" [119989-120868] -->
<h1><a name="appendix_f_--_change_gschemdoc_user-defined_preferences" id="appendix_f_--_change_gschemdoc_user-defined_preferences">Appendix F -- Change gschemdoc User-Defined Preferences</a></h1>
<div class="level1">
@@ -3594,7 +3594,7 @@ To select a different application launcher, simply edit the {binary-install-path
</p>
</div>
-<!-- SECTION "Appendix F -- Change gschemdoc User-Defined Preferences" [120905-122121] -->
+<!-- SECTION "Appendix F -- Change gschemdoc User-Defined Preferences" [120869-122085] -->
<h1><a name="appendix_g_--_breaking_a_large_symbol_into_smaller_symbols" id="appendix_g_--_breaking_a_large_symbol_into_smaller_symbols">Appendix G -- Breaking a Large Symbol Into Smaller Symbols</a></h1>
<div class="level1">
@@ -3603,7 +3603,7 @@ To be supplied…
</p>
</div>
-<!-- SECTION "Appendix G -- Breaking a Large Symbol Into Smaller Symbols" [122122-122213] -->
+<!-- SECTION "Appendix G -- Breaking a Large Symbol Into Smaller Symbols" [122086-122177] -->
<h1><a name="appendix_h_--_definition_of_terms" id="appendix_h_--_definition_of_terms">Appendix H -- Definition of Terms</a></h1>
<div class="level1">
@@ -3679,6 +3679,6 @@ Some terms used in the art of schematic capture:</p>
</p>
</div>
-<!-- SECTION "Appendix H -- Definition of Terms" [122214-] --></div>
+<!-- SECTION "Appendix H -- Definition of Terms" [122178-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_master_attributes_list.html b/docs/wiki/geda_master_attributes_list.html
index f6cf8a9..02fe8c4 100644
--- a/docs/wiki/geda_master_attributes_list.html
+++ b/docs/wiki/geda_master_attributes_list.html
@@ -7,7 +7,7 @@
<title>geda:master_attributes_list</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:25-0400" />
+<meta name="date" content="2007-07-10T08:43:39-0400" />
<meta name="keywords" content="geda,master_attributes_list" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -61,6 +61,8 @@
<li class="level3"><div class="li"><span class="li"><a href="#net" class="toc">net</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#value" class="toc">value</a></span></div></li>
<li class="level3"><div class="li"><span class="li"><a href="#symversion" class="toc">symversion</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#dist-license" class="toc">dist-license</a></span></div></li>
+<li class="level3"><div class="li"><span class="li"><a href="#use-license" class="toc">use-license</a></span></div></li>
</ul>
</li>
<li class="level2"><div class="li"><span class="li"><a href="#obsolete_attributes" class="toc">Obsolete Attributes</a></span></div>
@@ -85,7 +87,7 @@
<div class="level1">
<p>
-by: Ales V. Hvezda, ahvezda@xxxxxxxxxxxxx
+by: Ales Hvezda, ahvezda@xxxxxxxxxxxxx
</p>
<p>
@@ -93,11 +95,11 @@ This document is released under <a href="http://www.gnu.org/copyleft/fdl.html"; c
</p>
<p>
-July 6th, 2004
+July 10th, 2007
</p>
</div>
-<!-- SECTION "gEDA/gaf Master Attribute Document" [1-187] -->
+<!-- SECTION "gEDA/gaf Master Attribute Document" [1-185] -->
<h2><a name="overview" id="overview">Overview</a></h2>
<div class="level2">
@@ -107,7 +109,7 @@ This document describes all the attributes used in in gEDA/gaf (<acronym title="
</p>
</div>
-<!-- SECTION "Overview" [188-654] -->
+<!-- SECTION "Overview" [186-652] -->
<h2><a name="what_are_attributes" id="what_are_attributes">What are Attributes?</a></h2>
<div class="level2">
@@ -117,12 +119,12 @@ Attributes in the gEDA/gaf system are nothing more than text items which take on
</p>
</div>
-<!-- SECTION "What are Attributes?" [655-1425] -->
+<!-- SECTION "What are Attributes?" [653-1423] -->
<h2><a name="symbol_only_attributes" id="symbol_only_attributes">Symbol only Attributes</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Symbol only Attributes" [1426-1461] -->
+<!-- SECTION "Symbol only Attributes" [1424-1459] -->
<h3><a name="device" id="device">device</a></h3>
<div class="level3">
@@ -133,7 +135,7 @@ Attributes in the gEDA/gaf system are nothing more than text items which take on
</p>
</div>
-<!-- SECTION "device" [1462-2105] -->
+<!-- SECTION "device" [1460-2103] -->
<h3><a name="graphical" id="graphical">graphical</a></h3>
<div class="level3">
@@ -144,7 +146,7 @@ Symbols which have no electrical or circuit significance need a <strong>graphica
</p>
</div>
-<!-- SECTION "graphical" [2106-2520] -->
+<!-- SECTION "graphical" [2104-2518] -->
<h3><a name="description" id="description">description</a></h3>
<div class="level3">
@@ -154,7 +156,7 @@ The <strong>description</strong> attribute provides a simple one line descriptio
</p>
</div>
-<!-- SECTION "description" [2521-2711] -->
+<!-- SECTION "description" [2519-2709] -->
<h3><a name="author" id="author">author</a></h3>
<div class="level3">
@@ -164,7 +166,7 @@ The <strong>author</strong> attribute identifies the name of the author of this
</p>
</div>
-<!-- SECTION "author" [2712-3308] -->
+<!-- SECTION "author" [2710-3306] -->
<h3><a name="comment" id="comment">comment</a></h3>
<div class="level3">
@@ -174,7 +176,7 @@ The <code>comment</code> attribute can contain anything. This attribute can conv
</p>
</div>
-<!-- SECTION "comment" [3309-3582] -->
+<!-- SECTION "comment" [3307-3580] -->
<h3><a name="pinseq" id="pinseq">pinseq</a></h3>
<div class="level3">
@@ -190,7 +192,7 @@ This attribute replaces the obsolete <strong>pin#</strong>=# attribute.
</p>
</div>
-<!-- SECTION "pinseq" [3583-4275] -->
+<!-- SECTION "pinseq" [3581-4273] -->
<h3><a name="pinnumber" id="pinnumber">pinnumber</a></h3>
<div class="level3">
@@ -206,7 +208,7 @@ This attribute replaces the obsolete pin#=# attribute.
</p>
</div>
-<!-- SECTION "pinnumber" [4276-4698] -->
+<!-- SECTION "pinnumber" [4274-4696] -->
<h3><a name="pintype" id="pintype">pintype</a></h3>
<div class="level3">
@@ -253,7 +255,7 @@ Each pin must have a <strong>pintype</strong>=value attribute attached to it and
</table>
</div>
-<!-- SECTION "pintype" [4699-5217] -->
+<!-- SECTION "pintype" [4697-5215] -->
<h3><a name="pinlabel" id="pinlabel">pinlabel</a></h3>
<div class="level3">
@@ -265,7 +267,7 @@ This attribute labels a pin object. This attribute is primarily used by gnetlist
</p>
</div>
-<!-- SECTION "pinlabel" [5218-5551] -->
+<!-- SECTION "pinlabel" [5216-5549] -->
<h3><a name="numslots" id="numslots">numslots</a></h3>
<div class="level3">
@@ -275,7 +277,7 @@ If a component has multiple slots in a physical package (such as a 7400 (NAND) w
</p>
</div>
-<!-- SECTION "numslots" [5552-6015] -->
+<!-- SECTION "numslots" [5550-6013] -->
<h3><a name="slotdef" id="slotdef">slotdef</a></h3>
<div class="level3">
@@ -290,7 +292,7 @@ If a component has multiple slots in a physical package then you must attach a <
</p>
</div>
-<!-- SECTION "slotdef" [6016-6996] -->
+<!-- SECTION "slotdef" [6014-6994] -->
<h3><a name="footprint" id="footprint">footprint</a></h3>
<div class="level3">
@@ -302,7 +304,7 @@ If a component has multiple slots in a physical package then you must attach a <
</p>
</div>
-<!-- SECTION "footprint" [6997-7955] -->
+<!-- SECTION "footprint" [6995-7953] -->
<h3><a name="documentation" id="documentation">documentation</a></h3>
<div class="level3">
@@ -315,12 +317,12 @@ If a component has multiple slots in a physical package then you must attach a <
</p>
</div>
-<!-- SECTION "documentation" [7956-8714] -->
+<!-- SECTION "documentation" [7954-8712] -->
<h2><a name="schematic_only_attributes" id="schematic_only_attributes">Schematic only Attributes</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Schematic only Attributes" [8715-8752] -->
+<!-- SECTION "Schematic only Attributes" [8713-8750] -->
<h3><a name="netname" id="netname">netname</a></h3>
<div class="level3">
@@ -331,7 +333,7 @@ This attribute should be attached to a net object to give it a name. Multiple ne
</p>
</div>
-<!-- SECTION "netname" [8753-9112] -->
+<!-- SECTION "netname" [8751-9110] -->
<h3><a name="source" id="source">source</a></h3>
<div class="level3">
@@ -342,12 +344,12 @@ The source= attribute is used to specify that a symbol has underlying schematics
</p>
</div>
-<!-- SECTION "source" [9113-9734] -->
+<!-- SECTION "source" [9111-9732] -->
<h2><a name="symbol_and_schematic_attributes" id="symbol_and_schematic_attributes">Symbol and Schematic Attributes</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Symbol and Schematic Attributes" [9735-9779] -->
+<!-- SECTION "Symbol and Schematic Attributes" [9733-9777] -->
<h3><a name="refdes" id="refdes">refdes</a></h3>
<div class="level3">
@@ -417,7 +419,7 @@ This attribute is used to specify the reference designator to a particular insta
</table>
</div>
-<!-- SECTION "refdes" [9780-10891] -->
+<!-- SECTION "refdes" [9778-10889] -->
<h3><a name="slot" id="slot">slot</a></h3>
<div class="level3">
@@ -426,7 +428,7 @@ This attribute is used to specify a slot for a slotted component. It should be a
</p>
</div>
-<!-- SECTION "slot" [10892-11189] -->
+<!-- SECTION "slot" [10890-11187] -->
<h3><a name="net" id="net">net</a></h3>
<div class="level3">
@@ -435,7 +437,7 @@ The <strong>net</strong>= attribute is used to create power/ground and arbitrary
</p>
</div>
-<!-- SECTION "net" [11190-11593] -->
+<!-- SECTION "net" [11188-11591] -->
<h3><a name="value" id="value">value</a></h3>
<div class="level3">
@@ -446,7 +448,7 @@ Used mainly in the spice backend netlister to specify the value of the various e
</p>
</div>
-<!-- SECTION "value" [11594-11809] -->
+<!-- SECTION "value" [11592-11807] -->
<h3><a name="symversion" id="symversion">symversion</a></h3>
<div class="level3">
@@ -464,12 +466,34 @@ where major and minor are just plain integers (separated by a period). The major
</p>
</div>
-<!-- SECTION "symversion" [11810-13678] -->
+<!-- SECTION "symversion" [11808-13676] -->
+<h3><a name="dist-license" id="dist-license">dist-license</a></h3>
+<div class="level3">
+
+<p>
+ The <strong>dist-license</strong> attribute is used to specify the redistribution license for the symbol or schematic. It should be the name of a known license. Some examples values are: <acronym title="GNU General Public License">GPL</acronym>, <acronym title="GNU General Public License">GPL</acronym> version 2 only, <acronym title="GNU General Public License">GPL</acronym> version 3 only, public domain, Apache version 2, Modified BSD, X11, etc. <br/>
+ <br/>
+ For a list of licenses see: <a href="http://www.gnu.org/philosophy/license-list.html"; class="urlextern" title="http://www.gnu.org/philosophy/license-list.html"; rel="nofollow">FSF License List</a> and <a href="http://www.opensource.org/licenses/category"; class="urlextern" title="http://www.opensource.org/licenses/category"; rel="nofollow">OSI License List</a>
+</p>
+
+</div>
+<!-- SECTION "dist-license" [13677-14157] -->
+<h3><a name="use-license" id="use-license">use-license</a></h3>
+<div class="level3">
+
+<p>
+ The <strong>use-license</strong> attribute is used to specify the license for how the symbol or schematic can be used by other people in their own circuits or boards. Some example values are: unlimited, personal use only, not for sale, etc.<br/>
+ <br/>
+ <img src="lib/images/smileys/fixme.gif" class="middle" alt="FIXME" /> put a better list of examples here.
+</p>
+
+</div>
+<!-- SECTION "use-license" [14158-14457] -->
<h2><a name="obsolete_attributes" id="obsolete_attributes">Obsolete Attributes</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Obsolete Attributes" [13679-13710] -->
+<!-- SECTION "Obsolete Attributes" [14458-14489] -->
<h3><a name="uref" id="uref">uref</a></h3>
<div class="level3">
@@ -478,7 +502,7 @@ The uref= attribute is obsolete and cannot not be used. It was used to provide t
</p>
</div>
-<!-- SECTION "uref" [13711-13842] -->
+<!-- SECTION "uref" [14490-14621] -->
<h3><a name="name" id="name">name</a></h3>
<div class="level3">
@@ -487,7 +511,7 @@ The <strong>name</strong>= attribute should not be attached or appear in any sym
</p>
</div>
-<!-- SECTION "name" [13843-13996] -->
+<!-- SECTION "name" [14622-14775] -->
<h3><a name="label" id="label">label</a></h3>
<div class="level3">
@@ -496,7 +520,7 @@ The <strong>label</strong>= attribute is obsolete and cannot be used. It was use
</p>
</div>
-<!-- SECTION "label" [13997-14212] -->
+<!-- SECTION "label" [14776-14991] -->
<h3><a name="pin" id="pin">pin#</a></h3>
<div class="level3">
@@ -505,7 +529,7 @@ The <strong>pin#</strong>=# attribute is obsolete and cannot be used. It was use
</p>
</div>
-<!-- SECTION "pin#" [14213-14421] -->
+<!-- SECTION "pin#" [14992-15200] -->
<h3><a name="slot1" id="slot1">slot#</a></h3>
<div class="level3">
@@ -514,7 +538,7 @@ The <strong>slot#</strong>=# attribute is obsolete and cannot be used. It was us
</p>
</div>
-<!-- SECTION "slot#" [14422-14607] -->
+<!-- SECTION "slot#" [15201-15386] -->
<h3><a name="type" id="type">type</a></h3>
<div class="level3">
@@ -523,7 +547,7 @@ The <strong>type</strong>= attribute is obsolete and cannot be used. It was used
</p>
</div>
-<!-- SECTION "type" [14608-14780] -->
+<!-- SECTION "type" [15387-15559] -->
<h3><a name="email" id="email">email</a></h3>
<div class="level3">
@@ -532,7 +556,7 @@ The information in this attribute has been merged with <a href="#author" title="
</p>
</div>
-<!-- SECTION "email" [14781-14865] -->
+<!-- SECTION "email" [15560-15644] -->
<h2><a name="document_revision_history" id="document_revision_history">Document Revision History</a></h2>
<div class="level2">
<table class="inline">
@@ -560,9 +584,12 @@ The information in this attribute has been merged with <a href="#author" title="
<tr>
<td>July 6th, 2004</td><td>Added symversion= attributes.</td>
</tr>
+ <tr>
+ <td>July 10th, 2007</td><td>Added dist-license= and use-license= attributes.</td>
+ </tr>
</table>
</div>
-<!-- SECTION "Document Revision History" [14866-] --></div>
+<!-- SECTION "Document Revision History" [15645-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_pcb-quick_reference.html b/docs/wiki/geda_pcb-quick_reference.html
index ffc8885..9759359 100644
--- a/docs/wiki/geda_pcb-quick_reference.html
+++ b/docs/wiki/geda_pcb-quick_reference.html
@@ -145,7 +145,7 @@
<td class="centeralign"> m </td><td class="leftalign"> move to layer </td><td class="leftalign"> move the object under the cursor to the current layer </td>
</tr>
<tr>
- <td class="centeralign"> shift-m </td><td class="leftalign"> move selection to layer </td><td class="leftalign"> move selected objects to the current working layer (see <a href="http://geda.seul.org/wiki/geda:pcb_tips#how_do_i_move_one_set_of_layer_tracks_to_another_layer"; class="wikilink1" title="geda:pcb_tips">pcb tip</a>) </td>
+ <td class="centeralign"> shift-m </td><td class="leftalign"> move selection to layer </td><td class="leftalign"> move selected objects to the current working layer (see <a href="geda_pcb_tips.html" class="wikilink1" title="geda:pcb_tips">pcb tip</a>) </td>
</tr>
<tr>
<td class="centeralign"> ctrl-m </td><td class="leftalign"> move origin </td><td> set the origin to the current position of the mouse pointer </td>
diff --git a/docs/wiki/geda_pcb_footprints.html b/docs/wiki/geda_pcb_footprints.html
index 7639db8..fde55c8 100644
--- a/docs/wiki/geda_pcb_footprints.html
+++ b/docs/wiki/geda_pcb_footprints.html
@@ -6,7 +6,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>geda:pcb_footprints</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,nofollow" />
+<meta name="robots" content="index,follow" />
<meta name="date" content="2007-07-04T12:51:48-0400" />
<meta name="keywords" content="geda,pcb_footprints" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
diff --git a/docs/wiki/geda_pcb_tips.html b/docs/wiki/geda_pcb_tips.html
index cae794b..6efd72e 100644
--- a/docs/wiki/geda_pcb_tips.html
+++ b/docs/wiki/geda_pcb_tips.html
@@ -7,7 +7,7 @@
<title>geda:pcb_tips</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-06-19T09:16:57-0400" />
+<meta name="date" content="2007-07-24T17:36:35-0400" />
<meta name="keywords" content="geda,pcb_tips" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -75,7 +75,8 @@
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_change_the_routing_style" class="toc">How do I change the routing style?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#i_got_stuck_how_do_i_go_back" class="toc">I got stuck! How do I go back?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_move_one_set_of_layer_tracks_to_a_different_layer" class="toc">How do I move one set of layer tracks to a different layer?</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_change_the_soldermask_clearance_around_a_hole_via" class="toc">How do I change the soldermask clearance around a hole/via?</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_achieve_open_vias_clear_of_soldermask" class="toc">How do I achieve open vias clear of soldermask</a></span></div></li>
+<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_change_the_soldermask_clearance_around_a_hole_pad" class="toc">How do I change the soldermask clearance around a hole/pad?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_change_the_size_of_my_tracks" class="toc">How do I change the size of my tracks?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#how_do_i_drive_a_via_to_connect_a_track_to_a_ground_plane_on_a_different_layer" class="toc">How do I drive a via to connect a track to a ground plane on a different layer?</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#what_is_the_easiest_way_to_create_a_thermal_via" class="toc">What is the easiest way to create a "thermal via"?</a></span></div></li>
@@ -577,15 +578,57 @@ The universal undo key [<strong><code>U</code></strong>] works even while in the
</div>
<!-- SECTION "How do I move one set of layer tracks to a different layer?" [19165-19605] -->
-<h2><a name="how_do_i_change_the_soldermask_clearance_around_a_hole_via" id="how_do_i_change_the_soldermask_clearance_around_a_hole_via">How do I change the soldermask clearance around a hole/via?</a></h2>
+<h2><a name="how_do_i_achieve_open_vias_clear_of_soldermask" id="how_do_i_achieve_open_vias_clear_of_soldermask">How do I achieve open vias clear of soldermask</a></h2>
<div class="level2">
<p>
-You can increase the soldermask clearance from any hole/via by positioning the cursor over the object and typing the [<strong><code>k</code></strong>] key. You can decrease the clearance by using the [<strong><code><shift>-K</code></strong>] key.
+In pcb vias are covered by soldermask by default. You can achieve open vias by setting their clearance value to a proper value. This can be done individually for every object, or collectively for selections of objects.
+</p>
+
+<p>
+For individual vias:
+</p>
+<ol>
+<li class="level1"><div class="li"> Turn on the soldermask layer. This will make the k key refer to the soldermask clearance instead of polygon clearance.</div>
+</li>
+<li class="level1"><div class="li"> Position the mouse above the via (mouse cursor will change in recent versions of pcb)</div>
+</li>
+<li class="level1"><div class="li"> Type [<strong><code>k</code></strong>] several times until soldermask clearance exceeds the diameter of the via pad. Every strike of the key will increase the clearance by 2 mil. The first strike will let the pad of the via pop through the soldermask color. Yet, the actual clearance is only 2 mil at this point. You can decrease the clearance by using the [<strong><code><shift>-K</code></strong>] key.</div>
+</li>
+</ol>
+
+<p>
+ For groups of vias:
+</p>
+<ol>
+<li class="level1"><div class="li"> Turn on the solder mask layer.</div>
+</li>
+<li class="level1"><div class="li"> select the all the vias you want to clear from soldermask. You may switch off all the other layers to conveniently collect exclusively the vias.</div>
+</li>
+<li class="level1"><div class="li"> Type [<strong><code><ctrl>-K</code></strong>] key several times. [<strong><code><shift>-<ctrl>-K</code></strong>] will decrease the clearance of all selected objects.</div>
+</li>
+</ol>
+
+<p>
+ The command interface provides more control over the actual size of the clearance. Type ":" to get the command line window, then type:
+</p>
+<pre class="code">ChangeClearSize(SelectedVias, <delta>)</pre>
+
+<p>
+where <code><delta></code> is a size given in 1/100 of a mil. Thus the number 3000 corresponds to 30 mil. Simple integers for <code><delta></code> will set the clearance to this value. If the value is preceded by a minus "-" or a plus "+" the clearance will be decreased or increased. This also works with <code>SelectedPins</code>, <code>SelectedPads</code>, <code>SelectedLines</code>, <code>SelectedArcs</code> or even <code>SelectedObjects</code>.
+</p>
+
+</div>
+<!-- SECTION "How do I achieve open vias clear of soldermask" [19606-21381] -->
+<h2><a name="how_do_i_change_the_soldermask_clearance_around_a_hole_pad" id="how_do_i_change_the_soldermask_clearance_around_a_hole_pad">How do I change the soldermask clearance around a hole/pad?</a></h2>
+<div class="level2">
+
+<p>
+By default holes and pads will be cleared by an amount given in the corresponding footprint file. Sometimes this clearance might not be what your design needs. You can change the clearance on the fly for individual holes and pads just like vias. See the paragraph above for the details. If pad clearance is not compatible with the demands of your pcb-fab you may consider to make local copies of the footprint files and change the clearance accordingly.
</p>
</div>
-<!-- SECTION "How do I change the soldermask clearance around a hole/via?" [19606-19881] -->
+<!-- SECTION "How do I change the soldermask clearance around a hole/pad?" [21382-21908] -->
<h2><a name="how_do_i_change_the_size_of_my_tracks" id="how_do_i_change_the_size_of_my_tracks">How do I change the size of my tracks?</a></h2>
<div class="level2">
@@ -602,7 +645,7 @@ There are a number of ways to change the size of already laid down tracks:
</ol>
</div>
-<!-- SECTION "How do I change the size of my tracks?" [19882-20819] -->
+<!-- SECTION "How do I change the size of my tracks?" [21909-22846] -->
<h2><a name="how_do_i_drive_a_via_to_connect_a_track_to_a_ground_plane_on_a_different_layer" id="how_do_i_drive_a_via_to_connect_a_track_to_a_ground_plane_on_a_different_layer">How do I drive a via to connect a track to a ground plane on a different layer?</a></h2>
<div class="level2">
<ol>
@@ -625,7 +668,7 @@ There are a number of ways to change the size of already laid down tracks:
</ol>
</div>
-<!-- SECTION "How do I drive a via to connect a track to a ground plane on a different layer?" [20820-21305] -->
+<!-- SECTION "How do I drive a via to connect a track to a ground plane on a different layer?" [22847-23332] -->
<h2><a name="what_is_the_easiest_way_to_create_a_thermal_via" id="what_is_the_easiest_way_to_create_a_thermal_via">What is the easiest way to create a "thermal via"?</a></h2>
<div class="level2">
@@ -644,7 +687,7 @@ Here are some suggestions:
</ul>
</div>
-<!-- SECTION "What is the easiest way to create a thermal via?" [21306-22083] -->
+<!-- SECTION "What is the easiest way to create a thermal via?" [23333-24110] -->
<h2><a name="i_want_to_draw_a_track_between_two_segments_on_the_same_net_but_pcb_won_t_let_me_why" id="i_want_to_draw_a_track_between_two_segments_on_the_same_net_but_pcb_won_t_let_me_why">I want to draw a track between two segments on the same net, but PCB won't let me! Why?</a></h2>
<div class="level2">
@@ -663,7 +706,7 @@ You are likely drawing tracks with auto-DRC on. To connect the two segments, her
</ul>
</div>
-<!-- SECTION "I want to draw a track between two segments on the same net, but PCB won't let me! Why?" [22084-23402] -->
+<!-- SECTION "I want to draw a track between two segments on the same net, but PCB won't let me! Why?" [24111-25429] -->
<h2><a name="pcb_seems_to_munge_my_components_names_and_complains_that_it_can_t_find_proper_nets_for_the_pins_how_come" id="pcb_seems_to_munge_my_components_names_and_complains_that_it_can_t_find_proper_nets_for_the_pins_how_come">PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?</a></h2>
<div class="level2">
@@ -673,7 +716,7 @@ Most likely you named them such that pcb believes they are one part. Lower case
</p>
</div>
-<!-- SECTION "PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?" [23403-24040] -->
+<!-- SECTION "PCB seems to munge my components names and complains that it can't find proper nets for the pins! How come?" [25430-26067] -->
<h2><a name="how_can_i_set_color_and_thickness_of_the_rats_nests" id="how_can_i_set_color_and_thickness_of_the_rats_nests">How can I set color and thickness of the rats nests?</a></h2>
<div class="level2">
@@ -686,12 +729,12 @@ There is currently no <acronym title="Graphical User Interface">GUI</acronym> wa
</p>
</div>
-<!-- SECTION "How can I set color and thickness of the rats nests?" [24041-24392] -->
+<!-- SECTION "How can I set color and thickness of the rats nests?" [26068-26419] -->
<h1><a name="beyond_tracks_and_footprints" id="beyond_tracks_and_footprints">Beyond tracks and footprints</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Beyond tracks and footprints" [24393-24435] -->
+<!-- SECTION "Beyond tracks and footprints" [26420-26462] -->
<h2><a name="how_do_i_trace_a_drawing_a_print_or_another_pcb" id="how_do_i_trace_a_drawing_a_print_or_another_pcb">How do I trace a drawing, a print, or another PCB?</a></h2>
<div class="level2">
@@ -708,7 +751,7 @@ If you donâ??t like to use PCB confined to the area of the board, i.e. if you wa
</p>
</div>
-<!-- SECTION "How do I trace a drawing, a print, or another PCB?" [24436-25276] -->
+<!-- SECTION "How do I trace a drawing, a print, or another PCB?" [26463-27303] -->
<h2><a name="i_can_t_copy_component_pads_in_a_layout._what_gives" id="i_can_t_copy_component_pads_in_a_layout._what_gives">I can't copy component pads in a layout. What gives?</a></h2>
<div class="level2">
@@ -733,7 +776,7 @@ Then I go to paste the copied area… and all that moves are a couple of tr
</p>
</div>
-<!-- SECTION "I can't copy component pads in a layout. What gives?" [25277-25931] -->
+<!-- SECTION "I can't copy component pads in a layout. What gives?" [27304-27958] -->
<h2><a name="how_do_i_fill_areas_with_copper" id="how_do_i_fill_areas_with_copper">How do I fill areas with copper?</a></h2>
<div class="level2">
@@ -742,7 +785,7 @@ Use rectangles and polygon planes. These items will always avoid vias, pads and
</p>
</div>
-<!-- SECTION "How do I fill areas with copper?" [25932-26293] -->
+<!-- SECTION "How do I fill areas with copper?" [27959-28320] -->
<h2><a name="the_polygons_are_shorting_my_tracks_what_can_i_do_about_it" id="the_polygons_are_shorting_my_tracks_what_can_i_do_about_it">The polygons are shorting my tracks! What can I do about it?</a></h2>
<div class="level2">
@@ -751,7 +794,7 @@ You didnâ??t have â??Enable_new_lines_clear_polygonsâ?? checked in the settings
</p>
</div>
-<!-- SECTION "The polygons are shorting my tracks! What can I do about it?" [26294-26943] -->
+<!-- SECTION "The polygons are shorting my tracks! What can I do about it?" [28321-28970] -->
<h2><a name="how_do_i_change_polygon_clearance" id="how_do_i_change_polygon_clearance">How do I change polygon clearance?</a></h2>
<div class="level2">
@@ -764,7 +807,7 @@ The amount of the increment can be configured in the dialog File/Preference/Incr
</p>
</div>
-<!-- SECTION "How do I change polygon clearance?" [26944-27444] -->
+<!-- SECTION "How do I change polygon clearance?" [28971-29471] -->
<h2><a name="how_do_i_hide_the_polygons_while_i_edit_the_layout" id="how_do_i_hide_the_polygons_while_i_edit_the_layout">How do I hide the polygons while I edit the layout?</a></h2>
<div class="level2">
@@ -773,7 +816,7 @@ Put the polygons (and rectangles) on a separate layer. Use the preference to mak
</p>
</div>
-<!-- SECTION "How do I hide the polygons while I edit the layout?" [27445-27853] -->
+<!-- SECTION "How do I hide the polygons while I edit the layout?" [29472-29880] -->
<h2><a name="how_do_i_edit_polygons" id="how_do_i_edit_polygons">How do I edit polygons?</a></h2>
<div class="level2">
@@ -786,7 +829,7 @@ There are four basic ways to edit polygon outlines. You can move and delete vert
</p>
</div>
-<!-- SECTION "How do I edit polygons?" [27854-29039] -->
+<!-- SECTION "How do I edit polygons?" [29881-31066] -->
<h2><a name="how_do_i_place_vias_that_connect_to_a_polygon_for_full_thermal_dissipation_or_full_shielding_integrity" id="how_do_i_place_vias_that_connect_to_a_polygon_for_full_thermal_dissipation_or_full_shielding_integrity">How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?</a></h2>
<div class="level2">
@@ -815,7 +858,7 @@ You can also add another polygon on-top of the polygon to which you want to conn
</p>
</div>
-<!-- SECTION "How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?" [29040-30987] -->
+<!-- SECTION "How do I place vias that connect to a polygon for full thermal dissipation or full shielding integrity?" [31067-33014] -->
<h2><a name="can_polygons_be_un-masked_can_a_polygon_be_made_bare-copper_with_no_solder_mask" id="can_polygons_be_un-masked_can_a_polygon_be_made_bare-copper_with_no_solder_mask">Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)</a></h2>
<div class="level2">
@@ -824,7 +867,7 @@ Currently this is not possible in PCB. The usual workaround (for example if you
</p>
</div>
-<!-- SECTION "Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)" [30988-31545] -->
+<!-- SECTION "Can polygons be un-masked? (Can a polygon be made bare-copper with no solder mask?)" [33015-33572] -->
<h2><a name="how_do_i_place_mounting_holes" id="how_do_i_place_mounting_holes">How do I place mounting holes?</a></h2>
<div class="level2">
@@ -845,7 +888,7 @@ For footprint examples see <a href="http://www.luciani.org/geda/pcb/pcb-footprin
</p>
</div>
-<!-- SECTION "How do I place mounting holes?" [31546-32210] -->
+<!-- SECTION "How do I place mounting holes?" [33573-34237] -->
<h2><a name="why_is_it_possible_to_make_a_thermal_for_pin_but_not_for_a_pad" id="why_is_it_possible_to_make_a_thermal_for_pin_but_not_for_a_pad">Why is it possible to make a thermal for pin, but not for a pad?</a></h2>
<div class="level2">
@@ -854,7 +897,7 @@ The reason is that pins usually have sufficient spacing that the plane surroundi
</p>
</div>
-<!-- SECTION "Why is it possible to make a thermal for pin, but not for a pad?" [32211-32841] -->
+<!-- SECTION "Why is it possible to make a thermal for pin, but not for a pad?" [34238-34868] -->
<h2><a name="can_pcb_be_used_to_make_single_layer_boards" id="can_pcb_be_used_to_make_single_layer_boards">Can PCB be used to make single layer boards?</a></h2>
<div class="level2">
@@ -873,7 +916,7 @@ Yes. Just plot your gerbers and toss any layers that are not needed. You can jus
</p>
</div>
-<!-- SECTION "Can PCB be used to make single layer boards?" [32842-33639] -->
+<!-- SECTION "Can PCB be used to make single layer boards?" [34869-35666] -->
<h2><a name="what_resources_exist_to_process_pcb_files_using_scripts" id="what_resources_exist_to_process_pcb_files_using_scripts">What resources exist to process PCB files using scripts?</a></h2>
<div class="level2">
@@ -892,7 +935,7 @@ One of PCBâ??s great features is that it uses an easily understood <acronym titl
</ol>
</div>
-<!-- SECTION "What resources exist to process PCB files using scripts?" [33640-34924] -->
+<!-- SECTION "What resources exist to process PCB files using scripts?" [35667-36951] -->
<h2><a name="how_do_i_import_external_vector_graphics" id="how_do_i_import_external_vector_graphics">How do I import external vector graphics?</a></h2>
<div class="level2">
@@ -905,7 +948,7 @@ Import of external vector graphics is usefull if an irregular shape of the pcb i
</p>
</div>
-<!-- SECTION "How do I import external vector graphics?" [34925-36003] -->
+<!-- SECTION "How do I import external vector graphics?" [36952-38030] -->
<h2><a name="how_do_i_attach_a_name_to_my_layout" id="how_do_i_attach_a_name_to_my_layout">How Do I attach a name to my layout?</a></h2>
<div class="level2">
@@ -914,12 +957,12 @@ You can set the name of the current pcb with <code>Menu Edit - Edit name of - la
</p>
</div>
-<!-- SECTION "How Do I attach a name to my layout?" [36004-36274] -->
+<!-- SECTION "How Do I attach a name to my layout?" [38031-38301] -->
<h1><a name="auto_router" id="auto_router">Auto Router</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Auto Router" [36275-36300] -->
+<!-- SECTION "Auto Router" [38302-38327] -->
<h2><a name="how_do_i_force_the_autorouter_to_only_put_traces_on_a_particular_layer" id="how_do_i_force_the_autorouter_to_only_put_traces_on_a_particular_layer">How do I force the autorouter to only put traces on a particular layer?</a></h2>
<div class="level2">
@@ -928,7 +971,7 @@ Just unselect the layers you donâ??t want (usually green and blue) by clicking o
</p>
</div>
-<!-- SECTION "How do I force the autorouter to only put traces on a particular layer?" [36301-36512] -->
+<!-- SECTION "How do I force the autorouter to only put traces on a particular layer?" [38328-38539] -->
<h2><a name="how_do_i_force_the_autorouter_to_route_only_within_my_pcb_outline" id="how_do_i_force_the_autorouter_to_route_only_within_my_pcb_outline">How do I force the autorouter to route only within my pcb outline?</a></h2>
<div class="level2">
@@ -937,7 +980,7 @@ You can have the autorouter work only within a given area by drawing a copper po
</p>
</div>
-<!-- SECTION "How do I force the autorouter to route only within my pcb outline?" [36513-36944] -->
+<!-- SECTION "How do I force the autorouter to route only within my pcb outline?" [38540-38971] -->
<h2><a name="how_do_i_route_power_and_ground_planes_with_the_autorouter" id="how_do_i_route_power_and_ground_planes_with_the_autorouter">How do I route power and ground planes with the autorouter?</a></h2>
<div class="level2">
@@ -946,7 +989,7 @@ Connect the polygon that will become your power planes to a net and the autorout
</p>
</div>
-<!-- SECTION "How do I route power and ground planes with the autorouter?" [36945-37226] -->
+<!-- SECTION "How do I route power and ground planes with the autorouter?" [38972-39253] -->
<h2><a name="the_layout_produced_by_the_autorouter_is_inefficient" id="the_layout_produced_by_the_autorouter_is_inefficient">The layout produced by the autorouter is inefficient!</a></h2>
<div class="level2">
@@ -955,7 +998,7 @@ This is a technological limitation of the current auto router. It is gridless an
</p>
</div>
-<!-- SECTION "The layout produced by the autorouter is inefficient!" [37227-37407] -->
+<!-- SECTION "The layout produced by the autorouter is inefficient!" [39254-39434] -->
<h2><a name="the_layout_produced_by_the_autorouter_is_ugly" id="the_layout_produced_by_the_autorouter_is_ugly">The layout produced by the autorouter is ugly!</a></h2>
<div class="level2">
@@ -964,12 +1007,12 @@ Have you tried the various clean-up tools under connects–>optimize rout
</p>
</div>
-<!-- SECTION "The layout produced by the autorouter is ugly!" [37408-37550] -->
+<!-- SECTION "The layout produced by the autorouter is ugly!" [39435-39577] -->
<h1><a name="gerber_generation_and_file_i_o_issues" id="gerber_generation_and_file_i_o_issues">Gerber generation and file I/O issues</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Gerber generation and file I/O issues" [37551-37603] -->
+<!-- SECTION "Gerber generation and file I/O issues" [39578-39630] -->
<h2><a name="how_do_i_make_a_board_outline_to_go_with_my_gerbers_to_the_board_maker" id="how_do_i_make_a_board_outline_to_go_with_my_gerbers_to_the_board_maker">How do I make a board outline to go with my gerbers to the board maker?</a></h2>
<div class="level2">
@@ -994,7 +1037,7 @@ Itâ??s also possible to edit the native .pcb file format of your layout. I usual
)</pre>
</div>
-<!-- SECTION "How do I make a board outline to go with my gerbers to the board maker?" [37604-38450] -->
+<!-- SECTION "How do I make a board outline to go with my gerbers to the board maker?" [39631-40477] -->
<h2><a name="i_m_done_with_my_layout._how_should_i_check_my_design" id="i_m_done_with_my_layout._how_should_i_check_my_design">I'm done with my layout. How should I check my design?</a></h2>
<div class="level2">
<ul>
@@ -1027,12 +1070,12 @@ Besides running the DRC checker, it is essential to check your Gerber files. The
</ul>
</div>
-<!-- SECTION "I'm done with my layout. How should I check my design?" [38451-40670] -->
+<!-- SECTION "I'm done with my layout. How should I check my design?" [40478-42697] -->
<h1><a name="exporting_other_formatsraster_and_ps_files" id="exporting_other_formatsraster_and_ps_files">Exporting Other Formats: Raster and PS Files</a></h1>
<div class="level1">
</div>
-<!-- SECTION "Exporting Other Formats: Raster and PS Files" [40671-40729] -->
+<!-- SECTION "Exporting Other Formats: Raster and PS Files" [42698-42756] -->
<h2><a name="what_is_xy-max_in_the_png_export_dialog_box" id="what_is_xy-max_in_the_png_export_dialog_box">What is xy-max in the PNG export dialog box?</a></h2>
<div class="level2">
@@ -1041,7 +1084,7 @@ It limits the size of the image to NxN pixels, but maintains the aspect ratio.
</p>
</div>
-<!-- SECTION "What is xy-max in the PNG export dialog box?" [40730-41000] -->
+<!-- SECTION "What is xy-max in the PNG export dialog box?" [42757-43027] -->
<h1><a name="you_didn_t_answer_my_question._what_other_resources_exist_for_pcb_information" id="you_didn_t_answer_my_question._what_other_resources_exist_for_pcb_information">You didn't answer my question. What other resources exist for PCB information?</a></h1>
<div class="level1">
@@ -1056,6 +1099,6 @@ You can get fast responses from the geda-user email list. If you havenâ??t found
</p>
</div>
-<!-- SECTION "You didn't answer my question. What other resources exist for PCB information?" [41001-] --></div>
+<!-- SECTION "You didn't answer my question. What other resources exist for PCB information?" [43028-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_scm.html b/docs/wiki/geda_scm.html
index 499b15f..3c2ad43 100644
--- a/docs/wiki/geda_scm.html
+++ b/docs/wiki/geda_scm.html
@@ -6,8 +6,8 @@
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>geda:scm</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="noindex,nofollow" />
-<meta name="date" content="2007-07-04T19:34:57-0400" />
+<meta name="robots" content="index,follow" />
+<meta name="date" content="2007-07-14T20:01:43-0400" />
<meta name="keywords" content="geda,scm" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -167,7 +167,7 @@ Keep in mind that some of these tutorials are a little dated and may not cover c
</p>
</div>
-<!-- SECTION "Learning to use git" [1376-2242] -->
+<!-- SECTION "Learning to use git" [1376-2245] -->
<h2><a name="accessing_the_repository" id="accessing_the_repository">Accessing the repository</a></h2>
<div class="level2">
@@ -177,6 +177,11 @@ Keep in mind that some of these tutorials are a little dated and may not cover c
<pre class="code">git clone git://git.gpleda.org/gaf.git</pre>
<p>
+ If you are behind a firewall, you can also use the http access method (if you built git with curl and libcurl support) using:
+</p>
+<pre class="code">git clone http://git.gpleda.org/git/gaf.git</pre>
+
+<p>
For developer git access, you should contact Ales Hvezda to get an <acronym title="Secure Shell">SSH</acronym> public key installed and an account; having done so, the git <acronym title="Uniform Resource Locator">URL</acronym> to push to is:
</p>
<pre class="code">git clone ssh://<username>@git.gpleda.org/home/git/gaf.git</pre>
@@ -198,12 +203,12 @@ Port 5022</pre>
</p>
</div>
-<!-- SECTION "Accessing the repository" [2243-3053] -->
+<!-- SECTION "Accessing the repository" [2246-3230] -->
<h2><a name="making_and_committing_changes" id="making_and_committing_changes">Making and committing changes</a></h2>
<div class="level2">
</div>
-<!-- SECTION "Making and committing changes" [3054-3098] -->
+<!-- SECTION "Making and committing changes" [3231-3275] -->
<h3><a name="setting_up_user_information" id="setting_up_user_information">Setting up user information</a></h3>
<div class="level3">
@@ -214,7 +219,7 @@ Port 5022</pre>
$ git config --global user.email you@xxxxxxxxxxxxxxxxxxxxxx</pre>
</div>
-<!-- SECTION "Setting up user information" [3099-3356] -->
+<!-- SECTION "Setting up user information" [3276-3533] -->
<h3><a name="committing_patches_from_other_contributors" id="committing_patches_from_other_contributors">Committing patches from other contributors</a></h3>
<div class="level3">
@@ -284,7 +289,7 @@ Commit the patch, making sure that the Authorâ??s name and e-mail address are sp
</p>
</div>
-<!-- SECTION "Committing patches from other contributors" [3357-5208] -->
+<!-- SECTION "Committing patches from other contributors" [3534-5385] -->
<h3><a name="writing_good_commit_messages" id="writing_good_commit_messages">Writing good commit messages</a></h3>
<div class="level3">
@@ -313,7 +318,7 @@ currenly implemented as a macro.
</pre>
</div>
-<!-- SECTION "Writing good commit messages" [5209-6190] -->
+<!-- SECTION "Writing good commit messages" [5386-6367] -->
<h3><a name="push_is_destructive" id="push_is_destructive">Push is Destructive</a></h3>
<div class="level3">
@@ -326,7 +331,7 @@ Unlike <acronym title="Concurrent Versions System">CVS</acronym>, it is not the
</p>
</div>
-<!-- SECTION "Push is Destructive" [6191-6555] -->
+<!-- SECTION "Push is Destructive" [6368-6732] -->
<h2><a name="how_do_i" id="how_do_i">How Do I ... ?</a></h2>
<div class="level2">
@@ -335,7 +340,7 @@ Unlike <acronym title="Concurrent Versions System">CVS</acronym>, it is not the
</p>
</div>
-<!-- SECTION "How Do I ... ?" [6556-6679] -->
+<!-- SECTION "How Do I ... ?" [6733-6856] -->
<h3><a name="get_a_copy_of_geda_gaf_git_repository" id="get_a_copy_of_geda_gaf_git_repository">... get a copy of gEDA/gaf git repository?</a></h3>
<div class="level3">
@@ -350,7 +355,7 @@ Unlike <acronym title="Concurrent Versions System">CVS</acronym>, it is not the
<pre class="code">$ git clone git://git.gpleda.org/home/git/gaf.git</pre>
</div>
-<!-- SECTION "... get a copy of gEDA/gaf git repository?" [6680-6899] -->
+<!-- SECTION "... get a copy of gEDA/gaf git repository?" [6857-7076] -->
<h3><a name="keep_my_local_copy_current" id="keep_my_local_copy_current">... keep my local copy current?</a></h3>
<div class="level3">
@@ -366,7 +371,7 @@ Unlike <acronym title="Concurrent Versions System">CVS</acronym>, it is not the
$ git rebase origin</pre>
</div>
-<!-- SECTION "... keep my local copy current?" [6900-7314] -->
+<!-- SECTION "... keep my local copy current?" [7077-7491] -->
<h3><a name="commit_my_changes_to_the_local_git_repository" id="commit_my_changes_to_the_local_git_repository">... commit my changes to the local git repository?</a></h3>
<div class="level3">
<pre class="code">$ git commit -a </pre>
@@ -381,7 +386,7 @@ If you want to commit files in the current directory or want to explicitly commi
<pre class="code">$ git commit filename1 filename2</pre>
</div>
-<!-- SECTION "... commit my changes to the local git repository?" [7315-7868] -->
+<!-- SECTION "... commit my changes to the local git repository?" [7492-8045] -->
<h3><a name="undo_any_uncommitted_local_changes" id="undo_any_uncommitted_local_changes">... undo any uncommitted local changes?</a></h3>
<div class="level3">
<pre class="code">$ git checkout -f </pre>
@@ -391,7 +396,7 @@ If you want to commit files in the current directory or want to explicitly commi
</p>
</div>
-<!-- SECTION "... undo any uncommitted local changes?" [7869-8022] -->
+<!-- SECTION "... undo any uncommitted local changes?" [8046-8199] -->
<h3><a name="fix_change_my_last_commit" id="fix_change_my_last_commit">... fix/change my last commit?</a></h3>
<div class="level3">
<pre class="code">$ Edit whatever files
@@ -402,6 +407,6 @@ $ git commit --amend filename1..filenameN </pre>
</p>
</div>
-<!-- SECTION "... fix/change my last commit?" [8023-] --></div>
+<!-- SECTION "... fix/change my last commit?" [8200-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_suse_rpm_installation.html b/docs/wiki/geda_suse_rpm_installation.html
index b788e59..4196c74 100644
--- a/docs/wiki/geda_suse_rpm_installation.html
+++ b/docs/wiki/geda_suse_rpm_installation.html
@@ -7,7 +7,7 @@
<title>geda:suse_rpm_installation</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-27T01:25:18-0400" />
+<meta name="date" content="2007-07-28T14:58:18-0400" />
<meta name="keywords" content="geda,suse_rpm_installation" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -47,27 +47,27 @@
<div class="level1">
</div>
-<!-- SECTION "Installing gEDA rpm packages on SuSE" [1-53] -->
+<!-- SECTION "Installing gEDA rpm packages on SuSE" [1-55] -->
<h2><a name="available_rpm_packages" id="available_rpm_packages">Available rpm packages</a></h2>
<div class="level2">
<ul>
-<li class="level1"><div class="li"> libgeda (20070526)</div>
+<li class="level1"><div class="li"> libgeda (1.0.1 alias 20070626)</div>
</li>
-<li class="level1"><div class="li"> geda-docs (20070526)</div>
+<li class="level1"><div class="li"> geda-docs (1.0.1 alias 20070626)</div>
</li>
-<li class="level1"><div class="li"> geda-examples (20070526)</div>
+<li class="level1"><div class="li"> geda-examples (1.0.1 alias 20070626)</div>
</li>
-<li class="level1"><div class="li"> geda-gattrib (20070526)</div>
+<li class="level1"><div class="li"> geda-gattrib (1.0.1 alias 20070626)</div>
</li>
-<li class="level1"><div class="li"> geda-gnetlist (20070526)</div>
+<li class="level1"><div class="li"> geda-gnetlist (1.0.1 alias 20070626)</div>
</li>
-<li class="level1"><div class="li"> geda-gschem (20070526)</div>
+<li class="level1"><div class="li"> geda-gschem (1.0.1 alias 20070626)</div>
</li>
-<li class="level1"><div class="li"> geda-gsymcheck (20070526)</div>
+<li class="level1"><div class="li"> geda-gsymcheck (1.0.1 alias 20070626)</div>
</li>
-<li class="level1"><div class="li"> geda-symbols (20070526)</div>
+<li class="level1"><div class="li"> geda-symbols (1.0.1 alias 20070626)</div>
</li>
-<li class="level1"><div class="li"> geda-utils (20070526)</div>
+<li class="level1"><div class="li"> geda-utils (1.0.1 alias 20070626)</div>
</li>
<li class="level1"><div class="li"> gerbv (1.0.2)</div>
</li>
@@ -81,16 +81,16 @@
</li>
<li class="level1"><div class="li"> gwave (20051222)</div>
</li>
-<li class="level1"><div class="li"> gtkwave (3.0.28)</div>
+<li class="level1"><div class="li"> gtkwave (3.0.29)</div>
</li>
<li class="level1"><div class="li"> dinotrace (9.3e)</div>
</li>
-<li class="level1"><div class="li"> verilog (0.8.4)</div>
+<li class="level1"><div class="li"> verilog (0.8.5)</div>
</li>
</ul>
</div>
-<!-- SECTION "Available rpm packages" [54-522] -->
+<!-- SECTION "Available rpm packages" [56-633] -->
<h2><a name="installing_packages_from_the_suse_build_service" id="installing_packages_from_the_suse_build_service">Installing Packages from the SuSE Build Service</a></h2>
<div class="level2">
<ol>
@@ -114,8 +114,12 @@
For more informations read the <a href="http://en.opensuse.org/Build_Service/User"; class="urlextern" title="http://en.opensuse.org/Build_Service/User"; rel="nofollow"> generic installation notes</a> of the <a href="http://en.opensuse.org/Build_Service"; class="urlextern" title="http://en.opensuse.org/Build_Service"; rel="nofollow"> OpenSuSE Build Service</a>
</p>
+<p>
+You can also browse through repositories first: <a href="http://software.opensuse.org/download/home:/werner2101/SUSE_Linux_10.0/repodata/"; class="urlextern" title="http://software.opensuse.org/download/home:/werner2101/SUSE_Linux_10.0/repodata/"; rel="nofollow"> SUSE_Linux_10.0 repo</a>, <a href="http://software.opensuse.org/download/home:/werner2101/SUSE_Linux_10.1/repodata/"; class="urlextern" title="http://software.opensuse.org/download/home:/werner2101/SUSE_Linux_10.1/repodata/"; rel="nofollow"> SUSE_Linux_10.1 repo</a>, <a href="http://software.opensuse.org/download/home:/werner2101/openSUSE_10.2/repodata/"; class="urlextern" title="http://software.opensuse.org/download/home:/werner2101/openSUSE_10.2/repodata/"; rel="nofollow"> openSUSE_10.2 repo</a>
+</p>
+
</div>
-<!-- SECTION "Installing Packages from the SuSE Build Service" [523-1193] -->
+<!-- SECTION "Installing Packages from the SuSE Build Service" [634-1677] -->
<h2><a name="distribution_specific_notes" id="distribution_specific_notes">Distribution specific notes</a></h2>
<div class="level2">
@@ -124,7 +128,7 @@
</p>
</div>
-<!-- SECTION "Distribution specific notes" [1194-1311] -->
+<!-- SECTION "Distribution specific notes" [1678-1795] -->
<h3><a name="suse_10.0" id="suse_10.0">SuSE 10.0</a></h3>
<div class="level3">
<ul>
@@ -133,7 +137,7 @@
</ul>
</div>
-<!-- SECTION "SuSE 10.0" [1312-1336] -->
+<!-- SECTION "SuSE 10.0" [1796-1820] -->
<h3><a name="suse_10.1" id="suse_10.1">SuSE 10.1</a></h3>
<div class="level3">
<ul>
@@ -142,7 +146,7 @@
</ul>
</div>
-<!-- SECTION "SuSE 10.1" [1337-1361] -->
+<!-- SECTION "SuSE 10.1" [1821-1845] -->
<h3><a name="suse_10.2" id="suse_10.2">SuSE 10.2</a></h3>
<div class="level3">
<ul>
@@ -151,6 +155,6 @@
</ul>
</div>
-<!-- SECTION "SuSE 10.2" [1362-] --></div>
+<!-- SECTION "SuSE 10.2" [1846-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_tragesym_tutorial.html b/docs/wiki/geda_tragesym_tutorial.html
index aeda1cb..e20df8d 100644
--- a/docs/wiki/geda_tragesym_tutorial.html
+++ b/docs/wiki/geda_tragesym_tutorial.html
@@ -7,7 +7,7 @@
<title>geda:tragesym_tutorial</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:25-0400" />
+<meta name="date" content="2007-07-28T03:55:28-0400" />
<meta name="keywords" content="geda,tragesym_tutorial" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -74,16 +74,16 @@
</ul>
</div>
-<!-- SECTION "Required Steps" [451-872] -->
+<!-- SECTION "Required Steps" [451-873] -->
<h2><a name="step1open_a_tragesym_template_file" id="step1open_a_tragesym_template_file">Step1: Open a tragesym template file</a></h2>
<div class="level2">
<p>
- tragesym comes with two template files. One is <a href="_media/tragesym_template" class="media mediafile mf_" title="tragesym:template.txt">ASCII text</a>, the second is a <a href="_media/001tragesym_template" class="media mediafile mf_ods" title="tragesym:template.ods">OpenOffice spreadsheet file</a>. You can obtain them from the gEDA utility package, too (utils/examples/tragesym/template.src and utils/examples/tragesym/template.ods). If you prefer a different spreadsheet program, like gnumeric or kspread, just create your own template out of the textual template file. The only difference between the textual template and the spreadsheet template is the syntax of the key value pairs in the [options] and [geda_attr] sections. The textfile splits them with an equal sign (key=value), the spreadsheet has the value in the second column (which becomes a tab after beeing exported).
+ tragesym comes with two template files. One is <a href="_media/tragesym_template2.txt.txt" class="media mediafile mf_src" title="tragesym:template2.txt.src">ASCII text</a>, the second is a <a href="_media/tragesym_template2" class="media mediafile mf_ods" title="tragesym:template2.ods">OpenOffice spreadsheet file</a>. You can obtain them from the gEDA utility package, too (utils/examples/tragesym/template.src and utils/examples/tragesym/template.ods). If you prefer a different spreadsheet program, like gnumeric or kspread, just create your own template out of the textual template file. The only difference between the textual template and the spreadsheet template is the syntax of the key value pairs in the [options] and [geda_attr] sections. The textfile splits them with an equal sign (key=value), the spreadsheet has the value in the second column (which becomes a tab after beeing exported).
</p>
</div>
-<!-- SECTION "Step1: Open a tragesym template file" [873-1666] -->
+<!-- SECTION "Step1: Open a tragesym template file" [874-1673] -->
<h2><a name="step2download_the_part_data_sheet_and_find_the_pin_list" id="step2download_the_part_data_sheet_and_find_the_pin_list">Step2: Download the part data sheet and find the pin list</a></h2>
<div class="level2">
@@ -100,7 +100,7 @@ Inside the datasheet the pin list may only be in the drawing of the pin configur
</p>
</div>
-<!-- SECTION "Step2: Download the part data sheet and find the pin list" [1667-2440] -->
+<!-- SECTION "Step2: Download the part data sheet and find the pin list" [1674-2447] -->
<h2><a name="step3copy_the_pin_list_into_an_editor_and_prepare_it" id="step3copy_the_pin_list_into_an_editor_and_prepare_it">Step3: Copy the pin list into an editor and prepare it</a></h2>
<div class="level2">
@@ -141,7 +141,7 @@ The pictures above illustrate the steps:
</ul>
</div>
-<!-- SECTION "Step3: Copy the pin list into an editor and prepare it" [2441-3816] -->
+<!-- SECTION "Step3: Copy the pin list into an editor and prepare it" [2448-3823] -->
<h2><a name="step4insert_all_missing_data_into_the_spreadsheet" id="step4insert_all_missing_data_into_the_spreadsheet">Step4: Insert all missing data into the spreadsheet</a></h2>
<div class="level2">
@@ -196,7 +196,7 @@ Before going on set the attributes and the options to appropriate values.
</p>
</div>
-<!-- SECTION "Step4: Insert all missing data into the spreadsheet" [3817-5025] -->
+<!-- SECTION "Step4: Insert all missing data into the spreadsheet" [3824-5032] -->
<h2><a name="step5export_the_spreadsheet_into_a_tab_seperated_text_file" id="step5export_the_spreadsheet_into_a_tab_seperated_text_file">Step5: Export the spreadsheet into a tab seperated text file</a></h2>
<div class="level2">
@@ -205,7 +205,7 @@ Before going on set the attributes and the options to appropriate values.
</p>
</div>
-<!-- SECTION "Step5: Export the spreadsheet into a tab seperated text file" [5026-5290] -->
+<!-- SECTION "Step5: Export the spreadsheet into a tab seperated text file" [5033-5297] -->
<h2><a name="step6execute_tragesym_and_create_the_symbol" id="step6execute_tragesym_and_create_the_symbol">Step6: execute tragesym and create the symbol</a></h2>
<div class="level2">
@@ -222,7 +222,7 @@ If tragesym says that thereâ??s an error, just make some changes in the spreadsh
</p>
</div>
-<!-- SECTION "Step6: execute tragesym and create the symbol" [5291-5611] -->
+<!-- SECTION "Step6: execute tragesym and create the symbol" [5298-5618] -->
<h2><a name="step7check_the_result_with_gschem_and_do_some_artwork" id="step7check_the_result_with_gschem_and_do_some_artwork">Step7: check the result with gschem and do some artwork</a></h2>
<div class="level2">
@@ -247,7 +247,7 @@ Now we have a complete symbol. You can copy the symbol to your local symbol libr
</p>
</div>
-<!-- SECTION "Step7: check the result with gschem and do some artwork" [5612-6253] -->
+<!-- SECTION "Step7: check the result with gschem and do some artwork" [5619-6260] -->
<h2><a name="conclusion" id="conclusion">Conclusion</a></h2>
<div class="level2">
@@ -256,7 +256,7 @@ This was a simple example with a small pincount, but this method really pays off
</p>
</div>
-<!-- SECTION "Conclusion" [6254-6418] -->
+<!-- SECTION "Conclusion" [6261-6425] -->
<h2><a name="credits" id="credits">Credits</a></h2>
<div class="level2">
@@ -265,6 +265,6 @@ Many thanks to <Russ.Dill(AT)asu.edu>, who wrote the first version of this
</p>
</div>
-<!-- SECTION "Credits" [6419-] --></div>
+<!-- SECTION "Credits" [6426-] --></div>
</body>
</html>
diff --git a/docs/wiki/geda_transistor_guide.html b/docs/wiki/geda_transistor_guide.html
index e482d0a..6dd4223 100644
--- a/docs/wiki/geda_transistor_guide.html
+++ b/docs/wiki/geda_transistor_guide.html
@@ -6,8 +6,8 @@
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>geda:transistor_guide</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:57:07-0400" />
+<meta name="robots" content="noindex,nofollow" />
+<meta name="date" content="2007-08-18T14:59:56-0400" />
<meta name="keywords" content="geda,transistor_guide" />
<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -66,7 +66,7 @@
</p>
</div>
-<!-- SECTION "gschem symbols" [532-2550] -->
+<!-- SECTION "gschem symbols" [532-2551] -->
<h2><a name="pcb_elements" id="pcb_elements">PCB Elements</a></h2>
<div class="level2">
@@ -88,14 +88,14 @@ Hereâ??s a description of what seems to be the most common transistor outline co
</li>
<li class="level1"><div class="li"> <em>Small Signal Transistors - Metal</em>: Look at the transistor bottom with the pins pointing at you. The pins are numbered clockwise from the index tab (1,2,3,…) Metal can packages such as TO-18, TO-39, or TO-72 will frequently have 3 or 4 pins, while the TO-5 may have 3, 4, 5, 6, 8, or 10 pins. Because of the variable pin numbers, you could, for example, name the PCB elements TO-18-3 and TO-18-4, or you could use TO-18 and TO-18-4 assuming that a three pin can is more common and thus earns the base TO-18 element name.</div>
</li>
-<li class="level1"><div class="li"> <em>Small Signal Transistors - Plastic</em>: Look at the transistor package flat side (where the lettering is) with the pins pointing down. Almost all packages where the three pins are in a straight line will have the left to right pin number ordering of (1,2,3) and these can be the base TO-92 PCB element. There are a very small number of cases where the pins will be in a straight line and numbered left to right (3,2,1). You could have a distinct PCB element for these, but you could also decide to ignore the manufacturerâ??s pin numbering and pretend itâ??s the more common (1,2,3). However, if the package has the middle pin offset so the pins are in a triangular arrangement, the pin number ordering will frequently be (3,2,1) and this will possibly require a custom PCB element. But see my comments about my <a href="playground_transistor_guide.html" class="wikilink1" title="playground:transistor_guide">TO-92o</a> element below.</div>
+<li class="level1"><div class="li"> <em>Small Signal Transistors - Plastic</em>: Look at the transistor package flat side (where the lettering is) with the pins pointing down. Almost all packages where the three pins are in a straight line will have the left to right pin number ordering of (1,2,3) and these can be the base TO-92 PCB element. There are a very small number of cases where the pins will be in a straight line and numbered left to right (3,2,1). You could have a distinct PCB element for these, but you could also decide to ignore the manufacturerâ??s pin numbering and pretend itâ??s the more common (1,2,3). However, if the package has the middle pin offset so the pins are in a triangular arrangement, the pin number ordering will frequently be (3,2,1) and this will possibly require a custom PCB element. But see my comments about my <span class="curid"><a href="http://geda.seul.org/wiki/geda:transistor_guide#special_cases"; class="wikilink1" title="geda:transistor_guide">TO-92o</a></span> element below.</div>
</li>
<li class="level1"><div class="li"> <em>Surface Mount Transistors</em>: The SOT (Small Outline Transistor) packages are much more standard than the TO packages and the pins are consistently numbered counterclockwise from the top left as are IC packages. But for a transistor that has a TO and a SOT version, you canâ??t simply change the <strong>footprint</strong> attribute on the schematic because the package pin numbers donâ??t map the same to the emitter, base, and collector. You need a separate <em><strong>gschem</strong></em> symbol for them. For example: <strong>2N3904.sym</strong> for the TO and <strong>MMBT3904.sym</strong> for the SOT.</div>
</li>
</ul>
</div>
-<!-- SECTION "PCB Elements" [2551-6419] -->
+<!-- SECTION "PCB Elements" [2552-6414] -->
<h2><a name="general_procedure" id="general_procedure">General Procedure</a></h2>
<div class="level2">
@@ -114,7 +114,7 @@ Hereâ??s a description of what seems to be the most common transistor outline co
</ol>
</div>
-<!-- SECTION "General Procedure" [6420-7546] -->
+<!-- SECTION "General Procedure" [6415-7541] -->
<h2><a name="special_cases" id="special_cases">Special Cases</a></h2>
<div class="level2">
<ol>
@@ -134,6 +134,6 @@ tutorial by Bill Wilson (bill–at–gkrellm.net)
</p>
</div>
-<!-- SECTION "Special Cases" [7547-] --></div>
+<!-- SECTION "Special Cases" [7542-] --></div>
</body>
</html>
diff --git a/docs/wiki/index.html b/docs/wiki/index.html
index 7d7915d..6297660 100644
--- a/docs/wiki/index.html
+++ b/docs/wiki/index.html
@@ -7,7 +7,7 @@
<title>start</title>
<meta name="generator" content="DokuWiki Release rc2007-05-24" />
<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-06-22T08:52:51-0400" />
+<meta name="date" content="2007-07-27T08:15:10-0400" />
<meta name="keywords" content="start" />
<link rel="search" type="application/opensearchdescription+xml" href="lib/exe/opensearch" title="geda Wiki" />
<link rel="start" href="http://geda.seul.org/wiki/"; />
@@ -47,7 +47,7 @@
<div class="level1">
</div>
-<!-- SECTION "gEDA Project Wiki" [1-33] -->
+<!-- SECTION "gEDA Project Wiki" [2-34] -->
<h2><a name="what_is_geda" id="what_is_geda">What is gEDA?</a></h2>
<div class="level2">
@@ -64,7 +64,7 @@ All of the software in the gEDA suite can be found on the <a href="http://geda.s
</p>
</div>
-<!-- SECTION "What is gEDA?" [34-1159] -->
+<!-- SECTION "What is gEDA?" [35-1160] -->
<h2><a name="official_project_documentation" id="official_project_documentation">Official Project documentation</a></h2>
<div class="level2">
@@ -77,7 +77,7 @@ These are the official project docs. They have been converted from LaTeX and <a
</ul>
</div>
-<!-- SECTION "Official Project documentation" [1160-1460] -->
+<!-- SECTION "Official Project documentation" [1161-1461] -->
<h2><a name="faqs_and_informal_project_documentation" id="faqs_and_informal_project_documentation">FAQs and Informal Project Documentation</a></h2>
<div class="level2">
@@ -116,7 +116,7 @@ These are FAQs, HOWTOs, and tips/tricks to help you with the practical details o
</ul>
</div>
-<!-- SECTION "FAQs and Informal Project Documentation" [1461-2909] -->
+<!-- SECTION "FAQs and Informal Project Documentation" [1462-2910] -->
<h2><a name="developer_documentation" id="developer_documentation">Developer Documentation</a></h2>
<div class="level2">
@@ -145,7 +145,7 @@ These are pages concerning the development of the gEDA suite.
</ul>
</div>
-<!-- SECTION "Developer Documentation" [2910-4079] -->
+<!-- SECTION "Developer Documentation" [2911-4080] -->
<h2><a name="talks" id="talks">Talks</a></h2>
<div class="level2">
@@ -158,7 +158,7 @@ These are slides of presentations done about gEDA. They provide a good top-leve
</ul>
</div>
-<!-- SECTION "Talks" [4080-4319] -->
+<!-- SECTION "Talks" [4081-4320] -->
<h2><a name="translations" id="translations">Translations</a></h2>
<div class="level2">
<ul>
@@ -169,7 +169,7 @@ These are slides of presentations done about gEDA. They provide a good top-leve
</ul>
</div>
-<!-- SECTION "Translations" [4320-4435] -->
+<!-- SECTION "Translations" [4321-4436] -->
<h2><a name="geda_users" id="geda_users">gEDA Users</a></h2>
<div class="level2">
@@ -182,7 +182,7 @@ The so-called â??Free Dogâ?? organization ( <a href="http://freeedaug.org/"; clas
</p>
</div>
-<!-- SECTION "gEDA Users" [4436-4805] -->
+<!-- SECTION "gEDA Users" [4437-4806] -->
<h2><a name="about_this_wiki" id="about_this_wiki">About this Wiki</a></h2>
<div class="level2">
@@ -195,6 +195,6 @@ Anyone is welcome to contribute. Unlike wikipedia there is no button to create a
</p>
</div>
-<!-- SECTION "About this Wiki" [4806-] --></div>
+<!-- SECTION "About this Wiki" [4807-] --></div>
</body>
</html>
diff --git a/docs/wiki/playground_transistor_guide.html b/docs/wiki/playground_transistor_guide.html
deleted file mode 100644
index eedf96a..0000000
--- a/docs/wiki/playground_transistor_guide.html
+++ /dev/null
@@ -1,141 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en"
- lang="en" dir="ltr">
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <title>playground:transistor_guide</title>
-<meta name="generator" content="DokuWiki Release rc2007-05-24" />
-<meta name="robots" content="index,follow" />
-<meta name="date" content="2007-05-24T22:27:24-0400" />
-<meta name="keywords" content="playground,transistor_guide" />
-<link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php"; title="geda Wiki" />
-<link rel="start" href="http://geda.seul.org/wiki/"; />
-<link rel="contents" href="http://geda.seul.org/wiki/playground:transistor_guide?do=index"; title="Index" />
-<link rel="alternate" type="application/rss+xml" title="Recent Changes" href="http://geda.seul.org/wiki/feed.php"; />
-<link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=playground"; />
-<link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/playground:transistor_guide"; />
-<link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/playground:transistor_guide"; />
-<link rel="stylesheet" media="all" type="text/css" href="lib/exe/css" />
-<link rel="stylesheet" media="screen" type="text/css" href="lib/exe/001css" />
-<link rel="stylesheet" media="print" type="text/css" href="lib/exe/002css" />
-</head>
-<body>
-<div class="dokuwiki export">
-<div class="toc">
-<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
-<div id="toc__inside">
-
-<ul class="toc">
-<li class="level1"><div class="li"><span class="li"><a href="#gschem_symbol_and_pcb_element_transistor_guide" class="toc">gschem Symbol and PCB Element Transistor Guide</a></span></div>
-<ul class="toc">
-<li class="level2"><div class="li"><span class="li"><a href="#gschem_symbols" class="toc">gschem symbols</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#pcb_elements" class="toc">PCB Elements</a></span></div></li>
-<li class="level2"><div class="li"><span class="li"><a href="#general_procedure" class="toc">General Procedure</a></span></div>
-<ul class="toc">
-<li class="level3"><div class="li"><span class="li"><a href="#special_cases" class="toc">Special Cases</a></span></div></li></ul>
-</li></ul>
-</li></ul>
-</div>
-</div>
-
-
-
-<h1><a name="gschem_symbol_and_pcb_element_transistor_guide" id="gschem_symbol_and_pcb_element_transistor_guide">gschem Symbol and PCB Element Transistor Guide</a></h1>
-<div class="level1">
-
-<p>
- The issue is how to manage a library of <em><strong>gschem</strong></em> transistor symbols and a library of PCB transistor elements such that we can be confident of correct pin number correspondence between the libraries. We need to understand how to handle the many permutations of emitter, base, and collector (e,b,c) pinouts and the variations of package number of pins and pin numbering. This doc shows the approach Iâ??ve taken in my custom <em><strong>gschem</strong></em> symbols and PCB elements.
-</p>
-
-</div>
-<!-- SECTION "gschem Symbol and PCB Element Transistor Guide" [1-531] -->
-<h2><a name="gschem_symbols" id="gschem_symbols">gschem symbols</a></h2>
-<div class="level2">
-
-<p>
- There are a couple of ways to consider:
-</p>
-<ol>
-<li class="level1"><div class="li"> Have a base set of <em><strong>gschem</strong></em> transistor symbols such as npn.sym, pnp.sym, fet.sym, etc. which have a fixed and arbitrarily assigned pin number for the emitter, base, and, collector. To accommodate the different permutations of (e,b,c) to pin numbers that exist for transistor packages, you would have to have a set of PCB elements for each transistor package like <a href="http://en.wikipedia.org/wiki/TO92"; class="urlextern" title="http://en.wikipedia.org/wiki/TO92"; rel="nofollow">TO-92</a>-123, TO-92-132, TO-92-213, TO-92-231, TO-92-312, TO-92-321, and similarly for <a href="http://en.wikipedia.org/wiki/TO220"; class="urlextern" title="http://en.wikipedia.org/wiki/TO220"; rel="nofollow">TO-220</a>, TO-5, etc. The problem with this is that manufacturers do specify pin numbers for their packages and we would be making many elements with pin numbers not corresponding to real packages. Remember, a PCB element on a PCB layout is supposed to correspond to a physical electronic component.</div>
-</li>
-<li class="level1"><div class="li"> Have a base set of <em><strong>gschem</strong></em> transistor symbols which spans the possible (e,b,c) permutations which can exist for any given transistor package. The set of <em><strong>gschem</strong></em> symbols for npn transistors would be npn-ebc.sym, npn-ecb.sym, npn-bec.sym, npn-bce.sym, npn-ceb.sym, and npn-cbe.sym. There would be similar sets for pnp transistors and FETs (fet-sdg.sym, fet-sgd.sym, …). Then there would be PCB elements only for actual physical transistor packages.</div>
-</li>
-</ol>
-
-<p>
- It makes sense to me to say the second approach is obviously better. Setting up the <em><strong>gschem</strong></em> symbols is simple enough, just create the six symbols for each transistor type with the pin numbers of the emitter, base, and collector corresponding to the sequence indicated in the name. For example, the symbol npn-ebc.sym would have an emitter <strong>pinnumber</strong> attribute of <strong>1</strong>, a base <strong>pinnumber</strong> attribute of <strong>2</strong> and a collector <strong>pinnumber</strong> attribute of <strong>3</strong>. Now you only need to make PCB elements with correctly numbered pins for transistor packages as you need them and you need to have a systematic approach for naming these elements.
-</p>
-
-</div>
-<!-- SECTION "gschem symbols" [532-2550] -->
-<h2><a name="pcb_elements" id="pcb_elements">PCB Elements</a></h2>
-<div class="level2">
-
-<p>
- A point to keep in mind when looking at transistor package pin configurations and numbers is that a TO (Transistor Outline) designation is really only just that - a designation of a particular shaped and sized outline. It actually is not a specification of the pins coming out of that package. Manufacturers may have have a TO package designation qualified by their internal â??case styleâ?? or â??package numberâ?? code. This qualification determines the definition of the number of pins, the arrangement of the pins, and the pin numbering.
-</p>
-
-<p>
-However, most TO packages do conform to a standard pin numbering convention and have a predominant number of pins and pin placement configuration. So it makes sense to have PCB elements with a particular TO name which can be used for a majority of cases. Then when a non conforming case is encountered, we can make a new TO element for it.
-</p>
-
-<p>
-Hereâ??s a description of what seems to be the most common transistor outline configurations:
-</p>
-<ul>
-<li class="level1"><div class="li"> <em>Power Transistors - Plastic</em>: Look at the package front (where the lettering is) with the pins pointing down. The pins are numbered left to right (1,2,3). This is very common, so it makes sense to create initial sets of three pin PCB elements with this number order using base names such as TO-126, TO-220, TO-264, etc. For variations such as a five pin TO-220 package for a LM383, you could make a PCB element with its name qualified such as TO-220-5, or maybe TO-220-T05B if you wanted to qualify it with the National Semiconductor T05B package designation for their 5 pin TO-220 package.</div>
-</li>
-<li class="level1"><div class="li"> <em>Power Transistors - Metal</em>: This would be the TO-3 package which can have from 2 to many pins. There is no index tab on the package so you need to look at a diagram of the pin out to see the pin numbering. The common 2 pin package could be named TO-3, and N pin packages with N > 2 could be named TO-3-N.</div>
-</li>
-<li class="level1"><div class="li"> <em>Small Signal Transistors - Metal</em>: Look at the transistor bottom with the pins pointing at you. The pins are numbered clockwise from the index tab (1,2,3,…) Metal can packages such as TO-18, TO-39, or TO-72 will frequently have 3 or 4 pins, while the TO-5 may have 3, 4, 5, 6, 8, or 10 pins. Because of the variable pin numbers, you could, for example, name the PCB elements TO-18-3 and TO-18-4, or you could use TO-18 and TO-18-4 assuming that a three pin can is more common and thus earns the base TO-18 element name.</div>
-</li>
-<li class="level1"><div class="li"> <em>Small Signal Transistors - Plastic</em>: Look at the transistor package flat side (where the lettering is) with the pins pointing down. Almost all packages where the three pins are in a straight line will have the left to right pin number ordering of (1,2,3) and these can be the base TO-92 PCB element. There are a very small number of cases where the pins will be in a straight line and numbered left to right (3,2,1). You could have a distinct PCB element for these, but you could also decide to ignore the manufacturerâ??s pin numbering and pretend itâ??s the more common (1,2,3). However, if the package has the middle pin offset so the pins are in a triangular arrangement, the pin number ordering will frequently be (3,2,1) and this will possibly require a custom PCB element. But see my comments about my <span class="curid"><a href="http://geda.seul.org/wiki/playground:transistor_guide#special_cases"; class="wikilink1" title="playground:transistor_guide">TO-92o</a></span> element below.</div>
-</li>
-<li class="level1"><div class="li"> <em>Surface Mount Transistors</em>: The SOT (Small Outline Transistor) packages are much more standard than the TO packages and the pins are consistently numbered counterclockwise from the top left as are IC packages. But for a transistor that has a TO and a SOT version, you canâ??t simply change the <strong>footprint</strong> attribute on the schematic because the package pin numbers donâ??t map the same to the emitter, base, and collector. You need a separate <em><strong>gschem</strong></em> symbol for them. For example: <strong>2N3904.sym</strong> for the TO and <strong>MMBT3904.sym</strong> for the SOT.</div>
-</li>
-</ul>
-
-</div>
-<!-- SECTION "PCB Elements" [2551-6419] -->
-<h2><a name="general_procedure" id="general_procedure">General Procedure</a></h2>
-<div class="level2">
-
-<p>
- The process of using a transistor for the first time in a <em><strong>gschem</strong></em> to PCB design takes these steps (2N3904 used as an example):
-</p>
-<ol>
-<li class="level1"><div class="li"> Most transistor <acronym title="specification">spec</acronym> sheets can be found in pdf format on the web, so get one and determine the case style and pin name and number ordering. For the 2N3904 the case style is TO-92, the pin number order left to right is (1,2,3), and the pin name order left to right is (e,b,c).</div>
-</li>
-<li class="level1"><div class="li"> If we have a PCB element in our library for that case style with the correct pin number order, use it. If not, make a new PCB element. For the 2N3904, I have a TO-92 element in my custom library that has the pin number order of (1,2,3), so I can use it.</div>
-</li>
-<li class="level1"><div class="li"> Copy the <em><strong>gschem</strong></em> transistor symbol corresponding to the pin name order to a new transistor symbol name. For the 2N3904 example, the pin name order is (e,b,c) so copy the base symbol npn-ebc.sym into 2N3904.sym.</div>
-</li>
-<li class="level1"><div class="li"> Edit the new symbol and change the <strong>value</strong> attribute to the transistor name and the <strong>footprint</strong> attribute to the right PCB element. For our example, this would be <strong>2N3904</strong> and <strong>TO-92</strong>.</div>
-</li>
-</ol>
-
-</div>
-<!-- SECTION "General Procedure" [6420-7545] -->
-<h3><a name="special_cases" id="special_cases">Special Cases</a></h3>
-<div class="level3">
-<ol>
-<li class="level1"><div class="li"> I have in my library a TO-92o PCB element which has the middle pin offset so the pins are in a triangular arrangement. This element has the left to right pin number order of (1,2,3) and can be used in place of the TO-92 for layout considerations. You only have to slightly bend the middle pin of the transistor when installing it.</div>
-</li>
-<li class="level1"><div class="li"> The BC546 transistor <acronym title="specification">spec</acronym> sheet shows its pin number order to be (1,2,3) in a straight line and the pin name order to be (c,b,e). But Iâ??ve seen this transistor shipped from the factory with the middle pin prebent into the offset configuration. For this transistor, you would create the <em><strong>gschem</strong></em> symbol from npn-cbe.sym as expected but use the PCB element TO-92o.</div>
-</li>
-<li class="level1"><div class="li"> The BF240 transistor <acronym title="specification">spec</acronym> sheet shows its pin number order to be left to right (3,2,1) in a straight line and the pin name order would be left to right (c,e,b). If you made a new PCB element with pins numbered (3,2,1), then you would have to create the <em><strong>gschem</strong></em> BF240.sym from npn-bec.sym because pin 1 on the PCB element has to correspond to pin 1 on the <em><strong>gschem</strong></em> symbol. But it would be easier to just ignore this uncommon pin numbering and assume the transistor pins are actually numbered the standard left to right (1,2,3). Then you could use the existing TO-92 PCB element and create the <em><strong>gschem</strong></em> symbol using npn-ceb.sym. Some transistor <acronym title="specification">spec</acronym> sheets give the pin name order and do not give a pin number order, and for these you just make the same assumption that the pins are numbered left to right (1,2,3).</div>
-</li>
-<li class="level1"><div class="li"> In the second case above, the transistor had an offset pin 2 when the <acronym title="specification">spec</acronym> sheet showed the pins in a straight line, and the pin numbers on the <acronym title="specification">spec</acronym> sheet were ordered left to right (1,2,3). But many transistors have the offset pin 2 indicated on the the <acronym title="specification">spec</acronym> sheet and the pin numbers are ordered left to right (3,2,1). You could use an element such as my TO-92o by ignoring the <acronym title="specification">spec</acronym> sheet ordering as I suggested in case 3. But this configuration is much more common than the BF240 example so you might want to have a distinct PCB element for it with pins numbered to match the <acronym title="specification">spec</acronym> sheet.</div>
-</li>
-</ol>
-<hr />
-
-<p>
-tutorial by Bill Wilson (bill–at–gkrellm.net)
-</p>
-
-</div>
-<!-- SECTION "Special Cases" [7546-] --></div>
-</body>
-</html>
commit e7388fcf022cbb88f48bd5c400765c62c49ef700
Author: Ales Hvezda <ahvezda@xxxxxxxx>
Date: Sat Aug 18 15:36:44 2007 -0400
Updated wiki snapshot from the live wiki
diff --git a/docs/wiki/_media/tragesym_template2 b/docs/wiki/_media/tragesym_template2
new file mode 100644
index 0000000..f414b79
Binary files /dev/null and b/docs/wiki/_media/tragesym_template2 differ
diff --git a/docs/wiki/_media/tragesym_template2.txt.txt b/docs/wiki/_media/tragesym_template2.txt.txt
new file mode 100644
index 0000000..4e507c3
--- /dev/null
+++ b/docs/wiki/_media/tragesym_template2.txt.txt
@@ -0,0 +1,59 @@
+# This is the template file for creating symbols with tragesym
+# every line starting with '#' is a comment line.
+
+[options]
+# wordswap swaps labels if the pin is on the right side an looks like this:
+# "PB1 (CLK)". That's useful for micro controller port labels
+# rotate_labels rotates the pintext of top and bottom pins
+# this is useful for large symbols like FPGAs with more than 100 pins
+# sort_labels will sort the pins by it's labels
+# useful for address ports, busses, ...
+wordswap=yes
+rotate_labels=no
+sort_labels=yes
+generate_pinseq=yes
+sym_width=1400
+pinwidthvertical=400
+pinwidthhorizontal=400
+
+[geda_attr]
+# name will be printed in the top of the symbol
+# name is only some graphical text, not an attribute
+# version specifies a gschem version.
+# if you have a device with slots, you'll have to use slot= and slotdef=
+# use comment= if there are special information you want to add
+version=20060113 1
+name=
+device=
+refdes=U?
+footprint=
+description=
+documentation=
+author=
+dist-license=
+use-license=
+numslots=0
+#slot=1
+#slotdef=1:
+#slotdef=2:
+#slotdef=3:
+#slotdef=4:
+#comment=
+#comment=
+#comment=
+
+[pins]
+# tabseparated list of pin descriptions
+# ----------------------------------------
+# pinnr is the physical number of the pin
+# seq is the pinseq= attribute, leave it blank if it doesn't matter
+# type can be (in, out, io, oc, oe, pas, tp, tri, clk, pwr)
+# style can be (line,dot,clk,dotclk,none). none if only want to add a net
+# posit. can be (l,r,t,b) or empty for nets
+# net specifies the name of the net. Vcc or GND for example.
+# label represents the pinlabel.
+# negation lines can be added with "\_" example: \_enable\_
+# if you want to write a "\" use "\\" as escape sequence
+#-----------------------------------------------------
+#pinnr seq type style posit. net label
+#-----------------------------------------------------
_______________________________________________
geda-cvs mailing list
geda-cvs@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-cvs